Good advice. I've seen most of these, but had not seen the tip on "Use Is/Has/Should/Can Prefixes" with booleans. I'm experienced enough now to do that automatically, but it is good to see it spelled out regardless. It is certainly of benefit to learners.
Good advice. I've seen most of these, but had not seen the tip on "Use Is/Has/Should/Can Prefixes" with booleans. I'm experienced enough now to do that automatically, but it is good to see it spelled out regardless. It is certainly of benefit to learners.
Great article: simple to understand and apply the recommendations next
A simple but yet very effective tip. Great article, friend!
Thanks my friend!
Returning early is one of my favorite tricks to reduce complexity!
Good compilation, Daniel.
Thanks my firend!
I'll echo what Vinny has already said - great job!
Great content! :) and I’m checking the TDD course at the moment 😜
Great Article!
thank you bro for this article, clear and concise
thank you
thank you for this great article, clear and concise.
Some great tips my friend!
Re Reduce Nesting with Early Return
Reducing if-then-else nesting is a good thing. The refactored code checks each parameter, in its own bit of code.
Structured Programming has single entry and single exit to code section, so one return statement at end.
If you want to place some debugging code/breakpoint before the return, there is only one place.
The other naming tips are useful to avoid the dreaded double negative