Joe is down with OCP, Michael argues DRY, and Allen deletes our show notes as we dig into Components and Component Cohesion from Robert C. Martin’s (aka Uncle Bob) Clean Architecture.
Michael forgets what his favorite part of the show is, Joe makes us wait to learn what his favorite part is, and Allen pronounces it “pair-a-dig-’ems” as we continue our deep dive into Uncle Bob’s latest book: Clean Architecture.
Joe learns of our harebrained idea, Michael learns of Eisenhower’s matrix, and Allen explains polyfills as we begin our dive into Uncle Bob’s latest book, Clean Architecture.
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…]
This week, we continue our Clean Code discussion as we dive into the joys and pains of error handing.
This week we’re drawing a line in the sand between objects and data structures. Who will win? Take a listen and decide for yourself!
For the full show notes visit:
This week, Michael fails geography, Allen introduces us to Croom, and Joe has to potty as we head into our third installment of the Clean Code series.