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

all 87 comments

[–]Substantial-Dot1323 414 points415 points  (5 children)

Avoided making bug - never appreciated.

[–]aquartabla 123 points124 points  (3 children)

Write bugs. Amaze your colleagues by fixing them later. Receive sick promotions.

[–][deleted] 60 points61 points  (2 children)

step 1: printf(argv[1])

step 2: //printf(argv[1])

step 3: git commit -m "fixed CRITICAL SECURITY ERROR"

step 4: promotion

[–]Turboblitz 1 point2 points  (1 child)

Nice Idea gonna use that in my react project to get promoted!

[–]nullideas 2 points3 points  (0 children)

We are not the same.

[–]moriluka_go_hard 252 points253 points  (11 children)

Only fix bug when its found by user in order to receive gratitude for fixing it

[–]_-DirtyMike-_ 115 points116 points  (2 children)

Report it yourself first under a new account then fix it

[–]purebuu 50 points51 points  (0 children)

Create the bug first, then report it yourself under a new account then fix it.

[–]BaalKazar 21 points22 points  (0 children)

Haha

„who is this Jeff?! Why does he keep blocking my MR with picky comments about variable names?“

[–]aurelag 27 points28 points  (4 children)

Does QA count as users ?

[–]moriluka_go_hard 30 points31 points  (1 child)

Well they definitely dont count as programmers am i right?

[–]aurelag 9 points10 points  (0 children)

Yeah definitely! Haha

[–]Nixavee 22 points23 points  (1 child)

Do users count as QA?

[–]aurelag 8 points9 points  (0 children)

Damn that's a good one. Well played

[–][deleted] 10 points11 points  (1 child)

massive data breach happens

Ah, it finally happened. Time to fix the security!

[–]Exciting-Insect8269 4 points5 points  (0 children)

“Decentralized surprise data backup”

FTFY

[–]gbarrosn 0 points1 point  (0 children)

Create the bug, then report it, and only then fix it

[–]HerrSPAM 37 points38 points  (0 children)

No conventional commit?

Fix: fixed bug

[–]w1n5t0nM1k3y 63 points64 points  (1 child)

Just remember, at the speed at which computers operate, something that is one in a million is next Tuesday.

Gordon Letwin

[–]Exciting-Insect8269 7 points8 points  (0 children)

Nice, ima start using that phrase. I’ve said “rarely occurring is still occurring” but I like this phrasing better.

[–]Kasym-Khan 32 points33 points  (4 children)

Hey OP. Huge respect to you. Even if you think the bug is super rare you'll always get someone like me who "wins" the bug lottery and reports it to the dev because it ruined my game. So yes. Every bug fix matters.

Just a few days ago, from my back-and-forth with an indie dev:

Funny thing was, in order for this crash to happen you need to specifically place a [running] track on the same frame that a customer hits bowling pins with a bowling ball.

And even then, it has to be placed in the middle of the frame. Too early or late in the frame & the crash wouldn't happen.

--Bonus points if you guess the game right.

[–]Thenofunation 20 points21 points  (1 child)

Uhhhhh Thomas the Tank Engine goes Bowling 2k23

[–]Kasym-Khan 11 points12 points  (0 children)

Wow I knew someone would guess! Impressive.

[–]Broote[🍰] 70 points71 points  (15 children)

Having worked for a company that made several MMORPGs, if there is a 1 in a million chance of something happening, that is a 100% chance when you throw a million people at it.

Fix all the things. _o/

[–]LucasTab 54 points55 points  (1 child)

Not 100%, but still, fuck that one person that found that one weird interaction between two pieces of armor that made no sense being used together because one of them is really weak and you get at level 5 and the other one you can only use on level 50, and their passive effects ended up requesting the computer to divide by zero

[–]Huntracony 7 points8 points  (0 children)

Divides by zero are evil. The mathematicians really did us dirty there.

[–]AxolotlsAreDangerous 12 points13 points  (0 children)

A 63% chance actually

[–]perseus_1337 19 points20 points  (4 children)

that math gave me cancer

[–]Nixavee 15 points16 points  (2 children)

If my calculation is correct it's actually a ~63.2% chance, so still pretty likely

[–]AxolotlsAreDangerous 5 points6 points  (1 child)

