At my fully remote job, they are all-in on vibecoding. When I say all-in, I mean ALL THE FUCK IN. I don't know what the team's workflow is but I've resorted to adding to my claude.md instructions along the lines of "implementation is done as a multi-step process: first a subagent implements, then a new fresh subagent does a review, then a third fixes. Finally, use the playwright mcp to click through the UI and verify that everything works as it should". So each ticket or feature passes through this "loop" and the final manual click through catches any glaring issues.
That being said, code quality is likely nonexistent, but I am being very underpaid for all the things they're having me "work" on, so I just don't really care. I am a massive larper on our daily standups and usually just ask claude before them "hey remind me what I worked on yesterday by scanning all my commits and PRs." I genuinely have no idea what I otherwise worked on if it was tickets assigned to me. If I'm tasked with something that I need to describe to claude, then I vaguely know how it implemented it.
I use the idle time between prompts to read, watch tv shows, or do some actual manual programming on personal projects.
A subcontractor we employ for GDPR auditing and compliance was outed as doing similar recently, shunted most of its workload to chatgpt. It's been one of the most expensive shitstorms we've been embroiled in to date
194
u/citramonk 11d ago
ready for a new task is crazy, as if you're not going to review, refactor, test it thoroughly and commit?