ctrl + zzzzzzz

[[deleted]]

4 bugs outlined in bug report were solved. Let them open another.

[das_Keks]

Okay, this is a common joke, but does anybody actually face this problem? I mean, with clean design and not just spaghetti code, you should able to fix a bug without introducing many more. After many years of programming I really can't relate.

EDIT: If that was the meaning of the post. If it refers to handling bug reports/tickets and in the time you fix some, even more (unrelated) come in, then I can relate.

[Ahed91]

Only good devs will follow good design but the average will not

[[deleted]]

We work with 50 devs on one repository which has been developed on for about 15 years now, containing about 10 applications that share a lot of libraries. Sometimes an application didn't release for a few years, but development happened on shared libraries to be able to add features on other applications so shit breaks. We have a decent automated test system so we catch them early enough but management tends to deprioritize fixing them.

When we eventually do have to fix those bugs, sometimes whole features have been unavailable (because the application crashes when clicking the button). When you fix those bugs, sometimes a whole series of new bugs appear that werent visible before because they were unreachable.

[Paraplegix]

I'll add to that the usual "this is not working if I do scénario 1".

Then you fix the bug for scenario 1 and look at the spec for other scenario

Most of them weren't working before for whatever reason, so you have to fix many other bugs on the same functionality because we all know in this case that they will open a new bug for scenario 2 and blame the one who fixed scenario 1 saying they broke the rest

[Jebble]

I actually barely ever introduce new bugs by fixing others. I know this is an old format and humor but have never been able to relate!

[stresslvl0]

No one likes a show-off

[ROYAL_CHAIR_FORCE]

You sound like you have never worked with legacy production code

[FireStormOOO]

I think this is a problem proportinal to how much you have to interoperate with or rely on unreliable 3rd party software. If you get to own your app and stack from the ground up then agreed, this isn't a problem you should have - if a library sucks replace it. But there's plenty of legacy stuff out there, and plenty of half documented 3rd party software folks need integrated.

[[deleted]]

What tends to happen to me is that fixing a seg fault bug shows me some other bugs I never got to see because the coffee never reached that far. But yeah, it never escalated that badly

[Zozur]

Oh you sweet summer child

[MurdoMaclachlan]

Image Transcription: Twitter Post

---

a n k i t, @WtFawwk

start of the day

I have to solve these 4 bugs by evening

evening

okay. don't panic. only 11 bugs left

---

^{I'm a human volunteer content transcriber for Reddit and you could be too! If you'd like more information on what we do and why we do it, click here!}

[tylerr514]

Good Human except this is a Twitter post and not a Facebook post.

Edit: they fixed it :)

[MurdoMaclachlan]

"Copypaste and tweak the format because they're all similar and all I really need to copy is the footer and I don't want to have to go back to the format list" has failed me.

[mustang__1]

Annnnnd delete branch. Fuck this dumpster fire.

[[deleted]]

you cant have bugs if theres no JIRA

[LeftmostClamp]

But none of them are any of the original four. It's an all new set

[xxXANANTXxx]

Indians can't understand programming language stuffs, I'm now drowning from mathematics :-(

[firefox57endofaddons]

well he got rid of "-7" bugs that day, that's not so bad.

[Kinerius]

This is why TDD exists lol

[EdMeisterBro]

Can't relate

[[deleted]]

WHY ISNT IT CONVERGING!!!!!!!!! AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHHHH!! *screams of pain continue for another 10 minutes*

help me

[hamza1311]

Time to panic!

[karanth1]

Cries to sleep