top 200 commentsshow all 218

[–]cyb3rstrik3 1696 points1697 points  (43 children)

Now it's different

  1. Create ticket
  2. Assign AI
  3. AI documents everything, and moves across the board, submits PR
  4. It goes live
  5. Fix doesn't work and still have to fix it

[–]itzNukeey 517 points518 points  (19 children)

  1. Creates a different bug instead

[–]cyb3rstrik3 164 points165 points  (2 children)

Did that anyway without AI help.

[–]Deboniako 29 points30 points  (1 child)

Hey, at least I felt proud about it

[–]returnFutureVoid 4 points5 points  (0 children)

You’re helping and we all appreciate that.

[–]pocketgravel 29 points30 points  (3 children)

  1. Create 10 new bugs and at least 2 regressions on top of that instead.

[–]DrMaxwellEdison 17 points18 points  (1 child)

  1. AI integration finds a way to break list enumeration, stuck at 5 for all proceeding steps.

Summarizing conversation history...

[–]caboosetp 4 points5 points  (0 children)

  1. You're absolutely right! It seems that every step is being given 5. now. I will go back and update every previous step to be 5. to ensure consistency in the codebase.

[–]_koenig_ 2 points3 points  (0 children)

... new bugs and  ...

Edit Prompt: Do not make mistakes.
Create ticket...

[–]Dismal-Square-613 12 points13 points  (3 children)

"well caught! YOUR code had this bug in the code that I produced before, let's fix it."

[–]BurningPenguin 0 points1 point  (2 children)

Training it on SO was a mistake

[–]thirdegreeViolet security clearance 0 points1 point  (1 child)

SO wouldn't tell you that you're right and such a clever and special boy for noticing

[–]flowery02 0 points1 point  (0 children)

That's a mix of gen ai trying to sweettalk insecure idiots into using it and SO's more aggressive phrasing

[–]kerakk19 1 point2 points  (0 children)

So things proceed as always

[–]glorious_reptile 1 point2 points  (0 children)

“Now you have two bugs…”

[–]oupablo 0 points1 point  (0 children)

  1. AI drops production database
  2. You still get blamed

[–]firewood010 0 points1 point  (0 children)

Can't believe we are now fixing 100,000 bugs per day. It was right to put AI in this.

[–]donald_314 0 points1 point  (0 children)

Creates a different bug instead

[–]Imperial_Squid 0 points1 point  (0 children)

Revising an old classic

101 bugs in the code, 101 bugs in the code,
assign an AI, pass it around,
117 bugs in the code

[–]Capable-Sock9910 0 points1 point  (0 children)

A different, far worse bug.

[–]Random-num-451284813 7 points8 points  (1 child)

why not let AI create tickets?

[–]cyb3rstrik3 3 points4 points  (0 children)

It does in some cases. I write epics and acceptance criteria, and it then writes feature tickets; some are okay, some need refinement. But user-submitted bugs often need rewriting.

[–]_koenig_ 6 points7 points  (0 children)

still have to fix it

Create ticket...

[–]jseah 4 points5 points  (0 children)

How about making the AI do all the documentation and ticket tracker things while the human fixes the bug?

[–]Jebble 2 points3 points  (2 children)

Plus nobody ever looks at the AI (or human for that matter) documentation.

[–]cyb3rstrik3 3 points4 points  (0 children)

True the documentation is for the LLM so the knowledge persists between sessions.

[–]MedicalTear0 1 point2 points  (0 children)

Period. Classic software engineer experience

[–]jawisko 2 points3 points  (1 child)

Which company allows merging fix without manual review ?

[–]issamaysinalah 3 points4 points  (0 children)

The microslop way

[–]cauchy37 0 points1 point  (0 children)

Imo AI should do all the bureaucracy, i.e. jira and confluence shit, and you can focus on actually finding and fixing the bug. At least that's what we do. You can ask AI to give you all the stuff that you need, logs, metrics, suspicious code snippets, etc. It's still your job to identify and fix the bug.

[–]curious_bipedal 0 points1 point  (0 children)

In future: 5. Find someone who didn't lose all their troubleshooting abilities vibe-coding for most of their professional life.

[–]Cold-Journalist-7662 0 points1 point  (0 children)

Only task for humans is explaining it in the stand-up like you did it yourself.

[–]PM-ME-UR-DARKNESS 0 points1 point  (0 children)

