I don't remember exactly where or who, but writing re-usable code was impressed upon me as an important thing I now completely disagree with that. > Do not write reusable code. One of the worst things you can do when writing code is to make it "re-usable&…
I've covered never having nulls [https://quinngil.com/2017/10/15/uobjects-no-nulls/] and that's what the NullObject [http://wiki.c2.com/?NullObject] pattern is here to help us with. The NullObject pattern is one that I tried to implement earlier in my career (mostly after reading…
TL;DR: I loved the book. Go read it. [https://pragprog.com/book/rjnsd/the] -------------------------------------------------------------------------------- Over the past few years working with a team of XP devs who've been using the XP practices for well over a decade each has taught me a lot. These amazing colleagues…
Cohesion for objects is how well the behaviors in the class belong together. Some very non-cohesive behaviors would be multiplying two numbers and splitting a string. Multiplying and Raising to a power can be very cohesive behaviors. How do µObjects do cohesion? That's what this is about. The…
Read It It's a fantasic book; and you should read it. Beyond Legacy Code [http://beyondlegacycode.com] This is one of the books that will help developers understand the best practices that lead to quality code. I started reading this book a year after I started applying the…
There's a couple types of places where the code we write interacts with the code someone else wrote. This could be another team, a 3rd party library, or the operating system. When we interact with these components, we're tying our code to their code in some…