309
Why I always keep doing it... (thelemmy.club)
submitted 5 months ago by to c/programmerhumor@lemmy.ml
26 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 5 months ago (4 children)

We seemingly have a different opinion, what we regard as 'fun' ;⁠-⁠)

Stuff that can't be reproduced and "only" comes up because of some timing issue/race condition is often the most shit to hunt for

I'm currently in such an adventure - and I thought I had it...but the statistics show, that it only got better, but didn't catch all of the occurrences...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 6 points 5 months ago (3 children)

    Stuff that can’t be reproduced and “only” comes up because of some timing issue/race condition is often the most shit to hunt for

    Ah, but if you can't reproduce it, you can just put in an entry of 'could not reproduce' and close the bug report. Case closed. Go home and enjoy a nice beverage.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 5 months ago (2 children)

    Tell me that you have never worked on anything even remotely ”mission critical" without actually saying it...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 5 months ago (1 child)

    I've worked on "mission critical" things, but that doesn't mean I gave a shit about the "mission". If I'm working for minimum pay, I'm putting in minimum effort. Which means closing the bug report faster and with less effort is always desirable.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 5 months ago

    I agree with that. The only caveat I have is that if you are a junior, entry level, or even just an underpaid developer being asked to work on "mission critical" code, then that code is not "mission critical". It is code that management is obligated to provide but gives no real fucks about.

    Much like a bar mitzvah or quinceañera signals the beginning of the transition from childhood to adulthood, there is the junior to senior transition for developers. It often starts with the realization that the most recent in a long line of super critical bugs you are working on has been sitting around untouched for weeks and is only now "critical" because a customer has bitched about it not being fixed. The best part is when you follow the progress of the bug and see that your fix doesn't get touched by anyone for months because there never was an actual customer bitching about it in the first place, it was just some sales person or VP flexing their power because they felt ignored. So the bug got squeezed it into the already over packed production cycle by making it "mission critical" and assigning it to someone too junior to realize that it's bullshit work.

  • permalink
  • fedilink
  • source
  • parent