I think it really depends on how you utilize AI.
If someone treats it like magic and blindly vibe codes everything into production, then yes, they’re going to hit that 1% wall hard. Especially in ecosystems like WordPress or Envato where a tiny architectural mistake, security issue, or guideline violation can mean instant rejection. In those environments, deep understanding absolutely matters.
But if AI is used as an assistant rather than a replacement for thinking, it’s a different story. Drafting boilerplate, refactoring repetitive patterns, generating test scaffolding, exploring alternative implementations, speeding up documentation, that’s where it shines. The senior dev still needs to review, structure, and make final decisions. The tool doesn’t remove skill, it amplifies it when skill is already there.
About AGI and curing cancer, I agree the hype is out of control. Bold claims get headlines and funding. That doesn’t mean the current models are useless, it just means they’re not what marketing says they are. They’re probabilistic systems, not reasoning minds. Expecting them to replace engineering judgment is unrealistic.
Also, regarding the “unsalvageable codebase” point, that’s less about AI and more about process. If AI-generated code isn’t reviewed, versioned, and incrementally integrated like any other contribution, it will absolutely become chaos. But that’s true for human-written rushed code too. Version control, code reviews, and architecture discipline still apply.
I don’t think the industry is falling apart. It’s shifting. Junior roles may change, but fundamentals are still fundamentals. The devs who understand systems, constraints, performance, and tradeoffs will remain valuable. AI doesn’t remove the need for that. It just changes how fast we can move.
So yeah, these tools are useful. They’re not magic. They’re not AGI. They’re not the end of developers either. It really comes down to how responsibly and strategically we use them.