A rare bug appeared. It was my duty to finish it.

SH = Manager

SH: So when do you think you can finish the task?
Me: I still have to analyze the problem. Give me a moment and I'll get back to you.
SH: Alright.

*An hour later*

SH: *Approaches my desk* Have you found the source of the problem?
Me: Not yet. Please give me some more time.
SH: Ok.

*An hour later*

SH: *the approach* You found it yet?
Me: Yes, I've found the the source of the problem, But... *explains the problem and thus concluding that it's a complicated bug*
SH: Can you finish it by tomorrow?
Me: I'll do the best I can but I am not entirely sure if I can finish it by tomorrow.
SH: OK great!

*The next day*

SH: *Le approach* Hey I have a colleague here that may be able to solve the problem, he has skills with XYZ. Ok, I will leave you two at it then. *the leave*
Helper: So can you tell me about the issue here?
Me: *explains the bug and the source of the problem*
Helper: Have you tried solution A?
Me: Yes sir, but it yields a different output... *explains what happened with solution A*
Helper: Well, that won't work. What about solution B?
Me: I've tried that, too. *Another lengthy explanation*
Helper: Welp, ok. I'll get back to you on that.

(...But he never came.)

*A few hours later*

SH: *A.P.P.R.O.A.C.H.* Hey I have this team lead from another department. I think he can help you out on this one. *L.E.A.V.E.*
Helper 2: What seems to be the problem?
Me: *Explains again with all the solutions I tried but failed*
Helper 2: Wow. That really seems to be a complicated problem.
~~
Me (In my head): -_-
~~
Helper 2: Listen, I need to get back to my team. I'll keep you posted if I happen to find a solution for your problem alright?
Me: Alright thanks.

*Towards the end of the day*

SH: *APPROACHHHH* Have you resolved the bug yet?
~~
Me (In my head): You made me spend half the FUCKING day explaining to these people who didn't even give a piece of FUCKING SHIT to contribute to the problem and you are asking me if I am done with this FUCKING BUG? FUCK YOU, YOU SON OF A -
~~
Me: No, it is not finished yet..
SH: You have to finish this because we don't have tomorrow.
~~
Me (In my head): SHDIFHWISGSIFGSISBAUDBEIQBDIWGFIEBWIDHWIQBDOSBCISBDOSHDIAGSUSVDIFBDKDJWIQKDBDIDGSUWVDIABDIXBSIDBDIDBWUWGUSVDUWVDJQBDUDVWISHDUWVFG
~~

I went home for the day.

When you find a bug in your code...😭

How everyone uses stackoverflow:
1. Work on some project
2. Spot a bug
3. Try to solve the bug and fail.
4. Write a question for SO.
5. Post question on SO.
6. Get the answer and some points.

How I use stackoverflow:
1. Work on some project
2. Find a bug
3. Try to fix the bug and fail
4. Write a question on SO
5. Get scared that I might be downvoted.
6. Spend 45 minutes optimizing the structure of the question.
7. Try additional tests to cover all possible scenarios.
8. Still scared to click post.
9. Scrap everything and restart line by line writing further details of each step in your question.
10. Find the bug myself.
11. Click cancel on the question that took me 3+ hours to write.
12. Cry.

Introducing avatar pets & a new way to unlock avatar items! Pets include cats, dogs, birds and tigers. We know getting all those ++'s can take some time, so while all avatar items are just as reachable for free by earning ++'s from rants and comments, we now allow items to be purchased in-app based on the difference in ++'s you have to the ++ unlock value of the item. (To purchase, you'll need the latest app version)

Paying for avatar items helps us keep the devRant servers up and running and also is extra motivation to add more fun avatar items. If you have any questions or find a bug, please let me or @dfox know. Happy ranting!

Mail from client: There is a bug in project.
Me: mmmmkay where is it?
Client: How shitty developer you are! You should find it.
Me:f*ck you i'm out

1 - Programmer produces code he believes is bug-free.

2 - Product is tested. 20 bugs are found.

3- Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren’t really bugs.

4 - Testing department finds that five of the fixes didn’t work and discovers 15 new bugs.

5 - Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.

6 - Users find 137 new bugs.

7 - Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.

8 - Entire testing department gets fired.

9 - Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.

10 - New CEO is brought in by board of directors. He raises the programming team's salary to redo the program from scratch.

11 - Programmer produces code he believes is bug-free.

12 - fml

When I find a bug that I made

Exp. that made me doubt my skills?

My non programming sister managed to find a bug I was looking for...

I couldn't find the problem for hours and she just looks at the screen and goes "That looks odd!"

4 years ago I was placed on probation for not having the special format in source control check in comments. When I asked, the 'special format' was
clearly documented on page 18, sub-section 4, sub-paragraph 2, "All check in comments will include the solution name, separated by a colon,
and why the code was changed." My check-in comment was only missing the colon. Indecently, over 80% of the other comments consisted of 'adsf',
'bug fix', and several 'BOOM!'s. So I mistakenly said out loud 'This check-in policy appears only to exist to allow management to cherry pick
developers they do not like, find something wrong, and put them on probation.' That comment got on a 30-day ‘corrective action plan’ for openly disagreeing with a
company policy. Today, all those managers were either fired or quit and now I set policy. Dear Mr. ex-Bosses, I won.

That time when you search for a bug and find same question at StackOverflow, GitHub and Quora...

All from the same person, and all with no answer.. 😓🐜

*Lazy Friend has IntelliJ and Eclipse*
*Lazy Friend using Notepad++*
Me: Why don't you use IntelliJ? Its debugger really helps..
LF: It takes too much time to start, I don't have that much time..
*continues staring at his screen and using his mind debugger*

It's kinda funny when he just sits and stares at his screen after saying that he doesn't have any time..

It took way less time to find the (a?) bug when he finally used the debugger..

My boss literally spends half an hour finger-fucking his phone on the mobile site to find "bugs", that I can't replicate. A combination like: swipe, pinch, landscape, portrait, back pinch, open new tab, close tab, ash cigarette on phone, dunk in toilet, dry, double tap... Aha I've found a bug, there's 0.5 pixel line of space between the bag header and the browser bar.

Be me
> find an eslint bug
> report it on their github
> ask to assign it to self
> start working on it
> spend half a day to find out the source of bug
> realises the bug is coming from a library eslint is using
> report it on the library's github
> ask to assign it to self
🤦🏻‍♂️

1. Find bug
2. Try 3 methods of fixing
3. All fail
4. Tell yourself you're trying for the LAST time then you'll go on to something else
5. End up trying 5 more times
6. Repeat step 4 20 times
7. Cry
8. Finally take a break
9. Return next day, try another method, it works instantly

FML!

At my old company one of my colleagues introduced async / await into our csharp code. He created interfaces and showed us a great structuring of his code. Sadly a few weeks later he left the company, because of personal reasons and a bug appeared in his written service. Our senior developer took the issue and complained for like 1 week. That you can't find anything, that interfaces are useless, that async / await is slow and sucks and that we should stop trying to bring new structures into the code base and do things the old way. In the end he deleted all the great things that my colleague introduced and wrote bad and smelly code.

before programming class:
"yes easy af, imma finish this in a few minutes"

during programming class:
*types everything in 10 mins*
*compiles and runs perfectly*
"wtf this isnt supposed to happen"
*spends 30 minutes trying to find the bug*
"fucking hell, it should fucking work by now"

end of programming class:
"oh i put int instead of float, good job, my time was wasted because of one fucking word"

A real interaction I just had...

Team Member: "Can you handle this ticket for a bug fix?"

Me: "Whats the problem?"

TM: "We aren't exactly sure..."

Me: "Ok, so can you show it to me?"

TM: "We can't get it to happen again, and when it does the machine freezes and we can't debug it..."

Me: "So, if I find a fix then how do we test to make sure it worked?"

TM: "I'm not sure..."

Then today,

Product Manager: "How's that bug fix going?"

Me: "Well, let's see. The problem still hasn't been defined. I have never been able to recreate the issue. I have a hacky fix in a PR..."

PM: "Great, so we can deploy today?!?"

Me: "No, because we have no way to reproduce or test this issue at all..."

PM: "Do you think your fix will work?"

Me: "Honestly, no. If you're asking for my opinion then you can have it. IMO this is NOT a bug fix but a change to how the system operates altogether. This system was built by someone who didn't know what they are doing. We have done our best with it but it is a house of cards. And now the solution is to replace a card at the bottom layer. It is likely that no matter what fix we do (even when we can fucking test it) that it will topple the house of cards..."

PM: ~Looking at me in disbelief~

Me: "If you ask me for my honest professional opinion then you will get it. Keep that in the future if that honest response was outside what you expected."

PM: "I will do that, thanks for your assessment"

Where do we go from here? God only knows.

Praise Joe Pesci

When you want to report a bug. Only to find another one...

When your in apprenticeship and find a bug that allows the user to skip the payment... that was in production for multiple years...

Boss: you must fix this bug asap
Dev: I need more time for a proper fix so I will just hack a workaround
Boss: yeah, whatever. You can find a proper fix after the release.

