What is it like to ship software in big tech? Sean gives us his experience from multiple companies and what he’s learned. It's probably not what you think. It doesn't matter if you're vibe coding features or bash-ing devops, we all need to remember why we were hired.

Links:

• https://www.seangoedecke.com/how-to-ship/

https://fafo.fm/store

This Episode has a full spread of FAFOFM topics. Ellie has a breadth of knowledge across cloud, on-prem, hardware, and—of course—Kubernetes. We dive into some of the new hardware available as well as the importance of hardware to train the next generation of engineers. A full cycle of interests we think you'll love. 🧡

Links

• https://ellie.fm
• https://bsky.app/profile/ellie.fm
• https://devzero.io
• https://www.cloudlab.us/
• https://github.com/clastix/kamaji

https://www.softwaredefinedtalk.com/

Today's history lesson is about the non-markup language platform engineers love to hate, YAML Ain't Markup Language (YAML). Ingy tells us all about how and why it started, how it evolved over time, and what's happening next with YS.

Note: sorry about the audio issues in this episode. We did our best to clean it up.

Links:

• https://helmys.org/
• https://yamlscript.org/
• https://exercism.org/
• https://yamlscript.org/ingydotnet/

It's easy to talk about everything when you've been writing software for half a century. Bhaskar has some amazing insights from his impressive career building software using everything from punch cards to AI. If you like learning about the past to understand the future, this is an episode you don't want to miss.

Links

• YottaDB https://yottadb.com

Angie gives us a crash course on Model Context Protocol (MCP) and how you can get started using it with goose. We also talk about other projects Angie's worked on at Block and what drives her to keep learning new things in tech.

Links

• Angie's website: https://angiejones.tech
• Goose https://github.com/block/goose
• Angie's Modern Day Mashups talk https://www.youtube.com/watch?v=jZbXq5qu55U

After 25 years in tech it’s hard not to coast. Adriana has come from writing word docs for the ops team to deploy software, through Devops, and now has a focus on OTel and Kubernetes. How do we get more people from 100 to 400 levels and why is there no content in between? And why we need junior engineers to make our senior engineers better.

Links

• Bluefin wallpapers https://github.com/ublue-os/packages/tree/main/packages/bluefin/wallpapers
• Justin’s talk with balloons and a spreadsheet https://www.youtube.com/watch?v=A0mWGaBawR8
• Adriana on Bluesky https://bsky.app/profile/adrianamvillela.bsky.social

Disaster recovery is more than automation and infrastructure. There's a lot that goes into your services and some of those things can't be defined as code or automated. When was the last time you restored your database from a backup? How do you use least privileged access when your region changes and how do you even know you're having a disaster. Seth has a lot of experience and a ton of good insights in this episode.

Links

• Seth’s Linktree https://linktr.ee/setheliot
• arpio https://arpio.io/services/
• EKS Auto example repo https://community.aws/content/2sV2SNSoVeq23OvlyHN2eS6lJfa/amazon-eks-auto-mode-enabled-build-your-super-powered-cluster
• Disaster recovery white paper https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/disaster-recovery-workloads-on-aws.html
• Disaster recovery blog series https://aws.amazon.com/blogs/architecture/tag/disaster-recovery-series/
• Ship it! with Pete Naylor https://changelog.com/shipit/127
• Engineering Resilient Systems on AWS by Jennifer Moran https://www.amazon.com/Engineering-Resilient-Systems-AWS-Resilience/dp/1098162420
• Four Things Everyone Should Know About Resilience https://community.aws/content/2duX45O6vKOE7cmmXQ9Nj3tO3bL/should-know-resilience

Railway wanted to build a better cloud so they started on Google Cloud and ended up building datacenters. Through the burden of success, they figured out there was a lot of things they had to learn and build themselves if they wanted to offer the best cloud experience they could. Jake tells us how they accomplished the move in 9 months, why the built their own orchestrator, and what they’re working on next.

Check out Railway at https://railway.com/ and their blog at https://blog.railway.com. Specifically read the post discussed in this episode. https://blog.railway.com/p/data-center-build-part-one