Admin: "Wait, I noticed unusual traffic."

Me: "What is it?"

Admin: "Looks like we have a bot here."

Me: "A bot? Didn't know we are so popular."

Admin: "It makes constantly login requests through our API, it already surpassed 600.000! I will ban it right away."

Me: "wait, that just sounds like my bot.."

Admin: "DUDE, WTF? ARE YOU SERIOUS?"

When there is bug, you don't know of, it can end up quite embarrassing.

QA: There is a bug in your program, it doesn't work !

DEV: What? It is working on my machine, let me show you *opens app*

QA: Well, then I will tell our clients to use your machine every time they want the app

DEV: ...

*Manager enters the room quickly*

Manager: Coffe2Code, we have a serious problem on the application, (We are working on a chat app).

Me: What? now just few hours before the Demo?, what is it?

Manager: when I send or receive a media message (audio or video) the sound is not playing, the file seems like corrupted !

Me: that's strange, let me debug it and see.

*Me spending an hour and could not even reproduce the bug..*

Me: Boss, I cannot see the bug, can I debug on your device quickly?

Manager: Sure, here it is.

Me: hold the fucking device, press VOLUME UP, IT WAS FUCKING MUTE. THERE WAS NO ISSUE MOTHERFUCKER.

Manager, oups ok good no issue then, thanks

I was newly hired to company. A customer came in yelling saying "there's a bug, this should do this but it's doing that..."
PM came to me and told me to "urgently fix this as this is an important customer".

So I started debugging for hours and asking around and all follow devs agreed that this is a bug. Then I found it!! And it was clear that it was not doing what the customer wanted.

I decided to look through this code history and found out that this part of the code wasn't changed for a year but the code commited before it did actually what the customer was expecting (whaaaa....)

Gathered the devs and the PM showing them what I found. They all looked at each other and then one said "ouuhhh right...yes it was doing this but we changed it to that..."

Turns out it's a feature not a bug, and everyone forgot about it.

FML

Last night I had a dream about a bug and I woke up with a solution. When I got to the office and tried it out it worked...I have heard about this happening before but this is the first time I have experienced it!

I prefer silent kills.

× open Jira ticket classified as a BUG REPORT
× Title: "Mike"
× Description: "Mike is working with us"
× assign it to Mike

× reopen it every time it's closed

Today, I finally had the opportunity to say to a client: "It is not a bug, it is a feature".

No, seriously, it is a feature.

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

Manager: This code you wrote violates the single responsibility principle!!

Dev: How so?

Manager: You have one function that you call in *MULTIPLE* places. That’s too much responsibility for one function! Functions should only have one responsibility!! Creeping the scope of a function beyond that is a TERRIBLE way to write code!

Dev: But why spin up multiple functions that all perform the same thing?

Manager: Well if a function has a bug in it and you use that function multiple places then that bug exists everywhere you use that function. If a function only has one responsibility then if it has a bug that bug will only exist in the single place it is called! You really should think first before asking questions like that.

Dev: …

There is a spider outside my window at work that I've named Vanessa. She is a web developer. And every time I squash a bug, I feed it to her.

it doesn't work is not a bug report.

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
🤦🏻‍♂️

- Is it a bug or a feature ?
- Yes !

For fuck sake, one small bug and my app immediatly gets a 2 star rating. HOW ABOUT YOU REPORT THE FUCKING BUG TO ME SO I CAN FUCKING FIX IT. MY EMAIL IS IN THE GODDAMN DESCRIPTION. HOW FUCKING HARD IS IT TO SEND ME AN EMAIL INSTEAD OF A WORTHLESS RATING.

Got assigned to fix a bug in a validation function that would always return true even if the data is invalid.

I looked at the code from the function and noticed that the only line of code in the function was "return true;"

Apparently, the programmer who wrote this function a few years ago got fired and no one ever finished his work.

Now it amazes me that no one ever has looked at the problem and just assumed it would be a complicated bug.

Spotify in India??? Seriously?? Is it a bug or have they released it silently??

Rant! I found a bug in payment provider's api. The bug involves sending an invalid (!) Stripe ID to that API, (which I send on purpose btw) Which causes a complete white page when you login to their systems and view the details of that customer. Btw the API will accept that invalid Stripe ID without questioning and returns a 200 status code back.

So I send a mail to there support saying "look I found this bug by accident, this is how you can reproduce it"

And the support team send me a message back saying "then don't send an invalid Stripe ID"...

You don't freaking say... *sigh*

Every week is the same. Wake up, new jira ticket. “Build us a pink house”.

*i build a house*

Next day, “URGENT BUG REPORT!!! CRITICAL ISSUE IMPORTANT IMPORTANT IMPORTANT”, click on ticket, “bug report: the house doesn’t have sprinklers”

They didn’t ask for sprinklers. This is not a bug. *i add sprinklers*

Next day, “URGENT BUG REPORT!!! CRITICAL ISSUE IMPORTANT IMPORTANT IMPORTANT ASAP ASAP ASAP”, click on ticket, “bug report: the house is pink.”

HOW IS THAT A BUG TWO DAYS AGO IT WAS LITERALLY A REQUIREMENT

Meanwhile management makes triple my salary

Wait, there is a bug in high sierra making it possible to log in as root without a password. What the fuck? How does this shit even happen?

If you notice a bug, but the client hasn’t seen the bug, is it really a bug?

