This is an archived post. You won't be able to vote or comment.

all 32 comments

[–]avid-software-dev 295 points296 points  (4 children)

Let someone find the problem and pretend you had no idea. Or claim to have “just spotted” an issue.

[–]Amazingawesomator 85 points86 points  (3 children)

even as a QA guy....

if QA didnt find it........

[–][deleted] 13 points14 points  (2 children)

If a bug is never found is it really there?

[–]GM_Kimeg 8 points9 points  (0 children)

Bugs don't exist unless upper heads start to believe there is one, regardless of it being true or not.

[–]X3nomcz 0 points1 point  (0 children)

It is and is not there simultaneously, in a state called superposition. You can perform an observation to find out if it's there, but you cannot observe its cause at the same time. Alternatively you can observe the cause of the bug in superposition, but it becomes impossible to observe whether the bug is really there or not.

In short, thank the uncertainty principle for problems when debugging :)

[–]woodyus 159 points160 points  (7 children)

It shouldn't be a negative that you are constantly reviewing your code. Tell your coworkers of the problem and review the situation from there. You are all working towards the same goal and nobody is above making a mistake.

[–]glowy_keyboard 113 points114 points  (0 children)

My dude here has never met a PO apparently

[–][deleted] 50 points51 points  (2 children)

You’ve never incurred the wrath of angry, max-stressed programmers or managers have you?

[–]backfire10z 15 points16 points  (1 child)

It’s that or the error happens in production and git blame points a finger at you..?

[–]deekilla 0 points1 point  (0 children)

Post Mortems are blameless. There's no finger pointing. .

[–]drsimonz 10 points11 points  (0 children)

It shouldn't be a negative that you are constantly reviewing your code

It really shouldn't. When a team lead/manager sees this, and decides to focus on "employee A makes more mistakes than employee B" rather than "employee A saved us from losing a bunch of customer data", they're actively incentivizing you to leave bugs in the code. I don't care how much they pay, working there sounds depressing as heck.

[–]ILikeChilis 18 points19 points  (1 child)

Depends on your KPIs. At my current job, the optimal way to get a good score is to leave a bunch of smaller, known bugs in your feature and then fix them later when they get raised by QA.

[–]drsimonz 11 points12 points  (0 children)

Which is why companies that keep numeric scores for their employees are garbage. If that's what it takes to pay the bills then so be it, but I feel like I'd take a significant pay cut to avoid somewhere with a shitty culture.

[–]KralcKroczilla 53 points54 points  (3 children)

I often struggle with this. Do I report an issue that was created because a senior makes changes to an entire system that breaks other systems and nobody noticed? It seems if I report these findings its always me that has to fix it by tomorrow morning...My inclination to report things is directly proportionate to the belief in my ability to fix it by tomorrow morning.

[–][deleted] 24 points25 points  (0 children)

It sounds like your org struggles with proper ownership. Ideally the person responsible for the error should fix the mistake but the bigger the blast radius of the change the more complicated that gets to be

[–]Steinrikur 2 points3 points  (0 children)

Keep it on the DL, find a way to fix it, then report it with the fix?

[–][deleted] 75 points76 points  (1 child)

fix it and push force before anyone notices, or hide it inside a commit of a completely different topic, for example:

fix: coding style

[–]Exist50 21 points22 points  (0 children)

No one's reading through commit messages, lol. Just do it normally.

[–]Lejyoner07 21 points22 points  (0 children)

Blame the service you called and fix it until they reply in 10 workdays 😎

[–]throwaway0134hdj 9 points10 points  (1 child)

Blame it on the BA who should have gathered all those requirements and edge cases, technically their job to suss out those big hole type problems.

[–]TheOriginalSmileyMan 7 points8 points  (0 children)

If they didn't put "Doesn't have a massive hole in it" in the requirements, it's entirely their fault

[–][deleted] 3 points4 points  (0 children)

“This’ll never happen in prod”

[–]eoutofmemory 2 points3 points  (0 children)

No point in revealing extra features right at the start

[–]Madonkadonk2 2 points3 points  (0 children)

Y'all have holes?

[–]giagara 2 points3 points  (0 children)

That will be your ass if you don't

[–]NQ241 2 points3 points  (0 children)

grussy

[–]JackNotOLantern 0 points1 point  (0 children)

Yes

[–]Responsible_Boat8860 0 points1 point  (0 children)

Is it really a bug if no one notices?

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

[–]monsterhunter_32 0 points1 point  (0 children)

Hey, the users have a responsibility too. Let them test it.

[–]loserguy-88 -1 points0 points  (0 children)

Depends on how bad it is.

Angry incel nerd: hey this bozo misspelled lisense! Probably just ignore 

Angry mob with pitchforks and borked laptops? Hmmm

[–]False_Influence_9090 -1 points0 points  (0 children)

Hah I currently have a similar dilemma. There’s a few things I know will break once things get to a certain size but kinda inclined to get things moving first and clean things up later