It's software development. You get your stupid little Jira tickets like little quests and you get to solve them however you see fit. And then they get put on the deployment belt and run through all the checking steps in a satisfyingly rigid way. And then you're done with them and you don't have to think about them ever again. It's the perfect cycle.

[–] SlurpingPus@lemmy.world 6 points 5 hours ago

It's perfect when you know the application inside and out. A completely different story when you get dropped into a project that uses sixteen frameworks and libraries, including widely employed features that are barely documented. You get to do guesswork on whether this pattern is recognised by that library, while your system is constantly swapping under the weight of dozens of browser tabs with the docs and StackOverflows.

[–] devfuuu@lemmy.world 1 points 3 hours ago* (last edited 3 hours ago)

So, it's an adventurer's life from your typical isekai. I see. Makes sense now. Only that the things asked are never clear, change midway, the finish conditions keep being altered, the validation at the end keeps being enforced differently or that 3 weeks later someone will ask about the thing done and you have zero memories of that place. Or that because you did it one time now it will always be pushed onto you, even when you don't want it anymore. All of this while slowly killing you on the inside. Yep. Perfect.

[–] okwhateverdude@lemmy.world 7 points 6 hours ago

You cannot imagine how much must go correctly to end up in such a blessed state. And if the stars do align, enjoy every single one of those ephemeral minutes because inevitably, the PM leaves, there is a re-org, and the PM replacement who never touched jira before and has never delivered software is steering the team one week at a time without spending any time putting in the work to make jira smooth. I hate jira. It is a real skill (read: tolerance for bullshit) to arrange shit so that work is well organized. And it is massively missed when absent.

[–] ThunderComplex@lemmy.today 9 points 6 hours ago (1 children)

You get a JIRA Ticket
“Customer says X doesn’t work”
Try to reproduce the issue
It clearly works
Get to find edge cases and do 10 roundtrips with customer

Many such cases

[–] Zarobi@aussie.zone 5 points 5 hours ago (1 children)

Or, JIRA ticket: complete the entire 18 month project

[–] ThunderComplex@lemmy.today 1 points 2 hours ago

Honestly I don't mind this one that much. IFF it is well designed, the entire team is in the loop of what's to be done, and you don't get immediate unrealistic time pressure.
I've always preferred working on JIRA tickets that were meatier than having to work on 15 different tickets in one day. The context switch just eats a bit too much energy for me every time.

[–] zout@fedia.io 13 points 9 hours ago (1 children)

Your mentioning of Jira alone gives me the shivers. For some project I had to use it, and it sends you like a hundred emails a week.

[–] fraksken@infosec.pub 17 points 9 hours ago (1 children)

That's easy, just filter them away in a separate folder and never look at them

[–] zout@fedia.io 6 points 9 hours ago

Yeah I know, but why do I have to jump through a hoop to get a normal user experience?

[–] Walop@sopuli.xyz 9 points 8 hours ago (2 children)

I wish it was like this. But instead were getting tickets with barely a title. Or there's a report that the application misbehaves ones or twice per month with no reproduction steps, fix it. Or the delivery schedule is set, but there are no feature roadmap or milestones to track what is yet to be done and if we are on track. Or the project manager has got their position because they sucked at coding and the company couldn't figure out what else to do with them and you have to keep explaining basic technical decisions over and over to them. And everything will come back haunting you as long as you are in the company. One ticket keeps being resurrected for you because client keeps changing their mind on how it should work or keeps finding more esoteric edge cases. Or you're roped in to some legacy project over and over again, because you managed to do a minor fix for it two years ago and you're the only one left who has ever touched it.

[–] qevlarr@lemmy.world 3 points 5 hours ago* (last edited 5 hours ago)

I'm a manager with an engineering background, and this is exactly what good managers should solve for you. I love Jira but I know it sucks to configure correctly. Your problems are not because of Jira, but managers fucking up the process. But more than Jira (love it or hate it), this is about organization: People don't know how to do their jobs correctly, decisions not being made by the right people or the right time (or not at all), too much planning and not enough execution or vice versa, people not empowered to say no, all that stuff. Everybody always hates on management but it's a thankless and tough job to keep the whole operation running smoothly. It's like that old IT joke "everything is working already, what do I pay you for? vs nothing is working, what do I pay you for?"

[–] okwhateverdude@lemmy.world 2 points 6 hours ago

The curse of competence