Triple D

Programs must be written for people to read, and only incidentally for machines to execute.

Architecture represents the significant decisions, where significance is measured by cost of change.

How it is done is as important as getting it done

A document shouldn’t try to do what the code already does well.

If you think good architecture is expensive, try bad architecture.

The quickest methods aren't always the fastest methods

The quickest methods aren't always the fastest methods

The only way to go fast, is to go well

The only thing dumber than big design up front, is no design up front

If you can't deploy services independently, you don't have micro-services. You have a distributed monolith.

If you can't see and understand a solution. You can't evaluate it

A good architecture rarely happens through architecture-indifferent design

It is easy to say that a piece of code is bad. It is easy to complain or even laugh. But the question is: are you good enough to make it better?