zlacker

>>namany+(OP)
It's a tale as old as time that developers, particularly junior developers, are convinced they could "slap together something in one weekend" that would replace expensive SAAS software and "just do the parts of it we actually use". Unfortunately, the same arguments against those devs regular-coding a bespoke replacement apply to them vibe-coding a bespoke replacement: management simply doesn't want to be responsible for it. I didn't understand it before I was in management either, but now that I'm in management I 100% get it.

>>bandra+s01
sorry, what do you mean?

>>misiti+011
1. Enthusiastic employee (vibe-)codes a replacement for a turnkey SaaS product that the company uses.

2. Company uses it, maybe even starts to rely on it for important business operations, and for a time the employee supports that app.

3. Bugs creep in, feature request pile up.

4. Employee either leaves the company or moves on to another project.

5. Pain

>>sbarre+F11
And don't forget the safety in getting to say "our systems are down because of [X TRUSTED SOFTWARE FROM LARGE KNOWN BRAND] and we're just waiting for them to fix it" instead of "our shitty internal tooling is broken and no one knows how to fix it"