The larger the scope, the harder it is to fully understand.
Monthly Archives: May 2020
Kanban in three easy steps.
There’s not a lot to Kanban, which is one reason it is desirable.
Keep the build clean.
Don’t accept failed tests.
Don’t create God classes.
These monsters try to do too much.
Avoid paralysis by analysis.
It can halt your progress.
Beware bikeshedding.
Some decisions don’t get the consideration they deserve.
Avoid premature optimization.
There’s a time and a place for this and it’s not at the beginning.
Observe single test cases in your IDE.
It’s a powerful tool, extremely useful in examining code coverage.
Do not introduce extra logic for tests.
All logic should serve a business purpose.
An object should not have more than one trigger.
The trigger should have one job.
