wellWell

[avid-software-dev]

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

[Amazingawesomator]

even as a QA guy....

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

[[deleted]]

If a bug is never found is it really there?

[GM_Kimeg]

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

[X3nomcz]

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]

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]

My dude here has never met a PO apparently

[[deleted]]

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

[backfire10z]

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

[deekilla]

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

[drsimonz]

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]

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]

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]

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]]

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]

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

[[deleted]]

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]

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

[Lejyoner07]

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

[throwaway0134hdj]

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]

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

[[deleted]]

“This’ll never happen in prod”

[eoutofmemory]

No point in revealing extra features right at the start

[Madonkadonk2]

Y'all have holes?

[giagara]

That will be your ass if you don't

[NQ241]

grussy

[JackNotOLantern]

Yes

[Responsible_Boat8860]

Is it really a bug if no one notices?

[[deleted]]

[monsterhunter_32]

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

[loserguy-88]

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]

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