... this happend several years ago and the workaround is still in place...

Step 1: Create and deploy feature. Get feedback: It works fine!

A year passes...

Step 2: Add another small feature that is completely independent from previous feature.

Step 3: Notice that feature #1 is broken.

Why the HELL did it stop working?!? I didn't change anything related to that feature. I can't explain that!

Step 4: Examine bug and find out something unknown about the technology used in feature #1.

Why the HELL did that ever work in the first place?!?

Step 5: Get time to fix it. Don't get time to find out why it worked for a year...

The problem is solved, the mystery remains...

All the possible help is good to find a bug...

A few years ago, I used alert('Well that sux balls'); to debug a CMS custom module. Finished the project and went with the sales manager to demo the app to the clients board of directors. Trust a sales manager to find a bug during a live demo that QA didn't find...
All my temporary error messages are now boring and functional.

When you find a bug that leads you to find better ways of doing things

Dear Programming Languages,

if you only support weakly typed constructs, I wish you a special place in hell.

Dear Fellow Developers,

if you use a language that allows strong typing with weak typing, the next time we will meet after I have to fix a shitty bug due to that I will play piano on your teeth, and a melody you won't like.

And yes, that means PHP as well. PHP allows for strict types since php7.

So. Just. Fucking. Use. It.

There are no excuses!

I don't care if you don't see the benefit or find it "annoying" and tedious to write it out. Use a decent editor and it will be mostly code-completion anyway.

I just don't want to fix your fuckups. And if your fuckup is due to a typing issue that "slipped" by, you are part of the problem.

If you write software, it should be clear what type each and every variable or object has.

There are no excuses but your laziness.

If you want to be ambiguous, try poetry.

Me visiting home for easter:
Me: tries to find some good assets for adventurejam
Me: fixes a bug on the prodserver
Me: redesigns a gui of an app
Me: applies for a bunch of new jobs

Mom: "you are always computer-ing, do something productive"

- there is a bug in the code.
A: I have searched everywhere I can't find the bug
B: What was the last thing you wrote?
A: I called this function
B: did you check the function for bugs?
A: no, I just coded it, there can't be any bugs there

Boss: I wrote some tests and there is a bug in your code but I cannot find it. Fix it
Me: Sure. I'm on it.

Narrator: 5 minutes later

Me: Boss, I found the bug. It's in your testcode...

Seriously... WTF?!

(before someone suggests that my code should handle all test cases... He tried to measure the time the program needed to response and fucked it up...)

That moment that you've got a bug you know you're missing and you can't fucking find it.

Annoying as a motherfucker! 😠

Alright, the blog seems to be running again and its not breaking yet which is a good sign :P.

Although nothing has changed on the front end yet, the backend has been partly rewritten to be more efficient and of course, post sorting based on posting date!

I'm aware of most of the front end issues so no need to tell me all of them again, I'll look at that tomorrow as I need sleep right now :(

If you'd find any bugs/security issues, please, don't exploit them but report them instead! I take security very seriously and will try to patch any security bug as soon as I can :)

The problem with working on a debugger for a living is that you can end up debugging a debugger debugging a debugger that is remotely debugging a debugger which is debugging a program...

...only to find out there's a bug in the first debugger and you need to debug it.

MAJOR RANT:

Bug in question: Shortened URLs (that we generate dynamically because fuck you) would have a pipe character added in them, obviously breaking the URL.

I SPENT 3.5 DAYS DEBUGGING A MASSIVE, FRANKENSTEIN-LIKE CODE BASE TO FIND THIS:

Dear Managers,
This is not efficient:

Boss: * calls *
Me: * answers *
B: there's a bug in feature ABC! The form doesn't work!
M: ABC uses a lot of forms. Is it Form A, B, or C?
B: Umm... let's just go on a Zoom call!
* 5 minutes trying to set up a Zoom call *
* 3 more minutes trying to find the form *
B: This form in here.
M: It works fine for me. What data are you inputting?
B: * takes 5 minutes trying to reproduce the bug * (in the meantime, the call is basically an awkward silence)

You spent 5 minutes wasting both of our times trying to set up a Zoom meeting, and another 8 wasting MY tine trying to find the bug.

This is efficient:
B: There is a bug in form C. If I try to upload this data, it malfunctions.
M: Thank you. I'll look into it.

You saved me 8 minutes of staring at a screen and saved us both another 5 minutes of setting up a meeting.

When you find a UI bug in your car’s stereo and realize it’ll never be fixed.

So I once had a job as a C# developer at a company that rewrote its legacy software in .Net after years of running VB3 code - the project had originally started in 1994 and ran on Windows 3.11.

As one of the only two guys in the team that actually knew VB I was eventually put in charge of bug for bug compatibility. Since our software did some financial estimations that were impossible to do without it (because they were not well defined), our clients didn't much care if the results were slightly wrong, as long as they were exactly compatible with the previous version - compatibility proved the results were correct.

This job mostly consisted of finding rounding errors caused by the old VB3 code, but that's not what I'm here to talk about today.

One day, after dealing with many smaller functions, I felt I was ready to finally tackle the most complicated function in our code. This was a beast of a function, called Calc, which was called from everywhere in the code, did a whole bunch of calculations, and returned a single number. It consisted of 500 or so lines of spaghetti.

This function had a very peculiar structure:

Function Calc(...)
...
If SomeVariable Then
...
If Not SomeVariable Then
...
(the most important bit of calculation happened here)
...
End If
...
End If
...
End Function

But for some reason it actually worked. For days I tried to find out what's going on, where the SomeVariable was being changed or how the nesting indentation was actually wrong and didn't match the source, but to no avail. Eventually, though, after many days, I did find the answer.

SomeVariable = 1

Somehow, the makers of VB3 though it would be a good idea for Not X to be calculated as (-1 - X). So if a variable was not a boolean (-1 for True, 0 for False), both X and Not X could be truthy, non-zero values.

And kids these days complain about JavaScript's handling of ==...

Team leader: hey why this bug is taking too much time? You could fix it hours ago let me try to fix it. I really fuckin hate juniors ...

*Hours later*
Me: could you fix it ?

Team leader: ....

*Couple of years later*

Me: ah i see it's not an easy but could you find any solution bro?

Team leader: no it's not a straight forward bug. You are right am sorry i shouldn't prejudge

I always find it more productive to have at least two ongoing projects at once.

That way, if I get stuck on a bug/frustrated with the first project, I focus on the second and more often than not, when I go back to the first project I realize that I had made a dumb mistake and keep going.

Right, you pesky type initialization bug, I'm gonna find you. Hiding by throwing your exception in an external library won't help you. I'll download the sources, library by library, and look for you there too.

I *will* track you down, bastard, and exterminate you locally. Then, I'll make a pull request and kick your sorry ass off GitHub, off the internet and off the bloody surface of the earth. Oh, you have no idea how dead you're going to be when I'm done here!

If I died, I would have one regret.

I once worked in a code base whose messiness would make an oil spill in the fucking pacific ocean look like spilled milk on the floor in comparison.

Naturally, it had bugs. Oh BOY did it have bugs. Most of them were taken care of well enough. Or about as well as anyone insane enough to work in that code could.

There was just this one bug, which I still (un)fondly call "my bug of 2 years". It. Just. Didn't. Make. Sense.

It was written in JavaScript. Naturally. Which by itself, is the metaphorical programming language equivalent of a pile of horse manure. But this bug. It was the guano icing on top of the horse manure cake which is JavaScript.

I LITERALLY spent 2 years trying to find a solution. I woke up at night, thinking of explanations. I had dreams about fixing the damn thing. And I never did.

