Developers: What Not To Do
Filed in archive Management by jason on April 20, 2006

If we didn't make these decisions, and some people tend to draw the process out for an agonizingly long time, your project starts to fall behind schedule. I don't think the Project Managers and Functional Managers realize it but a lot of time on a project is lost because people simply have a hard time deciding what tool or technique to use in order to address a problem. That might be hard to understand but following me here. The Opportunity Cost that exists with all the different languages, IDEs, databases, Operating Systems, Application Servers, design patterns, etc... tends to be a bit overwhelming for some people: "What if I choose the wrong one"! Answer: You would be ridiculed for years to come by future generations of programmers who are enlisted
to maintain your application. Its a scary thing for some people to be put in that position. My technique for deciding what to do is make the best decision possible with what I know at the time. Then tell myself that this is just a proof of concept and we'll "refactor" things later to optimize the application. This tends to work well with managers and other non-technical folks in meetings. Honestly, I have no idea if I will have time later to refactor later, but if history tells me anything I won't. I do the best I can and move on.
On a lighter note, and possibly a detractor to my previous paragraph here, I've started reading The Daily WTF. It is funny as hell sometimes and can be very technical. Hopefully, I won't see a post someday and say: "Hey wait a minute... I've done something like that before."
Permalink: Developers: What Not To Do
Tags:
Programming Management
Trackback: http://www.creative-weblogging.com/cgi-bin/mt-tb.pl/20451












