Handle them differently than technical exceptions.
Sometimes it’s better to have something else handle those cases.
In this industry, if you quit learning new things, you’re done.
Avoid massive releases.
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.”
Performance problems are often caused by poorly formed SQL statements.
These may give you more options for the methods you use.
Your method definitions should not be overly long.
Avoid this temptation.
This is an amazing book that reflects many of the problems software development organizations face on a daily basis.