Fresh beats for endless flow state (News)

0:05What up nerds? I'm Jared and this is Changelog news for the week of Monday April 21st, 2025. A recently published study called The Effect of Deactivating Facebook and Instagram on Users' Emotional State proved what we all knew to be true, but previously didn't have a study to point to. Social media, at least in the form we've been using it for the past decade plus, is a total drag. Oh well, let's get into this week's news. Fresh beats for endless flow state. Our fourth full-length changelog beats album dropped today. It's called After Party, and it features beloved Breakmaster Cylinder tracks from our outros, ad rolls, and transitions.

0:55It's essentially 26 chill beats to help you get into a state of flow and stay there. Here's a sample of a few of my favorites, such as track 5, Severanced Package.

1:20Track 11, do not stare directly into the changelog.

1:35Track 25, sunken barge zone, Adam's sudden death version.

1:57And track 26, Last Light.

2:16If that one's familiar to you, yup, it's our longtime outro to Changelog interviews, which many, many people have asked us to make available to stream or buy. Well, now you can. Head to changelog.com slash beats for all the links to all the music platforms or simply search for Changelog Beats in your favorite music app and we'll see you at the after party. The 12-Factor Agent Dex Horthy, who has been hacking on AI agents for a while, set out to answer the question, what are the principles we can use to build LLM-powered software that is actually good enough to put in the hands of production customers?

2:58What he came up with is 12 factors in the spirit of the 12-Factor app. Here they are. 1. Natural language to tool calls. 2. Own your prompts. 3. Own your context window. 4. Tools are just structured outputs. 5. Unify execution state and business state. 6. Launch, pause, resume with simple APIs. 7. Contact humans with tool calls. 8. Own your control flow. 9. Compact errors into context window. 10. Small, focused agents. 11. Trigger from anywhere, meet users where they are. And 12, make your agent a stateless reducer. If those 12 bullet points are more confusing than enlightening, that's because, hey, they're just bullet points.

3:45Click through for the full explainers. How to build an agent. Speaking of agents, you might now be thinking it's super hard to build one. Thorsten Ball says, you're wrong. Quote, it's not that hard to build a fully functioning code editing agent. It seems like it would be when you look at an agent editing files, running commands, wriggling itself out of errors, retrying different strategies. It seems like there has to be a secret behind it. There isn't. It's an LLM, a loop, and enough tokens. End quote. Turns out you can build a small and yet highly impressive agent in less than 400 lines of code.

4:23Thorsten proves this out by building an anthropic-based agent in Go over the course of this blog post. I followed along and I have to say, it's all very basic stuff. Thorsten's closer, quote, these models are incredibly powerful now. 300 lines of code and three tools. And now you're able to talk to an alien intelligence that edits your code. If you think, well, but we didn't really go and try it, go and see how far you can get with this. I bet it's a lot farther than you think. And that's why we think everything's changing. It's now time for sponsored news. Teams with faster builds ship faster.

5:03Depot's CEO, Kyle Galbraith, recently shared his thoughts on the age-old question, build or buy for CICD. The fact is teams with faster builds ship faster and more. And teams that know how to CI well create faster builds. Imagine what would happen if your builds got 10x faster. Kyle found that when companies talk about building their own CI, what they actually mean is self-hosting runners from another CI provider. After analyzing hundreds of engineering teams, he identified three distinct archetypes. First, there's the abstraction first team. These folks know what matters and move fast. They discover Depot and immediately think, it's 10 times faster, half the price of GitHub Actions, and I just changed one line of code?

5:46No brainer. Then there's the infracurious team. They're in that honeymoon phase with self-hosting. GitHub Actions is slow, so they spin up their own runners in AWS. But now they own the uptime engineering, literally, and they now have to learn how to make the builds faster and keep them secure. These folks eventually become the third and last archetype, which I'll let Kyle cover in his post. It's linked up in your chapter data and the companion newsletter. Thank you to Depot for sponsoring Changelog News. Check them out at depot.dev. PocketFlow is a 100-line LLM framework. The author of PocketFlow, Zachary Huang, thinks current LLM frameworks like LangChain, CrewAI, LangGraph, etc.

6:30are all bloated. After reading Thorsten Ball's essay on how to build an agent, I can believe it. The 100 lines in PocketFlow capture the, quote, core abstraction of LLM frameworks, and you build on top of that to do multi-agent, workflows, rag, etc. One great example of Pocketflow in action is this repo that's linked up in your newsletter, which crawls GitHub repositories and builds a knowledge base from the code. It analyzes entire codebases to identify core abstractions and how they interact, and transforms complex code into beginner-friendly tutorials with clear visualizations. What a great way to learn a new codebase.

7:07Getting forked by Microsoft. As a sole maintainer of an open source project, Philip Lane was excited when Microsoft showed interest in Spiegel, his tool, to enhance Kubernetes cluster scalability through peer-to-peer image distribution. But then things got weird. At KubeCon Paris, Lane attended a talk about strategies to speed up image distribution that mentioned a Microsoft project called PeerD. Quote, while looking into PeerD, my enthusiasm for understanding different approaches in this problem space quickly diminished. I saw function signatures and comments that looked very similar as if I had written them myself.

7:46Digging deeper, I found test cases referencing Spiegel and my previous employer, test cases that had been taken directly from my project, references that are still present to this day. The project is a forked version of Spiegel maintained by Microsoft, but under Microsoft's MIT license, end quote. Spiegel is also MIT licensed, which does allow for forking and modification without contributing back, but does not allow, quote, removing the original license and purporting that the code was created by someone else, end quote. Not cool, Microsoft. What's an open source maintainer to do in this circumstance?

8:20Phillips says, As an effort to fund the work on Spiegel, I have enabled GitHub sponsors. This experience has also made me consider changing the license of Spiegel as it seems to be the only stone I can throw. That is the news for now, but also scan the companion changelog newsletter for even more links worth clicking on, such as Xmeralda is an AI chatbot just for Elixir. Pipelining might be my favorite language feature And an awesome collection of GPT-4-0 images and prompts Get in on the newsletter at changelog.com slash news Do it, do it We have some great episodes coming up this week On Wednesday, Kendall Miller from CTO Lunches joins me And on Friday, Matt Reier takes Adam and I to Matt World Have a great week, like, subscribe, and leave us a 5-star review if you dig the show And I'll talk to you again real soon

9:15Game on.