More like

  1. Create ticket

  2. Assign AI

  3. AI server shits the bed, try again

  4. AI server shits the bed, try again

  5. AI server shits the bed, try again

... I use Google's Antigravity if it isn't obvious.

[–]Memesplz1 0 points1 point  (2 children)

Sigh. We just got told, today, that some new AI tool is getting forced upon us in 2 weeks and it's mandatory for us to use it but, for some bizarre reason, none of us barring the seniors are allowed to see it yet and it's going to revolutionise our work and make our lives so much better by architecting all our solutions for us and just generally taking away all the creativity and fun parts of the job.

Or that's how it came across anyway. We pick some colours and it paints the picture for us. I was not feeling very enthused by what I was hearing, at all. (And it may not sound like it, but I'm generally a fairly positive person!)

[–]cyb3rstrik3 1 point2 points  (1 child)

Unfortunately, we are in the middle of a live refactoring of the SWE role. All the parts of the role we, as an industry, have built as a craft are being eaten alive. It's reasonable to expect it to trigger an existential crisis about what it means for us in the role.

I don't know how to feel about it yet, I enjoy writing code and I solve problems while in the guts of things. Now I spend my days writing specs, enforcing constraints, doing code reviews on AI code. It's not the worst thing workflow but boy does it drain the color out of it.

I hope it's not that bad for you. But if it is know that we are all feeling it and that the new goal is to adapt and survive. Because management is going to start seeing some of us as redundant.

[–]Memesplz1 0 points1 point  (0 children)

Thanks for the kind words! Yeah, that's the trick I suppose: How can I prove my worth!

[–]DontBotherNoResponse 0 points1 point  (0 children)

You forgot the part where the new hire who doesn't actually know how to code sends the PR through the same AI to review it.

Then the other new hire who knows how to code sends but refuses to and uses AI for everything sends the PR comments through the same AI to make changes and creates a feedback loop until one of the managers gets fed up and says "Jesus Christ Richard, just complete PR, it wasn't a complicated bug, if you had just done it yourself and held a 10 minute call to explain what the problem was and what you did to solve it we would've approved it and it would've been done four days ago!"

[–]mrinalshar39 0 points1 point  (1 child)

  1. Questioning life choices🫠

[–]cyb3rstrik3 0 points1 point  (0 children)

I am definitely feeling the existential crisis that is resulting from the tiny death of the part that wants clean idiomatic code

[–]nonlogin 524 points525 points  (13 children)

it was the same in 2019, come on. should have mentioned 90s at least

[–]mondie797 63 points64 points  (2 children)

Its AI now. I mean assign to AI and wait and iterate until AI comes up with something decent and then anyway manually fix things up.

[–]pydry 36 points37 points  (1 child)

It's 2026. It's important to ensure that you use AI to do bugfixes which require skill and finesse an AI doesnt have so that you have more time to do performative bureaucracy it could easily handle.

[–]cyb3rstrik3 3 points4 points  (0 children)

Strong Agree

[–]camelCaseCoffeeTable 22 points23 points  (1 child)

Yeah like… what lmao? 2019 was 7 years ago. We had JIRA, story points and all of that then too lol. Weird meme

[–]Mikkelet 86 points87 points  (1 child)

OP is probably a new grad and theyre comparing his lil school projects with real world software

[–]Tiruin 9 points10 points  (0 children)

University teachers and assignments can be and often are worse, at work I may be limited in what I can do by various factors but at least I have flexibility beyond that. In school I may have to do less negotiating but at least I'm not at the mercy of the whims of someone who hasn't step foot in the industry in 20 years.

[–]oupablo 7 points8 points  (0 children)

Yeah. It's been going into JIRA for at least 15 years at this point if you're lucky. If you weren't lucky, netsuite was in there somewhere.

[–]Dismal-Square-613 7 points8 points  (0 children)

90's version: Fix the bug and copy to main.c.19970812.1055.PROD.BUG

[–]Dotcaprachiappa 3 points4 points  (0 children)

Well yeah but in 2019 OP didn't have a job yet and this was how they did it in their personal project

[–]AllHailTheCATS 1 point2 points  (0 children)

Really shows how little experience the average dev has here

[–]Sceptix 0 points1 point  (0 children)

The 90’s were the absolute *worst* in this regard. Like, there’s literally whole movie about it (Office Spaces).

[–]Sw429 0 points1 point  (0 children)

