#Simple-Design
4 notas · última:
Simple Design
Kent Beck’s Simple Design rules prioritize working code first, then clarity, then avoiding duplication, and only after that reducing the number of classes, methods, and modules.
You Don't Hate Mocks; You Hate Side-Effects
The article argues that excessive mock expectations are a signal of side-effects in the design. Refactoring away from those side-effects often removes the mock and leads to simpler, more focused tests.
Yagni
Yagni says not to build a capability now if you will not need it yet. Fowler frames it as a simple-design practice, weighing build cost, delay, carry, and repair costs against future uncertainty.
Understanding the Four Rules of Simple Design
The book draws lessons from coderetreat workshops and Conway’s Game of Life to explain Kent Beck’s four rules of simple design and how they support flexible, adaptable software.
