Still the Painter

Everyone in those threads is grieving a job that was never really the job. Your capability didn't go down when generation got cheap. It went up, and here's the arithmetic.

By Jason Waldrip, with Claude August 9, 2026 16:20

The thread is always the same thread. AI is taking our jobs, we’re all cooked, learn a trade. A few hundred comments deep, and every one of them is a version of the same fear, written by people who are genuinely good at this and just watched something turn their best week into an afternoon. I read a lot of it before I closed the tab.

The one I was reading happened to be engineers. It could have been any of them. The illustrators are having it, the session players are having it, the designers are having it, the copywriters had it first and loudest. Same fear, same comment ordering, different room. They’re all right about what they noticed. Then they take a leap, and the leap is wrong.

Start with the part they got right, because it’s real and pretending otherwise is worse than useless. You spent ten years getting fast. Then you described a thing in a paragraph and got back a tested branch, or a finished layout, or a demo that would have cost you a weekend, before your coffee was cold. The floor moved. That’s not imagined. I’ve written the long version of it already: volume got commoditized, and if your value is denominated in output, you’re now in a race with something that doesn’t sleep, doesn’t get bored, and doesn’t have opinions about the brief.

The leap comes right after. Volume is free, therefore I am worthless. Every thread makes it, usually within three comments, and nobody stops to check it. It only follows if the volume was the thing that made you valuable in the first place.

It wasn’t. And I know that because I ran the experiment on myself for eight years.

the badge that was actually a warning

By the time I left GigSmart I’d written something like one in five commits in the company’s history. Most of anyone, by a wide margin, across the app, the libraries, the infra, the build, the deploy path. There was no hour on the clock without my name on something. For a long time I wore that like a badge.

It was a load-bearing wall with a green contribution graph. I’ve made that argument before and I’m not going to relitigate it here. The part that matters here is more personal: I had priced myself in throughput. Ask me what I was worth and the honest answer, the one underneath the one I’d have said out loud, was a number of commits. That’s the same math those threads are doing. I just did it while the number was going up, so it felt like confidence instead of fear.

Both are the same mistake. You only feel it when the supply of the thing you’re counting suddenly goes infinite.

what you were actually paid for

Brandfolder, 2015. Ruby was crashing generating large zip files. Heavy IO, wrong tool for the shape of the problem. We carved that one piece out into Go and shipped multi-gigabyte archives at minimal cost.

Point a fleet of agents at that codebase today and they’ll do good work. They’ll profile it, cache what’s cacheable, thread what Ruby lets you thread, chase the allocations, and hand you a well-documented improvement with tests. What they will not do, unprompted, is stop and say the language is wrong for this. That call took about ten minutes. It was worth more than every line I wrote that year.

The ten minutes is what I was paid for. The code that followed was just how the ten minutes got expressed, because in 2015 there was no other way to express it. If you wanted a decision to become a real thing, somebody had to sit down and type it out, and the typing was slow, so the typing looked like the job. It was the delivery mechanism for the job.

That’s the confusion at the bottom of every one of those threads. Whole professions spent decades being measured by their delivery mechanism, because the delivery mechanism was the bottleneck, and bottlenecks are what people measure. Then the bottleneck moved and everyone assumed their worth moved with it.

Test it on your own work, whatever your work is. The moment you knew the layout was fighting the content and the entire grid had to change. The take where you heard the arrangement was too busy and pulled three parts out instead of adding a fourth. Nobody was paying you for the hours of nudging type or re-tracking the part. They were paying for the ten seconds where you knew which way to go, and then for your willingness to go spend the weekend making it exist, because spending the weekend was the only way anyone would ever see the call you made.

run the arithmetic again

Here’s the thing nobody in those threads does, which is take the change seriously in the other direction.

Your judgment didn’t get cheaper. It got a bigger surface. The calls you can make in a day used to be capped by how much you could personally produce, because you spent most of the week being the supply. You’d make a handful of genuinely consequential decisions and then go implement them, and the implementing is where the week went. Now the implementing is cheap, and the cap is off. You can make those calls all day, and each one lands across more work than your hands could ever have reached.

That’s not a smaller job. That’s the same job with the friction removed and the blast radius multiplied. Your capability went up. What went down is the share of your day spent proving it.

The catch is the same one it’s always been, and it deserves one sentence rather than a section: a multiplier only works on what you feed it. Multiply real judgment by a fleet and you get something genuinely new. Multiply nothing by the same fleet and you get a beautifully formatted disaster, faster. Anything times zero is still zero.

So the question those threads should be asking isn’t whether the machine can do what you do. It’s whether you were ever clear on what you do.

the brush and the painter

A painter with a studio of assistants grinding pigment, stretching canvas, and laying in the underpainting is still the painter. Nobody stands under a chapel ceiling and credits the scaffolding. The assistants were real, they did real work, and the work is still his, because the thing that made it worth looking at never lived in the brush.

We already accept this everywhere else and find it completely unconfusing. The producer who plays none of the instruments made the record. The director never touches the camera. The architect has not laid a brick in thirty years and the building is still hers. Nobody has ever suggested a novelist owes the credit to the typesetter.

The ideas are yours. The origination is yours. The taste that says this one and not that one, the sense of which problem is worth a week and which one should be deleted, the twenty years that turn a crash, or a mix that will not sit still, into ten minutes of diagnosis. None of that moved. You may not be holding the brush anymore. You’re still the painter.

The people in those threads aren’t mourning their capability. They’re mourning the only proof of it they ever had, and they haven’t yet found the new one. That’s a real loss and it’s worth about a week of feeling bad. Then you get to the better problem, which is what to do with a calendar that suddenly has room in it, and a fleet that will build anything you can decide on.

That’s a much harder question than the one on Reddit. It’s also a much better one.