I feel I spend easily 3-5 times more on "QA" with LLM vibe coding than doing myself, the only difference, I couldn't code what I am currently making without LLM, the breath of knowledge required is just too vast.

Exactly the point I was going to make. Shipping something requires knowing how to ship it, monitor it, and fix it.

Writing code is the "easy" part and kind of always has been. No one triggers incidents from a PR that's been in review for too long.

It would probably have been more accurate to say "the cost of writing code" -- and you're totally right about the rise of other duties (and technologies) that expand to fill that gap.

As a dev team, we've been exploring how we grapple with the cultural and workflow changes that arise as these tools improve--it's definitely an ongoing and constantly evolving conversation.

I think the answer is that by the time AI can replace every function you do, it's also replaced everyone else and the world will either already have or will need to change radically.

I personally hope that the future becomes a UBI consumer-as-a-job thing, minus too much of the destructive impact that current consumerism has on the world.

Of course it's the case. However, "shipping code" isn't valuable and never has been. Shipping the right code that actually works and actually solves a problem is what is valuable.

Same here. I use Claude Code everyday, very useful, but nowhere near to where I don't have to jump in and fix very simple stuff. I actually have a bug in an app that I don't fix because I use it as a test for LLM's and so far not one could solve it, it's a CSS bug!

It's those who are shipping easily who are stupid. And what I mean by that is you can just ask the LLM to use the browser to get API keys and then use them to deploy. That's how the cost of shipping is zero. A hefty amount of YOLO code on top of YOLO deploy. I mean, you could also have the LLM build you a CI CD pipeline, but that's not YOLO.