While browsing through my daily dose of RSS feeds on Google reader, I came across this interesting website, which talks of "97 Things every software architect should Know". Here are my top three picks (not in any specific order) out of the list of 97 'things' :-
1. Simplicity before generality, use before reuse :- Couldn't have agreed more. Having been a developer myself, I have seen developers often resorting to speculative design, under the guise of re-usability
2. Seek value in requested capabilities :- With apt examples the author, describes, how the role of a technical architect should be to help sponsor understand what they need. Ties back well to the agile manifesto
3. Pattern Pathology :- At times we assume design patterns to be the solution to all complex business problems. We enforce certain design patterns in project without checking if there are any simpler/ better solution available. The Author describes this symptom as 'Pattern Pathology' and makes a Strong case against it
Recommended reading for all..would like to know what are your picks..