We’re not saying that Michael is Carmen Sandiego. We’re just saying that nobody has ever seen them in a room together. And this week, we don’t know where in the world either are, as Allen and Joe continue the Domain Driven Design discussion without Michael. Nor Carmen.
Stitcher is back and so are we as Michael proves he doesn’t have a career as a rapper, Allen can’t type on his phone, and Joe tweets with famous authors as we continue our dive into Domain Driven Design talking about aggregate roots, factories, and repositories.
We continue our Domain Driven Design conversation this week as Allen is indecisive, Michael decides for him, and Joe can’t handle the night life.
This week, Michael asks his customers about their anemic domain model, Allen talks in front of people, and Joe plays Rocket League as we begin our dive into understanding domain driven design.
This week we talk about all of the bad things we’ve done while making software. The good, the bad, … oh wait, it compiles, never mind.
We’re back with another deep dive into the infamous book Clean Code by Uncle Bob as Joe alters columns, Michael misreads things, and Allen has a positive customer service experience.
This week Allen is troubled by circles, Michael talks like a game show host, and Joe announces it’s twins as we continue our deep dive into the classic Clean Code book by Robert C. Martin. [Read more…]
When and why should you write unit tests, and just how important are they? Take a listen and see what YOU think.
In this episode we talk about how to insulate your application at it’s boundaries? What in the world does that even mean?! We’re not talking about those boundaries where others aren’t allowed to touch your keyboard (although that’s a real thing). No, we’re talking about making sure you make your code easier to maintain over time by coding to interfaces or wrappers for third party libraries or external APIs. Come join us on another deep dive into Clean Code, and our (polluted) thoughts on the topic. [Read more…]