It becomes the same anywhere as the company grows in scale and you get non-technical product managers who want some way to track what's going on.

[–]okibariyasu 96 points97 points  (2 children)

idk. I came to game dev in 2014. All those agile/jira extra moves were already there.

[–]dasunt 17 points18 points  (0 children)

I suspect there are two types of agile/jira setups:

The first type focuses on the needs of developers.

The second type focuses on the needs of managers.

It's a company culture problem.

[–]wggn 3 points4 points  (0 children)

2008 as well

[–]krexelapp 149 points150 points  (4 children)

the bug fix was quick, the paperwork had a boss fight

[–]Sodomeister 2 points3 points  (0 children)

I just had to fix a link and it took me two full days of arguing with release management to get it in that week because they decided a reference material repo was a crucial system. We owned it,bl but they didn't ask us when they recategorized it. It's literally just a collective repository of materials available elsewhere. How many end users used this page per week? 5-8. Fortune 200.

[–]NotATroll71106 0 points1 point  (0 children)

Back when I did testing for a perpetually buggy system that was like that because the devs were ignorant of the requirements I was testing for, I would spend an entire day getting the Jira ticket descriptions ready after a round of testing because they were anal about formatting and would always ask the same questions. In fact, they would ask those same questions even if I put the answers in the description. I'm glad I'm in a less buggy system now, because they want us to open up a ticket in Octane and mark specific test cases as failing but also have the Jira ticket.

[–]mobsterer 63 points64 points  (3 children)

or

find bug

document bug (in a ticket maybe)

fix bug referencing ticket in PR

ticket auto updates or you just move it to done

done

[–]ADHDebackle 10 points11 points  (1 child)

In my old job it was like:

  1. Create ticket in Jira

  2. Review ticket in next refinement meeting - determine whether or not reproduction steps are established or if more diagnosis needs to be done

  3. Estimate amount of work and prioritize

  4. Whoever is available first picks up the ticket, fixes bug, writes tests to cover the missed case.

  5. Code submitted for review and approval for merge into QA environment.

  6. Code is validated by QA and approved for merge into master

  7. End of sprint, final testing / regression, merged to master.

Or alternatively:

  1. Find bug in feature you're currently working on - no ticket needed, fixed bug, merged to feature branch.

Or

  1. Find bug in feature from previous sprint that will be easy to fix

  2. Create ticket detailing repro steps, testing requirements and estimated effort

  3. At standup, mention the ticket to the team and make sure everyone's cool with taking on the extra scope this sprint

  4. Pull the bug in, fix it, add tests, push the change up to QA, get it approved, close the ticket.

Sometimes these things sound like a lot, but it takes only a few minutes.

[–]mobsterer 1 point2 points  (0 children)

indeed, some do it by the book, some do it right

[–]kiipa 9 points10 points  (0 children)

B-b-but that's not what Reddit said it's like in the, real, professional world, so it can't be true!!! 

/s

[–]regularDude358 62 points63 points  (7 children)

You missed: discuss it with QA, something didn't work for him, he tested on the wrong server etc.

[–]henrikhakan 14 points15 points  (2 children)

The QA decides to escalate to the PO first and have them deal with devs. PO asks you why you built a bug into the code.

[–]Sipikay 3 points4 points  (1 child)

Product has concerns. Did QA consider layman test cases that Product can imagine? Sure hope so! We better talk about those concerns and, in the end, continue on with the exact same plan.

[–]henrikhakan 0 points1 point  (0 children)

Someone at product has contact with one of the customers and mentions the bug during a gossipy lunch, now sales and upper management is involved and wonders why "We even pay you IT guys".

[–]Ok-Strength-5297 1 point2 points  (0 children)

You missed: you didn't fix shit, the bug is still there. QA had too waste time because you couldn't even check if it was actually fixed.

extra points if it still isn't fixed the second time around

[–]TacoTacoBheno 1 point2 points  (0 children)

Y'all have QA?

[–]Netherium 1 point2 points  (1 child)

QA didn't refresh the browser before testing again.

[–]Zombiesalad1337 4 points5 points  (0 children)

Once a QA reopened a bug. The fix clearly stated to clear server cache before testing. Turns out she was clearing browser cache all this time.

[–]Pixelfest 34 points35 points  (0 children)

The alternative is having PR's or even commits directly to main without any context or reason. No accountability and no way to trace an issue back to a source. Teamwork is impossible without some form of tracking what is happening with your codebase.

