In the Beginning... ...there was no inheritance and no composition, only code. And the code was unwieldy, repetitive, blocky, unhappy, verbose, and tired. Copy and Paste were the primary mechanisms of code reuse. Procedures and functions were rare, newfangled gadgets viewed with suspicion. Calling a procedure was expensive! Separating pieces of code from the main logic caused confusion! It was a Dark Time.| Thoughtworks
When developers speak about the Single Responsibility Principle, nobody seems to agree. What means the SRP? Should we still use it?| The Valuable Dev
Is simplicity important? How to achieve it? How to manage complexity? Here's a detailed article about the KISS principle.| The Valuable Dev
What are the benefits and drawbacks of the DRY principle?| The Valuable Dev