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.
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.