Finding the bug. The usual flow:
"Omg! I think it's a bug in the compiler"
10 minutes later:
"OK, it surely is a bug in the runtime"
20 minutes later:
"I'm certain this is a bug in the core library"
2 hours later:
"Oh, it's a bug in my code. Again, as usual, I'm the idiot. Stupid world."

My Boss: When are you going to finish?

Me: There is a bug, I'm solving it, I need more time.

My Boss: Why have you introduced a bug in your code and now solving it? It were more simple if you didn't created any bug!

Me: WTF!!!

All the ++ counts are showing in binary... If this is an error I vote we keep it as a feature not a bug.

I bet everyone here knows these two situations:

1. You have a bug, show the code to somebody else for debugging and the bug is gone, but as soon as you're alone again, it reappears.
2. Your program works fine, you want to show somebody what you accomplished and...
IndexOutOfBoundsException: The index was outside the bounds of the array.

I live in an apartment building that has about 20 floors. About once every month, I'm either waiting for the elevator or in it, and the floor indicator display flashes "14" very quickly no matter what floor the elevator is actually on. Whenever this occurs, it's always 14 that gets shown.

This has made me think about what this bug looks like and if it will ever be fixed. Will they ever update the firmware in the elevators? Is it a software issue? It could also be a hardware problem. Either way, every time it happens I think about it and if this bug will ever be fixed.

I've decided to call it the "phantom floor 14 bug."

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...)

- 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

Stakeholder: There’s a bug on the site.

Me: That’s not a bug. The site is supposed to do that. Your team asked for that feature and we implemented it last summer.

SH: They did?

Me: Yes, they did.

SH: You sure it’s been like this since last summer?

Me: YES!!!

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.

Having to deal with stupid testers who think your app should be resistant to water and black magic and report a bug if it is not

Taking "fixing a bug in your head once you walk away from the machine" to a new level.

Fixed a bug, checked it in. Happy.
Go to a meeting 5 minutes later. 10 minutes into the meeting have the sudden realisation that the bug fix was wrong and while it would fix the issue it would break something else.

Anxiously sit there for 50 more minutes not really paying attention because all I can think about is that sucker being auto deployed to our Dev server.

Managed to fix it and get it committed without anyone noticing but FML.

If I flag a bug on your PR don’t fucking do this:

if (bugOccurs()) handleBug()

Fix what is causing the bug, don’t bandaid it.

Manager: wElL yOu NeEd To ExPlAiN tO tHeM eXaCtLy HoW tO fIx It, hOw ArE tHeY sUpPoSeD tO kNoW?!

Dev: …

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.

The security blog is up again, I fixed the bug.

Just wondering, why did it work in the first place? I simply required a composer autoloader twice but I've been doing that from the beginning and it didn't play up until last night...

I guess it shall remain a mistery 😞

Hunted a bug for 8 hours, thinking it was a problem in my code....

Found out it was someone else's code generator that injected the bug...

Contacted the concerned dev... Had to convince him for another 3 hours that it was his change to the code that caused the issue. He is still sure that his change can't break the code...... What the fuck are you..? A fucking God programmer who never makes mistakes??

I mean how hard is it to just accept when I just proved it to you??

Most coders think debugging software is about fixing a mistake. But that’s bullshit. Debugging is actually all about finding the bug, about understanding why the bug was there to begin with. About knowing that its existence was no accident. It came to you, to deliver a message, like an unconscious bubble floating to the surface, popping with a revelation you’ve secretly known all along.
-Mr Robot

So they discovered a small tiny bug in a thing anyone last touched about 3 months ago. It has been there for at least 6 months, and JUST NOW someone noticed it. But OF COURSE that bug is important enough to have me drop FUCKING EVERYTHING that I'm doing, despite us being very short on time already!

Fucking hell, if nobody noticed that shitty little crap bug the past 6 months how can it possibly be so important. Good thing I don't have a large wooden mallet nearby.

So thanks so much for having me fix this RIGHT NOW, or rather IN THREE FUCKING HOURS or however it'll take to set up this project's dev environment... absolute horseshit.

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

So I remember this QA I had for our thesis and the panelist asked me
"So is it a bug or a feature?
i answered
"Yes"

Me done fixing a bug.
Me commit the fix.
Me resolve issue in JIRA.
Few minutes later, Me receive a notification. QA reopened issue: "Bug is still there".
Me go have look to Jenkins.
Pissed off, Me respond to QA: "Can you just wait for Maven to finish building the goddamn thing before testing it please?"

Every. Fucking. Time

Testing demands a “bug” fixed. It isn’t a bug. It is a limit where as the amount of records updated in a single request overloads the RAM on the pod overloads and the request fails. I say, “That isn’t a bug, it fits within the engineering spec, is known and accepted by the PO, and the service sending requests never has a case for that scale. We can make an improvement ticket and let the PO prioritize the work.

Testing says, “IF IT BREAKS IT BUG. END STORY”

Your hubcaps stay on your car at 100km/h? Have you tried them at 500km/h? Did something else fail before you got to 500km/h? Operating specs are not bugs.

I write blocks of code like this:
If(condition){
code
}

I'm trying to fix a bug and the previous dev is doing it like this:
If(condition)
{
code
}

Does anyone know any good nerve calming pill ? 😜

Why does it take a client, who needs the bug fixed immediately, over 24 hours to respond to my query about what the problem is?

Out of all the bugs, the most annoying are the ones that come out and make me say "WTF?!?!? WHY THE FUCK HAS IT BEEN WORKING FOR THE LAST 2 YEARS??!!?!!??? THERE"S NO WAY IT COULD HAVE!"

