Changelog Master Feed Changelog Media
-
- Teknologi
-
Your one-stop shop for all Changelog podcasts. Weekly shows about software development, developer culture, open source, building startups, artificial intelligence, shipping code to production, and the people involved. Yes, we focus on the people. Everything else is an implementation detail.
-
Why your framework doesn't matter (Changelog News #93)
Bahaa Zidan says your web framework doesn’t matter, DHH writes about magic machines, Dylan Huang reviews thousands of opinions on HTMX, Tim Ottinger says programming is thinking & Tim Spann says small language models (SLM) for the win.
-
Managing Meta's millions of machines (Ship It! #102)
Anita Zhang is here to tell us how Meta manages millions of bare metal Linux hosts and containers. We also discuss the Twine white paper and how AI is changing their requirements.
-
The Wu-Tang way (Changelog & Friends #42)
Our friend Ron Evans is a technologist for hire, an open source developer, an author, a speaker, an iconoclast, and one of our favorite people in tech. This conversation with Ron goes everywhere: from high-altitude weather balloons, to life on Mars, to Zeno’s paradox applied to ML, to what open source devs should learn from the Wu-Tang Clan & more.
-
SSR web components for all (JS Party #321)
Brian LeRoux joins Jerod to share how the Enhance team are bringing server side rendered web components to everyone. With Enhance WASM, you author components in friendly, standards based syntax and reuse them across multiple languages, frameworks & servers.
-
Castro leans into indie (Changelog Interviews #589)
This week we’re joined by Dustin Bluck to discuss his acquisition of the well known (and beloved) Castro podcast app to take it indie-focused once again. As previous users of Castro, we were excited to dig into the details behind this popular podcast client to see what’s next, how the deal was done, a peek into the code, and where exactly this indie and creator focused podcast app can go.
-
Go workshops that work (Go Time #314)
What makes a good, bad, and truly great workshop? How do you put together a Go workshop that works, and how do you get the most out of workshops you attend?