Both promise a set of actions before any details are filled in. Both stop you from creating an object directly from them. So why do object-oriented languages bother offering both? This thirteen-chapter guide unpacks what each one really is, five side-by-side differences, a small Vehicles-and-Rechargeable code example, whether a class…
Four ideas hold up almost every large piece of software you have ever used — encapsulation, abstraction, inheritance, and polymorphism. They sound technical, but underneath, they are just clever ways of organising things. This twelve-chapter guide walks through what OOP itself really is, the difference between classes and objects, each…
Why write the same thing twice when one class can simply borrow it from another? Inheritance lets related pieces of code share what they have in common — while each one still keeps what makes it special. This thirteen-chapter guide walks through what inheritance really is, the “is-a” relationship, how…
One class, one job, one reason to change. It sounds almost too simple to matter — until you see what happens to a codebase when nobody bothers to follow it. This thirteen-chapter guide takes a deep dive into the “S” in SOLID: the formal definition from Robert C. Martin, what…
Five short letters — S, O, L, I, D — five simple habits, and decades of hard-won wisdom about writing code that does not fall apart the moment it needs to grow. This thirteen-chapter guide walks through what each letter really means in plain language: Single Responsibility, Open/Closed, Liskov Substitution,…
One instruction, delivered to different objects, produces different but each perfectly appropriate results. That is the entire secret behind polymorphism — one of programming’s most useful ideas. This thirteen-chapter guide unpacks what the word literally means (Greek for “many forms”), what polymorphism really is in code, why it matters, the…
A software architect draws the map. But a map drawn by someone who never walks the streets tends to be wrong in ways nobody notices until it is too late. This thirteen-chapter guide unpacks what “staying hands-on” really means, what happens when architects stop coding entirely (the ivory-tower drift), the…
Encapsulation bundles data and the actions that work on it into one protected unit, then hides the messy inner details from everyone else. This twelve-chapter guide walks through what it really is, why every serious project relies on it, the four ingredients of a capsule, how it differs from abstraction…
Long before software existed, people were designing complex things that had to stand up, work well, and feel right to humans — buildings. The rules they discovered along the way are the same ones a good software architect leans on today. This twelve-chapter guide walks through balance, emphasis, proportion, rhythm,…
Architecture is the plan; infrastructure is what the plan gets built on. This friendly, twelve-chapter guide walks through both — what each one really means, how they stack together, the building blocks of infrastructure, on-prem vs cloud vs hybrid, Infrastructure-as-Code vs Architecture-as-Code, who owns what, and why mixing the two…