Revenge of the junior developer (News)

0:04What up nerds? I'm Jared and this is Changelog news for the week of Monday March 24th, 2025. 5. Ikea is tapping in to our collective enjoyment of all things Severance with a new ad campaign highlighting their minimalist desks, acoustic screens, and moody lighting that they say is perfect for work that is mysterious and important. Well played, Ikea. Well played. Meanwhile, I'm still working my way through Severance Season 2. Slowly, surely, mysteriously, and importantly. Okay, let's get into this week's news. Revenge of the junior developer. Steve Yeggie's latest rant about the future of coding comes replete with charts, bad news for CIOs, and a dish junior devs will be able to serve cold.

1:02That's revenge, if you don't know the saying. Where do we start? By cruising right past the vibe coding craze to what's coming next. Quote, Vibe coding is in a steep ascent, and chat-based coding is indeed also still on the rise, for now, but agentic coding, the subject of this post, will soon rocket by chat coding as if it's standing still. End quote. Agentic coding, according to Steve, will have fully arrived in Q3 of this year and is going to completely change the game. Quote, Once you've tried coding agents and figured out how to be effective with them, you will never want to go back. They are going to stomp chat coding.

1:44And the great thing is, with agents, you are still vibe coding. That's why it's not a modality. You can vibe code with any non-manual AI modality. Chat, agents, clusters. As long as the AI is doing the work, you're vibing. The only difference with agents is that you don't rendezvous with them as often. End quote. The downside of agentic coding is it's going to be expensive Like, really expensive. The upside is, Steve works for an agentic coding tools provider, Sourcegraph, so it'll be totally worth the cost. I kid a little, but it's worth keeping in mind when the most bullish of the bulls are incentivized to be so bullish.

2:25Still, Steve is a smart guy, and I 100 % believe he believes what he's saying here. Where do the junior devs fit into this future? Why and how do they get their revenge? I won't spoil the ending for you. Check for the link in the newsletter. Life-altering Postgres patterns. Ethan McHugh says, Believe it or not, I don't think that title is clickbait. There is a set of things that you can do when working with a Postgres database, which I have found made my and my coworkers' lives much more pleasant. Each one is by itself small, but in aggregate, have a noticeable effect. End quote. Ethan is talking about things like using UUID primary keys, giving everything created at and updated at fields, using schemas, a very cool feature in Postgres, enum tables, and much more.

3:17Verification-first development. Hillel Wayne takes some time to make the case that test-first development, TFD, is different than test-driven development, TDD. Quote, the former is write tests before you write code. The latter is a paradigm, culture, and collection of norms that's based on TFD. More broadly, TFD is a special case of verification-first development, VFD. And TDD is not. End quote. Hillel goes in-depth on what exactly VFD is, some benefits and drawbacks, and why he thinks VFD is a technique which he appears to like, not a paradigm which he appears to dislike. It's now time for Sponsored News.

4:04I see what you did there, Augment Code. Did you know Augment Code now sees what you see with inline image support in VS Code with IntelliJ support coming soon? No more struggling to explain things that are easier to show. While most tools just attach images as files, disrupting your workflow, Augment embeds images directly within your conversation flow. It's like giving your AI assistant a set of eyes to see exactly what you're working on by sharing screenshots, diagrams, or any visual content directly in line with your chat. Here's what you can do now. 1. Communicate complex architectures by sharing system diagrams to get insights with perfect context.

4:462. Accelerate UI development by dropping in mockups to get suggested implementations using your existing components. 3. Squash visual bugs faster by showing Augment exactly what's happening instead of struggling to describe it 4. Explain design pattern implementation by sharing diagrams to get code structure suggestions that match your code-based conventions All of this lets you build faster and more creatively Learn more about this feature at the link in the newsletter or by going to augmentcode.com The pain that is GitHub Actions Gerd Zellweger had to redo their CI setup on GitHub Actions and shares a bunch of the pain points he hit along the way.

5:30Quote, Our CI is complex. Merge queues, multiple runners, self-hosted, blacksmith, GitHub-hosted, Rust builds, Docker images, and heavy integration tests. Every PR we merge burns through an hour of CI time running across multiple parallel runners. There are a few things we'd like to have, which we deem as good software practice, but it's nothing unheard of. Such as, one, everything that goes into main must pass all tests. Two, trivial mistakes, like formatting, unused depths, lint issues, should be fixed automatically, not cause failures. Three, the artifacts we test with NCI should be the exact ones we release.

6:14And four, CI should complete quickly, to keep developers happy. GitHub Actions technically allows all of this, but setting it up is a frustrating mess full of hidden gotchas, inconsistent behavior, and a debugging experience that makes me question my choices. End quote. One of my concerns when GitHub first got into the CI game was that their advantage by already being the host, which is real and pretty great, would be so massive that they wouldn't have to innovate much beyond the basics to completely take over the market. Maybe that concern was valid? What do you think? Let me know in the comments.

6:52A web-based ASCII diagram builder. CASCII, C-A-S-C-I-I, is a web-based ASCII and Unicode diagram builder written in vanilla JavaScript. Quote, it has zero dependencies on any servers, webpacking, libraries, and is no markup and no style sheets. You can start building diagrams by simply opening the casci.html file in a browser. Kasky is also hosted at Kasky.app, where you can get short links to your diagrams, open up an account, etc. End quote. Check out the newsletter or your chapter image for a picture of a diagram built with Kasky that loosely explains how Kasky is structured internally. That's the news for now, but also scan the companion newsletter for even more links worth clicking on, such as the Vibe Coding Manifesto, the model is the product, they lied to you, Building software is hard.

7:48And of course, our world-famous unordered list of awesome links. Get in on the newsletter at changelog.com slash news. Have a great week. Leave us a five-star review if you dig our work. And I'll talk to you again real soon.