This is the thing I hate about web development - "Here's this fantastic new feature that solves all of your problems - But you'll have to wait several years to use it because loads of iPhone users are still on old Safari versions"

Ultimately I enjoy being a software engineer, not a project manager. If you're 100% vibe coding, then you're just being a project manager. The coding is the fun part!

But AI still regularly makes very severe mistakes so needs careful reviewing. And I usually only use it for the more boring "side tasks" like tooling setup, unit tests etc, while doing the coding of the main features myself, helping keep my skills up.

Ah yeah I see. My view is that AI is great if you're using it to augment your development, but unsustainable if it's 100% vibe coded.
As long as I'm reviewing it's output, fully understand it, and find the silly mistakes it's made, then it's a great productivity boost

I think you've misinterpreted their argument - They were saying that things you'd do as a hobby project to practice your skills people are now outsourcing to AI - So you're losing some practice of skills, which I think is valid.

What would you put in a style guide that isn't enforced by the formatter+linter? Writing a style guide for your repo seems unnecessary to me now we have automation tools for it