> ...this shift advantages people who can build fast with AI tools and disadvantages people who can't. The bias to action is genuine, but it isn't neutral. The engineers who've adopted these tools effectively get heard more often, get their proposals taken seriously more often, and shape direction more than those who haven't.

If only this was limited to engineers.

I'm seeing this applied to every role across organizations. The designer that gets heard is the one who can vibe code the best. Same with strategists, writers (seriously), and other people for whom "coding" is not remotely their expertise or function. This exponentially accelerates the "cost of aligning organisationally" when you have not only several eng groups but every single person in your team regardless of role proposing their own solutions, that as an engineer it is now your responsibility to babysit (or as we are terming it, "harden").

Meanwhile, the quality of creative work suffers because instead of working in a surface that's designed for their trade and process (e.g. Figma) they jump straight to Claude or Cursor or v0 or whatever, where they're bounded by (and graded on) their ability to manipulate a bot, rather than their actual skillset.