Documenting Architecture Decisions

Michael Nygard – November 15, 2011
“Architecture for agile projects has to be described and defined differently. Not all decisions will be made at once, nor will all of them be done when the project begins.
Agile methods are not opposed to documentation, only to valueless documentation. Documents that assist the team itself can have value, but only if they are kept up to date. Large documents are never kept up to date. Small, modular documents have at least a chance at being updated.”
Read the complete article at:

Towards Progressive Delivery

James Governor | @monkchips | August 6, 2018
” I have been waiting for a term to emerge to describe a new basket of skills and technologies concerned with modern software development, testing and deployment. I am thinking of Canarying, Feature Flags, A/B testing at scale. Advances in approaches to application and service Observability. On the technology side, Kubernetes and Istio bring new management challenges, but also opportunities – service mesh approaches can enable a lot more sophistication in routing of new application functions to particular user communities.”
Read the complete article at:

Is High Quality Software Worth the Cost?

Martin Fowler
“A common debate in software development projects is between spending time on improving the quality of the software versus concentrating on releasing more valuable features. Usually the pressure to deliver functionality dominates the discussion, leading many developers to complain that they don’t have time to work on architecture and code quality.”
Read the complete article at:

The Clean Architecture

Robert C. Martin
“Over the last several years we’ve seen a whole range of ideas regarding the architecture of systems.”
Read the complete article at