@carnage4life I had the same experience earlier this month
My boss essentially vibe coded their own version of jira with some customizations to replace assigning a proper PM to a project we’re launching
We had to reassign a dev for several days to even figure out how to pry the thing off of replit and stand it up in our own aws vpc.
It was never architected for cloud. It’s exactly the same as the 30-something docker mini-apps I built at home.
The difference is I would never take them to work and be like “this is part of our infra now!”
@carnage4life Not really a new problem. Had a boss in 1999 who rewrote the core of our Java code “over the weekend” and we suffered through it for a while. He almost threw a fit when I eventually refactored it so we weren’t shipping the entire codebase as the client applet.
And it gave the CTO (one of those “CTO only bc they were the early-joiner”) confidence to drop a similar rearchitecture without consulting the team.
Maybe this is why I am not interested in vibe coding… 🤔
@carnage4life hot take from someone that loves well-designed, working code: answering product questions is where the value is. I used to think that product stuff was easy and low-value in my younger days, too, so no blame on the OP.
Engineers are expensive, and making engineers build the wrong thing is expensive.
Poorly designed products can limp along a long time before requiring total replacement.
The problem is that it works, you spend all your time putting out fires instead of building new features and innovating.
@carnage4life This bot has been asked to generate an alt text for your image by @enne. If you consent, you will grant altbot a one-time permission to process this specific post. All processing is done privately with no third-parties. Any and all content is deleted after processing.
The full privacy policy: https://github.com/micr0-dev/Altbot/blob/main/PRIVACY.md
Do you consent? Reply with 'Y' or 'Yes' to proceed.
@carnage4life
We recently had a designer deliver a heavily animated site they'd vibe coded for major internal stakeholder: the problem? Somehow it didn't work on any browser on any of the PCs in the office (and the stakeholder was presenting it on a PC at a global town hall in a couple of days)...
None of our front-end Devs could work out what Cursor had done, and so ended up rewriting it from scratch.
"i would rather debug a linker" is sure a phrase to describe just how bad something else is