When the bug surfaces, you investigate and see that it indeed IS a bug and there's no way it would ever work w/o a fix. But then SOMEHOW it's been working just fine for years....

It's like server elves went on strike and said "no more, it's enough covering that bug - it's time you fix it, lazy-ass idiot!"

a missing semi colon is overated, the white space character at the end of a string is the real OG. Been hunting a bug for three days because of it!!

QA : There is a bug, come at my desk now !
Me : I'm busy on some feature, can you make an issue on Jira I will fix it later.
QA : NO! It's a major issue
Me : Ok... I come.
* 3 hours later *
QA : I just created you the Jira you asked
Me : I told you, the bug is already fixed since 2 hours
QA : yeah but I will not test it until you mark the issue as done on Jira

.... Are you kidding me ??? So you interrupted me in my work two times for one stupid issue...

A bug is never just a mistake. It represents something bigger. An error of thinking. That makes you who you are.
-ElliotAlderson:

Just about to start a milestone presentation, when suddenly the boss froze and yelled:

"Wait! Don't move! There is a bug, let me take it back to nature where it belongs..."

*Grabs a bug on my shoulder and carries it to the window*

"I keep complaining to you guys every day about this bug and nothing happens!"

Firstly, it ain't a bug. Secondly, you're not complaining, you're whining. Thirdly, complaining is a bloody limited resource. If you do it once a year, everyone's going to sit up and take notice. If you do it daily, it's just "Duncan having another moan", and the only thing anyone will do is play "what time of day will Duncan rant" sweepstakes.

Is it just me or is there a bug in which the clear button disappears at times?

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

