96
‘Devastating blow’: Atlassian lays off 1,600 workers ahead of AI push
(www.theguardian.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Mar 2026
96 points (99.0% liked)
Technology
42519 readers
199 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 4 years ago
MODERATORS
Totally true, but I’m talking an order of magnitude or two difference…
A query returning ~100 jira tickets would take about 250-300ms on our old beater running Postgres on busted old SAS drives shared with a bunch of other crap. Seek times were atrocious but not catastrophic. It usually didn’t timeout, and only crashed once in a while.
Sunning the same search on jira cloud now takes 2-3 seconds, often even more because the page first has to load 20 MB of JavaScript bullshit. Time from clicking a link to seeing information is so long you’ve got enough time to take a sip and put the coffee down.
Like I get it, distributed systems are hard. And having a multi tenant system as big as they run is probably crazy complicated. But come on, there’s no excuse for that level of consistently bad performance!!