Full-breadth developers for the win (News)

7 Jul 2025 · 9 min

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

The Changelog: Software Development, Open Source

Episode Summary

Full-breadth Developers for the Win (News)

This episode focuses on the emerging concept of "full-breadth developers" as discussed by Justin Searls, alongside several important technical advancements and industry news.

Key Discussions

  1. Full-breadth Developers
  2. Definition: Justin Searls introduces the term "full-breadth developer," individuals who encompass both product and programming roles, effectively bridging the gap between problem recognition and solution implementation.
  3. Significance: He argues that these developers will thrive amid AI advancements because they can adapt to changes more efficiently. He cites his own experience of completing two months of work in two days utilizing generative coding tools.
  4. Challenges: Searls acknowledges the anxieties developers face regarding AI's impact on job security and the ethical concerns surrounding AI training. He stresses the necessity for developers to understand their employer's financial dynamics to remain relevant.
  1. Cloudflare's Pay-per-Crawl Initiative
  2. Overview: Cloudflare is proposing a new model that allows content creators to charge crawlers for accessing their content, moving beyond the binary choice of allowing or blocking access.
  3. Mechanism: By implementing the HTTP 402 status code, Cloudflare aims to enable a nuanced monetization strategy for content publishers. This system would require crawlers to authenticate and agree to payment terms.
  4. Potential Impact: The success of this initiative could empower content creators and alter how web content is accessed and monetized.
  1. Critique on AI Agents
  2. Hugo Bowne-Anderson's Insights: He shares frustrations with the common practice of building complex AI agents that often fail due to their intricate designs.
  3. Key Takeaway: He advises against the premature development of agents and stresses the importance of simplifying LLM-powered systems to avoid unnecessary brittleness and debugging headaches.

Sponsored Content & Tools

  • CodeRabbit: A new AI-powered tool providing free, comprehensive code reviews directly in VS Code, aiming to improve code quality and developer experience.
  • Job Worth Calculator: An open-source tool to evaluate job value based on various factors such as salary, work hours, and environment, enabling users to make informed career decisions.
  • PlanetScale for Postgres: Announced by CEO Sam Lambert, this initiative aims to extend PlanetScale's capabilities to support Postgres databases following customer demand. It signifies a strategic direction towards enhancing database scalability.

Conclusion This episode highlights significant trends in software development, emphasizing the evolving role of developers in the age of AI, innovative monetization strategies for content, and cautionary advice on AI implementation. The discussions encourage developers to adapt and seek out opportunities that align closely with business objectives to ensure their continued relevance in a rapidly changing landscape.

Call to Action

  • Subscribe to *Changelog* for more news and insights.
  • Leave a five-star review if you find the content valuable.

