563
When happy teams are an issue
(programming.dev)
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 21 Sep 2024
563 points (98.5% liked)
Programmer Humor
19214 readers
1141 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
I absolutely love how this implies that the team is happy before going to Jira.
so not only can Atlassian not write software, they can't develop a usable product, and they can't even market it without insinuating how shitty it is.
I read "happy ___ starts with ___" as stating that happiness was the eventual result of a process that started with ___.
Yes, like most normal people do.
There's a lot of discussion when you're a software dev about the best way to do things, and a lot more is spent on this debate than on actually writing code. One could wonder if there is so much discussion because there are so many good ideas that it's difficult to choose the one that is optimal for the situation.
But then you read one of these posts on lemmy and you are reminded that someone with internet access and thumbs could spare the short time they have to take a shit to egregiously misunderstand a simple fucking slogan, smugly post about their shit take on the internet, and then return to their job where they will then spend hours misunderstanding the simplest of fucking concepts, slowing down everyone else along with them.
Jira is great software if you ignore all the insufferable bugs in it that Atlassian ignores just to make their on-prem option so clunky you have no choice but to use their SAAS offering. I know, I know, "ThEy DrOpPeD sUpPoRt AlReAdY!"
ever had to rebuild a sprint because Jira failed to properly migrate the old cards over to the new one, but instead throws them all into the backlog randomly and now you have to hunt them down over the next hour?
how about when you're writing an update to a card and you're two paragraphs in with log examples and the UI decides to dump your entire content when you accidentally click outside the wysisyg?
But how can I forget the worst one! have you ever had your session timeout while you're writing a detailed bug report with screenshots, logs, and example data, and when you finally submit it you lose EVERYTHING because you need to login again and you can't go back?
I have, and you know what, I'll still use Jira because even the best trash can be better than the worst trash.
yeah, I'll take a fat dump on shitty products all day long because the negligence of Atlassian product development is abhorrent and deserves to be called out.
No, never. Did you maybe not select the ‘move to new sprint’ option when closing the old one?
That has never happened to me, either.
congrats, you've had a far better experience than I have. just because you haven't had the joys of experiencing Jira in its true form doesn't negate the atrocious UX many others have. if Jira was the perfect product that you claim, then why is there so much vitrol and hate for the product at all?
I started my career as a big supporter of Jira. It made the work so easy to manage and report on. then sometime in 2020 an update came through that absolutely shit on my already over-burdened workload.
I used to deal with the sprint problem every kickoff, and yes I did select migrate to new sprint. no it doesn't work when the process breaks in the middle and doesn't recover or rollback. now I don't handle kickoff, so not my problem anymore but I witness it happen literally every kickoff.
I also used to deal with the WYSIWYG issue daily. now I don't post updates to cards outside of one-liners like "check the logs at this time" or "fixed upstream in xy branch".
I get why people share their hate online because misery loves company, but I just don't get why anyone would waste so much effort on defending it. example; I use spaces over tabs. lots of hate either way online. never have I defended or argued over one vs the other. it's a preference much like Jira. forced to use it at work and have to make the best of it.
so, why be a white knight for Atlassian if you're not employed by them? and if you are employed by them, why be so dismissive about the issues brought up?
I've often wondered if Atlassian even uses the products they sell. There's just so many stupid bugs that I would assume no one at Atlassian would put up with if they had to eat their own dog food. Instead, those bugs don't seem to get fixed and seem to linger in their products forever.