What are the main principles a software architect should know? Some colleagues of mine are compiling a list, “97 Things Every Software Architect Should Know” which will eventually be a book. So far they’ve got 49 axioms such as Don’t put your resume ahead of the requirements, One line of working code is worth 500 of specification, and Architectural Tradeoffs. Check it out. Technorati Tags: software architecture, software architect | | Digg it | Slashdot it | Post to del.icio.us |
97 Things Every Software Architect Should Know
Related with "97 Things Every Software Architect Should Know"
97 Things Every Software Architect Should Know (Kindle Edition)
In this unique technical book, today’s leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects — including Neal Ford, Michael Nygard, and Bill de h ra — offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many[...]
10 Stupid Things ERP Software Salespeople Say
Vinnie Mirchandani has witnessed his fair share of vendor negotiations first-hand—as a consultant to companies in the RFP and vendor-evaluation processes with his firm Deal Architect, as a global ou read more 10 Stupid Things ERP Software Salespeople Say[...]
Software Web Developer
Software Web Developer · Great development role within a dynamic and successful company. · Excellent career/life balance · Work with a talented and intelligent team of professionals Role: The Software Web Developer will be developing Java based solutions. All Development work is done[...]
Afterthoughts of Software Architect
I have come to the end of the 3 day conference and what are my thoughts: Firstly I believe to get the most out of the sessions you need to have the right mindset, if you regard being a developer as from 9 till 5 then switching[...]
For the Business Analysts and System Architect
For the Business Analysts and System Architect Posted by moeen on January 11, 2008 The maintained costs of the software increases as we rise to enterprise level. The ideas conceived at the Requirement Specification could cause any type of software team to turn up side down, only[...]