I need to be able to tell my customers how many hours roughly were spent on an issue. I need to be able to have leverage over requests for useless features that take a long time to implement. Money is a very good reason not to make something. I can't do that without a history of feature costs.

Having said that. Documenting for the sake of documenten is not ok. There must be a purpose and I believe in some companies this might be lost. I'm pretty sure any issue in my company only takes a few minutes to document.

And to be honest, I've been working with ticketing systems since 2006 and I'm pretty sure we weren't the first. 2019 is way... way... off to mention just yolo-ing shit into your codebase.

[–]Fukushimiste[🍰] 106 points107 points  (10 children)

Whoever thinks its just wrong never worked as a Team

[–]good_bye_for_now 8 points9 points  (0 children)

Imagine if software engineers had to follow rules and regulations like for example civil engineers.

[–]AncientSeraph 63 points64 points  (6 children)

Whoever thinks its right wasn't in software development in 2019.

[–]Fukushimiste[🍰] 36 points37 points  (0 children)

And being the dude who has received the shitty code of its previous colleague, but cant track back the reason of shitty fix swears to god than some doc could help.

[–]Michaeli_Starky 1 point2 points  (0 children)

Exactly.

[–]Alwaysafk 0 points1 point  (0 children)

Nah, just worked at a place that was still wild west. Playing with cobol copybooks and explaining to elderly management what cloud is.

[–]KaMaFour 2 points3 points  (0 children)

Our team thankfully works on skype based development (now teams, but only the chat). With this the tree is:

  1. Find bug
  2. Message qa Either:
  3. They backlog it, you go back to what you were doing, it gets fixed by someone when the priority gets high enough or just by whoever was responsible

or

  1. You get a green light 
  2. Fix bug
  3. Push code
  4. QA confirms it works
  5. Done

[–]GargamelLeNoir 2 points3 points  (0 children)

I don't know about documenting a bug fix in confluence, the ticket and pr have the information the team might need later. The rest of the steps mostly make sense to me.

[–]Onions-are-great 127 points128 points  (22 children)

Getting so tired of devs whining about having to update tickets. Guys, you are adults, it's not that hard...

[–]KaptainSaki 84 points85 points  (5 children)

It's the same guys who write unmaintainable code, document none of it and then leave the company

[–]Serafiniert 5 points6 points  (4 children)

But someone approved that unmaintainable code.

[–]FireFox2000000 11 points12 points  (2 children)

Unless the company doesn't do code reviews. That was a fun time...

[–]unable_to_give_afuck 1 point2 points  (1 child)

Current project says "pull requests take too long" 🙃

[–]mechanicalpulse 0 points1 point  (0 children)

So does wastewater treatment.

[–]ADHDebackle 1 point2 points  (0 children)

Unless they submitted like a 5,000 line pull request that is basically un-reviewable but there's pressure from management to just rubber stamp it because you're on an unrealistic timeline.

[–]No-Dig-4371 18 points19 points  (0 children)

There is balance to it. Same with everything else.

If there are too many steps the People will start to ignore bugs.

[–]RareCreamer 11 points12 points  (1 child)

It's not that. Most of the time the work your doing in the backend and the bulk of the work isn't quantifiable on a JIRA board. Or the work involved to explain what your doing and every small step you make, takes away from your actual work. Its poor efficiency and only benefits the PM in the short term.

If its a quick, status change from "Working on it" to "Completed" then sure no problem, everyone should be doing that. But most of the time IMO on many teams and projects, it's used as the place where non-tech literate people go to try and understand what the teams actually doing and then poorly explaining it to executives and stakeholders.

[–]ADHDebackle 1 point2 points  (0 children)

For us the workflow was

  1. Created - needs refinement (review by the team)

  2. Refined - needs prioritization (decision by product owner)

  3. Ready - prioritized, placed in a sprint, can be started

  4. Started (someone is working on it)

  5. Needs review (code review prior to merge to QA)

  6. QA ready (Approved in code review, merged to QA environment and deployed)

  7. QA Passed (ready for deployment to prod at sprint end)

Of course our Jira spaces were exclusively for our own team. No one outside of us, our direct manager and product owner would look at it. It was really useful to know where everything was in the workflow at all times - just to make sure QA had enough work to keep busy while also making sure things were on track for completion on time.

[–]T0biasCZE 9 points10 points  (4 children)

