Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atlassian to cut roughly 1,600 jobs in pivot to AI

reuters.com

Post reply on HN
Print view View original

201–210 of 320 posts

Re: Atlassian to cut roughly 1,600 jobs in pivot to AI

#201

Post by MeetingsBrowser »

NoPicklez wrote: post #191
MeetingsBrowser wrote: post #63

Layoffs because of AI make no sense to me. Imagine you own a company that is paid to deliver packages. You use horses and differentiate by delivering quicker than everyone else. Then cars are invented and everyone starts delivering packages faster. In what world does a healthy growing business react to this by laying off couriers "in a pivot to automotive transportation". Would a healthy business not switch everyone…

In a world where you don't need 10 horses to do the job of 5 cars, because your business doesn't have a market for 10 cars.

Then you are not laying off because of cars. You are laying off because there is no market for what you are selling and you are not able to find new customers.

In other words, the business is not doing well

Re: Atlassian to cut roughly 1,600 jobs in pivot to AI

#202

Post by mekael »

verelo wrote: post #30
piker wrote: post #17

Earlier quoted context omitted.

That would be a stupid reason to fire someone when the jury is still out on the net productivity benefits of using AI to code at scale.

Sure, but would that really surprise you? Edit: that is to say, if you had a % of your workforce avoiding helping you explore a current trend (valuable or not tbd sure), I can see rational arguments around removing them from the team.

If, as a member of the c-suite, I find that a noticeable percentage of my company's workforce isn't "helping to explorer a current trend" then either they know something I don't or I haven't given them the time/methods by which to explore.

The latter is actually the more pertinent item, as I've seen several times that an initiative get rolled out by leadership, some teams have free time to play around and use it, and other teams have so much on their plate that they're barely able to keep their heads above water, let alone take on another experiment. If someone is worried about getting a project knocked out by end of month/quarter/year in order to keep their job, they're not going to mess about.

Now, that's a leadership failure, but it happens more often than not.

Re: Atlassian to cut roughly 1,600 jobs in pivot to AI

#205

Post by marc_g »

telman17 wrote: post #112
Rapzid wrote: post #95

Earlier quoted context omitted.

TBF they have made major improvements, IMHO, to Jira and Confluence over the past few years.

Perhaps I just haven't noticed them, which is unfortunate. I have noticed that I often have to double or triple click to open a ticket on my board. There's no reason for such a core functionality to be that slow.

Same! This nightmare seems to have started recently from what I have experienced. I find myself hard refreshing constantly to get the damn tickets to open.

If anyone from atlassian reads this: please, for the love of god resolve this issue.

Re: Atlassian to cut roughly 1,600 jobs in pivot to AI

#206

Post by grantith »

lousken wrote: post #57
mjfisher wrote: post #35

Can anyone recommend good alternatives to Jira? Things that keep me defaulting to it: - Scales well from simple configuration and workflows to more complex multiboard views/custom fields/layouts per issue type etc - Good OOTB integration with common CI/CD - see PRs, deploys etc from each ticket - Good (adequate?) integration with their wiki in Confluence - JQL for being able to do custom reporting tooling (get me all…

We've switched to Jetbrains Youtrack, it doesn't have as many features, but turns out nobody was using most of them anyway. It's Jira + Confluence bundled together including SSO.

I enjoy youtrack for its simplicity, native markdown support, command pallette, and solid vcs integration. So much bloat and friction with jira.

Re: Atlassian to cut roughly 1,600 jobs in pivot to AI

#207

Post by FireBeyond »

mattdm wrote: post #176
pokstad wrote: post #160

Atlassian is cutting jobs because no new sane company wants to use their products. Confluence was once innovative but now has gone stale. Jira is a nightmare and is most ripe for the AI based replacement. Bitbucket is a neglected product that has lost ground to GitHub and GitLab. The writing has been on the wall for Atlassian for years.

Jira is, uh, not my favorite software (ask my manager), but "AI-based replacement Jira" is the worst AI thing I've heard, and that's saying _a lot_.

If you want to fall in love with Jira, try ServiceNow Agile Development (flick through some screenshots on Google Image Search to feel the pain).

Re: Atlassian to cut roughly 1,600 jobs in pivot to AI

#210

Post by atomicnumber3 »

dragonwriter wrote: post #194
prpl wrote: post #178

Earlier quoted context omitted.

Agile itself is predicated on software being difficult to ship/expensive. It might not make sense to continue (waterfall might be better actually) The real problem is that company decisions will never be made as fast as software can be written (and rewritten) now.

> Agile itself is predicated on software being difficult to ship/expensive. No, the opposite; it is predicated on software being cheap and easy to ship, but hard to correctly anticipate the needs for. > It might not make sense to continue (waterfall might be better actually) Waterfall, not agile, is predicated on software being difficult to ship/expensive.

The vast majority of "AI is changing everything!" takes I read say more about people's fundamental misunderstandings of the software development lifecycle (the real one that companies actually do, not the one that people think they do or what companies say they do) than about anything AI is going to change about software eng.

If anything, their solving the complete wrong problems and being blind to the actual problems is probably a reason AI won't actually result in any real, top-level appreciable gains in shipping speed.

Post reply on HN