Description of a Bug in JIRA:
Hi guys, there is "another" bug :-))))))!!!! :-((( with the customer list:
- The list of Customers (**which one? we have 4 fucking lists **) is sorted by Name, not by Birthday date (**wait, it's a sortable table, with a sortable name, city ,zip column, it's not sorted by birthday because the birthday column was not even required **)
- If I click on the details I see some data missing (**which data? which customer? there are thousands of them and most work**)
- In addition the arrow on the right is too small, can you make it a little bigger (**excuse me**)?
- I also need to export everything in excel.

Categorised as: Bug

Moron. You are part of a League of Morons...

I love it when adding a breakpoint fixes the bug...

I have no clue what is happening...

It's not a bug if a feature is working how you told me it should work but not how you wanted it to work.

When you have a huge project, and encounter a bug, but don't know where it is, and why it is happening...

Coworker made a tool to automate part of our job and she sent it to me. After 5 seconds of using it I found a bug... she has been using it for weeks. Now I don't trust anything she has done around here. (It's a financial tool and the bug is changing certain numbers to negative so it subtracts instead of adds...)

Overheard a conversation between programmers:

.... Your dirty hack finally caught up with you!
.. it is responsible for bug A, B , .. E ... F..

That "temp" code was not touched in years.

Mom: what is it you do exactly?

Me: I make web sites and test computers for bugs.

Mom: What is a bug?

Me: it is when a program does something you do not want it to do.

Mom: k, I don't understand how money is made in that. But, you know (random store) is hiring.

I'm struggling with a bug. It's not my bug, it's in a lib - in an assembly function commented as "this is where the magic happens". After 27 hours of trying to determine what triggers said bug my best guess is it's a relationship between the position of Mimas and the mood of my neighbour's chonker. If it's not triggered by the Saturn's moon and a pet animal... I'm out of ideas.

Now how do I break it to my PM that we have to kill a cat?

"Most coders think debugging software is about fixing a mistake, but that's bullshit. Debugging's actually all about finding the bug, about understanding why the bug was there to begin with, about knowing that its existence was no accident. It came to you to deliver a message, like an unconscious bubble floating to the surface, popping with a revelation you've secretly known all along. A bug is never just a mistake. It represents something bigger. An error of thinking. That makes you who you are. When a bug finally makes itself known, it can be exhilarating, like you just unlocked something. Because, after all, a bug's only purpose, it's only reason for existence is to be a mistake that needs fixing, to help you right a wrong. And what feels better than that? The bug forces the software to adapt, evolve into something new because of it. Work around it or work through it. No matter what, it changes. It becomes something new. The next version. The inevitable upgrade." - Elliot, Mr. Robot

I like how in every other profession if something doesn't work it's called a mistake or a fuck-up but in software development it's called a bug and it is absolutely expected.

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.

One of our customers calls everytime when he thinks he found a new bug. Then he literally yells "I found a new bow" since he thinks "bug" is a german word, so emphasizes it like that. In german "bug" means "bow of a ship".

Dear people who leave bad reviews...

Do not use a review as a bug report, saying something crashes on your device and telling the developer to "fix this" isn't a review.

It is barely a bug report but a review is on quality, not individual issues .-.

Just used my first "It's not a bug, it's a feature" explanation 😂. However, the irritating part is, I had to explain it to another person from IT industry (I mean testers) who is from another company.

And it's really a feature and not a bloody bug. Stop reporting it on the bugs list 😥

Devs: We fixed a bug, so watch out for some changes.
Management: The new values are too bad, you need to change it back.
Devs: But ... it was a bug?
Management: Rollback ... now!

I swear, the moment shareholders are involved, management is just about who has the best lie.

Tldr; my "this is not bug, its a feature" moment actually turned my bug into a feature.

Today we were presenting a project which has imposible deadline. I am developing this small project alone (which is probably good). I implemented core features first but I know project still have bugs and a lot of tech debts. Another friend started to presenting our demo and a wild bug appeared as expected. He was adding rows to a table. To add a new you gotta open new modal by clicking + button and fill the form. One of the fields had a bug. When you add row by clicking Ok button, the value of the field stayed there after you open modal again. So its basically a state problem in React. I forgot to clear previous state of modal. When they see that and my friend said "oh we got a bug there". Then I enabled my mic and said "thats not a bug, thats a feature. I didn't want to enter that field again and again when I adding multiple rows and made it persistent." and you know what? They liked the idea! They requested to add that bug to two more fields. I was just joking and my "this is not bug, its a feature" moment actually turned my bug into a feature. Instead of fixing it, I'm creating more of this bug. LOL!

The 8 year old is learning Python, and after a dealing with a syntax bug she asks: "If the computer knows I'm missing a semicolon here, why won't it add it itself?"

I don't know. I really don't know.

??????????????????? What??????

???? What???????

I couldnt solve a bug for hours.
Hours of googling.
Hours of mental trainwreck.
Hours of stress.
1:28 am.

I cant solve it.

HOLD ON I HAVE AN IDEA.

ChatGPT AI. HELP ME.

i copy and pasted the part of code thats bugging me. Keep in mind that this is a VERY large and robust system and this is just tiny percentage of code.

I told the AI to help me fix this shit bug.

ChatGPT literally explained me what the bug is as if im retarded and wrote code how to fix it.

LOOK AT THE SCREENSHOT U CANT EVEN MAKE THIS SHIT UP

HOW????

Noticing a bug once or twice but not being able to reproduce it after that gives me anxiety. This job is detrimental to one's mental and physical health. Serious question. How to unfuck yourself?

These rare moments when you realize:
"it's not a bug - IT IS a feature!" o_O

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"

One of my biggest pet peeves is when I see people say shit like "fix it now" when a bug pops up.

Like bitch go fix it since you're such a fucking intelligent individual. You can't? Well then, shut the fuck up and let them fix it. They're human too, ya know

I been seeing spam on devrant lately. It is usually a new account which only have 1 rant (a spam)

Maybe devrant should include some kind of "Are you a developer captcha" which make you fix a bug before creating an account.

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 :)

I love it when rather than fix the bug that is causing the faulty data you write a bot on a schedule to clean up the faulty data. It's like a bot battle who can mess up / clean up the data the fastest. Unless your clean up bot has a bug then you are just F'ed.

@dfox just noticed a bug (or is it a feature?)

If you happen to double tap a rant slow enough that it doesn't +1 it. But fast enough that the rant view isn't opening yet it seems to register two single tap events and opens two views, needing to go back twice do return to the feed.

Not sure if that's important enough to report as a bug. :)

Ps: I'm on a LG G4, android 6.0

People on devRant: "it took me 1/2/3 hours to fix that bug, omg, what a time waste!!"

Me: *wrestles some bugs for 1/2/3 DAYS*

I'm confused, how is fixing a bug within hours a ranting material...?

The new version of the (unofficial) client (now UWP and with "Stories") for Windows 10 is here... but I can't release it due to a Microsoft Store bug... 😢

Hope to see a Microsoft fix soon, because I can't wait to share it with you! 😝

-Is it a bug or feature?
-No.

When your app is in internal testing and you tell them specifically "this part won't work in test" .. Then 20 minutes later you get an email about it as a bug. 😞

I spent two days in a row fixing chairs at work because our whole dev team was waiting for issues (which means helping QA team and playtesters testing the whole game).

Just when everyone left and Im standing up to go as well a playtester comes up with a release breaking bug in the handwriting recognition code...
Since this game is build for a charity which will release it in a country at war we cant push the release date.

Guess who is making overtime trying to fix this bug?

When you have a bug that only comes up randomly, try a fix, after 100 tries, appears it is working, push, same bug pops up.

I promised i'd be home at 18:00
We discovered a bug at 17:30
We need to have an output for tomorrow
The process takes so many hours so we need to fix this bug before leaving so it can run all night long.
It's 19:06

Wife is gonna get mad...

No one is complaining about the bug anymore, it is no longer a priority.

Sleeping the Thread for 1 sec, because the database had no real timestamp and a transaction on the same item within the same second would lead to a doubled primary key...

No real feature, but it is a bug and this makes it a feature I guess.

If Android phone has a bug and doesn’t receive fix: nobody cares

If iPhone has a bug and Apple fixes it after 2 days: WOLOLOLOLO, APPLE SUCKS! THE END OF APPLE IS NEAR!

[Applies for RedHat OpenShift Beta on April]

this will be lit I said, since I was quite a bug reporter for Eclipse Che/Codenvy

[Took me until november to open up a ticket so they can take me in]

oooh shit this is lit

[Starts an Eclipse Che Workspace]

huh, why isn't it provisioning?

[inb4 OpenShift devs says its both a OSIO infra issue and a known bug in the OpenShift panel]

oof.

[Makes it work using workaround]

Woo this is gon-

[Haha no, Too Many tedirects for you]

REEEEEEEEEE

Conclusion: Openshift.io is a lit platform, it just happened to be very VERY beta.

I like the kubernetes "pods" tho

When you realize that the bug is happening because you copied your own code and forgot to replace some variable after you pasted it... Damn you brain! Do not copy/paste ok? Or I swear I will drink a lot on Friday....

A bug? Heck no, it is an awesome feature

I just want to make it clear to all of us here...

Not every goddamn thing is a bug from X or a bug from Y most of the time I, Us, We as programmers fucking make mistakes or don't know the issue because it's vague!!! IT'S NOT A FUCKING BUG!!!

When there is a hard high priority bug come up and someone on the team assigns it to themselves and writes on JIRA: "I volunteer as tribute".

This is what my iPhone seems to suggest in most locations. I don't have a problem. It must be a bug.

Client writes a bug report: This and that doesn't work.
Me: This functionality never was implemented. Please open a feature request.
Client: But this is a bug. Without this feature, the service won't work as we expect.
Me: But this wasn't in the requirements for release. So you have to contact the PM for a feature request.
Client: THIS IS A BUG! FIX IT!
Me: GO FUCK YOURSELF! THIS IS A NEW FEATURE AND YOU HAVE TO PAY FOR IT!
Unfortunately, I never sent the mail. But I kept it in the drafts. Maybe someday...

Lets play a game of spot the bug...

Too easy you say?
What if I told you that this code was written by a well paid dev over an exceptionally large period of time?

Crazy huh, but that's still nothing. The most ludicrous thing about it - is that you (like me) probably suffer from a mild case of impostor syndrome.

I just ended that suffering. The only thing worse than impostor syndrome is believing you actually know what the fuck your doing. Keep it in check but learn to love it... it's probably the reason you could spot the bug after all.

Is it a bug or a feature?

> Client complains acceptance testing is too expensive and that he'll do it himself.
> Client complains acceptance testing wasn't thorough enough when a bug hits production.

Got a weird bug report, 6 red bull later i'm a energizer bunny on speed. But have found and fixed a severe underlaying bug. Can't believe noone had noticed for years.

Now i'm afraid to report it to my boss cause it most likely costed us a lot of money over time. And I just got shafted in the pay raise so my loyalty is low.

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.

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.

Code is sat in UAT for a month and no one looks at it. Two days before the (completely arbitrary) go live date and testing commences, finding one bug which is immediately fixed. And now I'm the one allegedly delaying roll-out. Err OK...

Is it just me or devrant has a bug of showing false notification badge?
It's stuck on this number even though I don't have any new notifications

Fuuuuckk. My phone made a video whilst being in my pocket. Google photos uploaded it... Now I'm 2GB over my data bundle limit on the 3rd of the month.... 😑

Apparently the android function "auto-disconnect from network" has a bug, which is gonna cost me

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!

Client: it's not a feature it's a bug
Me: comparing with the old system and proofing that it is currently definitely working like it did in the old system
Client: I didn't instruct you to check the old system

Wtf?

a quick 'bug' fix to my laptop...

Wonder if anyone can detect what it is...

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

I cant believe im crying while coding because i cant fix a bug. Is this a mild reaction of a burnout. Instead of giving up I'm literally crying and i cant control it. Good thing im alone in the room so nobody can see me

Tester raises major "bug" about fundamental part of the system 1 week before sign-off....
What was it you ask?
"This field is validating my input and is showing an error"...
Me: "But sir, you have pasted text into a number input!"

I just noticed that the about page doesn't go all black. Is it a bug or is it intentionally left that way?

Everything works fine until your manager starts looking at your code and all of a sudden your screen starts interacting with your manager- "Here is a bug there is a bug and you have got a lazy developer who ignores me like a dumb."

And I am here like wtf ... Wasn't it working fine earlier...

Manager in anger... Me in shock and code is totally in revenge mode...

Oh god... turn this Monday back to Sunday!!!

Scary Monday story begins....

All things have ends. Nothing lasts
If I am currently sad, this situation will pass.
If I am currently happy, this situation will pass too.

If there is a bug, boss like shit.. it'll pass, it doesn't deserve to be that sad ans depressed..

If there is no bug, and the work is perfect.. it'll pass.. there will be moments when sadness come..

it's just everything is going, nothing deserves to be sad or that happy.

i have been working on a web-based game and this is my daily routine (also i listen to rock and metal)

college to home to coding
thinking
coding...
looks like theres a small bug
shouldnt take much time
maybe this can work
*screaming*
i am not the first with this bug *here i come stack*
dont do this to me stack... theres suppose to be a fix for it
*extreme head banging*
F*** it
*changing songs*
nope this not helping
F***
F*** THIS SHIT
*rhythmic head banging*
oh god kill me
F***
am i really that bad
*autistic screaming*
humming song instead of thinking of bug
(8 - 8:30) me: mom i am hungry
this shit is taking toooo much time
*high intensity screaming*
F*** you bug
coding, its not form me
*surfing devrant*
*felling i am normal*
(10 - 10:30) mom: when are you eating
*high pitch screaming*
i am leaving coding for sure now
its too late time to sleep
fml its late again, i am gonna miss the first lecture again
back to coding

A thousand year later...
Bug status: Still not fixed

Right now, I'm tracing a bug that causes some of our data to be lost.
and I found a table with 'xxx' field on it. ohhh. what is it for?

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.

Last sprint is a mess.

Working on three products that are related one with another a little bit.

1. Bug reports are coming in;
2. We fix it and give for QA to test;
3. QA starts testing and it doesn’t work;
4. Because another team updated something in product A and product B depends on it.

Repeat for straight 14 days

Developing in your local environment? A few bugs here and there. Deploying it to production in a completely different environment? The whole app is a bug...

Most coders think debugging software is about fixing a mistake, but that’s bullshit. Debugging’s actually all about finding the bug, about understanding why the bug was there to begin with, about knowing that its existence was no accident. It came to you to deliver a message, like an unconscious bubble floating to the surface, popping with a revelation you’ve secretly known all along.

-Mr Robot

Anybody encountered any bug you have been searching on the net for hours and it is like a nightmare for you.. then your friend comes and fixes it for you in seconds.. and then you just feel useless :(

Can someone please write a plugin that automatically translates bug tickets into startup-ese? It would make it very easy to present the most common offenders to higher management on quarterly reviews.

Example:
-
$< "screen A is all messed up"
$> "We are disrupting the establishment in screen A"
-
$< "API B is not responding, giving timeout errors"
$> "We are facing logistical challenges in API B"

How hard is it to make a git GUI that is 1) pretty 2) not sluggish 3) bug-free?

