Software development quotes
“If the layered style is the most common targeted style [in software architecture], the big ball of mud style is perhaps the one most often actually achieved. It is characterized by the absence of any evident structure, or perhaps vestiges of now-eroded structure. Also typical is promiscuous sharing of information, …
I am currently reading the book “Practices for Scaling Lean & Agile Development” by Craig Larman and Bas Vodde. This book is full of very interesting material that covers the full spectrum of the software development domain and is the “sequel” of “Scaling Lean & Agile Development – Thinking and …
Some interesting thoughts borrowed from my notes of the “How to Become an Agile Architect” talk presented yesterday by Uwe Friedrichsen from Codecentric at the Jazoon 2011 conference in Zurich. * Architecture is a set of skills and not a role: if you don’t have these skills available for your …
Dan Leffingwell proposes eight principles for the development and maintenance of enterprise-class architectures in the lean and agile enterprise: 1. The team that code the system also design the system 2. Build the simplest architecture that can possibly work 3. When in doubt, code it or model it out 4. …
I am currently reading the excellent book “Managing Software Debt – Building for Inevitable Change” written by Chris Sterling. The book deals with the debt that created at every stage of software development. In its introduction, the book offers an interesting list of the software quality attributes. Even if the …
“One way to simply and intuitively define project management is that it is a set of tools, templates, and processes designed to answer the following six questions: 1. What business situation is being addressed by this project? 2. What do you need to do? 3. What will you do? 4. …