On the day I left the job, I had to pass it on to a friend (who hasn't solved the fucker yet either).

I hated that bug with all my heart. But..

Now that I think back, all the books I read, all the docs that I scoured, every non working fix I coded and every failed efforts I made on it, eventually made me a better programmer.

So cherish your bugs and issues. Sometimes, they come, not to hurt you, but to help you grow (unless you use JS, those bugs just wanna fuck you).

Once the system "lost" a user_id var that says who started a batch, but it was a mandatory field that was filled at the beginning of the process.

I tried to find the reason, failed, called a senior for help, he also failed to find the reason.

After a couple of hours I looked to him, he looked back and I said,
"Let's call it a solar flare bit flip?"
"It's the only logical explanation"

So it became a bit flip issue to the PM, we had a good laugh, we send as "system instability" to the client.

The bug never happened again, no one ever found the true reason, maybe it was really a bit flip 🤔

So today, I managed to make one of my colleagues feel like an idiot. In this contract, I work mostly for ui integration, while he build the pages with angular before I add all the html structure and fancy css.

We are building the front-end/ui for an industrial device with a touch screen. For that last 2 days he was blocked on a bug that when you click the confirm button on a delete popup, it would somehow select an input in the page before it was deleted and would lock the ui when showing the virtual keyboard (the poor thing didn't know what to do and wouldn't close).

During those two days, he asked all the other devs for help, trying to find a pattern or anything that could help, while I was focused on writing my css and stuff since it was my priority and I was hired specifically for that (I was aware of the bug and gave my input but I never saw it being reproduced)

So today, he start his new routine of raging at his desk and he decides to show me on my device for some reason. I immediately notice a pattern. It would always select one of the two fields behind the popup, in the click area of the button (it's a big button). Then, I noticed that I could press a random spot on the screen, drag my finger on the button and let go and nothing would happen.

It's at this moment I knew I had found the bug. The button was set to emit an event on mousedown while the inputs behind it were set to emit an event on mouseup (like it should be everywhere). So the popup closed when you placed your finger on the screen and the input was selected immediately after when you removed your finger (which was usually faster than the page code which was not yet optimized)

After that, it was just an easy fix to change the listener and I had a free beer.

WordPress related, get ready for some disgust.

So today early in the morning my boss forwarded me an email from a client, it was about a bug, and asked me if I can have a look at it and fix it.
"Yaay, WordPress!" I thought and opened the page containing the mentioned bug. She wrote that in the italian version of the page, users can select dates in the calendar, which should be disabled, like in the german version.

So yeah, I opened the code. Everything in the function looked perfect. Really. And the Data was also correctly set in the backend of WP.

The function was only 3 lines of code:

- Get the german post ID of the current post (german or italian) by its ID (using a Polylang function)

- Get an Advanced Custom Fields field by name and from a post with the ID from before

- json_encode its content and echo it to a JS var for initialization and later use in some AngularJS.

No fucking missing semicolon, it was fucking perfect like a sunset with your soulmate.

So I tried to find the bug with my personal way of debugging:

"Shitstream Debugging"
When a creek suddenly is full of water mixed with shit, walk upstream through the turds until you reach clear water. This is where the bug is.

=> So I first looked at the HTML source: Turds.
=> Then the ACF field content: Still turds.
=> Then the ID of the german post: Shit stain and turds (var_dump: null)
=> Please god at least $post->ID? Nope, fart smell and turds.
=> Nothing more to check: Clear fucking water and the flowery smell of 99 devVirgins

So it replaced $post->IT with get_the_ID() and it worked like a charm.

Afterwards I feel stupid, but $post->IT worked all the times before...

Conclusion:
FUCK YOU WORDPRESS YOU UGLY PIECE OF HUMAN-CENTIPEDE-PROCESSED-DOGFART.

Thanks for your patience.
Only one beer was sucked dry during the writing of this fucking rant.

Chasing a bug down in CSS, fuckity fuck fuck.

I will find you, and I will squash you.

I just thought this would be a good place to find beta testers. Mainly because the developer is prone to get bored and if they encounter a bug they will be a lot more helpful than "its not working"

If you ever find yourself having serious problem with a bug... relax. Go take a walk around the block for 5-10 minutes, don't think about it, feel the sun on your face, look at girls/guys, whatever.

The answer will come to you automatically.

If that doesn't work, someone you know has adderal.

You know when somebody complains about a bug in your software at a meeting to everybody, you go to their office, find out that the bug is actually an user problem, and then on the next meeting, when asked about the bug the person reports "we fixed it" and you correct them, explaining in detail how there was nothing to fix because the problem was completely user driven?
I love these moments

Is there a lot of people in the same boat as me?

I'm a self taught guy. Never in my life had I a senior developer i could bug for answers. Every little bug and inconveniece i have ever experienced - left alone to cope and find solutions. I just feel like sooo burned out. I have some large complex system questions building up and googling doesnt give me the answers anymore. This is frustrating. I'm supposed to be a mid level developer, but I'm acting as a senior to one of my colleagues even though I have so many questions and doubts in my mind. I think I developed a lot of plot holes in my knowledge and I have no real way to know which are which. I feel I dont know so much. Fuck. Where do I go from here?

!rant

I'm building a complex software that computes stuff with advanced algorithms and linear programming. That kind of software that proved itself strong, but you know a bug discovery would be a disaster.

The client is a dick, always acting as a bully in every email.

Last email, writes me about a supposed error of the software, while of course complaining that the software is complete crap to ensure that I keep a positive attitude.

After some hours of trying to find the cause of the fucking problem, I realized that the software was actually right since the beginning.

I've replied explaining *why* the software says what it says (acting like it was the most obvious thing in the world). Waiting for a response.

I hope that moron will feel humiliated at least a little bit.

Sometimes taking a break can really clear your head. Yesterday evening, I was programming with my mate and couldn't find a very persistent bug. Didn't want to get a break because I just wanted to solve it. He convinced me to go downstairs and get a drink. Reached the bottom of the stairs aaaaand poof, figured out the bug!

So, a few years ago I was working at a small state government department. After we has suffered a major development infrastructure outage (another story), I was so outspoken about what a shitty job the infrastructure vendor was doing, the IT Director put me in charge of managing the environment and the vendor, even though I was actually a software architect.
Anyway, a year later, we get a new project manager, and she decides that she needs to bring in a new team of contract developers because she doesn't trust us incumbents.
They develop a new application, but won't use our test team, insisting that their "BA" can do the testing themselves.
Finally it goes into production.
And crashes on Day 1. And keeps crashing.
Its the infrastructure goes out the cry from her office, do something about it!
I check the logs, can find nothing wrong, just this application keeps crashing.
I and another dev ask for the source code so that we can see if we can help find their bug, but we are told in no uncertain terms that there is no bug, they don't need any help, and we must focus on fixing the hardware issue.
After a couple of days of this, she called a meeting, all the PMs, the whole of the other project team, and me and my mate. And she starts laying into us about how we are letting them all down.
We insist that they have a bug, they insist that they can't have a bug because "it's been tested".
This ends up in a shouting match when my mate lost his cool with her.
So, we went back to our desks, got the exe and the pdb files (yes, they had published debug info to production), and reverse engineered it back to C# source, and then started looking through it.
Around midnight, we spotted the bug.
We took it to them the next morning, and it was like "Oh". When we asked how they could have tested it, they said, ah, well, we didn't actually test that function as we didn't think it would be used much....
What happened after that?
Not a happy ending. Six months later the IT Director retires and she gets shoed in as the new IT Director and then starts a bullying campaign against the two of us until we quit.

*can't find the bug after an hour of searching*
"This is impossible, this can't be my mistake"
*finds bug one minute later*
"Nevermind me"

At least once or twice a week!

!rant
Friend got me a rubber giraffe because he couldn't find a rubber duck for my birthday. This is a toy for infants and it's perfect. Apart from satisfying the use case of a rubber duck for debugging, it has added features like you can chew it when you're too frustrated (coz it's made chewable for babies) and when you press it, it makes the weird peep peep noise so that you can express your glee in successfully finding and fixing a bug.
10/10 would recommend.

"Why is this style not appearing in the browser??? All is perfectly written! No missing semicolon."
*staring 5 minutues at HTML source*
"Oh there you go: I put two times class="..." in the same tag..."

Manager: Hey software engineer, how's the project going?

Software Engineer: Good, just debugging my code.

Manager: Debugging? What kind of bug are you trying to fix?

Software Engineer: The ones that make my computer turn into a lava lamp.

Manager: Ha ha, very funny. But seriously, how can I help?

Software Engineer: Well, I need a bigger monitor. My current one doesn't have enough real estate to display all the errors.

Manager: How about a second monitor?

Software Engineer: No, I need a bigger universe.

Manager: I'll see what I can do. In the meantime, keep coding. We have a deadline to meet.

Software Engineer: No problem, I have all the time in the world. I just need to find a way to slow down time.

Manager: I wish I had your optimism. Just let me know if you need anything else.

Software Engineer: How about a unicorn? I heard they're good at coding.

Manager: I'll see what I can do, but in the meantime, stick to using a keyboard.

WHAT THE FUCK.
I have to deal with a fucking bug that crashes my app only when I'm NOT looking for it.
I investigate another bug? Then BAM, here it is and crashes the app. And I have to start over again find the right conditions to not trigger it again.
I investigate that bug? Nope, everything runs as smooth as velvet.

It's like a Heisenbug, but the cat is dead in the box AND pissing all over the lab at the same time.

Drove my colleague mad with console.log("you cant find me"), that stare he gave me across the room when his stuck with a bug. made me lol in the office literally

We were in a meeting today and it came my turn to talk.

me: "I am working on something not fun. I am tracking down a bug in X software that a customer has issues with."
boss: "It is like an easter egg hunt."
me: "Yes, but instead of eggs I am going to find a pile of crap."
boss: "Laughs..."
me: "Its not chocolate..."
boss: "next..."

The original code I am wading through is very likely my boss' code.

We have a 15-machine cluster that went down last night because one machine in the cluster went down. Apparently having a cluster for redundancy is just a nice idea and doesnt actually work in practice.

Also I shouldnt have to go to a vendor's forums to find out the bug that is causing my cluster to go down is fixed in a future version. It should be in the goddamn patch notes!!!

A woman has bugs in her home, she wants to find a bug hunter to get rid of them. She calls a man who does bug hunting, he comes to her house and says: "I am a bug hunter, you called me. Where's your laptop?"
Woman confused as she is asks the man: "Why do you need a laptop to hunt and get rid of the bugs?"

"Well how else am I going to debug those bloody programs you wrote?"

Note: I promise I made this up, if anyone else already posted this, I wasn't aware.

I have a dream that one day i will push a code to beta and QA will not be able to find a bug.

4 hours! four fucking hours! f.o.u.r. h.o.u.r.s.!
It's the amount in the time domain this bug has cost me to fix. The cost in the sanity domain is immeasurable...
I swear, the god damn ass births of devs who coded this abomination should be slowly mutilated and then raped by their own severed limbs.
It took me 4 hours to figure out that their 12 year old binary CLI tool they used to generate PDFs from PHP could not handle neither HTML5 nor some linebreaks at specific places. Some part of it is due to them using REGEX to find and replace HTML tag.
Yes, I am indeed very pissed. And I need a 🥃 or 3

What we learned:
- Don't use REGEX to "parse" HTML
- Don't call random compiled CLI tools from PHP if there are PHP packages to do the same shit

> be me
> work on a nice project with friends: A, B and C
> joined in a bit later, but before any real progress was made + we scrap the existing code, because it was Python2 or something
> decide on a framework
> A wants to create one himself, instead of using an existing one
> we fight for a little, but let A do his thing
> 2 months later
> been waiting the whole time
> +1000 lines on github, but still not finished
> "Wouldn't it be better if we would use the normal framework?"
> "No, mine is hand-crafted for that task"
> "But it is full of bugs"
> "If you find one major bug, we'll ditch my framework"
> finds major bug
> "That's fixed, just give me a min-"
> finds another bug
> "Thats just because you don't know how to use the framework"

- Documentation inside ONE gigantic README
- Library is missing the core features we needed/those which are implemented don't work
- Both B and C were on my side from the beginning (in that we should use "Already Existing Fully Documented Popular And tested Framework Which Does Everything We Need")
> "But i dont understand this framework so explain it to me"
> send him a few code examples + a tutorial??? (dont remember if i actually sent im the tutorial before i left)
> "explain it to me, i can't understand it"
> I CANT UNDERSTAND YOUR FUCKING FRAMEWORK DUMBASS
> ragequitted the server+project

To this day i still don't know, which framework they are using..
Also that Python 2 code in the beginning was because A didnt know the difference and copied (yes by hand) the code from atom to github without testing anything.

When will I fuckin learn that
a) customers lie
b) customers are sloppy
c) customers are wrong
d) customers do not do their work (properly)
e) customers want us to do their (dirty) work
f) possibly all of the freakinly above?! + khm....