Additional Links

  • Subscribe to the newsletter [here](https://changelog.news).
  • Explore the tools mentioned in the episode for enhanced development experiences.

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:28What up nerds? 30 minutes prior to our 10 a.m. start. So if you were planning on arriving just before 10, get your ear holes to the Oriental Theater a little bit earlier. And if you haven't bought your ticket yet, you now have one more reason to get in on it. They're 15 bucks cheap and free for Changelog++ members. Head to changelog.com slash live. What are you waiting for? An engraved invitation? Okay, let's get into this week's news. Full breadth developers for the win. Much like myself, Justin Searles turned the corner on generative coding tools. Quote, it may not map to any particular splashy innovation or announcement, but everyone agrees generative coding tools crossed a significant capability threshold recently.

1:19It's what led me to write this. In just two days, I've completed two months worth of work on Posse Party. End quote. Justin explains how he did it, but the key insight is this. He embodies the entirety of the problem-solution space. He is both product Justin and programmer Justin. If you were to split him in two, it would have taken weeks, not days. In this post, Justin coins the term full-breath developer and describes why he thinks full-breath devs will be the big winners of the AI upheaval. He also disambiguates my frequent call to move up the value chain. Quote, A lot of developers are feeling scared and hopeless about the changes being wrought by all of this.

2:04Yes, AI is being used as an excuse by executives to lay people off and pad their margins. Yes, how foundation models were trained was unethical and probably also illegal. Yes, hustle bros are running around making BS claims. Yes, almost every party involved has a reason to make exaggerated claims about AI. All of that can be true, and it still doesn't matter. Your job as you knew it is gone. If you want to keep getting paid, you may have been told to move up the value chain. If that sounds ambiguous and unclear, I'll put it more plainly. Figure out how your employer makes money and position your ass somewhere directly in between the corporate bank account and your customer's credit card information.

2:50Cloudflare experiments with pay-per-crawl. Many content creators are rightfully concerned about LLMs crawling their sites and scraping their hard-produced content. Up until now, the options have been limited to a binary let-them-do-it or don't-let-them-do-it. Enter Cloudflare. Quote, We believe your choice need not be binary. There should be a third, more nuanced option. You can charge for access. Instead of a blanket block or uncompensated open access, we want to empower content owners to monetize their content at internet scale. We are excited to help dust off a mostly forgotten piece of the web, HTTP response code 402, end quote.

3:32By leveraging the 402 payment required status code, Cloudflare has devised an experimental pay per crawl system where publishers control their monetization strategy. Crawlers authenticate via the web bot auth protocol and indicate their payment agreement via headers. And Cloudflare acts as the settlement layer. I love seeing smart people throw their ideas into the web arena like this. Will it work? I have no idea. Does it stand a chance? I think it might. Stop building AI agents. Hugo Bone Anderson is frustrated by seeing the same pattern after advising dozens of teams building LLM-powered systems.

4:12Quote, Everyone reaches for agents first. They set up memory systems. They add routing logic. They create tool definitions and character backstories. It feels powerful and it feels like progress until everything breaks. And when things go wrong, which they always do, nobody can figure out why. Was it the agent forgetting its task? Is the wrong tool getting selected? Too many moving parts to debug? Is the whole system fundamentally brittle? End quote. Hugo learned this the hard way by building a research crew of three agents five tools, and perfect coordination on paper, the system, like others he'd built, failed spectacularly, leading Hugo to create this flowchart about should I use an agent, where the hint is, probably not.

4:57This post is about what Hugo learned from those failures, including how to avoid them entirely. It's now time for Sponsored News. Free AI code reviews in VS Code, Cursor, and Windsurf. CodeRabbit just launched AI-powered code reviews directly inside VS Code with support for Cursor, Windsurf, and more on the way. Now you can code, review, and commit, all without leaving your IDE. It's a seamless review-in-flow experience. CodeRabbit doesn't just help you write code, it catches AI slop too. hallucinations, code smells, logical errors, missing unit tests. They all get flagged in real time with configurable rules.

5:40Even better code reviews in your IDE are free. CodeRabbit gives you senior engineer level reviews in your IDE for free. If you've been waiting for AI reviews that feel like part of your workflow, this is the one to try. Learn more at coderabbit.ai or follow the link in the newsletter. Once again, that's coderabbit.ai. Calculate the actual value of your job. Is your job worth the grind? This job worth calculator calculates a job value rating based on your salary, work hours, commute time, environment, and more. It does international salary comparison with purchase price parity conversion across 190 plus countries.

6:21It lets you customize it with personal factors like education level and work experience, and then it generates a shareable, downloadable job analysis report for you. It's open source and on the web. Find the link in the newsletter. Announcing PlanetScale for Postgres. Here's Sam Lambert, PlanetScale CEO, announcing that the Vitesse cloud provider is adding Postgres to its shortlist of supported databases. Quote, PlanetScale has been successful hosting some of the world's largest relational databases so why are we building for Postgres? The reason is simple, customer demand, end quote. This is fascinating in the wake of Subabase recently hiring Vitesse co-creator Sugu Sugumarane, which I still don't know how to pronounce, but we'll have him on the show soon, so I'll find out for sure, to help them build Multigress, which is Vitesse for Postgres.

7:15On that topic, Sam says, quote, Vitesse is one of PlanetScale's greatest strengths and has become synonymous with database scaling.

7:39So, PlanetScale, which is historically all about Vitesse and MySQL, plans on bringing Vitesse-like sharding to Postgres, but not with Vitesse itself. Meanwhile, Supabase is working on pretty much the same thing with some of the team that built Vitesse in the first place. Imagine what they could create if they teamed up on this initiative, but something tells me that's never going to happen. Quick disclaimer, I am a small investor in Supabase because I wanted to make a bet on the future of Postgres and their Postgres maxis. Maybe I should invest in PlanScale now too. That's the news for now, but go and subscribe to our changelog newsletter for the full scoop of links worth clicking on, such as the email startup graveyard, backlog.md, a new developer dictionary definition for Scrum, and our award-worthy unordered list of interesting links.

8:35Get in on the newsletter at changelog.news. Have a great week. Like, subscribe, and leave us a five-star review if you dig our work. And I'll talk to you again real soon.

8:51Game on!

From the publisher

Justin Searls describes the "full-breadth developer" and why they'll win because AI, Cloudflare comes up with a way publishers can charge crawlers for access, Hugo Bowne-Anderson explains why building AI agents fails so often, the Job Worth Calculator tells you if your job is worth the grind, and Sam Lambert announces PlanetScale for Postgres.

More from The Changelog: Software Development, Open Source

All 232 episodes
Full-breadth developers for the win (News)The Changelog: Software Development, Open Source · 9 min
Listen in VO