What 'Technical' Means Now: A Non-Engineer's Take on AI-Powered Building

I don’t have a computer science degree. I’ve never been a software engineer. Twelve months ago, if you told me I’d ship 35 working apps, I would’ve laughed. But here we are.

Let’s put it this way: the tools have changed what “technical” means.

1. You don’t need to master a stack to start building. For years, “technical” basically meant you could write code in the right languages and frameworks.
2. You still need to think systematically. You need to take a messy problem, break it into parts, and reason about how those parts interact.
3. You need product judgment. User empathy. Trade-offs. What matters now versus later. That’s the real work.

And I’ll be quite straightforward about one thing: those thinking skills didn’t come from software for me. They came from decades in strategy and operations, long before I opened a product builder.

AI-powered tools like Lovable basically unbundle two capabilities that used to be glued together: thinking about software and writing software. Historically, you needed both. Now you mostly need the first. The implementation still matters, but it follows the clarity.

Now, fair enough, this does not mean engineering expertise is obsolete. Not even close. What I’ve built are prototypes and MVPs, not production-grade systems. There’s a massive gap between “it works” and “it’s scalable, secure, reliable, and maintainable.” Engineers who build those systems bring depth that no tool replaces.

What’s actually changed is who gets to participate early. Ideas that used to die in a slide deck because there was no engineering bandwidth can now be tested in hours. People with deep domain knowledge, who could never previously ship a real prototype, can put something working in front of users.

So yeah, that’s the shift: engineering isn’t ending. The funnel into building is widening. And honestly, that’s the dream.