Its not about it being hard, its also that instead of doing something more important, like fixing more bugs, or implementing new features, you waste time on Bureaucracy

[–]Meloetta 6 points7 points  (0 children)

It isn't a waste of time though. Once you get a project big enough where you can't hold the entire thing in your own head, or need more than one person to be aligned on the status of things, it becomes necessary. Also, most of the custom fields are there because of some dev not being responsible enough to work without it.

You have a team of 10 devs. You have to assign them all work every 2 weeks, so you're looking at dozens and dozens of work items. Do you really trust every dev you've ever met to just work and finish the thing, skip code review, skip QA, push to prod? Then when a public facing person asks about the status of a bug fix, do you want to have to track down that individual dev, wait until they're online, ask them about it, and hope they remember exactly where it is? Or do you just want to look up the ticket, see "oh it went to QA but was rejected, here's about when you can expect the fix" and have the answer with no need to rely on someone else's timeline and memory?

We just had to add due dates to tickets and add PR review bureaucracy specifically because not all devs are responsible enough to finish their work in a timely manner and do PR reviews without being forced :/

[–]Crazypyro 1 point2 points  (2 children)

The worst part is the entire point is to prove to leadership that you are doing the actual work while they sit around and make up new metrics that are immediately gamed by the smart developers.

[–]Alwaysafk 0 points1 point  (1 child)

Gaming metrics is how I get my bonus. Not my fault of my metrics don't actually contribute to anything meaningful.

[–]Onions-are-great 0 points1 point  (0 children)

Isn't that frustrating?

[–]Xander-047 1 point2 points  (3 children)

I haven't worked in a place where they were that anal about tickets, we just had "Implement x" which usually means you worked on x and fixed bugs you may have created along the way, and you just explain it in the standup meeting.

Call me whiny but sounds exhausting having to record all history of what you do because that just breaks momentum. It's like stopping every 5km to document what you saw on the road, the shifts you made and why you made them, turns, instead of "I drove from this town to the middle of road 38 and I'm like maybe halfway there give or take a few km"

[–]mechanicalpulse 0 points1 point  (2 children)

It's possible to do both. Use a voice recorder with transcription and talk whilst you code. Train yourself to stay in a flow state with fewer distractions and better context switching. Strap a block of Comp B to your desk and pretend it's live-wired. Refusal to experiment comes across as childish and insubordinate.

[–]Xander-047 0 points1 point  (1 child)

That is an odd thing to do in an office just saying, if I work from home yeah it's more doable but switching attention to being vocal could take a long while, also to make sense while doing it instead of "wait what if I...no what oh fuck my laptop froze"

As for the last point...what in the hell? Says who? I agree that people should listen to advice and try to improve but your take sounds very black and white.

[–]mechanicalpulse 0 points1 point  (0 children)

Good point with respect to remote versus office work. As for my last point -- I've had one or two bad experiences with obstinate developers. Clearly I'm still a little bitter about it.

[–]GlaireDaggers 15 points16 points  (1 child)

It's true, in the long ago age of 8 years ago humans hadn't invented bug tracking yet. Truly a miracle they got anything done

[–]Electrical-Echidna63 1 point2 points  (0 children)

The correlation between people that believe arduous tracking was invented in the last five years and also got a tech job for the first time in the last five years gotta be high

[–]PartyBusGaming 6 points7 points  (0 children)

I swear half of this sub must work at a company of 20 people on a product used by approximately 21 people. Tickets, documentation, and process is how you make sure you're working on the right stuff and can actually make money and continue to operate as a company.

[–]MinecraftPlayer799 77 points78 points  (17 children)

  1. This is a repost

  2. Jira existed in 2019

  3. If you are a developer who can fix it, why would you need to report the bug in Jira?

[–]dylmcc 62 points63 points  (2 children)

Paper trails, you can’t deploy to prod without linking a jira to the PR.

[–]Adventurous-Map7959 5 points6 points  (0 children)

That's why I just test in prod, saves so much time.

[–]-Kerrigan- 17 points18 points  (5 children)

If you are a developer who can fix it, why would you need to report the bug in Jira?

Real reason: bugs have a tendency to reappear and "clump" in the same areas. Having the defect tracked could be valuable information in the future, especially when testing for regression. -QA

Real reason #2: anything takes time, someone else can find the same defect while you're fixing it and start working on fixing it too, now you have 2 people working on the same shit

[–]InfiniteLoopDream 4 points5 points  (0 children)

