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
> "just do the parts of it we actually use".

25 years here. You can absolutely do this. Most software is orders of magnitude more complex than it needs to be.

The junior programmer you are talking about who wanted to rewrite it in a weekend tends to come back with a working program, not empty handed.

>>ground+sq1
Yes, I didn't really doubt the developer could do it, the problems are:

1. That's not a great use of the developer's time, and

2. anything in-house increases our training and support costs

>>bandra+Dx1
And both are completely different arguments then your original post.

>>ground+NE1
No, those are the two main reasons management don't want to have internal systems belong to them

>>bandra+1P1
I see. I misread. My mistake. I agree - the issue is not technical it’s the responsibility for the project.