[NwtnsMthd]

That last sentence holds a lot of truth.

Our company has drastically downsized its dependence on Atlassian in the past month, we will be completely free in a few more. With the help of modern AI tools we've been able to replace their products with internal tools that are better tailored to our needs.

[jorvi]

Still feels weirdly inefficient.

Why have every company vibe code their own semi-good bespoke tool when instead one company can handcraft the tool with optimisations much better than AI can ever dream of, and then sell that tool for a reasonable enough markup that the value proposition is big enough. Especially if the tool is open source open core, so companies can PR improvements they think will be broadly applicable.

[intexpress]

> one company can handcraft the tool with optimisations much better than AI can ever dream of

You have never used an Atlassian product

[hedora]

I last used Atlassian stuff about a decade ago.

Did they ever get around to fixing basic bugs like "Jira and Confluence use different markdown dialects"?

They've had a decade to address those sorts of obvious problems that bite 100% of the end users of their stuff, and apparently employed over 1600 people during that decade. That's 160 centuries of person time. I wonder what it was wasted on, if not making their fairly small core product suite usable.

I think we're going to see more and more incumbent companies with big moats and terrible products get replaced with vibe coded solutions over the next year or two.

[bombcar]

No, they simplified it by cancelling almost all non-cloud instances and moved to being a direct per-seat SaaS, with (apparently) all the same bugs but fewer features.

[Zigurd]

I was talking to people I know about this topic and looking for obvious big success stories of vibecoding replacing enterprise tools like Atlassian I found they are very hard to find. At this stage I have no doubt that there are IT departments trying to displace SaaS products and re-engineer legacy systems, but it's probably too early to measure results.

[habinero]

And you're not likely to see any either, frankly, because you buy SaaS when you don't want to DIY.

It's easy to think of DIY software as "free" because you don't pay seat licenses, but DIY is expensive like a free yacht is expensive. It's a bottomless pit of money and time and upkeep.

Even if it's simple to implement, you still have to support it, update it, get people to use it, be on call if it tips over, teach people to use it, be forced to take it over when the person who wrote it leaves, etc, etc, etc

IT is a cost center and isn't staffed at the level of your revenue generator eng teams. You don't buy SaaS because you don't have other options, you buy SaaS to throw money at a vendor to take care of a problem for you, so your IT people can do the work you actually want them to do and not dick around rebuilding software that you already have.

[Smar]

If a thrown-together-quickly-with-left-foot tool is more or less as good as Atlassian's products, I wonder why they have been used in first place. Surely it can't be quality of the products. Nor price, as there are existing (even open source) alternatives that do the job well enough.

[fred_is_fred]

I think any company with some motivated developers and a budget for h/w or cloud could rebuild a good enough JIRA in a month. I don't see how Atlassian survives long term

[ebiester]

Because you see the IC side of the Atlassian toolkit. The management side is much more expansive and this starts mattering when you are coordinating larger projects.

That said, if you are a smaller company, you absolutely could kill Jira pretty quick.

[bombcar]

Jira isn't the product, it's the development platform that builds the product (which is a codified version of all the bad business decisions your company has ever made).

[habinero]

I hate Jira just as much the next engineer, but this is not at all accurate lol. The reason all ticketing systems are kind of terrible is they have to deal with a lot of complexity. Jira has waaayyyyy more features than you think it does.

Ticketing systems are not dumb CRUD apps, they're systems that build workflow engines. If you've never built a workflow engine, they're annoying but fine. Building an engine that can implement any special snowflake flavor of business workflow in a way that's reasonable with a reasonable UI is difficult.

And yes, you could write it for your special use case, but use cases change a lot and different groups need different use cases and the time you spend dicking around on building ticketing software that already exists is time you're not spending on shipping, and at the end of the day Jira is like $15/seat at sticker price, why are you bothering?

And that's why Jira is both terrible and still popular.