They will fuckin aaaalwaaaays say sth is not working after the update..
And I will alwaaaays assume I fucked up something..even if I didn't touch that part of the code/data..
And almost aaaaalways it turns out that the bug they complain about is how the system worked (or didn't work) before the update and/or some fuckup from their side..

Anyhow, I rushed over, grabbed the files went testing in dev..wtf, output is different, mine is ok, theirs is..wtf is that shit?!

Transfer newly built dll to test..same shit as on prod..wtf?! How?!

I assumed they have thing A correctly linked to thing B.. ofc thing A was linked to thing C in their case and in another case (our test) to correct thing B..
I got chillies when grabbing files, that
I should have tripple checked that they didn't fuck up something on the link part, but I just assumed they know what they were doing & that they checked they linked correct files with correct content already, before being pissy that the update fucked up things.. riiiight!! :/

I wanted to find solutions to this fuckup asap so I disregarded my gut feeling..yet again!! Fuuuck!
I've spent too much time trying to find ways to fix a bug that wasn't even a real bug to begin with.. :/

Fuuuuuck!!

So yeah, always treat the customers like they are 3yrs old & have no clue what they are doing & check exactly wtf they were indeed trying to do..it will save you time & nerves..

And note to self: reread this shit daily!! And imprint it in your brain that everything is not always your fault!!

*looks through code trying to find and fix a bug that crashes server, thinking heavily*

*Coworker comes up*

> Oh hey did you see the email I sent you?

*Forgets everything and has to reread code from top to understand*

repeat indefinitely

Whenever I'm stressed out on a bug or what not...

I find some of my best ideas have come from sitting on the toilet

So we have a bug.
Yesterday I spend the morning sorting through other people's code to find out what is causing this bug report it to team leader once I find it. He asks me find out who made it and hunt them down! So git blame... Turns out it was him :S felt awkward mentioning it to him so didn't. 5 minutes later team leader "oh it was me"

When you think you've either found a bug in Python, or you're going insane, so just to double check, you make two mutually exclusive assertions that could never both be true, and yet, your tests still pass.

I think it's time to find a new job.

When you find a bug in a "min" js file and you don't have the not minified version anymore... ok, it's not a bug it's a feature.

That feeling when a bug has been bugging me for 3 days, I find that little information in API source code and using that I make a fix.

Developer life is so worth it :)

Trying to find a bug. Found a possible line in the code where it might be originating from.

Not I put a breakpoint in there. I can't reproduce the bug anymore.

