In another great post Jeff wrote yesterday: Good programmers get off their butts. One particular thought resonated very much with my own observations: As software developers-- and especially if we have pretensions of being so-called "architects"-- we should always make decisions based on experience and data.

 

I have noticed a trend among more experienced developers of calling themselves “software architects” [I have been guilty of this myself as well]. There is a great quote that defines software architects (came from Don Box, not sure who said it) Software Architects - over 40, over confident ;). Now, I am not over 40 yet (haven't even made mid-thirties) but I admit being most likely over confident :) Still, considering yourself an architect is justified if you get off your butt and write code as Jeff nicely puts. Too many people assume being an architect relieves you from having to write code. Considering how much design process is mixed with actual development, that cannot be true.

 

Few more notes on design/coding... I find writing code helps with “designer's block”. Every now and then you get stuck with your design, just like a writer cannot continue writing until he/she is inspired again. I like to bridge these gaps by writing some code. There is always some low level (trivial from design point, thus boring) building block that needs to be implemented, or something needs to be refactored. If nothing else, there are unit tests pending (admit it, you are delaying writing these as long as you can ;)). Usually, while writing this code it dawns on me what I should do with the design.

Permalink | Comments (0) | Post RSS