The headlines are terrifying. Every day seems to bring another story about how AI is going to wipe out entire categories of jobs. “The Disappearance of the Entry-Level Job” is a popular one.

These articles paint a grim picture of a world with no starting point for a career.

Like most things, the truth is somewhere in-between. While it’s true that many familiar junior-level positions are being changed or eliminated, that doesn’t mean there are no junior-level positions.

Say it with me: “the jobs will change”.

There’s a lot of chatter about AI reshaping hiring, but it’s not as simple as “replace recruiters” or “solve everything.” The impact depends on how it’s trained, how it’s prompted, and how it’s used. It could streamline things or make them worse, depending on the setup.

Today we are releasing an early version of the Resume Editor, a web-based tool for creating and managing resumes.

This is an alpha release. This means we are still actively adding features and fixing bugs. The project is open source, and we are looking for feedback.

I’ve written quite a bit about the overall process of AI-assisted development. Not the “write code” part of it - if anything, that’s the easy part. There’s a process to writing a project which can be maintained, with bug fixes and new features.

What’s a little tough right now is constantly being in the position of being a manager, stakeholder, business, and end-user. I’ve understood it in an abstract, and tend to be careful about considering them.

It’s so very visceral now.

Most of the big players (Anthropic, Google, et. al) provide all-in-one solutions for writing code. If that’s what you’re doing, that’s fine, but you may be missing out.

For one thing, they can be pretty expensive (unless your company is paying for it). Anthropic’s best - Opus - can get really expensive, really fast. Admittedly, it still costs less than paying for an overseas team, but if it’s coming out of your wallet you’re bound to notice.

Considering how quickly everything is moving, I’m sure this post will age like milk.

So, you’ve got a great process down for developing your code. You’ve got great documentation, 100% test coverage, good git branching and tagging, and all the other detailed steps for generating code.

It sure is a lot of typing, though, isn’t it? Very repititious. Obviously, you should automate those steps! You’re only a little bit away from typing in “Write me an app that does X,Y, and Z!” and then taking a nap while it does the work!

Not so fast…

“AI is just a bubble!” Yep, sure is. So what? That’s no reason to ignore it, or to brush it off as a fad. While nobody can be 100% sure exactly how it will make the world look in five years, you can be sure the world will look different.

Calling something a “bubble” is often a way to dismiss it. But history shows that even when a bubble pops, the underlying technology doesn’t just go away. It sticks around and changes everything.

There’s been a lot of noise about AI replacing developers. Spoiler: it won’t. But your job is changing in ways nobody’s really talking about.

Ever wonder why AI sometimes acts like your chatty friend and other times like a stiff librarian? The difference often comes down to two invisible ingredients: the system prompt and your user prompt. Let’s peel back the curtain.

AI isn’t going to take your job, it’s going to change your job. There are things you do as part of your job now which will go away, but new parts will be added.