Wednesday, March 28, 2007

Why simple is good

I've noticed that in most cases entry level application developers (people who just start their careers as developers) have long forgotten how to be basic users. They know that and many times they try to solve application issues with powerful back end features and presumptions of knowledge. This can work, not necessarily well but it can work in the enterprise world or with small user bases, where training and lots of personal communication occur more frequently. Now I'm guilty of this too and have found that in most cases that is due to an inability to effectively write complete applications or simply put its being over engineered.

Apparently when most developers start their careers they want to "save the world" its like a digital version of a hero complex, we want more for our users than the dreary basic features in short we get feature happy. The thoughts of "wouldn't it be great" tend to take our attention from improving core functionality which is usually very boring so it tends to have the least amount of time spent on it. Instead we build sledge hammers to hammer thumb tacks, this is a classic rookie move and usually doesn't happen right away. Mostly because entry level programmers aren't given their own projects right away. When they do they want to show that they can bring more to the table, this is something that I'm told never goes away you just have to handle it. I'm not sure what that means but I'm sure I'll find out sooner or later. So here is the warning to all your rookies out there, don't make the mistakes of the many... if you do try and make them small.

No comments: