Six months ago, managing a web platform meant you needed a developer on board. Or you figured it out alone.
Today it’s different.
I’m not a developer. That’s always been a problem when discussing infrastructure, SQL, or why something was slow. I had gaps. Things I didn’t understand. And people around me assumed I’d just learn “like everyone else” or give up.
Except “like everyone else” means YouTube + documentation + Stack Overflow, and that requires patience you don’t have at 10pm when your site needs to be back up tomorrow morning.
Today I ask Claude. And I ask it to repeat. Rephrase. Give examples. Try again because I didn’t get it the first time.
That’s what changed. Six months ago, this didn’t really exist. Or it did, but it wasn’t smooth.
Why it’s an advantage
A real developer has patterns. They know “how things are done.” So they don’t ask certain questions. They assume you understand why you’d use a loop over something else, or what actually happens under the hood during a migration.
I ask the dumb question. “Wait, why do you put that there and not there?” And the person (the AI) explains. And I actually learn. Not just “this is how we do it in 2024.” But why.
An experienced developer won’t bother re-explaining the same thing 15 times. They’ll tell you “read the docs, you’ll figure it out.” Knowing you won’t, but that’s not their problem.
Claude says yes. Rephrases it. Draws a diagram. Gives an example in my context (WordPress, multisite, real stuff). Tries again.
What does that mean for Platform Owner roles? It means being non-technical is no longer a limit. It was a handicap. Now it’s a reason to learn better.
Not coding yet, but already different
I don’t code. I have no intention of coding. But I understand what’s happening now. I can read an error and guess where it came from. I can explain to someone else why their site is doing this weird thing.
It took me two months. Before, it would’ve taken six, with huge gaps.
The crazy part is this is exactly the opposite of what we said two years ago. Back then you had to “absolutely learn to code” to be a PO. Or manage infrastructure. Or understand the production chain.
Now? If you don’t code, you have an advantage. You ask questions a developer would never ask. You learn the actual structure of things, not just patterns.
What this changes for you
If you’re reading this and you’re a PO without technical training, you’re not behind. You’re ahead of people who think you have to learn to code first.
If you’re reading this and you’re an experienced developer, maybe you’ll recognize that re-explaining the same thing 15 times is annoying. And maybe you’ll end up turning to something that doesn’t give up on attempt three.
The profession changed. Not in some huge, visible way. But enough that “I’m not a developer” is no longer a conversation ender.
Now it’s a beginning.