Great summary of a lot of the common sets of rules. One I'd add next to DRY is AHA--avoid hasty abstractions. Usually it's good to have the problem repeated at least twice before turning it into an abstraction. On the third time, it usually makes sense to abstract.
Great summary of a lot of the common sets of rules. One I'd add next to DRY is AHA--avoid hasty abstractions. Usually it's good to have the problem repeated at least twice before turning it into an abstraction. On the third time, it usually makes sense to abstract.
Nice list of Software acronyms! And the visuals help to understand them better!
I can see the actionable strategy, after reading Anton's post and your comment. I hope it works! :)
I'm glad you found them useful, Rafa!
Yes, let's see if this post goes viral 😉
Let's go! 🚀
Also, know when to break the rules. Best practices are guides, not laws. Great read!
Thanks Daniil! I agree, we are the ones to choose when and where to apply them
Wow, there are so many acronyms indeed!
Thanks for the mention as well, Fran.