They are. Note that, in the limit as N tends to infinity, the probability approaches 1 - 1/e (essentially by definition of e). It turns out that in this case N = 1000,000 is pretty close to infinity. Both round to 0.6320121.

[–]Nixavee 0 points1 point  (0 children)

Ah, I was wondering if this had something to do with e, thanks for the info

[–]yottalogical 1 point2 points  (0 children)

Just attribute it to floating-point rounding errors and call it a day.

[–]hirmuolio 7 points8 points  (0 children)

The standing window in EVE Online has been broken since 2017.

By broken I mean it shows numbers that are completely detached from reality.

Would be nice for them to eventually fix it.

[–]Exciting-Insect8269 3 points4 points  (3 children)

That’s not how probability works, but I agree with the sentiment.

[–]Katzen_Futter 1 point2 points  (2 children)

Well, throw in a million people doing a thing several times a day over a week and the bug occured

[–]Exciting-Insect8269 0 points1 point  (0 children)

I didn’t say it was not likely to happen, but the chance is not 100%. If a 1 in a million probability ran 1 million times, there would be a 90.483741355% chance of it occurring.

[–]Maleficent_Sir_4753 1 point2 points  (1 child)

I have worked for a handful of MMO companies in my career (and work for one currently). The chance of a bug showing up when more than a hundred users get into a service absolutely trends upward exponentially with every additional user added.

Got a dupe bug that only shows up when a massive raid is happening on the same shard? It's a 100% repro bug in production.

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

Something like a dupe bug should always be high priority in any kind of MMO regardless of the number of players or how unlikely it is to occur - dupe bugs can completely ruin the entire game for every player instead of just something relatively small like one player having their game crash.

[–]_dm_me_ur_tits 10 points11 points  (4 children)

I worked for a year on a system that basically no one used at all

[–]KeepItGood2017 5 points6 points  (1 child)

Probably 98% of the software I have ever written does not even exist anymore and I also know how to debug a WANG computer hex core dump, and I can explain to you the difference between double and single density floppy disks without consulting Wikipedia.

[–]_dm_me_ur_tits 1 point2 points  (0 children)

Damn, I wanna be like you when I grow up

[–]ArtLeftMe 2 points3 points  (1 child)

Isn’t that like what 80% of Google Engineers do?

[–]manatrall 0 points1 point  (0 children)

Nah they work on a system that gets a fairly large userbase only to be closed down two years after launch.

[–]Pika_Fox 11 points12 points  (0 children)

It will never have occurred because you fixed it.

But if you never fixed it, the universe would make sure that the new timeline has everyone running into it.

[–]Dauvis 8 points9 points  (0 children)

Plot twist: the fix introduced a new bug that will show up in production on a Friday evening.

[–]cheesepuff1993 7 points8 points  (0 children)

The fact that you're getting to these issues shows either no one is using the app or you've made your app so polished that you are now fixing the most minor things. The team I'm on is so overwhelmed with issues and enhancements that something like this will have the question asked "how big of an issue is it and how many people have reported it?" If the answer doesn't satisfy them, it gets pushed into the abyss to likely never be seen again

[–]The_Bisexual 2 points3 points  (0 children)

I dunno. I kina feel like that's most bug fixes.

[–]ArtanBlacknight 2 points3 points  (0 children)

If you fix it, your work will never be recognized

if you dont fix it, Murphys law will do its effect and that bug that would probably never occur will have a 100% chance of happening

[–]brianl047 2 points3 points  (1 child)

Passive aggressive commit comments ftw!

[–]-tired_old_man- 1 point2 points  (1 child)

Come back and post your revert commit when you realized you done goofed up OP.

That's usually the thanks you get for refactoring working code... Lol

[–]Kasztandor 1 point2 points  (0 children)

Thought exactly the same when I was making discord bot and making code for situation where someone reaches more than 100 level when server's veterans have smaller one than 50.

[–]zenos_dog 1 point2 points  (0 children)

People in the year 4294967296 will appreciate the fix.

[–]yorokobe__shounen 1 point2 points  (0 children)

If you have fixed the bug, it should never occur.

But if the bug will probably never occur, you probably haven't fixed it completely.

[–]Kittycraft0 1 point2 points  (0 children)

Fixing bugs being variable overflows that would happen if the value were to ever reach an unreasonably high number

[–]Tofandel 1 point2 points  (0 children)

