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
what if this time it's senior developers and they actually can slap something together better then the expensive SAAS offerings?

what if the expensive SAAS offering is just as vibe coded and poor quality as what a junior offers?

>>mitten+f31
You're not considering opportunity costs and buyers vs. users.

If your senior developers can slap together something better than an expensive SAAS offering you want them directing that energy at your core products/services rather than supporting tools.

And the people deciding to buy the expensive SAAS tools are often not the people using them, and typically don't care too much about how crappy the tool may or may not be for doing the job it's advertising as doing.

>>ytoaww+Dc1
And it's never just the slapping together. it's the ktlo: a perpetual tax on your eng team for every thing they own.

>>x0x0+3q1
No matter what it's a tax on your engineering team to keep it together. But the most brittle parts are always right at the seams. It's not as hard to sew together components when you can cut the cloth down to fit together. Who knows how it'll shake out.