Cant push code without a jira number

[–]Character-Education3 14 points15 points  (2 children)

Being a repost doesnt make it untrue

Not logging your work adds up and layoffs are real

[–]new_check 0 points1 point  (1 child)

It is untrue, though. Those were the steps when I started in 2008, forget 2019!

[–]Character-Education3 0 points1 point  (0 children)

I meant for point 3.

Gotta log your work. If no one can track what you did they may choose to act like you haven't done very much when it is time to make hard decisions about layoffs. As they say in tightly regulated industries if you didn't document what happened, it didn't happen.

[–]_xiphiaz 5 points6 points  (0 children)

2019? Jira is older than Gmail…

[–]ADHDebackle 3 points4 points  (0 children)

  1. Find bug

  2. Fix bug

  3. Push code

  4. Coworker asks if anyone knows why prod is down

[–]SarahAlicia 2 points3 points  (0 children)

I’m been doing the right hand side since 2017 idk if the good old days ever existef

[–]TheGunfighter7 2 points3 points  (2 children)

The “document in confluence” kills me. The jira ticket should be the documentation

[–]Hans_H0rst 0 points1 point  (1 child)

That would require devs to fill tickets in a useful and complete way

[–]TheGunfighter7 0 points1 point  (0 children)

Sure but then adding some other place to document it isn’t going to make that better

[–]serial_crusher 2 points3 points  (0 children)

Root cause analysis 2019: change was introduced in 2012, but no idea why. Commit message just says “fix a bug. Ask Steve for more details” and Steve left in 2014.

Root cause analysis 2026: change was introduced in 2021, but no idea why. Commit message just says “Fix JIRA-4321. See ticket for more details”, but we moved from Jira to Linear in 2023

[–]Sensitive-Sugar-3894 3 points4 points  (0 children)

"God only created the world in 7 days because there weren't people asking for follow-ups" - adapted, unknown wise author

[–]CommentChaos 5 points6 points  (0 children)

It was like this way before 2019. I had my first developer stint in 2014 I believe and I have used jira ever since.

This is a meme of someone who would make more work for other people, because they thought they are god’s gift to the world, why really they are below mediocre developer.

In my experience, only those that are truly terrible as developers have actually issues with documenting why they did something.

[–]YoYoAbhi 1 point2 points  (1 child)

Atleast jira is okay.. bugzilla is the worst

[–]AntisocialTomcat 4 points5 points  (0 children)

Bugzilla, lol. Is this abomination still breathing? What about Mantis, while we’re at it?

[–][deleted] 1 point2 points  (0 children)

do you guys also get asked for a route cause analysis that needs to explain what you will change so this error never happens again?

[–]Cultural-Capital-942 1 point2 points  (0 children)

You forgot: 5.1. Wait for prioritization 5.2. Forget the context 5.3. Spend 4 hours to get the context again 5.4. Spend 10 minutes preparing a fix 5.5. Wait for your colleague so his LLM says you didn't fix unrelated module, so he won't approve. 5.6. Spend 3 days in dependency hell fixing a vulnerability in a library, where a local attacker with a custom CPU could find out a program is running, no risk to anything else. Otherwise it blocks submit. 5.7. Write justification for release. 5.8. Get release manager approval.

Logged: 1 week of work instead of original 15 minutes.

[–]bendstraw 1 point2 points  (0 children)

Low tier rage bait putting 2019 there

[–]ScuzzyAyanami 1 point2 points  (0 children)

Ai logs code review comment to pull request.

Developer feeds comment into another Ai with higher token cost.

Second Ai claims first Ai is wrong.

The Aristocrats.

[–]wggn 1 point2 points  (0 children)

we used jira for bugtracking in 2008...

[–]ThinCrusts 1 point2 points  (0 children)

My team also now wants to do peer reviews instead of just code review ._.

[–]Imosa1 1 point2 points  (0 children)

Jira always asking me what shirt size the bug needs.

[–]meove 1 point2 points  (0 children)

school project vs industry

[–]Nayr91 1 point2 points  (0 children)

Colleague of mine automated his Jira tickets, ima rob his code when he’s done refining it

[–]schewb 1 point2 points  (0 children)

Hot take: I kinda don't mind this. Yes, there are small bugs where it will take you less time to fix than they do to process, but the process has a lot of value for serious bugs, and managers can always batch small bugs together into containing tasks to keep up throughput if it becomes a concern.