Sometimes I think I should just go home and play games :(

Be us
Be pair devs
Be doing PHP
Be explaining code to each other to find bug.
Be confused. Code checks out.
Be laughing asses off
Be realise the filename had a m instead of n
@TheCapeGreek

So I had this conversation with my boss yesterday...

Me: Hey, I found this bug in the other team's code that has a major impact on what we're trying to do. Can you ask them to look into it?

Boss: No, I don't want to be the one who has to tell them there's a major bug in their code. Find a workaround.

M: But... It isn't really a major bug, it just has a big impact on our side of things.

B: Workaround!

Fuck bosses who value how they think they look to other devs over a day of my time. Fuck.

Unpopular opinion: I find most office gimmicks which have been popularized by FAANG companies are stupid.
I don’t care about pool tables/videogames/nerf guns, I find these things fun but I’m not 9 therefore I don’t need them at my workplace, I can take care of myself so I don’t need mindfulness seminaries, if I get interested by the topic I’m able to provide myself books or seminaries and don’t get me with the salary I get every month and don’t get me started about the trend of office dogs: most dogs needs a lot of attention and are high energy animals, that’s not what I would need around me when I’m making an urgent bug fix.
Luckily my company hasn’t got into this shit and understands which all an adult professional needs is “just” a good pay and a good work environment.

I wrote a random string/int/other stuff API somewhere this year which I still regularly use because I'm a lazy fuck.

Never posted anything about it on here and the documentation isn't entirely complete (and not all the endpoints are extensively bug-tested yet) but if someone is interested I'll see if I can patch some stuff and put it on here as I find it useful!

When they find a bug at 4:50

Teaching new devs, hired straight from India.

This is today.

Bug1: We have four lists, each item in these lists has a variable called "Charge". This var is a double and we need to convert it to currency.

Dev creates fifth list called "All lists" and converted it's charge to currency then questioned why it didn't work.

I explained, his solution? Convert each list into currency.

I explained that's wrong and told him what he needed to do. He did List1:Charge into currency, but left his other conversion in place just in case.

I walked him through fixing it which took 10 times as long as necessary, only to find out he randomly converted four booleans into currency for no reason.

Bug2: we take integer, convert to string and concat "Months" on the end.

Doesn't work for him, tells me he doesn't know why.

I told him that he's not outputting the variable that we did it to, he is instead outputting a custom variable he made and didn't do anything to.

Bug 3: followup to #2, he fixed it as I instructed, but then added months as static text to the output so now it reads "Months months".

Bug 4: to make his code cleaner, he presses enter in the text box. Unfortunately he did that IN A STRING so his output is full of random /r/n

How do you guys deal with coworkers like this? He isn't new, this is supposed to be an experienced developer. Im only in my 2nd year

Hotest bug: a server in Vietnam kept going offline then popping back a few seconds later. While logged on I couldn't find anything wrong, so eventually I decided to go check on it. It turns out the aircon in the server room situated right above the server has started leaking, so the ever-helpful ops people onsite has wrapped the whole rack in plastic, covering all vents. Surprisingly hard to kill, old HP servers...

I practice what I call "Aggressive Oriented Programming" or AOP.

Whenever I'm investigating a bad bug, working on a project that I really hate, or dealing with messy code written by a messy developer, I often find myself resorting to an [internal] state of violence.

It's not like I scream and smash my screen (although sometimes I want to). It usually consists of a few git blames and some curse words in print statements for debugging. This is just my way to vent.

Working on my Google Foo Bar level 4 challenge.

9 days past figuring out how to solve this problem..

And finally reached on a working solution. When started compiling my solution.

And then i Find out, the fucking Google tool is facing some bug and not allowing compilation. Tried hard to do everything but still getting errors...
And after searching on Google just found I'm fucked up.. It's on Google's end and they are not fixing it since so many days..

Just 5 days left to complete.. And i have no idea what should i do...

4 month work just fucked up

When I had to postpone the release of v2 of devRant UWP for 3 months because I changed a few minutes before the final build a "loaded" event to a "loading" event.
Something that for some stupid reason I thought will make the startup faster (maybe by 2ms) has caused crashes on mobile and some Windows 10 versions.

Of course I didn't spend 3 months to find this bug, but at least a few days in December and then I didn't have enough free time so I had to stop until mid February when I finally fixed it.

To find the reason I reverted the code to the previous update and started to add every feature one by one.
So much time wasted for a fucking "-ing".

I guess that counts? Some of the local burger kings once had an online game they advertised, where you could win free burgers if you are the first on the highscore (the other 2 places got some sort of coupons for cheaper meals), turned out there was a score submit bug you could abuse after finishing a game (me and a colleague noticed, while trying to find some sort of bug), when I reported it they didnt care (didn't get any response, maybe spam filtered?), so I got us some free burgers, scanned in the receipt and send it again, they paniced or just realized you can generate any amount of free burgers for the time of the game being online, took down the game for a day or two, sent me a short email thanking me, thats it.

When you find a bug in your team mate code.

This is a short tale that can be summed up as "oh fuck meee".

After finishing an API the night before I settled in for a day of bug fixes and tidy ups. Until slack went off.

The front end dev was getting an error, a code breaking error. After doing the standard process of request checking i went okay must be me. I find the script that is has the error and the line that it is failing at.

Que 2 hours of the full cycle of anger, sadness, pleading, and finally acepting that it had finally happened I had gone insane. The code was to documentation best practise correct and it still had the same error.

I the cheaked the DB on a whim and I found that my code was not wrong and it was doing exactly what I wanted the data however had a single record that was old and the schema had change juuussstt enoigh to break everything at that record. One 3 secound deletion later code ran perfectly.

Took me a week to find and fix my bug!! 😃😃 A round of apple juice on me!!

Most of the work we do is committed into various branches. Everything is merged into the master branch.

Colleague was on vacation. I was working on a bug that was fixed by him some time ago. All I had to do was find the commit and merge it into the relevant branch. I didn't know which branch to search so I just looked into master. Search all commits on master made by colleague.

All I see is:

"Merged into master"
"Merged into master"
...
"Merged into master"

MERGED FUCKING WHAT INTO MASTER?

spotted a huge bug 2 days before launch. My boss was panicking and he asked. "how long more you need?!" I look at him and almost said "Don't rush art" then I swallow my saliva and said "give me 2 hours" he said ok hurry up.

yea 2 hours after i find out what went wrong

A cache - related bug that gets triggered only at high loads, 10k parallel sessions or so.

Parsing 30GB of logs, trying to find something to work with....

yippee......

I just got a bugreport for an ages old release of a software which was assumed finished. Problem is, i couldnt find the source anywhere.

"hey, could you send me the file so i can check the bug?"
*sends jar file*
"yay im saved"

thanks java, for being easily disassembled 👌😍

I am beginning to hate the relationship between email and my clients. I never thought it would come to the point where email is the worst communication platform I've ever used because some of my clients simply don't know how to use it properly.

I have one client who never uses the subject header in his emails. This makes conversational threads very difficult to follow, and I can't just scan the inbox I have for him. I have to actually do searches on my emails just to find recent conversations.

For some reason nobody knows how to start a new email thread. I have multiple clients that will just take the last email that I sent them, regardless of what it's about, and start a new conversation completely unrelated to the other email by hitting"reply". I end up with email threads that are 60 to 100 emails long and contain many different subjects, which again makes it hard to find anything. Never mind that they've usually put two or three important attachments, or username password combinations, or other valuable information in there amongst all the noise.

Worst of all, I have a few clients and co-workers who insist on starting a new email thread whenever anything about a particular issue comes up. This means that just today I have five separate email threads about the same goddamn issue from the same damn person. Am I supposed to respond to each thread with the same damned information? One of these people is supposed to be both a media consultant and an SEO expert and really should know better. Also, if you do actually send me an email with a subject like "the robot.txt error", please don't give me one sentence about that and five paragraphs about what color you'd like the background to be. That's ridiculous. How the hell am I supposed to find that later? Especially since we already discussed this in the other email that sitting in my inbox.

I swear I am setting up a bug tracking system simply so that my clients can log in and leave me bug reports, and feature requests, and will stop filling up my poor email boxes with what amounts to piles and piles threads that I have to sort through.

For a person who suffers with a form of ADD this is extremely frustrating. Why is it so difficult for my colleagues and clients to write good emails with good subject lines, and reply to the right damn emails?

Am I just being too anal, or does this bother others as well?

We have this lovely little old lady who works in QA and whenever she finds a bug she goes across the office to the developers desk and taps them on the shoulder and spends like 15 minutes explaining and showing the bug...

This is infuriating as you lose all concentration on what you are working on and wastes so much time... But I can't bring myself to tell her to stop just can't find kind enough words. She's a lovely person and means well but it seems her world runs a lot slower than everyone else's.

!rant
If you have software in production please have some way for a user to find some contact email (create for this reason only if needed.)

I have run into crippling bugs in huge essential systems (state dmv new system, the ticket system utility marking) which they were oblivious to until I went out of my way, like a stalker to get some contact of someone remotely related to someone I could drop this info in the lap of, and so far it was a total shock to them (the dmv system was taken offline for 3 days to resolve)

I get not wanting to run a helpdesk to support users, but give technical users some contact info ( even if you think you have full coverage analytics because, being software, it may have a bug)

/rant

For me there are two kinds of bugs. The ones where you lean backward and the ones where you lean forward.

If you found a bug and you lean backwards in your chair resting your hands behind your head you feel proud and relieved that you found that sneaky bastard. Good for your dev soul.

If you lean forward, resting your forehead on your fists or on the desk then it was a very stupid bug. Not sneaky at all. Something plain obvious. It makes you doubting all your career and life choices you made so far. Like needing one hour to find out that you named the "MANIFEST.in" accidentally "MAINFEST.in"...

Want to share any embarrassing bugs to make me smile again?

Deep Thought Rant

It's funny how the world works these days...companies only looking for "senior *something*" developers to work...

Mentorship and internship also do matter. What's happening?...sure you can contribute to open source but having a mentor also helps. Working as an intern allows one to see not only tech bit but workplace environment. How to deal with deadlines, feeling good and wasted at the same time when one bug that took a 3 minutes to fix but 3 hours to find, presenting your work; well what's working only, being bashed when it's your fault or not (even though that sucks), learning from your mentor and so on

Are their companies that still do this?

It was a nightmare about a nuclear attack, I was afraid and looking for some cave or basement to hide from radioactive winds.
Then I woke up to find 5 missed calls and emails about a critical bug in production.

Yet another day at work:

My job is to write test libraries for web services and test others code. Yes I know to code, and have a niche in software testing.
Sometimes developers (whose code I find bugs in) get so defensive and scream in emails and meetings if I point out an issue in their code.
Today, when I pointed a bug in his repo, a developer questioned me in an email asking if I even understood his code, and as a tester I shouldn’t look at his code and only blackbox test it.

I wish I can educate the defensive developer that sometimes, it’s okay to make mistakes and be corrected. That’s how we deliver services that doesn’t suck in production.

Is it possible to find a fix to a bug while you’re having a lucid dream?
Because as soon as I woke up I ran to my computer and heck it actually worked!

Which would mean subconscious mind knows why every error is occurring and how to fix it.

Which means our subconscious mind is playing our conscious mind.

Superiority complex.

STOP sending me fucking videos of the bug you are experiencing. I don't get paid as much as I do to sit around and watch your stupid fucking screen captures for 37 minutes just to find 30 seconds of meaningful information to reproduce something you could have put in a paragraph and emailed to me.

Either you meet me halfway and actually understand the expected outcome and how it differs from what you experience enough to verbalize it, or I ain't fucking fixing your shit. For fucks sake, a 40 minute screen recording with no audio does NOT count as a valid reproduction.

Costumer called.
feature xyz doesn't work.

Spent hours trying to find the bug causing the malfunction, couldn't reproduce it on my devices.

Called to the customer to have a look on his device.
Feature xyz works as intended, the only bug: Too less patience at Layer 8.
Device just needs a little moment to establish a connection.

Patience is a virtue.

what would you do if you find a bug inside here?

Back when I used be a junior fresh out of school, my senior used to say, when releasing a first version or a major version of any software, app or website always implement easy to fix bugs.

End users or clients, especially the ones that tasked you with the creation of it, will look for a bug until they find one, if it isn't one you will spent hours trying to figure it out, instead give them one.
You know how to fix it and the client is satisfied they found one.

To this day, i still do that, although mostly not even aware of it. Eg: I know that's a bug but i'll fix that when (not if, when) they complain about it.

I even find myself telling the juniors, i develop with, giving them similar if not the same advice.

And that is what experience means, skill is something they teach you in school.
Experience is what makes you a senior or a junior, not your level of skill or the amount of keywords on your Linked In profile.

A mail I got two days ago started out like this:

"Hello Mr. $myLastname,

I know the Internet Explorer is quite old but we found some errors[...]"

My mind: "NooooOOoOOOO"

They find a lot of weird stuff too, dropdowns, carousels all that major stuff didn't work.

Turns out it was a bug with bootstrap 4.1.0. It's fixed in 4.1.1 and until, release we can use 4.0 just fine.

My feelings in those 15 minutes resemble a sine wave.

When you find a bug before debugging.

CEO announced a bug bounty programme for devs to do stuff in their free time for additional cash.

Cash is decided by business people based on their idea of how complex the given problem is.

And it's not for bugs one could just find and fix. Only some fixes/features decided by them.

Like second shift.

Quick Tutorial: How to find a missing bug.

0) Wake up & have breakfast
1) Goto work
2) Do your job until the end of the working day
3) Make a backup
4) Shutdown your PC
5) Stand up
6) Go to the office door
7) Grab the door
8) Now the phone rings
9) Turn and go back
10) Take the phone
11) Now you get the bug report

