Handle them differently than technical exceptions.
Monthly Archives: April 2020
Avoid excessive switches and flags.
Sometimes it’s better to have something else handle those cases.
Always be learning.
In this industry, if you quit learning new things, you’re done.
Make small incremental changes.
Avoid massive releases.
Everything should have a code review.
Don’t let it be a rubber stamp. Code reviews correct mistakes. A second (or third) set of eyes looking over your code may catch some areas of concern that you missed. This helps prevent bad code from being promoted forward, saving you rework later. They also provide a nice way to share knowledge. The peopleContinue reading “Everything should have a code review.”
Blame the SQL.
Performance problems are often caused by poorly formed SQL statements.
Examine method signatures in your libraries.
These may give you more options for the methods you use.
Require a small number of parameters.
Your method definitions should not be overly long.
Don’t start over from scratch.
Avoid this temptation.
The Phoenix Project had great ideas.
This is an amazing book that reflects many of the problems software development organizations face on a daily basis.
