This was all possible pre-AI. The reasons that some Saas companies win have nothing to do with how quickly or cheaply code can be written for the Saas.
The stock market is trying to predict that people will vote with their dollars in the future. I’m not quite sure people are really replacing enterprise Saas at large corporations yet. It’s more of a projection.
There is no way you would get anything close to as good as JIRA. Your best bet with that budget would be trying to integrate an existing open source on-prem solution (not sure what that alternative is for JIRA).
Yes, you wouldn't get something near as complicatedas JIRA, but that would be a good thing! Look, it's enterprise software, so I'm sure there's somewhere that needs to have the overcomplicated permissions system otherwise contractors are going to steal everything that isn't bolted down, but most places I've been don't need, and thus don't use most of all of that crap. If the ticket can only go from planned to done by a certain group of users, backed by LDAP... let's just say, I'm not going to miss configuring which group gets which permissions system.
JIRA's the perfect example of disruption, too. Everyone's got their bespoke workflow, and JIRA has to be customizable to suit all of them. Bespoke software just doesn't have to the same way.
It also means your data is one unfortunate coffee spill on the laptop keyboard from being gone forever. Unless you are doing your own cloud backups of your data and syncing it somehow. Which now the vibe coded app is really starting to grow in requirements then. Most people want that just handled for them.
What if you don’t know the problem? That’s kind of the crux of the issue here. You still need an expert operator, and at that point it is just saving some typing, but not even necessarily saving time with all the back and forth.
But those code generators were deterministic (and indeed caused huge headaches if the generated code changed between versions). Seems like a totally different thing.
reply