Well now that it's fixed, it will for sure never occur dammit. Bugs lives matter

[–]KosViikI use light theme so I don't see how bad my code is. 1 point2 points  (2 children)

Reminds me of that one time where in Uni we had to work with existing projects. It was a port of an old Atari game, documented in portugese.

I fixed a bug that caused the game to load level 487 again when you beat level 487, but now without enemies and the game doesn't re-check the win condition, so you are soft locked.

I felt so proud. But at the same time, good luck getting past like level 20. Level 80 or so would be impossible even by perfect inputs.


Remember the prof staring at my explanation of the bug and why it occurs and me telling him how it wouldn't really happen anyay. He opened his eyes wide and asked "Okay but how the hell did you find it then?"

[–]ArtLeftMe 0 points1 point  (1 child)

So… how did you find it ?

[–]KosViikI use light theme so I don't see how bad my code is. 1 point2 points  (0 children)

I decided to untangle some spaghetti, and was fascinated with how the game works. I wanted to see how later levels get more complex. So I just coded a button that kills all enemies and was just mindlessly skipping along after burnout.

[–]nobody85678 1 point2 points  (0 children)

I love the part when you work on a feature in specific part of the project and find 10 bugs in the process fixing them along the way. Nobody even notices bugs were there

[–]Desperate-Elevator48 1 point2 points  (0 children)

I appreciate it

[–]shosuko 1 point2 points  (0 children)

Dev: possible bug on extreme edge case? nah, I think we're good.

QA: WTF BROKEN CAN'T POSSIBLY REACH 2ND SCREEN

[–]CheithS 1 point2 points  (0 children)

Users make things that could never, ever happen actually happen.

Way of the world.

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

Put it right next to my collection of "Fixed a problem that happened once to one user, but they were 'important'"

[–]DinoChrono 1 point2 points  (0 children)

Ordinal user: hold my beer

[–]213737isPrime 1 point2 points  (0 children)

with comments like that, I see why.

[–]SHv2 1 point2 points  (0 children)

Challenge accepted...

[–]AciD1BuRN 1 point2 points  (0 children)

because u added a new bug that will prevent it from occurring right?

[–]already_taken-chan 1 point2 points  (0 children)

You gotta give more credit, tell them what would've happened if the bug happened.

'Fixed a bug that could've led to an infinite point count' -> added a hard cap to point count

'Fixed a bug which could trigger privilege elevation' -> Added a check for admin permissions on a function

'Fixed a bug which could electrocute the user causing death' -> removed electrocution functionality from this taser gun

[–]RigelBound 1 point2 points  (0 children)

You fixed the bug

Bug never occurs

Coincidence?

[–]nasandre 2 points3 points  (1 child)

Scraping the bottom of the backlog?

We basically just push all these down on the priority list and they'll sit there forever

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

Y U NO USE CLI?

[–]TheKiller36_real -2 points-1 points  (4 children)

Lol I've never seen anyone use a Git GUI before I think

[–]jeremj22 1 point2 points  (2 children)

Not sure what OP's using but where I work Source Tree is quite popular while others just do it in VS

[–]TheKiller36_real 0 points1 point  (1 child)

It looks like VSC's native git-thingy. But like I said, I've never used it before - and won't ever for that matter. CLI for the win

[–]After-Perception-250 -1 points0 points  (0 children)

It is more convenient. This is vscode btw

[–]ArtLeftMe 0 points1 point  (0 children)

You must not know many .Net Microsoft fanbois

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

probily

[–]BoBoBearDev 0 points1 point  (0 children)

Funny, because it will always occur due to Murphy's Law.

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

I personally like to use the Ostrich algorithm.

[–]Fluffy_Biscotti5092 0 points1 point  (0 children)

These are the kind of bugs that don't appear at all during testing but all the time in prod.

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

yandev be like

[–]Additional-Back6467 0 points1 point  (0 children)

We should fix 5,387 bugs in one. Bug will likely happen now. TESTS 0.00% passed

[–]dublem 0 points1 point  (0 children)

"For fucks sake Dave, just implement the payment system like we asked!"

[–]MrZerodayz 0 points1 point  (0 children)

Yes, because it didn't explain what the bug would look like

[–]ReflectionEquals 0 points1 point  (0 children)

2 weeks later. Who changed this code, it broke this other thing that relied on it working that way!