A good name describes its returned value.
Author Archives: fooyay
Sometimes a class isn’t worth it.
Not everything deserves to be a class.
Have a plan before you code.
Know where you are going and what you are going to do.
Learn how to give good presentations.
This is an essential element of improving your communication skills.
Measure twice, cut once.
It pays to be extra careful.
Business exceptions are different.
Handle them differently than technical exceptions.
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.