Hi, I'm Jamie Tanna 👋🏼

Craig Kerstiens returns to talk about the ever-expanding world of Postgres: a deliberately boring core, a thriving extension ecosystem, and pg_lake bringing DuckDB and Iceberg into the mix. We dig into the pain of ETL, what Craig is watching in Postgres 19, the impact of AI on open source maintainers, and why the datab...

Good Hang with Amy Poehler · Episode

Sylvain Kalache, who runs the AI lab at Rootly, walks Matty through what AI SREs can and can't do during an incident. They get into why handing every small…

Can you trust software written without AI? We examine the risks of manual coding versus automated vulnerability exploits.At Rails World 2026, a show of hands revealed that writing material amounts of code by hand is becoming a rarity. We discuss whether that human-written code is actually safer, especially after reviewing the eMudhra certificate authority compromise where private keys were recovered in under a second. Between open-weight models demonstrating Mythos-class exploit skills and the ongoing debate over AI consciousness, the security landscape has shifted significantly.This conversation is for engineers navigating the reality of AI mandates at work and the impact of agents that continue running after you log off. We also cover the practical side of professional development, from Bethany building a holiday gift-list app to Brittany replacing cloud subscriptions with local transcription tools. By analyzing these technical shifts, we aim to help you maintain a grounded perspective on your career trajectory.Subscribe for weekly software engineering breakdowns, and comment on which professional challenge you want us to tackle next.HostsOvercommitted: https://overcommitted.devBethany Janos: https://www.trustyduck.devBrittany Ellich: https://brittanyellich.com

Episode 13 of AI Frontiers with Sean Escriva. Industry experts run down all the AI news for engineers. Adam Jacob, Paul Stack, and Nick Stinemates are…

Recorded as part of GoSF. Thanks Bill for co-hosting, and Antithesis for hosting! 🇯🇵 GopherCon Japan 🪝 Guest Posts: Hooking into the Go Toolchain 🦙 go-llama

Positive comments from The Real Reviewers Lance Ulanoff at TechRadar: 'Satisfying' is the best way to describe the feeling of repeatedly opening and…

Do the 2026 Go Developer Survey, and tell them Cup o' Go sent you! Go 1.27.3 and Go 1.26.10 are released due to eMudhra Intermediate CA Compromise Interview with Ainsley ClarkAinsleyClark.com templ

Quinn and Thorsten sit down together in San Francisco to answer the question they get asked most: how does the Amp team work? They walk through a week at Amp, from Thorsten's Sunday post and the single Monday meeting to writing down goals in silence. They explain why Amp has no quarterly goals, no departments and no territory, and how feature flags and the work in progress, orb good and orb bad channels keep a team of 21 in sync. They also cover reviewing changes with agents, pushing to main without mandatory code review, and why they think more companies will soon work like this.