We newbies and the application design and architecture

After being around for some time in this world of IT I have started to realize why these experienced guys are so furious with the newbies. I use to read a lot of newbie bashing on web and use to think WTF. Now, I must say "Old is Gold".


There are three types of newbies I have come across. One who really do not want to design and just wants to get the job done in a procedural way. Second who know a thing or two about design and want to design there application the best possible way (constraint being there knowledge). Third who thinks they know everything about design and that is how things should be designed.


The real problem arises when they are working on an application from scratch. The first type may come up with a class or two and finish the code in a monolithic manner. The third type will create a design either too good or to brittle. These two types will surely get the work done even though extensibility and maintainability may not be there and thus the cost of every change will be just too high. 


I have found the second type getting stuck more often then not. They are always circumspect about there design and some times they just think too much about it. They google for some hints and solutions (more often then not they find something). The problem is knowing whether the solution is right for there case or not. 


I am not against any one type and neither I favor one. I put them down just so that one can realize where they fall. I have been lucky to get chance to work on an application or module design from scratch and some time on existing applications as well. Initially I found really difficult to move even an inch as I was two confuse about my design. I have been the second type and I have been the third. 


Here are few of my learning's:

1. Never be the first type. You never know you might be the one working on the change tomorrow. 
2. Design evolves. There is know best design. You can always better it gradually. 
3. Follow the basic principles. Separation of concerns, Coupling, Cohesiveness are the few principles which I think if followed will always allow you to refactor your code latter.
4. Work in layers when needed. 
5. You might be the best around (for the Third type) but may be you can learn from others mistake or can make them understand their mistake. Keep looking for the better solution or for the mistake you should not do yourself. 
6. You might be technically very strong but you need to understand the needs of your customer then only you can design something good for the customer. You are not designing for yourself. You are designing for the customer. There is cost associated with whatever you do (do not spend too much at design) and obviously there will be cost associated with any change (do spend time on design).
7. There are simple techniques which when followed always allows you to improve latter. e.g. interface based programming, DI etc. Do the small things right and the rest will follow.
8. Do not hesitate in doing pair programming. You will always learn.

Most importantly do not just remain stuck. Start with something and realize the shortcomings and fix them. I am still learning and believe that we learn from our mistakes. I still believe I have spent too much time analyzing and trying to get the things right the first time (Being stuck). That said, please do invest lot of time at architectural design as module design can change comparatively easily and with less cost.