Do you know guys why a programming bug is called so? It's because the very first time a software crashed it was because of a bug ( a real bug stuck in a bus on the machine!) That caused that 😂 imagine if something else was stuck instead! Like someone's​finger : hey I fixed that finger but still got 2 critical fingers and 4 small ones

Devs! Heard about this thing called going to sleep without dreaming about ways to fix a bug?

Whenever I force myself to sleep whenever I get stuck on a bug or confused about the implementation of a feature and started dreaming about the approaches I can take. Most of the time I wake up around 2 or 3 am to try out an idea I had and most of the time it works.
Now I fear this is becoming a habit. Is it something I worry about or ignore since my problem is getting solved?

So what's up with some devs, QAs and managers that create bug tickets with little to no information on what is the actual bug? I can semi-understand in the case where you document it only for you to read later.

Fuck you if you think that a ticket with only a title saying "fix all the bugs for this release" or "this feature is not working" is an appropriate way of documenting a bug.

Fuck you even more if when you are being asked to provide more info to reproduce the issue so someone else can actually be sure it is fixed or not (environment, steps, expected result, actual result, etc.), you simply say that you don't have the time for it and documenting tickets is a waste of time.

Hiring YOU was a waste of time!

coolest bug our team had was not a actually a bug but a feature that is misused and abused.

