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
It that works, nobody would be using Jira anymore, because people would just use a competitor that's cheaper or vibe code their internal Jira tool.

Somehow that has not happened yet in 2026.

>>g947o+W71
This is because what management wants and what builders want are not aligned, not because the quality of JIRA is so amazing that no other alternative could ever be created. JIRA is fine but many people I know that use have some qualms with it because the bloat is pretty crazy.

>>mym199+F91
As Spolsky said a quarter century ago, "bloat" is just "bugs somebody already fixed". (He may have actually said that about "cruft", but the idea still applies.)

>>bandra+Ua1
Hard to believe that it was that long ago!