Web developers have standard processes and techniques to get their jobs done. They also have informal habits and opinions that influence their work — the kinds of things that no one is formally trained on but picks up from peers over time.
In this article, I’ll share a few common beliefs from developers that I’ve experienced since 2004, while working with dozens of developer teams. To be sure, not every developer shares these views.
Confessions of an Ecommerce Developer
Perfect features are impossible. You requested a feature from a developer, he finished it, and it’s nothing like what you wanted. This occurs all too often.
Building software that does exactly what someone wants is extremely difficult. It’s rare that it is right on the first try. Even when I’m working on my own software, many times a feature doesn’t end up exactly as I planned.
There are, typically, two root causes to this: failure in communication and not enough resources.
Communication failures occur when a client doesn’t share enough information with a developer, or maybe a developer didn’t ask a critical question, or maybe even the data that prompted the project was flawed.
The other cause is scarce resources. I often think to myself that if I had infinite time, money, and people, I could create software to do anything.
In the real world of business that’s not the case. There’s a limited amount of time, money, people, and computing resources. Given those constraints, sometimes the feature just can’t be done as requested.
Thus, developers adopt the view that perfect features are impossible. But there…