tldr: its a feature that became a bug

we have an app that has a "test print" feature to test the printer and the format of the document to be printed. it has the word TEST for fields and all that.
it became a bug when suddenly, the users use that feature to print documents, instead of using the app with the business rules and all, and just manually strike off the TEST words with a pen.
the feature became a bug because it has become a security risk.

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.

>makes a bug report about the JS linter in Eclipse Che not working

> makes it a P2 bug (moderate severity)

> confirms in their current implementation it doesnt work

> escalates to P1 (high severity)

wow for once Eclipse is actually making their shit better

jim :"this is not a bug.. you just can't use localhost for developing on your machine.. it is forbidden.. things break"

So we have this really annoying bug in our system that customers keep complaining about. I've explained in detail, multiple times, why the part they think is a bug is not a bug and the workaround they keep asking me to apply doesn't make sense, won't fix the issue, and won't even stick (the system will notice that the record they want me to delete has been removed and it will repopulate itself, by design).

I've told them what we need to do as an actual workaround (change a field on the record) and what we need to do to properly fix the bug (change the default value on the record and give proper controls to change this value through the UI). We've had this conversation at least three times now over a period of several months. There is a user story in the backlog to apply the actual fix, but it just keeps getting deprioritized because these people don't care about bug fixes, only new features, new projects, new new new, shiny shiny new.

Today another developer received yet another report of this bug, and offered the suggested workaround of deleting the record. The nontechnical manager pings everyone to let them know that the correct workaround is to delete the record and to thank the other developer for his amazing detective work. I ping the developer in a private channel to let him know why this workaround doesn't work, and he brushes it off, saying that it's not an issue in this case because nobody will ever try to access the record (which is what would trigger it being regenerated).

A couple hours later, we get a report from support that one of the deleted records has been regenerated, and people are complaining about it.

🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄

When QA keeps on filing bug but you go and check and it's a feature.
No. Seriously IT IS a feature.
Like c'mon! I told you it is a feature. Go and check sys req!
What is wrong with this world? >.<

GIT LOG VERSION 110
---------------
a9c2934 I don't believe it
fb8d2e6 I am Root. We are Root.
6be9078 FINALLY FIXED THE FUCKING BUG IN THE CODE, DO NOT EVER EVER FUCK ME AGAIN YOU MARON
3d08a88 THIS IS THE FUCKING WORKING VERSION
013faed THIS IS NOT WHAT YOU ARE LOOKING FOR, GO TO A PREVIOUS COMMIT
af5d013 We'll figure it out on Monday
49e238b de-misunderestimating
a40351b happy monday _ bleh _
a5f345d Fixed unnecessary bug.
485a26a pay no attention to the man behind the curtain
c4fcbde s/import/include/

lol nvidia-bug-report.sh

it collected an xorg log that is not the current one.

For some reason, my arch openbox logs to $HOME/.local/share/xorg/Xorg.0.log.

What a goddamn trainwreck. I'm not necessarily saying it's nvidia's fault. But it is a trainwreck.

When QA isn't smart and you spend way to much time talking and in meetings.... "Listen, we are only testing for new bugs related to this fix, if there is a pre-existing bug, document it and move on".

QA finds a pre-existing bug and stays fixated on it for 3 days....

