In this episode, we’re talking about lessons learned and the lessons we still need to learn. Also, Michael shares some anti-monetization strategies, Allen wins by default, and Joe keeps it real 59/60 days a year! The full show notes for this episode are available at https://www.codingblocks.net/episode212. News Exceptions vs Errors in Java Question from Twitter: (thanks […]
We’re back after a brief break for a busy month of May, and we’re here to talk about some pretty cool stuff happening in the developer world. Outlaw took vacation and can remember nothing, Joe introduces us to Sherlocking, and Allen discovered what all the fuss was about with Chat GPT as a software developer. […]
In this sequence of sound, we compute Joe’s unexpected pleasure in commercial-viewing algorithms, Michael’s intricate process of slicing up the pizza, and Allen’s persistent request for more cheese data augmentation. Will you engage in this data streaming session? The full show notes for this episode are available at https://www.codingblocks.net/episode210. Resources we like Tip of the week
In this episode we talk about several things that have been on our mind. We find that Joe has been taken over by AI’s, Michael now understands our love of Kotlin, and Allen wants to know how to escape supporting code you wrote forever. News Visited with Jamie Taylor from the .NET Core Podcast, Tabs […]
We’re doing a water cooler talk today. Also, Allen can tell you how not to leak secrets, Michael knows how to work a spreadsheet, and Joe has been replaced by an AGI. The full show notes for this episode are available at https://www.codingblocks.net/episode208. Topics Resources we like
We’ve got a new / old opening…Allen goes off / on script? Michael denies Joe the “swing” vote, and Joe is all in on AI assistance Testing for concurrency issues is hard because it’s non-deterministic – basically you get unlucky due to the timing of things Serializability Common Implementations Actual Serial Execution Encapsulating transactions in […]
What are lost updates, and what can we do about them? Maybe we don’t do anything and accept the write skew? Also, Allen has sharp ears, Outlaw’s gort blah spotterfiles, and Joe is just thinking about breakfast. The full show notes for this episode are available at https://www.codingblocks.net/episode206. News Preventing Lost Updates Detecting Lost Updates […]
There’s this thing called ChatGPT you may have heard of. Is it the end for all software developers? Have we reached the epitome of mankind? Also, should you write your own or find a FOSS solution? That and much more as Allen gets redemption, Joe has a beautiful monologue, and Outlaw debates a monitor that […]
Ever wonder how database backups work if new data is coming in while the backup is running? Hang with us while we talk about that, while Allen doesn’t stand a chance, Outlaw is in love, and Joe forgets his radio voice. The full show notes for this episode are available at https://www.codingblocks.net/episode204. News Thanks for […]
It's time we learn about multi-object transactions as we continue our journey into Designing Data-Intensive Applications, while Allen didn't specifically have that thought, Joe took a marketing class, and Michael promised he wouldn't cry.
We decided to knock the dust off our copies of Designing Data-Intensive Applications to learn about transactions while Michael is full of solutions, Allen isn't deterred by Cheater McCheaterton, and Joe realizes wurds iz hard.
Michael spends the holidays changing his passwords, Joe forgot to cancel his subscriptions, and Allen's busy playing Call of Duty: Modern Healthcare as we discuss the our 2023 resolutions.
We step back and look at how things have changed since we first started the show while Outlaw is dancing on tables, Allen really knows his movie monsters, and Joe’s math is on point. The full show notes for this episode are available at https://www.codingblocks.net/episode200. News Thanks for the review nickname222Apple<3! Want to help us […]
We talk about career management and interview tips, pushing data contracts “left”, and our favorite dev books while Outlaw is [redacted], Joe’s trying to figure out how to hire junior devs, and Allen’s trying to screw some nails in. The full show notes for this episode are available at https://www.codingblocks.net/episode199. News Thanks for the reviews […]
We take a peak into some of the challenges Twitter has faced while solving data problems at large scale, while Michael challenges the audience, Joe speaks from experience, and Allen blindsides them both.
It's that time of year where we've got money burning a hole in our pockets. That's right, it's time for the annual shopping spree. Meanwhile, Fiona Allen is being gross, Joe throws shade at Burger King, and Michael has a new character encoding method.
We gather around the watercooler to discuss the latest gossip and shenanigans have been called while Coach Allen is not wrong, Michael gets called out, and Joe gets it right the first time.
We wrap up Git from the Bottom Up by John Wiegley while Joe has a convenient excuse, Allen gets thrown under the bus, and Michael somehow made it worse.
This episode, we learn more about Git's Index and compare it to other version control systems while Joe is throwing shade, Michael learns a new command, and Allen makes it gross.
It's time to understand the full power of Git's rebase capabilities while Allen takes a call from Doc Brown, Michael is breaking stuff all day long, and Joe must be punished.
We are committed to continuing our deep dive into Git from the Bottom Up by John Wiegley, while Allen puts too much thought into onions, Michael still doesn't understand proper nouns, and Joe is out hat shopping.
It's surprising how little we know about Git as we continue to dive into Git from the Bottom Up, while Michael confuses himself, Joe has low standards, and Allen tells a joke.
After working with Git for over a decade, we decide to take a deep dive into how it works, while Michael, Allen, and Joe apparently still don't understand Git.
Once again, Stack Overflow takes the pulse of the developer community where we have all collectively decided to switch to Clojure, while Michael is changing things up, Joe is a future predicting trailblazer, and Allen is "up in the books"
We're going back in time, or is it forward?, as we continue learning about Google's automation evolution, while Allen doesn't like certain beers, Joe is a Zacker™, and Michael poorly assumes that UPSes work best when plugged in.
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.
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.
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.
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.
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.
