‘…now has access to a server-side container environment’

Headline demonstrates why SWEa don’t have to worry about vive coders eating their lunch. Vibe-coders don’t know what a container is, nor why it would be good for it to be in the context of an environment (what’s an environment?), or be server-side for that matter. Now if there were a course that instructed all this kind of architectural tradecraft that isn’t taught in university CS courses (but bootcamps..?), then adding vibe-coding alongside might pose a concern m, at least till the debugging technical debt comes due. But by then the vibecoder had validated a new market on the back of their v0, so thank them for the fresh revenue streams.

I don’t think any serious programmer feels threatened by vibe coders

At most it’s just a maintenance issue. A junior dev or plucky marketing team member might produce something that makes it to production and the senior devs might have to probe it to do more things

et voila: https://www.ulam.io/software-services/we-clean-up-after-vibe...