Don’t write complex software just because the technique looks cool. From time to time new techniques will appear on the web, and then everyone will start over-using them for anything and everything. A couple years ago it was the repository pattern. This pattern has its uses, but when working with a framework that already hasContinue reading “Don’t get clever.”
Tag Archives: simplicity
Agile Principles #10: Keep it simple, stupid.
Simplicity — the art of maximizing the amount of work not done — is essential.
Look out for comments at the end of a block.
They may seem helpful, but they’re also a bad sign.
Code shouldn’t need an explanation.
Sometimes comments are a red flag.
Don’t use conjunctions in method names.
Two great ideas taste great together, but not in a method.
Write shorter routines.
Studies have shown that longer and more complex routines are subject to error and more expensive to maintain.
Don’t over-engineer.
This is a widespread problem that seems to most teams at some time.
Don’t create God classes.
These monsters try to do too much.
Deleted code has fewer bugs.
This is a simple one.
Don’t run with scissors.
Accidents happen when you’re not careful.
Today's Card 