The Changelog: Software Development, Open Source - This new AI role is exploding (News)

Episode Date: November 10, 2025

A new AI-led tech role has emerged with a massive increase of job postings, Corey Quinn explains why younger devs won't tolerate pain in the AWS, Thomas Ptacek makes the case that you should write an ...agent, Paul Kinlan goes deeper on his dead framework theory, and Andrew Gallagher says to stop vibe coding your unit tests.

Transcript
Discussion (0)
Starting point is 00:00:00 What's up, nerds? I'm Jared, and this is ChangeLog News for the week of Monday, November 10th, 2025. So, Spencer Chang made a thing, a thing that made my day. It's called the Alive Internet Theory, and it makes the case that the Internet will always be filled with real people, looking for each other, answering calls for help, and sharing laughs even in the midst of arguing. This is a website that's better felt than telt, so I'll just leave you to follow the link in the newsletter.
Starting point is 00:00:39 Okay, let's get in to this week's very alive news. This new AI role is exploding. AI-related job losses and future non-hires are the talk of the software town right now, but at least in the short-slash-near term, a new AI-led tech role has emerged with a massive increase of job postings, up 800% over the last nine months. Quote, forerunners in the AI race, such as Anthropic and OpenAI,
Starting point is 00:01:08 are actively recruiting software engineering specialists called Forward Deployed Engineers FTEs to help with tailoring AI models to meet customer needs. More than just working with back office coders, these engineers are embedded within customer and product engineering teams. end quote. Still not sure what a forward-deployed engineer or an FDE does exactly. Quote, unlike traditional software engineers, FDEs go beyond writing code to go out in the field and understand where AI can make the biggest impact. Their mission is to bridge the last mile of AI, transforming a general purpose model into scalable
Starting point is 00:01:48 AI solutions that reflect complex client requirements and solve their problems. end quote. If this trend has any staying power, and if you want to be in demand in 2026, now is the time to ensure you can confidently and truthfully put FDE on your resume. Younger devs won't tolerate pain in the AWS. Corey Quinn, who is hilarious, by the way, finally realized what I've known since the first time I tried shipping a Rails app on EC2. AWS, for the uninitiated, it's pure pain.
Starting point is 00:02:22 Quote, recently I was spitting up. yet another terribly coated thing for fun, because I believe in making my problems, everyone else's problems, and realized something that had been nagging at me for a while, working with AWS is relatively painful. End quote. Corey lays out what a typical zero-to-one AWS setup often requires, then compares it to the silky, smooth experience Versailles provides on top of AWS. His explanation for the discrepancy, it's generational. Quote, this feels generational to me. For folks of a certain age, Gen X and Millennials, AWS and GCP have made their bones. We came of technical age with the platforms and we are used to their foibles. Azure is of course the boomer cloud,
Starting point is 00:03:05 but Gen Z is using platforms that aren't designed as tests of skill to let customers prove how much they want something. End quote. Hat tip to Corey for calling Azure the boomer cloud. That's amazing. However, I don't think this is a generational thing. There's an entire group of elder devs like myself, who have always preferred Heroku-style deployment platforms over AWS. While his view of the past seems skewed from inside the AWS bubble, he might be right about the future. Quote, AWS spent two decades building the most powerful cloud platform in the world. They may spend the next two watching it become irrelevant to anyone who wasn't already bought in. You should write an agent. Thomas Toczek makes the case that to truly Grock
Starting point is 00:03:51 LLM agents, so you can be the best hater or Stan that you can be. You need a right one. Quote, agents are the most surprising programming experience I've had in my career, not because I'm odd by the magnitude of their powers. I like them, but I don't like, like them. It's because of how easy it was to get one up on its legs and how much I learned doing that. End quote. I had this experience back in April when Thorsten Ball's Post walked me through it step by step. Thomas isn't wrong. Building an agent for yourself brings clarity to what is likely the most important developer-facing technology of the decade. It's now time for sponsor news. Why GitHub Actions slash checkout is slow for 98.5% of orgs. Depot just dropped another deep dive and this one
Starting point is 00:04:40 hits home for anyone using GitHub Actions. They analyzed thousands of workflows and found that 98.5% of orgs are running actions slash checkout slower than they need to. Turns out, the default settings most teams use are not great. Cold clones, missing shallow fetches, and bloated histories waste precious CI minutes. And this is before your build even starts. Depot's post breaks down why this happens, how much time it's costing you and what you can do to fix it. The takeaway, CI performance isn't just about bigger runners.
Starting point is 00:05:14 It's about smarter ones. Depot's obsessed with shaving seconds off every step, and this new data proves there's a ton of low-hanging fruit hiding in your pipelines. Read the full breakdown at depot.dev and CY's Speed matters more now than ever. Full link to the blog is in the newsletter. Dead Framework Theory Paul Kinlan says he was wrong last October when he predicted that LLMs would abstract away framework choice. Well, maybe he wasn't wrong, but he was wrong about the timeline. The reality is more interesting and more permanent. React isn't competing with other frameworks anymore. React has become the platform, and if you're building a new framework, library, or browser feature today, you need to understand that you're not just competing with React. You're competing against a self-reinforcing feedback loop between LLM trading data, system prompts, and developer output that makes displacing React functionally impossible. End quote.
Starting point is 00:06:11 When he says self-reinforcing feedback loop, he is not exaggerating. Today I learned Replit, Bolt, and tools like them are literally hard-coding React into their system prompts. Quote, they have to. If you're building a tool today to attract developers, you need to give them code they can maintain. And code developers can maintain now means React for the vast majority of web developers, end quote. I remember back in 2022 when Josh Collinsworth declared React isn't great at anything, except being popular, and he even debated this with us on the pod, turns out that being popular might be all it needed.
Starting point is 00:06:48 Stop vibe coding, your unit tests. We're still trying to figure out this whole agentic coding thing. Should we make the agent write the tests and we write the implementation ourselves? Or should we write the tests and make the agent write the implementation? Or maybe we should just sit back and say, hey, agent, take the wheel. Andrew Gallagher has thoughts on these questions. There is a growing sentiment that, LLMs are good for crud, boilerplate, and tests. While I am not so sure about how good
Starting point is 00:07:16 AI is it making crud or thumping out boilerplate a year of working as an SWE in the modern LLM-powered AI Codescape has proven to me that LLMs write unconstructive, noisy, brittle, and downright bad unit tests. Please, do not vibe code your unit tests, end quote. Andrew does say there's a way to get good tests from LLMs, but right now it requires you to make them right tests one at a time. Ain't nobody got time for that. Ain't nobody getting time for day. Ain't nobody getting time for day. That's the news for now, but go and subscribe to the change log newsletter for the full scoop of links worth clicking on, such as reviving classic Unix games.
Starting point is 00:08:01 Off-grid, long range, decentralized mesh networks. And what is so special about MCP? Get in on the newsletter at changelog. News. Last week on the pod, Andrew Nisbitt told us all about the world of open source metadata on Wednesday. And on Friday, we played a heated game of pound to find with our previous champs. Coming up this week, it's Hacker News's favorite blogger, Sean Gettoke. Have a great week. Like, subscribe, and five-star review us if you dig the show.
Starting point is 00:08:33 And I'll talk to you again real soon. Game on

There aren't comments yet for this episode. Click on any sentence in the transcript to leave a comment.