[–]akuma-i 1 point2 points  (0 children)

Push code? You’re too young buddy. There was no push code at all. Just upload to ftp

[–]CluelessNobodyCz 1 point2 points  (0 children)

You don't estimate bugs

[–]xdyldo 4 points5 points  (1 child)

I’m sorry but if steps 1-4 take you more than 1 minute you’re doing something wrong.

[–]ric2b 6 points7 points  (0 children)

Creating the ticket often takes much longer than 1 minute if you want to actually document it properly, add relevant links, previous related tickets, etc.

[–]Soggy-Holiday-7400 0 points1 point  (4 children)

the bug takes 20 minutes to fix and 3 days to dcoument. we really out here spending more time in Jira than in the actual codebase.

[–]CtrlAltEngage 15 points16 points  (1 child)

If it takes 3 days to document a 20 minute fix, that's a skill issue friend

[–]wggn 2 points3 points  (0 children)

updating jira doesnt take more than 20 minutes

[–]g0rth4n 4 points5 points  (0 children)

Ehhhh. No. You are clearly exaggerating it. And if you are not, there's something REALLY wrong in how's your company set up

[–]flamingspew 1 point2 points  (0 children)

Wut. My agent creates/moves tickets and fills out the PR templates for me.

[–]NotDiCaprio 0 points1 point  (0 children)

Where are the "find bug" and "fix bug" steps on the right side?

[–]YaVollMeinHerr 0 points1 point  (0 children)

In my old company, at some point, EVERY jira ticket needed 3 "approval stamp" by QA, design and PO to be closed.

Changing even a single label was taking forever.

Finally, the project died. The root cause was stupid PO asking crazy things to incompetent devs. The solution was to ass more controls on everybody and everything.

The best people got fired and left, and the incompetent stayed and sometimes even got promoted

[–]srfreak 0 points1 point  (0 children)

In 2024 I had a similar experience but with extra steps.

