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
I like to bring up JIRA example. You could replace it in-house yeah it is just tickets with statuses. /s

But then keep in mind one who built the replacement will become the owner of an application that business doesn’t want to pay for and that person will be cost center for the company.

That person better get marketing and negotiating skills that Atlassian has on board because that person will be responsible for the app and will not be getting salary increases for working on something that is not core business of the company.

Even if you can make LLM to do the app for you.

>>ozim+3f1
You guys keep using services like Jira, Salesforce, Stripe, Datadog, etc. While those are definitely the biggest names, I don't think people are referring to those SaaS platforms as the ones they will replace or try to build an inhouse version of. It will be things like ETL pipeline services, data scraping services, maybe some internal analytics SaaS. The niche things that cost a lot because they’re in a sweet spot where only a few people need them, but no one used to have the resources to build them in-house. So, when the salesperson called and offered a perfect solution to their problem, they bought the service. Those are the ones that will be more targeted for in-house solutions.