I don't understand some developer's thought processes when they fix a bug/issue.

Let's say the error is -> "Cannot read property id of undefined".

My first thought is to add a check for undefined and null and figure out if further code should be executed if a null or undefined is encountered, depending on what the code is supposed to do.

But some devs are like, "Yesterday the sunrise was at 5:30 AM, Earth's rotational axis is titled at 15 degrees to the left, My aunt asked me about how I am doing today, so therefore the bug fix is required at line 65,456 of this particular kernel file".

And they implement it, and it WORKS.

Weird.

every bug is a feature if it is unfixable enough

>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

I like our daily stand-ups, but our team only does it when our scrum master is present, if he takes a day off, no one cares about it
I think it's healthy for scrum teams to have that every day

What do you guys think? Are you also doing scrum? How bug is your team?

Is it normal to be frustrated when you can't solve the bug for a day and all you can do is update on what you've tried solutions?
3 months in this company

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?

Why do people put "!rant" at the beginning of their rants? Is it a bug?

Happy days, yesterday we updated form 16.3 to 16.4 and thanks to them fixing the bug in 'getDerivedStateFromProps' my broken code is now breaking.

Don't you just love it when features inadvertently depend on bugs. The entire component ONLY worked properly because of a react bug.

So my boss thinks of debugging as a guessing game. As in you just say random things that have not even the slightest relation with the code where the bug is ... now i know why it take days to fix a little bug...

Your Telerik Kendo UI has a bug? I can fix it. It shouldn't be difficult because there is just so much support and documentation.

@DFox @trogus found a bug- not sure how easy it will be to fix... if you change your username, mentions in rants and comments still have the old username which will be confusing for people trying to figure out who the mention is for.

Is it possible that on editing a username, all mentions in all comments and rants are renamed as well?

Today I heard my first "This is a feature, not a bug" from a enterprise which gives us a SaaS.

They were damn serious, and never in my life I wanted to punch an IT guy so hard in the face more than today

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.

Sometimes I think that my computer is possessed.

The story goes like this (typical): adding a new feature creates a bug with something that worked perfectly until now. I find and solve the bug in a few minutes. Now the spooky part: with that sort of bug, even the code that worked up to now shouldn't have worked. But it did. Does someone knows a good Ghostbusters service?

Designed and implemented a bug tracking service for the team that I was working, even now everyone is loving and using it.

I'm at DreamHack Dallas, and I just saw a guy at his booth open Unity, fix a bug, and rebuild the game.
No judgment from me brah, I get it,
but it is nice not to be my broken demo for a change.

MSG for dfox and trogus
Hey guys, have you seen my bug reports?
For all the others.. Do you have a bug where your app crashes when uploading a IMG from Android or is it just me?

When a tester found a bug that you never think of and you cannot reproduce it. What is your response ? 😄

Is anyone else having issues with TutaNota?
I haven't been able to use it for a week now. 😕

(Yes, I've submitted a bug report or six.)

Not a specific bug, but I always have that satisfactory feeling when I fix a bug inside a code like this:
1. Spaghetti af
2. Duplicated af
3. Heavy use of static fields instead of passing via callback when required
4. variable names like: textbox1 ..etc.
5. No comments

It is true that is a huge pain in the ass to deal with, but then I look at it as I was able to create something out of that mess, I mean all is mixed up nothing is clear, no clue where it starts and what caused it, but then I put the pieces together and end up with a solution of what I thought to be: It will never be solved when that mess is here.

Not an excuse for messed up code, I try fixing whenever possible, but hey, at least I did not run away and give up

MFW

me: debugging an issue from a customer for three hours and ask my colleague for help

him: oh, that's not a bug, it is a user error

me: 😶

As some of you might know I am currently working in a QA Team.
One of my "colleagues" asked me to help him with the automation of a simple page.
The tool we are using could not determine if a checkbox on a mask was checked or not so he decided to open a BUG!
This is not a bug the page is working fine (the checkmark is visible and the server handles the data correctly)!!
When I asked him why he opened the bug he said "Because I want the developer to make that easier for me!!!"

WTF This is your job! JUST GET IT FUCKING DONE!

I work my ass of to close the gap between testers and developers...

BUT IF I SEE THINGS LIKE THAT I UNDERSTAND EVERY DEV WHO WANTS TO PUNCH HIM INTO HIS FACE!

Here’s a snippet of code that I found in our production codebase. I found this while fixing a bug. This is not part of the bug though but I see this a problem. Should I say this to my senior that his logic is off here?

First he doesnt have to do explicitly strict comparison since the return type is boolean and it could be true or false. Also the returnUrl will alway be undefined because redirectIfUserLoggedIn is called first before it was set.

He dosent like me. Hell get mad for sure. I think ill let this go.

The tags disappear from your drafts.
Anyone else experiencing this ?

Also I can't scroll through the tag suggestions.

Is it a bug or a feature ? @dfox
(This still happens even after updating the Android App)

I'm using a Lenovo device with Android M.

When something finally works as expected but it still looks like there is a bug.

Windows 10 insider preview had a critical bug like half a year ago where most browsers would freeze the PC. I've reported it multiple times but my feedback didnt get any attention. The bug made it to production months later...

Now, the story is repeating. I've discovered a bug. Everytime there's a software update for apps that with a built-in updater in the main .exe (JetBrains IDEs, VS etc.) the updater fails, program is corrupted and needs to be reinstalled. For instance, there's a minor bump in Android Studio version, if you try to use autoupdater it will corrupt your Android Studio and you'll have to reinstall.

Been trying to reach out to them but the only "real issues" that are highlighted are "no CPU temp in task manager" or "pls improve automatic problem resolving"

Why the fuck do you even have a feedback program if you're ignoring the people who are reaching out to you, you pieces of shit

If a bug is logged don't mark it as resolved unless you commit that resolution.

Also don't mark it resolved without at least a one-liner of the fix/expected behavior.

Soo insyde BIOS got a big bug via 17.10 ubuntu iso
- Settings not getting saved in bios
- USB booting is a no-go.
- suspend never wakes up without battery removal
Infected systems mostly include acer, LENoVO and hp mainly

I am surprised it took them this long to notice the bug.

Is it a bug ,if you have the hairstyles which I have kept on my avatar, you can't have facial hair? Really devRant? I'm the living example and I have both

when viewing a profile and scrolled down enough to hide the avatar and the user description, it does not show up back again when scrolled up... is it a bug or a feature? 😂 @dfox

The iOS DevRant app is so bad, sometimes it just crashes when I try to open a rant... wth DevRant how can you fuck this up so badly?

I submitted to the bug reporter many times and they don’t do much...

Hate those bugs, where you stumble upon a fix but have no idea why it fixes it or what is causing the bug!

This is just a sweet little harmless block of code, why should I unit test it?

3 months later...
Bug in production : This is why.

"Write the failing test first."

Oh, I know. This is probably simple, but when you're stuck on support tickets - there's no faster way than to write a test for whatever the issue is and run it.

You wind up having a quick way to verify your bug fix and you now have a test going forward to ensure the bug never happens again.

Has to fix a bug in our old products web interface, how did I ever put up with it. In some places it has 7 nested iframes. It is also some of the worst code I have ever seen, no user input is sanitised plus there is no structure to the code, try looking for a CDs element without going into chrome dev tools is impossible as there are 52 separate CSS files

When you have a bug filed for a feature you created to spec, questions it, and then they state the the bug shouldn't exist as it is "common sense" even though it's not in the spec.

What is it with wget and repeatedly getting this odd bug where it segfaults or passes invalid sizes to free() or malloc() when you resize a terminal it's running in? For fuck's sake

@dfox
I recently posted a rant containing the tag "$" (php, you know).

But if I search rants with the search pattern "$", the search returns no results.

I guess this has something todo with $ as a special character ;)