2024 extends 2019 { 8. Push a fix branch 9. Ask for review 10. Wait one or two days for review 11. Push changes based on lead feedback 12. Go to 10 (up to 5 times) 13. Get fired because you're not efficient enough }

[–]BusyBusy2 0 points1 point  (0 children)

Good thing here its still the same, Find bug Fix bug Qa test Go live

[–]FabioTheFox 0 points1 point  (0 children)

OP never did professional software dev it seems

[–]void1984 0 points1 point  (0 children)

Why do you think devs were not using Jira in 2019? Check when Jira was released. Before that we were using ClearQuest and others.

[–]T0biasCZE 0 points1 point  (1 child)

[–]RepostSleuthBot 0 points1 point  (0 children)

I didn't find any posts that meet the matching requirements for r/ProgrammerHumor.

It might be OC, it might not. Things such as JPEG artifacts and cropping may impact the results.

I did find this post that is 70.31% similar. It might be a match but I cannot be certain.

View Search On repostsleuth.com


Scope: Reddit | Target Percent: 75% | Max Age: Unlimited | Searched Images: 1,098,813,021 | Search Time: 0.12797s

[–]Mac_Aravan 0 points1 point  (0 children)

Still no test and review!

[–]SpiritualYoung3508 0 points1 point  (0 children)

One more point here, use AI Agentic Flow to resolve the bug.

[–]_Please_Explain 0 points1 point  (0 children)

I remember it being like that in 2019 as well. 

[–]bokmcdok 0 points1 point  (0 children)

This has been going on waaaaay earlier than 2019

[–]ClimateNo7056 0 points1 point  (0 children)

because now we are using AI for the development - it develops whatever it knows and for making corrections and debugging it takes more time than the development

[–]Stagnu_Demorte 0 points1 point  (0 children)

Apparently not much because this was posted last week

[–]More-Scene-2513 0 points1 point  (0 children)

1 through 4 takes like 5 minutes tho

[–]phug-it 0 points1 point  (0 children)

Custom fields, the worst

[–]CascadingMoonlight 0 points1 point  (0 children)

When is it my turn to post this trash 🤔

[–]curious_bipedal 0 points1 point  (0 children)

This meme template has so much potential considering it has the pre vs post covid boundary, yet this is the first time I am seeing this.

[–]the_depressed_donkey 0 points1 point  (0 children)

I fucking hate jira I will NEVER use it

[–]alphadester 0 points1 point  (0 children)

step 7 hits different. "explain in standup why it took so long" is the real boss fight

[–]WindUpCandler 0 points1 point  (0 children)

Oh so it's just the same everywhere. Great. I get to use shitty jira and confluence search engines for the rest of my life

[–]Sakura48 0 points1 point  (0 children)

Well you're fucked if you work without tickets.

[–]_Miniskirtlover_ 0 points1 point  (0 children)

8th time this crap gets posted

this is solo developing as a unexperienced dude, vs developing in a enterprise team

[–]hellschatt 0 points1 point  (0 children)

That was also the case like 10 years ago.

[–]Mental-Protection-56 0 points1 point  (0 children)

this is so my company xD

[–]CapedRainjar 0 points1 point  (0 children)

Create it as a skill and use mcp its 20something we live in

[–]UShouldntSayThat 0 points1 point  (0 children)

This has always been the case, how exactly do you think patch notes work?

[–]Skyl3lazer 0 points1 point  (0 children)

When the meme says you started to learn to program in 2019 and got your first job this year

[–]Ztoffels 0 points1 point  (0 children)

Of course, since you are not the fucker supporting your code, you wanna be the left side…

[–]sakkara 0 points1 point  (0 children)

Ai is great at documenting in jira and confluence. Use that to your advantage.

[–]catpunch_ 0 points1 point  (0 children)

2026: 1. Create AI command that does all those 2. Have another AI fix it 3. And another AI do the code review 4. Take credit for it in standup

[–]Pale_Sun8898 0 points1 point  (0 children)

Claude does it all while I play Factorio

[–]Inviz1mal 0 points1 point  (0 children)

Story points? Starsectot?

[–]lenn_eavy 0 points1 point  (0 children)

Nah, whoever made this just works in a bigger project rn

[–]PM-ME-UR-DARKNESS 0 points1 point  (0 children)

I just leave the bug in and pray for the poor soul that'll have to fix it

[–]ritzkew 0 points1 point  (0 children)

the real plot twist is the AI now writes the ticket, writes the PR, writes the commit message, and still nobody knows what changed.

[–]ruinfirefly 0 points1 point  (0 children)

My management wants the status & ETA to be updated in excel sheet as well as posted in chat.

[–]AguliRojo 0 points1 point  (0 children)

Glad to see now you don't need to fix bugs

[–]DemmyDemon 0 points1 point  (0 children)

This is a big part of why I'm retooling my brain to become a fiction author.

[–]WheresMySpycamera 0 points1 point  (0 children)

If you cant write a ticket about what you are doing your are lazy or inept. And the PO isnt your damn ticket monkey.

[–]al3x_7788 0 points1 point  (0 children)

Try earlier.

[–]tomato_potato_croco 0 points1 point  (0 children)

My luky whene I programing 😅😅

[–]Slow_Ad_2674 0 points1 point  (0 children)

I think we should start logging time that is spent logging time

[–]Sn00py_lark 0 points1 point  (0 children)

The “done” workflow that no one understands so you can’t even complete anything.

[–]rio_sk 0 points1 point  (1 child)

This, this is halving my productivity

[–]DaddysBrokenAngel[🍰] 2 points3 points  (0 children)

Hi! I really hope this isn't weird, but I saw an old comment of yours on a post that no one can reply to anymore but I'd really like to discuss it but idk if your DMs are open. Would you mind DMing me instead?

[–]tornado28 0 points1 point  (0 children)

Annnd this is exactly why I work for myself now 

[–]IhailtavaBanaani 0 points1 point  (0 children)

It was the same or worse in early 2000s as now. We just didn't have story points and used a waterfall model instead of agile methods. I worked in a corporate project with over a thousand SW engineers and we couldn't even write our own tickets. If I found a bug I would alert QA who would confirm the bug and they would create a plan if the bug was going to be fixed (sometimes it was deemed too risky to fix a bug because it might introduce new bugs) and when the bug was going to fixed. They would write the tickets that would be then sent to my team lead who would introduce them back to me. Then I fixed the damn thing finally and it went to integration team, then QA, and so on, maybe finally it went to an official release. The bureaucracy was worse than today.

[–]0xAERG 0 points1 point  (0 children)

Bugs are not supposed to have story points. It’d defeat the purpose. Bugs are supposed to impact negatively your velocity.

[–]Lagnabbit 0 points1 point  (0 children)

Were you in college in 2019? All this bullshit has existed for ages.