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
This may be true pre-LLMs, but I think you need to account for the baseline build-vs-buy tradeoff shifting.

Companies in most cases don’t want to build SaaS because it is expensive to hire engineers to do it, not because they are allergic to owning teams.

If in-housing becomes substantially cheaper than the alternatives then companies will adapt.

But even if the new equilibrium is to hire a contract dev shop to build something custom to keep avoiding responsibility, this would have the same impact on SaaS.

So I’m pretty skeptical of this first-principles prediction expressing right level of uncertainty.

>>thepti+eL1
The same cost savings could be captured by SaaS. Potentially not by incumbents, but by up and comers.

If you can spend $10K/year to keep your in house one alive but $5K/year on the new SaaS option, you stop building your own again.