Is it a bug or is it a feature? *g*

When IT is like : hey our new grafana is at this place "some URL"

I submit a bug ticket: "I can't see metrics about this server that has been running for a while"

Their comment on the ticket : the URL to the old grafana

Me: There is a bug in the most recent "standard global software" release that causes data not to send properly to the device. There are 3 ways to send the same data to the device in the current release but they apparently don't do the same thing like they should. (Sent screenshots of the issue)

Standard Dev Support: "it's not a Bug it's a feature. So the development found out, that there are several problems with sending data to devices using "x" method. So they decided to stop "x" function in the latest release. Use "y" method instead."

Me: "X" and "y" methods are both still there. You didn't remove it in the latest release. So it is a fucking bug moron?!?

Wtf!!!!!

pros of working on a full C++ project:

Time to browse XKCD while it is building to fix a small bug my predecessor made.

Working on a bug that in my opinion never worked. “Sr. Dev” dares to say the function has worked before. I’m a 100% sure it never did.
“Yes but everything is being tested before we go live.”

Dude, we have a monkey testing our stuff are you serious!?

Colleagues find it weird how happy I can be when a bug is found in my code in development phase.

Trying to find if there is a bug on Devrant.
I'm calling the herd (meaning a group of Devranters I added on a list for a specific topic).
If you are on the list and didn't receive a notify, please tell me so I can report it.

when the website is so huge and a bug is causing every to be delayed a minute before loading, the debugger isn't showing anything, and the project lead's best solution is to throw more RAM at it

Is it a Bug or a Feature?
Why am I seeing all the ++ scores in Binary?

(I Checked, those are up votes in Binary)

Devs are you drunk? Or is it April fools?

EDIT : steps to reproduce
1.open devrant app
2.click on any rant that appears in the feed

Is it just me, or does everybody regularly have to hit F5 on YouTube after the first 3-6 seconds when it stops playing? I have this in one out of 4 videos I think. hugely annoying

The weird thing about it is that I remember YouTube having this bug for a few months back in 2013 or so (hence the 'is it just me'? )

So I got assigned to this project last week to help other developers to remove bugs from a android app. First bug I have to deal with: field that should only accept integers is accepting other characters and thus crashes the app.

Alright seems like a simple bug to get into the project and Xamarin. So I set some break points and find the bug: "uncaught FormatException on line 789 Convert.ToInt(string, v) .

OK then, implement some try-catch and add a warning message to the user.

let's try it out... alright, message works, close message and app crashes

-Tsc... dammit

search for the bug in code... "uncaught FormatException on line 899 Convert.ToInt(string, v)"

what the...

wait a minute, ~ Ctrl + F ~ - "Convert.ToInt"

17 matches on file

oh fuck me...

Ohhh 😲😲😲 are you kidding me ? xxx TB !!!!!! 😅😅😅🤤🤤

IT must be a bug or is it really my usage !!? 🤔🤔🤔🤔 let me investigate 😂😂😂😂😂

Is it a bug if a user tries to do something they shouldn't be able to do and the program stops them but doesn't give an error message?