The pizza shop is expanding it's offerings! CALZONES! We'll do a 1/2 calzone and a full calzone! $8 and $14 respectively. Based on how we did the Medium pizza last time... Not expecting much work for these. Which... THAT'S THE POINT! µObjects make…
Pizza's going great! We've got our system in place; we've cleaned up our code! We have µObjects everywhere! In my ideal; there aren't enough tests. All behavior is still covered; test coverage is at 100% for everything except our Money object. Which…
We return to our pizza shop to refactor. I like to check out my "TODO" or "Smelly" comments and see what I can clean up. I normally go for "TODO" as most tools have a way to list them for easy access. Visual Studio…
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…
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…
µObjects: By Example - Playing Cards I've been a bit remiss on good code examples for µObjects. I've been planning a few things; never got them done. Almost entirely because I'm lazy. So... I'm going to try a simple example of 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…
Inheritance is a code smell. Composition over Inheritance This is a known suggestion to improve the maintainability of software. How does this play into microObjects? Everything has a single responsibility. It's doing A thing; as I talk about in µObjects: Principles to code by [https://quinngil.com/2017/…