Over the last few years, the baseline for what a single engineer can build has exploded. Between mature frameworks, cloud primitives, and AI coding assistants, the friction from "idea" to "deployed system" has never been lower.

If you are a technically competent person today, you can build practically anything. Need a highly concurrent backend in Golang? You can spin it up. Need a complex React frontend with real-time state? Easy.

But that’s exactly the problem.

The Problem Isn't "Can We Build It?"

Execution is a commodity now, which means we’re drowning in software. Anyone who knows me knows my immediate skepticism for tech-first pitches—especially the ones lazily duct-taping "AI" onto a non-problem. The reality? Most of what gets shipped today is technically impressive and completely useless (lets not get started on maintenance or reliablitly). We have engineers sweating over microsecond latencies for apps with zero users, or architecting hyper-scalable backends for chatbots nobody asked for. It’s pure engineering theatre (hackathons are practically built on it, and its a solid way to lose every time). Building the thing isn't the bottleneck anymore. Figuring out what to build is.

Product Intelligence, Not Just Engineering

In the past, strong engineering was the primary moat. Today, product sense is the moat. It doesn't matter how clean your TypeScript is or how secure your system architecture is if you are building the wrong thing. Product is everything. Real value comes from:

• Understanding the actual user constraints
• Tracing the root cause of a business problem
• Knowing what not to build
• Prioritizing clarity and utility over complex features

If you can't trace where a user's problem came from and why they actually need it solved, your code isn't useful.

Engineering Still Matters (But Context Matters More)

This isn't a post about abandoning engineering. I still care deeply about building secure, scalable systems that just work. When you hit real scale, deal with sensitive data, or handle complex logic, strong engineering actually matters.

But the order of operations has flipped.

You can no longer just be a ticket-taker. The best engineers I’ve worked with whether during my adventures aren't just technical wizards. They are product people who happen to write code.

If you're just executing, you're competing in a race to the bottom against AI and an endless supply of cheap compute. If you can bridge that gap, if you can figure out the what and the why before writing a single line of code, that's where the real impact is.

And its a almost guaranteed way to build something that people actually want (and to win hackathons).