This is a well approved method.
It always works!

When you find a Bug, but don't know why it is not working.

Fixed a bug in a code wrote 11 years ago.
It took 11 years for a user to find a bug.
The user must have a prize: a Bug Bounty.
My Boss does not like Bug Bountis

The longer it takes to find a bug, the smaller the required fix will be

Your front end may look gorgeous, but I see a bug that scares me. Can you find it?

That feeling when you have found an impossible to find bug after digging in and you attempt a fix as soon as you find it and the first 1 fixes everything

Today morning my sales manager calls me and tells there is a bug in one of the integration module and he tells the client has called us yesterday pls come early to office today and fix it. I asked which end point they have issue, he replies I don't know. I don't know what is the bug where is the bug, but there is a bug when they send data to us, pls find and fix it before 11 am. The worst part of this is that integration module I never worked on and the person who developed it has left the company long before and there is no documentation. when I go to that folder I see many controllers and many end points. now how will I figure out the issue 😂 I don't even know the work flow of that integration. the bug reporter (my sales manager) don't even know at what end point what issue happened.

I'm freaking done trying to get Linux on my machine. I've tried every distro with many different versions of the kernel and I always run into the same problem on my desktop.

The computer super stutters for 2 seconds ish than freezes.

I've spent DAYS looking into this issue trying to find something. The worst part is that it can happen 5 minutes when I boot or 5 hours. At first I thought it was Compton. Then I thought I installed arch wrong. Maybe an update to the BIOS? How about downloading updated microcode? Maybe this obscure bug with AMD processors and setting power idle to typical? Nothing. I'm now behind on my school work because of the massive amount of time ive spent getting this fixed. It works just fine on my laptop, but it doesn't work on the machine I built to code with. I'm done. Give me Force Lightning, a red lightsaber, and call me a Sith baby because I'm joining the dark side. Here I come Windows.

For those who are wondering my setup:
Ryzen 7 1700
Rx 480
Asus x-370 prime
16 gb Corsair RAM

And no, Windows has never had this bug.

If I find myself stuck for more than a reasonable time on a single bug, never plough on.

Get up, listen to some music, relax on your memory foam mattress, close your eyes and simply relax. Get back to your workstation and I always find myself solving it within seconds and wondering, "SHIT, WHY DIDN'T I THINK OF THAT BEFORE"

And I find myself answering it's because I never took a break!

You know, one of my worst fears as a programmer isn’t a bug, or shitty clients, it’s not even happening on my computer.

It’s when I can’t find a good playlist to listen to because the good ones I listen to way to much and I get sick of them so I get stuck with nothing and my Brain simply can’t function without a butt shaking toon!

Come back from a week's vacation, 3 apps in review. Sit down, set up Xcode, pull latest changes. Run code for the first time, tap through two screens, find a critical bug and I have to reject all 3 apps and resubmit.

5 business days away and I found an obvious bug in 5 minutes.

Someone's not doing their job...

Tried to find a bug for hours and now found it...

I have a bug that shows null but i got an "null" string which is nasty. To someone who did this, i'll find you and i'll kill you

!Rant

Wrote a crawler and now has 18 million records in the queue. About 500.000 files with metadata.
1 month until deadline and we have to do shit many things.

