Developers build systems to solve problems. Business problems. In the planning of an application, we are, unfortunately, not immune to the forces of economics. When we consider a budget and a timeline, our primary concern is feasibility. That is, can we set expectations such that we will deliver what we and the client have agreed on?
Requirements discovery is hard, and it’s unrealistic to expect all requirements to be clear at the outset of a project. New information will be unearthed and new stakeholders will contribute their viewpoint down the line. In fact, it’s likely that the project you’ve scoped originally will change materially by the time you deliver it.
Software dominates the world. But how well does the world know the people who develop it? Let’s look at what some recent developer surveys say.
Would anyone have guessed that more developers are dog people than cat people (except in Germany)? Or that developers prefer Star Wars to Star Trek (unless they’re over 50)? (more…)
A delivery truck driver named John has a new application. He arrives at his destination, parks the truck, picks up his mobile device and steps out. As he unlocks his device’s screen, the app instantaneously refreshes with the package information for the customer at that location. He didn’t even need to touch the app… he smiles…
His device picks up the beacon at the door and orders the back doors to open. A green light goes on at the exact section where the package is…he smiles again. (more…)
First, the bad news: IT complexity will not go away.
The good news?
There’s a rule to help you decide what part of it you should tame yourself, and what part you should let go. We’ll get to that soon. (more…)