Pragmatic talk about software design best practices: design patterns, software architecture, coding for performance, object oriented programming, database design and implementation, tips, tricks and a whole lot more.
Site Reliability Engineering - Evolution of Automation
We explore the evolution of automation as we continue studying Google's Site Reliability Engineering, while Michael, ah, forget it, Joe almost said it correctly, and Allen fell for it.
Site Reliability Engineering – (Still) Monitoring Distributed Systems
We finished. A chapter, that is, of the Site Reliability Engineering book as Allen asks to make it weird, Joe has his own pronunciation, and Michael follows through on his promise.
Site Reliability Engineering - Monitoring Distributed Systems
We haven't finished the Site Reliability Engineering book yet as we learn how to monitor our system while the deals at Costco as so good, Allen thinks they're fake, Joe hasn't attended a math class in a while, and Michael never had AOL.
Site Reliability Engineering - Eliminating Toil
We say "toil" a lot this episode while Joe saw a movie, Michael says something controversial, and Allen's tip is to figure it out yourself, all while learning how to eliminate toil.
Site Reliability Engineering - Service Level Indicators, Objectives, and Agreements
Welcome to the morning edition of Coding Blocks as we dive into what service level indicators, objectives, and agreements are while Michael clearly needs more sleep, Allen doesn't know how web pages work anymore, and Joe isn't allowed to beg.
Site Reliability Engineering - Embracing Risk
We learn how to embrace risk as we continue our learning about Site Reliability Engineering while Johnny Underwood talked too much, Joe shares a (scary) journey through his mind, and Michael, Reader of Names, ends the show on a dark note.
I’m binging on your podcast recently
I’ve been an on and off listener since your “I is for Interface” episode. I was but an entry level developer when I started listening and wasn’t particularly keen on the literature just yet, so I didn’t understand half of what you guys were saying. But now that I’ve been in the software industry for 5 years, I find myself going back to your past episodes and finally understanding and appreciating the bit of knowledge you guys impart within each episode. Keep up the good work, I’ve learned and still am learning a lot from you guys, while at the same time reinforcing good software practices from your episodes. Thanks again!
Such a wealth of knowledge! 🧠
This is one of the most insightful podcasts that I have ever come across! Allen, Michael, and Joe do such a great job of sharing their industry wisdom and I learn something new every time I tune in. Highly recommend checking this show out - you won’t be disappointed!
Really Great Concept For A Podcast
I’ve been looking for a podcast that reads classic/relevant programming books and then gives their hot takes or brings up examples from their career.
This is the closest I could find. I’ve only listened to a few episodes and I would say it’s about 60% material discussion and 40% talking shop. For me, this is the perfect ratio. I work remote so I don’t get time to just talk with my coworkers most of the time. Having this on in the background makes me feel like standing around the water station again. If you really want to get something with 100% analysis and no fun, just read the book or find a free course somewhere. My one wish is that they’d put time stamps for material discussion in their show notes. I find myself skipping around an episode when I can’t find the relevant discussion point.