Now we discover we have a flaw in our crawler ( I don't see it as a bug ).. We don't know how much metadata we missed, but now we have to write a script that scrapes every webpage that we've already visited and get that metadata..

What's the flaw you ask? Some people find it funny to put capital letters in their attribute names.. *kuch* Microsoft.com!! *kuch*

And what didn't we do? We didn't lower case each entire webpage and then, only then, search the webpage for data..

Just before the holidays started I was given a task by my manager, $M.

$M: "Kyntak, while I'm away I want you to look into this new way of starting $important_service"

$me: "Okay $M, is there a bug for this that explains what is needed?"

$M: "Yes, you should be able to find it"

Goes looking, finds someone else working on something connected but not the same, finds the code change that makes this available... It doesn't explain how to use it, when the async events fire or (well, to a junior engineer like me) really anything.

Message the other (very experienced) eng.
$me: "Hey I've been asked to make $important_service use the new starting API, can you tell me about?"

$eng: "Yup, here's a bug for that and I'm happy to answer any questions you have" *goes offline*

I read the bug. It doesn't mention the original problem I was trying to solve, it doesn't even mention $important_service. There's no design doc mentioned. The bug has a higher priority assigned than any of my other work. It has an expected completion date only days after I get back from holidays (which $M told me to take).

I try to contact $M and $eng. They've already left for holidays.

"Hmm"

Implements as much of the fairly inevitable boilerplate that I can infer from the bugs and surrounding code.

"Hmm"

So, I'm into my second week of holiday and am starting to think about the potential shit storm I may return to.

I hope the bug's priority was wrong.

Just...Macbooks

(sigh)

The entire day wasted having to install a new OS to install a new Xcode to export an app, only to find the xcode was installed under a different user (who has long since gone from the company) to then have to look up what to do, to then just sit...........and....................wait.............for Xcode to download again.
And I know when I try to export my app (which had zero problems being exported to Android) I'm going to hit an entire day tomorrow of bug fixing for ios sh...stuff

I really don't get the frustration people have with debugging...
It's one of the most fun parts of programming for me.

I don't mean the missing semicolon (I use an ide cause I care about my time).

When all your seniors have spent hours on trying to find a bug and after a few days you're able to present a fix to them, that honestly is the best feeling, potentially better than "finishing" a product (let's be honest, it's never finished)

Product Owner: There is a major bug with your code it's not working.

I then spend hour looking at code to find out.

It's a content problem!

I don't know why is that everytime you guys find a security bug or a data leak or that someone is saving plain passwords on their database, you try to cover and censor the company name. Listen people, fuck the company and their name and their brand if someone's data might be in danger. Everybody should be aware of what is happening with their personal information.

Also, maybe would be great if devRant would let users to post anonymous rants for this kind of issues or a special thread with latest news about our online security.

FUCK FUCK FUCK FUCK FUUUCJKKK OOOOFFFFFFFFFFFFFFFF (wasted hours why im being redirected to 404 when trying to access a route thats being guarded (u need to login first to access it) only to find out i changed /login into /auth/login and forgot to update this bs into the guard so the guard was redirecting to /login which indeed doesnt exist and is a 404 instead of redirecting to /auth/login)

This is such a fucking dumb bug I have to take a fucking break im going outside for a jog and then intense home workout to unfuck my mind

I just wasted 2 hours together with a colleague to trace a bug, through several modules, functions, data, etc to find out it was usage of the wrong information in the wrong place. The data used was never intended to be used this way.

I HATE SUCH SOFTWARE ARCHAELOGY.
Carefully uncovering layer over layer, getting one detail after another, from which you don't know if it's really necessary to trace the bug, until you lose the sight of the whole picture. Then when you're confused to the maximum, try to figure out what's important and what not and reassemble the puzzle until you can see where the road is heading.

At least we found the cause of the bug, so it wasn't useless. Now we have to waste more time to develop a solution (...preparing for next rant 🙇)

Once i worked on an application which has very long form and submit to a soap endpoint (post). I felt my life was so pointless when testing after i made changes. So I automated the testing by generating post request so i can just run it.

I filled the user name with Brandon Boyd, Alan Turing or Ryan Gosling. And it increments like Boyd1, Boyd2.

Once my colleague found a bug, the data never get saved but all the boyds persists. He knew it was me, who uses that kind of name

My barbaric manager (was involved) kind of pointed his finger at me. I sweat a bit though i couldn't find logical explanation why Boyds stay. but turned out someone changed the sqlscript.

The infuriating edgecases of python copypasta.

If you're like me, and you find it easier to noodle in notepad++ and the console, then you may have encountered this peculiar bug.

Try padding blank spaces on an empty string variable, and follow it with print(blanks + str(var))
#for any variable

Now copypaste that along with at least one other line at the same time.

Observe how no matter what you do, print will always output the blanks variable on a separate line, with quotes.

Try rewriting right-justify? No good.
Try using f-format strings? No good.
Raw strings? Inspecting bytes to see where the newlines and carriage returns are being inserted? Nothing.

Copypaste with multiple strings will *always* insert quotes and a new line when printing *any* variable with a string thats been justified.
And this is 100% non-congruent with pasting the same *line* of code *by itself*, which works as intended, no quotes or additional new lines are inserted.

I just went ahead, turned the snippet into a function, and called it from there, which solved the problem entirely.

Worked with a team on a mobile app project. The system needed to contact a system coded in php.
When a call was made to php, it would be stored in a variable $call. Weirdly it never worked. After spending days trying to find the bug, it turned out that a junior Dev had created a variable $call in another file that was being included into the api file.

We partied the day the bug was fixed 😎

Me: Hits blocking bug in someone else's code. Everyone's busy and stressed, I'll have a look myself. Find the problem, find associated documentation. In a language I don't really know, so pass this to appropriate dev.
Them: It's not a problem for me.
Me: ... Wut?

I don't work there anymore...

I joined in June to work on a project due to release in July. It released in December.

I spent hours trying to enable CORS on AWS Lambda through API gateway (it was supposed to be simple and Amazon had a nice tutorial) but it turns out that there's a known bug that makes Lambda Proxy Integrations not adhere to any setting in the API Gateway, you have to respond with the headers through the Lambda yourself.

Amazon now mentions this in the tutorial, but if you click "Enable CORS" in API Gateway, it'll show you green check marks and tell you that everything went fine, but you'll find that the Lambda does not respond with the CORS headers. They shouldn't even have "Enable CORS" as an option when you use their Lambda Proxy Integration.

When you find a bug that affects all browsers EXCEPT Internet Explorer... How...?

Trying to learn C and thought a easy file copy was a good start. The program read the size of the file, reserved that size in memory, can copied data there and then to the new file. For some reason I never thought that the file might be bigger then available memory... Took a couple of BSOD to find that "bug".

Feels good when you find a solution to a bug in 10 minutes because of stackoverflow.

Wouldn't call it a software bug but related:

Was developing an order system to expand in the UK. We have been developing it for the last 2 years and always had a one nasty bug in the system... Whatever we do, it still appears... Tried debugging to find the source, tried covering with tests - nothing helped it was still there. We even rewrote the whole system 3 times and it still was there!

One day, we have been given a stupid request from our manager - take a black background and make it even more blacker... That was it and I went to the CEO with letter where I stated that we should remove the manager... As I'm the Senior there, he did ask me why and eventually removed the manager...

Oh my guys, I've never felt so good after removing a bug! Since then - our application went live, we had our first customers and we were happily rolling new updates. And the best part - there was no BUG! Everything we did just had undocumented features or missing links but we haven't really had a single bug that was not caught by our automated tests!

---

Moral of the story:
Not only software can have bugs. People also can be "bugs" while bugging you about every single details they think is not working correctly.

Just got off the phone with a csr about a bug they found. No biggie, I said I'd fix it. Basically until it gets fixed I told them that when they do their process to make sure to do "foo" first, then "bar" second. As soon as I got off the phone, had to poop so I went to the bathroom, and as soon as I sat down I get a message from the same CSR, "Hey I did bar first, can I type foo then bar again?"

WTF DID I JUST SAY LITERALLY 2 MINUTES AGO ON THE PHONE. TBH IT WOULD BE BETTER IF YOU JUST DIDNT DO ANYTHING FOR 15 MINUTES BUT NOW I HAVE TO COMB CLOUD FUNCTION LOGS, FIND THE DOC UID YOU CREATED, FIND THE DOC YOU MADE, DELETE IT, DELETE THE ASSIGNMENT IN YOUR TRASH ASS WORKPLACE PORTAL, AND STILL FIX THE SAID BUG

It took me two full weeks to study this complex system (the system is a nice piece of work) and learn about graph theory to trace this bug reported by the client in order to find out that it was a data-entry issue. I had to trace x and y coordinates to debug this issue.

Although the result was a bit frustrating, it made feel capable and responsible. It was a good feeling in the end.

At my job we have these days where we have to BUG-BASH, meaning we do any stupid thing on the software to test it and find bugs.

I hate it.

I didn't sign to be a QA.

Just installed Mint and I got a few questions: 1. There are no icons showing up on my desktop. Is this just a bug or normal? 2. Where can I find Firefox,VLC etc?

Every time you find a bug in your code ... 😢

Product manager: When building new features, we find we have bugs that reappear in other parts of the app where the bug was solved before. We have to find a solution to this issue.

Dev: These are called regressions, they happen all the time in software development.

Product manager: ...

Dev: Fuck outta here! Its friday!

How I feel when I finally solve a bug I couldn't find

Apple: Mojave update breaks OpenGL code and causes a black screen? It's ok, no rush, nothing to fix here. Anyways OpenGL is deprecated right?

I literally spent a couple of hours debugging my engine because it would show a black screen until the rendering window was moved or resized. Only to find out it's a known OpenGL bug after the Mojave update. No biggie.

I'm just frustrated. I wanted a simple, statically-typed language that doesn't get in your way and offers GC. I can't find anything "just perfect".

- Go: enforces a style on you, nono.
- Rust: ownership system. I love it, but it's too low level for what I want.
- Scala: seems to have a bunch of useless and bug-prone features.
- Java: I hate how you have to declare and catch exceptions. Good practice, yes, but the code gets bloated with try-catch statements.
- C and C++: Too low level, no GC.
- C#: maybe? idk

I want to make a back-end for an app but I want it to be easy and fast. I need something with a gentle learning curve, not keep fighting the language. I'm between Java and Rust. Java's easier to use. Rust is rust <3, but it's hard, I haven't learned it properly and I just keep fighting the fucking compiler.

If you think you found a solution, think twice.
If the implementation is taking too long (too many changes in different functions and classes to fix a single bug) there may be a better solution, it's never too late to reverse the changes and start again, it's not a shame, in the worst case you will reimplement the same solution, but better, in the best you'll find an easier and better one.

Don't run, even if there's a deadline.
It's much worse having to deal with negative feedbacks later.

I'm using framework X, I managed to google and fix the bug in a few seconds, nice!

I'm using framework X with library Y, I managed to google and fix the bug in a few minutes, nice!

I'm using framework X with library Y and Z that adds certain features, I managed to google and fix the bug in a few hours, I need a bathroom break and coffee but great!

I'm using framework X, runtime environment version 3, library X and Z and am trying to achieve T because god knows why and managed to only find 2 old stackoverflow topics and 1 reddit post almost completely unrelated but I tried their code anyway and I feel so miserable I'm behind schedule and can't seem to be able to fix this stupid issue what am I doing with my life oh please...

I released an Android lib on JCenter.

So far so good. What I didn't realize was that I had a terrible bug related to a content provider.

Since I was using the ContentProvider to make my CursorLoader work, if someone installed an app with my lib, you couldn't install another one with it because it would conflict the providers.

I had to quickly find a solution and dispatch a new release.

Today we found out that my brother has a condition, triggered by a stressful event, that causes his heart to try and shutdown.

The dev in me is screaming "fix the bug!"
The crazy in me wants to start punching doctors in the face til we find a solution.

But the rational side of me knows there's nothing that I can do because that magical asshole in the sky didn't commented his code...

1. Exporting fat jar
2. Transferring to cluster using WinSCP
3. Running it in the cluster.
4. Find a small bug.
5. Repeat

I HATE IT

To that nasty animation bug I’m dealing with for a week already...

I don't know who you are. I don't know what you want. If you are looking for ransom I can tell you I don't have money, but what I do have are a very particular set of skills. Skills I have acquired over a very long career. Skills that make me a nightmare for bugs like you. If you let my project go now that'll be the end of it. I will not look for you, I will not pursue you, but if you don't, I will look for you, I will find you and I will kill you.

>building the same app once again because of a bug
>look in the unity editor settings for android
>find "proguard"
>google it, find it might be useful to minify, obfuscate code and other stuff
>try to minify the shit of the app
>original app was 25.1MB
>minified app is 24.6MB
>minified app using "Gradle (Experimental)" is 24.5MB

Debugging your JavaScript Code for 2 hours and trying out every imaginable solution because it works on the demo page but not your site... and then you find out the fking library had a bug and the Readme.md contained a cdn link to an old version and the demo page was up to date... arrgghh

I just don't get the WordPress hate or CMS hate in general. Using these is not perfect, but neither is _anyone's_ code. Get over that and be more productive for your client. Unless you're the best coder the world has ever seen, and you're _always_ available to push content for an organization of 90 or 900 or 9,000 people, nobody CARES about your "coding purity". They want a website that they can still operate if your ass gets hit by a bus. Don't like WP? Find a CMS that ticks most of the boxes for your client's needs. If you have the time, budget, and long-term inclination to provide bug fixes for it, write your own Awesomesauce Custom CMS(TM) and release it to the open source community so we can finally replace WordPress with the next best thing.

Otherwise, launch site, get check. Repeat until you can retire.

Working on this bug for a day. Frustrated Friday afternoon. Decided to explain to my manager and senior why I can't find a fix and while explaining it to them, I eventually figured out the problem and fixed it.

I just realized I used my manager and senior as rubber ducks.

Everytime im visiting msdn, I'm about to start criying. Especially today. Im having until wednesday to fix a bug, and the only documentation I can find that talks about this issue is on msdn and the site takes fucking forever to load, pouring salt in my wounds.

Our PM just send a mail to our team, that after testing the latest extension we made to the project, he could not find a single issue or bug (usually there are some minor UI problems or some edge case bugs we did not think about or know existed)
and what a incredibly great job we did, and he also forwarded the mail to all our managers up the hierarchy right under the CEO.
The appreciation is a nice change to the self-hatred I feel while coding

untangling some spaghetti deep in a tech-debt-ridden repo:

find the bug causing function

only comment:
`//TODO: replace this once <jira_ticket_url> is done`

go to url

updated: 3 years ago

I miss CS undergrad

I was almost 2 days in a task to find the reason of a bug in a client's process, then I found something really weird, that made all the team go to my desk to see wtf was happening, then a guy says, "wait, this was not supposed to be in there, I was editing this process in other environment (he knew it because of the number)" , what did we discover? Someone (they haven't told me who), was supposed to put a file in a folder, just it, but the motherfucker did put the file in the wrong environment folder. I lost 2 days chasing a bug that never existed '-'.

