Don’t try to optimize your application by guessing which part is slow.
Monthly Archives: July 2020
Beware Hofstadter’s Law.
It always takes longer than you expect, even when you take into account Hofstadter’s law.
Don’t write flaky tests.
Stop chasing your tail with unreliable tests.
Write code to be read.
Software code and tests are read much more than they are written.
Avoid 3D effects.
Don’t use clever 3D effects in pie charts and bar charts.
Don’t get clever.
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.”
Welcome revisions.
Don’t be offended when your code gets refactored.
Agile Principles #12: Review and improve.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Agile Principles #11: Don’t micromanage.
The best architectures, requirements, and designs emerge from self-organizing teams.
Agile Principles #10: Keep it simple, stupid.
Simplicity — the art of maximizing the amount of work not done — is essential.
Today's Card 