Hi all,When we talk about skills in software development we tend to think about the hard skills first. Java, JEE, Maven, UML, PHP, HTML, Object Oriented Design and so on. We think about them first because we think they are important. And, yes, to some extend they are. But there is more to it.Once you start working with all these hard skills and apply them in your projects you learn the concepts behind them. And once you see the concepts you will see the concepts behind the concepts which are the general principles/guidelines in software development every developer and software architect should know and work with.Richard Monson-Haefel has done an excellent job in writing down some of the most important concepts, principles and guidelines together with the community. It is something I have been looking for a long time. A great effort from him. Check it out on http://97-things.near-time.net/wiki.One of the best ones I like from the site is this one http://97-things.near-time.net/wiki/show/challenge-assumptions-especially-your-own. I make this mistake still to often.Enjoy it and hopefully learn from it(and challenge it if you will :-),Bart.
Saturday, August 23, 2008
Other voices: 97 Things
My colleague, Bart Kooijman, wrote an internal e-mail with the subject "97 Things Every Software Architect Should Know":