A few days ago I published a lighthearted post about building a coding mascot generator with Google AI Studio. The app itself — MascotCraft Studio, complete with a mascot named Octo-Byte — wasn't the point of the post. It was a fun side project. But the comments turned into something I've been thinking about ever since.
Someone left a comment that's been rattling around in my head:
"We're moving from an era where implementation was the bottleneck to one where judgment becomes the bottleneck. When anyone can generate code, interfaces, and integrations in minutes, the differentiator becomes identifying worthwhile problems, defining clear requirements, and recognizing whether the result is actually good."
I read that, nodded, moved on with my day — and then kept coming back to it.
Think about what it took to build something like MascotCraft Studio even three or four years ago. You'd need:
That's a team. Or at minimum, a single person wearing a lot of different hats, each requiring real expertise.
I described what I wanted in a paragraph. The implementation step — all of the above — happened in minutes.
If the hard part used to be "can we build this," and that part is now fast, what's the hard part now? Based on that comment thread, it's things like:
Here's the thing I keep circling back to: judgment isn't something you can prompt your way into.
You can ask an AI to "review this code for bugs" or "tell me if this design is good," and it'll give you an opinion. But knowing whether that opinion is trustworthy — knowing enough to push back, to say "actually, for my use case, that tradeoff doesn't make sense" — that still requires you to understand the problem space yourself.
In other words: the easier it gets to generate things, the more it seems to matter that you actually understand what you're generating and why. It's less "know how to build everything yourself" and more "be able to tell good implementation from bad, quickly, across a much wider range of things than you could personally build by hand."
I don't have this fully figured out, but it's shifted how I think about a few things:
I don't have a tidy conclusion here, because I don't think there is one yet — this feels like something the whole industry is figuring out in real time. But I'm curious: if "judgment becomes the bottleneck," how do you actually practice and sharpen that judgment deliberately, rather than just hoping it accumulates as a side effect of experience?
If you've got thoughts on this, I'd genuinely like to hear them. 🌸