The high when you find the root cause of a bug. Wow, that makes it all worth it.

Fucking hate people who can't appreciate what you've worked on. And just find the fuckin faults in your task. Would it kill them to just shut the fuck up and not start the conversation with ooohh I've found a bug, just fuckin try to make something first of your own and then be an asshole to others.🖕🖕🖕🖕🖕🖕🖕🖕🖕

receive multi year old confused bug/feature request from a former CEO

why

are there not other people who can immediately answer the questions instead of playing broken telephone when it arrives to me, to go find them

do you not have better things to do with your time and other directional priorities for the company or should i really muck around this low priority thing?

i guess i just lack the CEO M I N D S E T, also the compensation package

Been working on a new project for the last couple of weeks. New client with a big name, probably lots of money for the company I work for, plus a nice bonus for myself.

But our technical referent....... Goddammit. PhD in computer science, and he probably. approved our project outline. 3 days in development, the basic features of the applications are there for him to see (yay. Agile.), and guess what? We need to change the user roles hierarchy we had agreed on. Oh, and that shouldn't be treated as extra development, it's obviously a bug! Also, these features he never talked about and never have been in the project? That's also a bug! That thing I couldn't start working on before yesterday because I was still waiting the specs from him? It should've been ready a week ago, it's a bug that it's not there! Also, he notes how he could've developes it within 40 minutes and offered to sens us the code to implement directly in our application, or he may even do so himself.... Ah, I forgot to say, he has no idea on what language we are developing the app. He said he didn't care many times so far.

But the best part? Yesterday he signales an outstanding bug: some data has been changed without anyone interacting. It was a bug! And it was costing them moneeeeey (on a dev server)! Ok, let's dig in, it may really be a bug this time, I did update the code and... Wait, what? Someone actually did update a new file? ...Oh my Anubis. HE did replace the file a few minutes before and tried to make it look like a bug! ..May as well double check. So, 15 minutes later I answer to his e-mail, saying that 4 files have been compromised by a user account with admin privileges (not mentioning I knee it was him)... And 3 minutes later he answered me. It was a message full of anger, saying (oh Lord) it was a bug! If a user can upload a new file, it's the application's fault for not blocking him (except, users ARE supposed to upload files, and admins have been requestes to be able to circumvent any kind of restriction)! Then he added how lucky I was, becausw "the issue resolved itself and the data was back, and we shouldn't waste any more yime.on thos". Let's check the logs again.... It'a true! HE UPLOADED THE ORIGINAL FILES BACK! He... He has no idea that logs do exist? A fucking PhD in computer science? He still believes no one knows it was him....... But... Why did he do that? It couldn't have been a mistake. Was he trying to troll me? Or... Or is he really that dense?

I was laughing my ass of there. But there's more! He actually phones my boss (who knew what had happened) to insult me! And to threaten not dwell on that issue anymore because "it's making them lose money". We were both speechless....

There's no way he's a PhD. Yet it's a legit piece of paper the one he has. Funny thing is, he actually manages to launch a couple of sort-of-nationally-popular webservices, and takes every opportunity to remember us how he built them from scratch and so he know what he's saying... But digging through google, you can easily find how he actually outsurced the development to Chinese companies while he "watched over their work" until he bought the code

Wait... Big ego, a decent amount of money... I'm starting to guess how he got his PhD. I also get why he's a "freelance consultant" and none of the place he worked for ever hired him again (couldn't even cover his own tracks)....

But I can't get his definition of "bug".
If it doesn't work as intended, it's a bug (ok)
If something he never communicated is not implemented, it's a bug (what.)
If development has been slowed because he failed to provide specs, it's a bug (uh?)
If he changes his own mind and wants to change a process, it's a bug it doesn't already work that way (ffs.)
If he doesn't understand or like something, it's a bug (i hopw he dies by sonic diarrhoea)

I'm just glad my boss isn't falling for him... If anything, we have enough info to accuse him of sabotage and delaying my work....

Ah, right. He also didn't get how to publish our application we needes access to the server he wantes us to deploy it on. Also, he doesn't understand why we have acces to the app's database and admin users created on the webapp don't. These are bugs (seriously his own words). Outstanding ones.

Just..... Ffs.

Also, sorry for the typos.

When you find a bug about the feedback button.

I'm on an iPhone 4s and unable to get to feedback.

I don't know why I'm doing this but when I go to websites that aren't mine and found that there's a bug in their site or system, I kinda happily report these bugs and issues to their email with screenshots, findings and steps to reproduce the bug.

Just recently, I just went to a site and found a peculiar timeout error, eventhough it was less than a second to respond back. Only to find that there was an undefined JavaScript variable in their code.

Is there a bug bounty for fixing code?

Everytime I face a new bug, my innerself tries to convince me that I can never find a solution to this.
But my gut feelings know that sooner or later I've always found a solution.

Thanks to all the devs sharing their problems in the internet.

Finally, fucking finally I fixed a damn bug that seems to be freaking popular on asus machines. This damn bug captures the fn keys needed to regulate the screen brightness.

All tools that display your keypresses didn't find them at all and I had a pretty tough time find the source of problem.

You can create as many arch memes as you want but you cannot deny that the they are truly MVPs imo.

Today I also:
* Fixed and refactored a bit of code
* added shortcuts for volume and keyboard backlight control
* Installed lots of fonts
* Got Steam to run
* Found out the meaning behind the Arch linux
* Felt disgusting using windows 10. Learned that 10 stands for the number of minuts before I must vomit 🤢
* Learned a bunch of linux stuff

But most importantly
*installed sl

Wow. This piece of bullshit runs completely flawlessly in the debugger, but throws exceptions like fuck when running it normally. How am I even supposed to find that fucker of a bug?

Stayed up extra late fixing a bug. Fucking bug is buried in a thousand lines of MOTHERFUCKING SML.
FUCKING ASSHOLE SHIT-WAGGLING COCKSMEAR AND THAT SHITTY, GODDAMNED BACKWARDS FUCKING LANGUAGE!
Fucking wasted an entire night chasing down a fucking bug in SML with no positive effect.
I wound up commenting out 7/8 of the entire fucking codebase to try to find the fucking bug. No positive effect.
Finally had to go to sleep because my son was about two hours from waking up.
Getting back to work, and within twenty minutes I found the fucking bug and fixed it.
Fucking wasted nearly an entire night's sleep, and I ended up fixing the fucking bug before finishing my morning coffee.
I seriously fucking hate motherfucking SML.

So the other day, I was working on some Python project when there was this bug that kept transforming. Like seriously, I would turn from "bool not defined" to "function does not exist" to literally "file does not exist"... within the FILE. And when I fixed them, new bugs kept popping up, and I couldn't find anything that was a problem. Nothing. There was this one function in there that, if I changed even the comments in there, would break. And so.... I turned off Atom and turned it on again. ( ha ) Didn't work. I restarted my computer. I copy pasted the file into another file. I used another IDE. I restarted GHCI. I restarted Jupyter Notebook... and after 6 hours... I found that it was because an if statement has a comparison between a bool and a bool, with a = in the middle. (not ==). I swear I almost threw the computer on the floor.

I'm not a beefy dude, But I consider myself as a terminator 🔫 because when I find a BUG I fucking console log the shit out of it !

for one split second I thought I had discovered a way to manage multiple states with one reducer function in react,

turns out it was a bug in my code,

I had already gone to brag about it on my react group chat, until I went back to my code and as I was cleaning up and closing brackets and all that stuff, my new feature stopped working.

I need to find that bug