Please enable JavaScript.
Coggle requires JavaScript to display documents.
Clean Architecture Chapter 1-2 - Coggle Diagram
Clean Architecture
Chapter 1-2
capitolo 1-2
sustainability
a change should be only proportional to the scope of the change, not to the shape of the change
refactoring
enables
scope
what the feature does
shape
structure
all the implementation details
what is more important?
having a sw system that works?
having a sw system that is easy to change?
is it the "right thing" to build?
is quality worths the cost?
https://martinfowler.com/articles/is-quality-worth-cost.html
Kent Beck's 3X
Eisenhower's matrix
urgent vs important
behavior is urgent
architecture is important
prioritize!
unimportant features vs important architecture
tell the important features vs the unimportant ones
dev team should assert the important of architecture over the urgency of features
OCP
business is calculating area
adding a new shape is easy
what about calculating the perimeter?
there's no difference between
design
and
architecture
but have two different view levels
really?
scalability
security
...
slow and steady
the more haste, the less speed
there's no time to reflect, we have to rush!
repeating the same errors
iterative development
is slow
Simplicity--the art of maximizing the amount
of work not done--is essential.
https://agilemanifesto.org/principles.html
overconfidence
will drive the redesign into the same mess as the original project
"Accelerate" book
deployment lead time
deployment frequency
mean time to recover
maximize mean time between failure
this slow down a lot
architecture should be as shape-agnostic as practical!
how much could you live with a shape-agnostic architecture?
introduction
getting sw right is hard!
"right"!?
build the
right thing
build the thing
right
no need to have a LARGE team
no need to do overtime
how much time live a feature?
disposable software
Conway's law
the architecture of your sw and the architecture of your org are tight!
Sandi Metz
a codebase should be
inspiring
with less or no "broken windows"
code should communicate its conventions
as a "new kid in town", start from understanding the codebase first
POODR book