Classic Mistakes Enumerated Some ineffective development practices have been chosen so often, by so many people, with such predictable, bad results that they deserve to be called "classic mistakes." Most of the mistakes have a seductive appeal. Do you need to rescue a project that's behind schedule?
A Trace in the Sand January 2014 Happy New Year! I hope you have an awesome 2014, filled with dreams and realizations, joy and becoming. What's a Trace? My Trace is a playground for developing ideas, for exploring architecture and the role of architects. I don't know where these ideas are going to come from, so I explore, finding the dots to connect and sharing them, and the connections I make, playfully and thoughtfully, here.
Free 'Writing Quality Code' e-book (with information on both Native and Managed Code Analysis) - Code Analysis Team Blog Some of the local Australian developers have got together and written a e-book on Writing Quality Code with Visual Studio Team System. It contains chapters on both Native and Managed Code Analysis, as well unit and web testing, performance-tuning and custom check-in policies. You can download the e-book from here (you will need to install the reader first). These guys are the best in the business in both Australia and around the world, so make sure you check it out.
Smart Client Software Factory patterns & practices Developer Center Shop for patterns & practices books online April 2008 Summary
MSDN Library patterns & practices Retired Desktop Development Smart Client Software Factories Smart Client - Composite UI Application Block
Welcome to Sparx Systems Enterprise Architect, a UML 2.4 based modeling tool for designing and constructing software systems, for business process modeling, and for generalized modeling purposes such as visualizing existing systems and processes. Introduction to Enterprise Architect, UML Modeling Tool [EA User Guide]
mgmtArchitecturePaper-hpdc.pdf (application/pdf Object)
How to Design Exception Hierarchies - Krzysztof Cwalina I still get a lot of questions on how to design exception hierarchies, despite several attempts to describe it in talks, the FDG book, and in posts on this blog. Maybe the guidance gets lots in the in the complexities of the full guidance surrounding exception handling or I am a bad communicator. Let me assume the former :-), and so here is one more attempt at describing the guidance in the most succinct way I am capable of: · For each error condition you reusable routine can get into, decide whether the condition is a usage error or a system error.
Enterprise Architecture, Software Architecture, Architects, and Architecting
E2AF A0 New Poster 03-2005 version 1.4.pdf (application/pdf Object)