Each week our hosts will discuss their development experiences. We'll talk about Ruby, Rust, Go, and anything else that has drawn our interest this week. Subscribe below to be notified when new episodes are published!
14: TIL database connections aren't cheap
A background job should be a function. So, putting more things in it is always a good idea! Sean announced that he shipped background jobs for crates.io. It's been in production for more than two weeks, and no issues have been reported. It's made life much easier because he no longer needs to spend time manually cleaning or cloning the index before changing a config bar. Now, he's working on librafying "Swirl." Also, Sam expressed frustration with his decision to use heredocs and block local variables in his Ruby autoformatter (Rubyfmt) - big mistake that caused big problems.
13: "As much time as I can without reading C" with James Coglan
Do you use Git practically every day, but have no idea how to implement it? Need a more accessible and easier way than reading original source code to understand how it works? Want to know how to rebuild Git in a high-level language to learn the concepts involved? Sam talks to James Coglan, who wrote the book, Building Git. It teaches readers how to rebuild Git in Ruby and helps them develop debugging skills. Also, James shares his thoughts on Sam’s Ruby autoformatter (Rubyfmt), which takes a radically different approach to RuboCop. Rubyfmt won’t offer any configuration options that allow users to effect its style opinions.
12: A new cat named Merb!
Sean and Sam talk about debugging a memory leak with Crates.io when upgrading to Rust 1.32 that could only be reproduced in production.
The Parse.y Hole
Derek Prior, engineering manager at GitHub, joins Sam to talk about what they’ve been working on these days. Derek’s doing GitHub projects that can’t talk about. But, he did mention that GitHub recently shipped small-scope changes to its issue templates. Sam dives deep into details about building a Ruby auto formatter and not wanting to be the sole dictator of style for the rest of Ruby for all time. Feedback from others through a request for comments (RFC) process is valuable for adoption and implementation. For the goodness of the community, get them to tell you all their style opinions! Then, everyone can look forward to using Sam’s auto formatter.
10: Deleting all of a user's comments is probably a bug
Ruby's language development is off the charts. Also: we talk about programming. Sam and Sean discuss Ruby, auto-formatting, and whether Hash Rockets are good. They bring other languages, such as Go, Rust, and Elixir, into their formatting discussion. Also, Sam shares some work-related news. He’s leaving his job at DigitalOcean. Before he goes, he wants to get as much done as possible to give his team the best opportunity to succeed. That’s the mark of a truly great manager. But, at the same time, he’s looking forward to his next gig!
9: Tools That are Well Built Will do it for us!
We’re still time travelling, Sam has since left DigitalOcean, but in this episode, he talks about his experiences there.
Sean talks about his experiences managing the crates.io team, and incidents on an open source project with volunteer time. Sam talks about his experiences scaling go programs, and processes vs threads, as well as why kubernetes makes the trade offs between goroutines and processes pretty unimportant.
Customer ReviewsSee All
These guys both have deep knowledge across many software engineering domains. If you enjoy digging into gnarly computering topics, this is the show for you!
Even with only one episode, I can already tell I'm going to have to sit down to listen to this each time so I make sure I don't miss anything.
Love the hosts, love the content, this is gonna be a good one.