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
Even more accurate (I work in this space):

3. Bugs creep in, feature request pile up.

4. Employee continue in the company and request help (or the managers see the need):

4.1 They hire more, but if all are vibe-coders too

4.1.1 The product gets more complicated (no more complex, that good developers can manage!)

4.1.2 Bugs creep in, feature request pile up.

4.1.3 People start to get desperate, not worries! now:

4.1.3.1 Somebody vibe-code a new alternative that solves the immediate problem

4.1.3.2 Bugs creep in, feature request pile up.

4.1.3.3 Needs to sync with the other tools

4.1.3.3.1 Somebody vibe-code the sync that solves the immediate problem

(the saga continue)

In parallel:

4.2 Eventually is obvious that need external help

THEN:

4.2.1 They ask for consultors for build tool, of course, from a company that has embraced the IA!

4.2.2 They build new shinny tool!

4.2.3 Bugs creep in, feature request pile up.

4.2.4 Needs to sync with the other tools ....

AND:

4.3.1 They ask for consultors, to teach them what to do, of course, from a company that has embraced the IA!

4.3.2 New shinny theory of how do the thing with IA is now being implemented!

4.3.3 It require a rewrite of not only past solutions but, a change of how the company behave!

4.3.3.1 Needs to sync with the other tools .......

4.3.4 And it spark beautiful office/political debates around some philosophical whatever that also trigger changes in the structure, hiring or whatever, alienating the people that has been working there, that after months, has started getting the handle of it!

4.3.5 Employees either leaves the company or moves on to another project.

4.3.6 New employees arrive, with a wild new IA tool and different vibes that vibe-coding!

... the saga continues

5. Is now clear that it need to buy a product form a well stablished software provider

5.1 And all of them are now in the IA craze!

.............

>>mamcx+of1
All of this will create noise whilst up-starts and competitors who dont fall for the trap carry on making real forward progress.

lol