HN user
50 years writing software. I use AI heavily — it collapsed my build cost by 40-60x and I run 56 microservices as a solo founder. But I read every line. I design every boundary. AI is the best junior engineer I've ever worked with, and like every junior engineer, it needs supervision. The problem isn't the tool — it's people skipping the decades of judgment that tell you when the tool is wrong.
Solo founder running 56 microservices and 69 autonomous agents in production. AI collapsed the build cost by 40-60x, but every architecture decision, security boundary, and ops choice still required experience. The article gets the direction right but the conclusion wrong — subscriptions don't die, per-seat pricing does. When agents are doing the work instead of humans clicking dashboards, you price
Running MCP tools in production — the security gap isn't theoretical. The spec gives you a tool execution model with no opinion on who gets to call what, or how you scope access when tools span multiple services. WebMCP inherits all of that plus exposes it to every page visitor's browser. The protocol needs an auth and permissions story before it's a standard.