Coding Blocks

We're not saying that Michael is Carmen Sandiego. We're just saying that nobody has ever s

Stitcher is back and so are we as Michael proves he doesn't have a career as a rapper, Allen ca

We continue our Domain Driven Design conversation this week as Allen is indecisive, Michael decides

We’re back with another exciting episode as Michael questions Hollywood, Allen dreams of his Hackint

This week, Michael asks his customers about their anemic domain model, Allen talks in front of peopl

This week we talk about all of the bad things we’ve done while making software. The good, the bad, …

We’re back with another deep dive into the infamous book Clean Code by Uncle Bob as Joe alters colum

This week Allen is troubled by circles, Michael talks like a game show host, and Joe announces it&#0

When and why should you write unit tests, and just how important are they? Take a listen and see wha

In this episode we talk about how to insulate your application at it’s boundaries?  What in the worl

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

Ever judged a book by its cover?  Of course you have.  Ever passed judgement on some code simply bec

This week, Michael fails geography, Allen introduces us to Croom, and Joe has to potty as we head in

We continue talking our way through Clean Code, taking a deep look at the building blocks of program

In this episode, we take our first dive into the book Clean Code by Robert Martin and specifically w

Storing smaller subsets of data in a faster, closer memory can make astronomical differences in perf

In this episode we give a general overview of caching, where it’s used, why it’s used, and what the

This week on Coding Blocks, Allen says www as best he can, Joe eats the microphone, and Michael does

This time we’re talking about problems with nulls, stored procedures, and impostor syndrome. Link to