zlacker

I think you can avoid the pain by thoughtfully designing it to avoid lock-in. You want it so that if needed, a dev can vibe-code a migration tool to the equivalent SaaS offering. AI lowers the barrier for creating these in-house replacements, but it also lowers the barrier for scrapping them too.

>>pverhe+(OP)
The thing about lower barriers is that it makes it easier for e.g. Salesforce to raise the level of expectations. And that's the moving target. New employees will come from elsewhere and wonder how a company is operating using tools from 2020 when X, Y, Z are becoming industry standard.

The key here is that the moving target will _never_ be "what can 1-2 people vibe code without any expectation of being the best at what it does?"

(Also: training people on bespoke tools takes much longer than training on configurations of standard tools. Imagine if you had to learn a new source control system at every job, like in the '80s.)