Uncle Bob SOLID principles

Yup the common take on interfaces is that they are contracts, and if you inherit it then you need to implement all of its methods. The original reason interfaces were introduced in C with objects was to reduce coupling, yes. Think of a dependency tree with high level modules at the top, and low level ones down at the bottom. Without interfaces, if I change code in a tiny module at the bottom then everything has to recompile all the way up to the top instead of just that single module. That makes the entire tree more fragile, and our compile time is a lot longer So in short, its to reduce coupling. I really first started appreciating interfaces when I learned about SOLID coding, and a good…

…can conceive of' without covering any of the middle ground. The principles - SOLID, DRY, YAGNI and KISS - are a real grey area. The critical one to get to grips with is SOLID. The SOLID principles are most commonly associated with Robert C. Martin, colloquially known as Uncle Bob. There's a video explaining the concepts, explained by him, here: [video The truth is that so much of this is subject to interpretation by so many people. Ultimately, you'll need to **learn by doing.** Try it - take a stab at something. Build a simple calculator, then build it again when you've learn more principles, then build it again and fix what yhou didn't like, then get your code reviewed and then build…