Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "bug fix"
-
When you "fix" a bug not by actually fixing the bug but by disabling the user's ability to cause the bug.13
-
"hey there is this bug, could you fix it?"
me: sure whats the bug?
*explains the bug*
me:... thats.... thats your feature request from last week8 -
*alright,let's go to bed now*
*finally in bed and about to sleep*
*figured bug out in head*
*gets out of bed, fixes the bug*
*gets back into bed*
.
.
.
*heeeey wait, if I do it like this.... *
*gets out to fix second bug*
*back to bed*
.
.
*Hoooold on... *fixes third bug while laying in bed**
*really has to go to bed now 😩*28 -
Start coding for work this morning, immediately notice a ui bug, ugh. Want to get cracking with another bug I'm supposed to fix.
Fix the bug, and it incidentally fixes the other bug. Two in one.
*Suspicious*4 -
That moment when you've been trying to fix a bug for hours then suddenly realize you've fixed it hours ago but just didn't clear the cache5
-
Every time you squash a bug before someone else even sees it...
Lead: "There's a bug, you fix"
Me: "The PR for that has been waiting for your review since yesterday..."5 -
The Linux kernel team working on the Intel bug considered naming their fix:
Forcefully Unmap Complete Kernel With Interrupt Trampolines, aka FUCKWIT.
😂😂😂1 -
When a system-breaking bug ends up fixing a different bug and actually produces a new feature we didnt intend but actually love5
-
"Never fix a bug which has stayed in the system for a long time, unless asked for. The bug might actually be a feature for the user."
- My supervisor1 -
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...8 -
I have been 6 hours trying to fix a bug in more than 3000 lines of code.
Removed one line and bug fixed...
WHAT THE FUCK
I will pack my things and go home...4 -
Hehe, just inherited a bit of JavaScript code. Ashamed to say I physically lol'd a little :) Guess I have an easy "bug" to fix.6
-
I was just trying to fix a "bug" for 2 hours and then found out I only had to "clean" to project..6
-
I created a repository called FixAnyBug: https://github.com/KartSriv/... It literally deletes your file and creates an empty one. This is the best joke repository. I want to make it realistic so people will believe it for a split second6
-
My first contribution to a GitHub project was finally merged to the master branch today! It was just a bug fix but it’s a start!!11
-
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.2 -
Been working on a bug fix for 3 hours. Literally nothing I do will fix it. Finally I realize I'm not even calling the function.5
-
Ever been stuck in a bug, you sleep it off, dreamed of the code to fix it and you woke up, tried it, and it worked??7
-
My boss, who can't code, just gave me a bug to fix and said should be a quick fix...
It might be, but since you can't code, maybe don't assume
🤦♂️5 -
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 prejudge5 -
That moment when you make a bug fix on your local dev deployment and keep refreshing PROD web page hoping to reflect the change.2
-
I just sent an email to a client about a bug fix with Bootstrap 3 Date/Time Picker, which was not working with Firefox and Safari.
My email was like this "The bug has been fixed and it will work on most browsers except IE and Edge."
He replied "Great!! I don’t like internet explorer anyway…"
I love these kinds of clients.4 -
As a senior developer, I introduced a bug in the hiring system at the company I worked at and it took HR nearly 2 years to fix it.
Bug: Every candidate I interview on Wednesday between 12:30 PM and 4:15 PM gets selected irrespective of performance.
Impact: 270 candidates got a job
1st Fix [1.5 years in]: Add multiple developers to conduct a single interview (still did not fix it completely after all I was a senior developer)
2nd Fix [2 years in]: Removed me from the hiring committee
3rd Fix [though was not needed but for HR's extra safety]: Started recording all interviews
It was a good time.4 -
When you've tried for hours to fix a bug, But you know you have to try and get some sleep, and at the same time know you won't be able to sleep if you can't solve the bug...1
-
Sex feels good and all but have you ever felt the pride of submitting a bug fix to software you use on GitHub?4
-
I found a weird bug where the output wasn't what I expected to be. After a few tries to fix it, I typed in something I expected was not going to work. It worked....2
-
while(freeTime == true) {
if(iHavePlans == true)
waitUntilDone();
/*
* TODO: Fix bug that causes
* coding to call the gaming and
* relaxing methods so often...
*/
code();
}7 -
I wonder how a bug report on devRant may look like.
Something like a bug report and a fix on the same email?1 -
9 year experience in programming im 17 and still sometimes feel like I was an amateur and cannot fix sometimes easy bug. Am I the only one having this ?36
-
Just dragged a button in the UI to fix a bug.
Hell yea, now I'll write about my Objective C skills in my CV...2 -
guys do you know what is the best thing that makes you happy every time ?
When you fix a f*cking bug !2 -
There are milions of programmers on the world why they didnt make IDE what have button "Fix every bug and error" ?3
-
Me: *finds bug*
Me: *starts working on a fix*
*4 hours later*
Me: "It's a total whack job but at least the bug is gone"4 -
When friend trying to fix a bug for a week and then call you to fix it and you fixed it in a minute then he looked at you and say "omg how ? You are a god"
-
-Friday
Me: *pushes fix for an issue in app*
-Tuesday, the next week
Colleague: "Hey, dude, fid you fix that issue?"
Me: "Yeah, it's available since Friday morning"
Colleague: *e-mails me screenshot with the issue still present*
Me: "That's odd, let me check that on your machine"
Me: *opens the app on his machine, the issue really is there, starting to freak out that I messed up the repo*
Me: "Why the hell would that not work... wait a sec, lemme check something.."
Me: *checks the app version and discovers that it's from 2 months ago*
Me (turns on colleague): "I guess, you should update it to see the newest functionality"
Me: *goes to the toilet, locks himself up, cries*2 -
Spent 18 hours debugging and finding a fix for a critical bug, casually told about the fix to a senior programmer and left home. Couldn't go to office the next day and what I see on the day after that is endless mails praising the senior guy for fixing the bug. He stole my fix!5
-
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 know2 -
When I can't fix an bug and I can't make it as feature because the bug prevent the app from working normally. 😭😭😭😭😭15
-
There’s a bug in production, where a user account is vulnerable to simple bruteforcing 15 minutes after signing up. I’m the only one who knows. To fix or not to fix 🤔7
-
Error, coffee, fix, bug, coffee, fix, 1am!
Time for bed, last minute compile..
Error.
Bugger this, I'm going to be a dam hooker!7 -
That moment...after hours of fighting with the internet and the part of your mind that says you can't....found a fix for a bug
-
Well done windows a zero day bug that escalates privilege. Google was so pissed about it they released the info before Microsoft could fix it 😂8
-
I am a simple man. I see a bug - I fix it. Then, I fix my fix of the bug. Then, I just fix my fix of my fix of the bug. Then, (error: maximum call stack size exceeded)
-
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 :) -
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.
-
git commit -a -m"fix image"
git commit -a -m"fix image 2"
git commit -a -m "fix image 2 bug"
git commit -a -m "fix image 2 bug bug"
git commit -a -m"fix image final"4 -
😯😂😂😂😂
Some times I open the production site and then try to make edits locally to fix a bug, only to realize that I was so stupid.1 -
Most satisfying bug to fix...
Literally any API bug that returns JSON. Nothing quite like seeing that JSON blob come back correct.1 -
that moment when the client reports a bug on the website, and you ask if they cleared the cache, but you fix the bug in the meantime...6
-
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!13 -
The moment a support tells you they won't fix the bug, because it had existed for so long that it's a feature now.1
-
Have you ever told yourself to code till 12am and realised that you wanted to fix that bug to the point the clock struck 5...1
-
The feeling when you leave work frustrated because of that unfixed bug and in the night you lay on the bed, trying to fix the bug writing code in your mind and getting more frustrated because your imaginary code doesn't fix the bug.1
-
Love it when you try to fix a bug and realize the bug only occurs in debug mode.
No clue why, but also not my fucking problem, users ain't gonna debug :D7 -
I'm the happiest person alive!! Finally!! Fvck this bug! Everytime I fix a bug it turns out creating another bug itself -_-5
-
I'm currently tired, stressed, anguish and frustrated.
I have a live issue(a bug to hot fix asap), 7 files to reprocess to be finished by tomorow, 2 enhancements( 1 under pre-live testing, 1 for live release), and an unstable internet connection today. Tomorrow is saturday. Clock is ticking.
How am i suppose to finish everything on time? :(7 -
If you don't know, there are 2 types of bug fixes:
Hot Fix - Patch files directly on the production
Quick Fix - Deploy fix on production and then test it4 -
"This needs to go into production NOW"
Five hours later...
"That fix is on production now"
"Thanks, did you fix that other bug on production? We need it fixed now" -
I changed "Bug" in TFS to "Monstrous Hideous Defect". That'll get the mindset right. The word bug is so common that nobody cares anymore. New Monstrous Hideous Defect? Holy crap, better fix that right away! 😃
-
When you just figured out a fix for a bug, your on your way to the fix, but suddenly your co-worker asks everyone in the room "Would you rather be on a helicopter or airplane that lost all power". Then you get into a 10 minute discussion about which and why, and now that bug is permanent.5
-
Gah! Person in work has an issue I suggest a fix and even give them the bleeding code. For them just to say it won't work due to x y and z, I know it will work heck I use this 'fix'. Then later someone who has been there longer gives them the same fix and they are suddenly all appreciative. Ffs wouldn't be so annoyed if this was the first time this has happened.1
-
Couldnt fix a bug that conflicted with an unrelated codebase. A 1 in a million issue on github.
Had a wank.
Bug fixed, pushed, and deployed 30 minutes later.4 -
Lets fix this bug in production on a Friday afternoon. (did that three times on the same project). Never went wrong :)3
-
WHY DOES GOOGLE CHROME CACHE THIS SHIT AND WON'T LOAD IT AGAIN. I THOUGHT I DIDN'T FIX THE BUG BUT GOOGLE CHROME IS THE BUG. THIS FLYING FUCK9
-
So, I'm feeling a real programmer right now XD
Tired af and with a bug to fix.......
How's your day?2 -
Beware of scope creep. If it's a bug, fix it for free. If it's a new feature or changed from the original signed off scope, charge for it.1
-
Me: Writing an amazing code
Client: say nothing
Me: making a stupid bug, the client complains, I fix it instantly
Client: WOW you're amaizing3 -
Lead: how long do you think it would take to fix the bug?
Programmer: 20 mins with a testing
**Lead an hour later**
Lead: I don't see PR for the fix
Programmer: the fix broke all the unit tests so I am fixing them now. -
In a hospital bed and in my cellphone, web app went down, sended a bug fix while mildly conscious, typhoid fever btw1
-
Yay for technical debt.
For each bug I attempt to fix, I am finding > 1.0 more bugs that are related to it that also need fixing, leading to exponential bug discovery. -
When you have a bug in code that you are trying to fix for a century and then when you fix it you, make 15 more bugs by solving that bug like wtf2
-
Spent 2 hours trying to fix a bug.
Realized the problem was my test code. Easy fix.
Bam, program works perfectly.
Mad that I wasted 2 hours, but I guess I should be happy I found it when I did...3 -
Note to self, don't fix a minor bug that will not effect the demo right before the live demo. My program that was working great didn't work anymore during the demo because of my quick bug fix I figured I had a few minutes to add to my code.1
-
PM: "This is a critical bug fix needed before we submit to Apple."
Me: *reads bug story*
Me: "Wait, this is only repo on a Galaxy S5?"
PM: "Yup! It's stopship."
Me: 😑 "No." -
Management: Let's roll back this bug fix so we don't have to tell the client and have an extensive talk about this bug
Oh geez.2 -
My codes has mutate from a minor bug to a monstrous one.
It happened when I try to fix the minor bug. Looks like I add more bugs instead.4 -
Bug requires 2 developers, full-time for 4 days to trace, debug, scratch heads, analyse logs. Third developer helping occasionally. Finally identify fix. Fix is 2 lines. D'oh.3
-
The moment you sit down to try to fix a bug and you just stare and the screen for an hour not understanding how this even happened1
-
Get a ticket for a low priority bug, reported internally. Fix the issue mentioned in the bug.
Moves to QA environment, the original bug reporter tests and *passes* the ticket.
Moves to Staging environment, same exact individual then *fails* the testing. Cites totally new/unrelated changes that need to be made.
Apparently our the workflow is -
Code->QA->Staging->Requirements
Makes sense! :)1 -
Job security:
- Create bugs purposely
- Discover the bugs after a while (if you discover it too quickly it will look suspicious)
- Fix the bug1 -
1. Push a bug with a bug fix.
2. Fix the bug created during previous bug fix.
3. Push the bug fix which solves the bug created during previous bug fix.
Try not to cry...
Cry a lot 😭 😭1 -
ever been rushed to the hospital and suddenly your team lead calls you and asks if you can fix a bug? that happened to me.1
-
I was wondering why my td wasn't the correct size so I opened dev tools... Now I need to fix another bug...
-
2nd part to https://devrant.com/rants/1986137/...
The story goes on...
After I found more bugs that seem to be related to the communication break, and took a closer look, I sent detailed logs of my research and today we had a conference call.
"We have 2,5 million user, our system is widely-used and there is no plan to change it" they said.
And "We cannot reproduce the issue, but even if there is one, you will have to work around the problem, because we cannot make changes on our side" was one answer
As well as "If we would make changes, we will have to re-certify everything"
So I said we told 'em about the issue to let them improve their system. And I can work around it, I already figured out a solution for my side, but if there is a bug, they'd better fix it for future releases.
And with my additional research I have a bad vibe of some kind of memory leak involved on their "certified" implementation, and that could trigger various other problems.
But it is as always, if I try to be nice, I just get kicked in the ass. I should really be more of an asshole. -
Let
y="coffee beans"
Then (for devs)
y'="coffee powder"
y''="cup of coffee"
y'''="code"
"bug in production which requires urgent fix"=y''''1 -
My final commit in 2017 is a bug in my salt state 😢 but my friends are waiting so the fix has to wait until tomorrow!
-
What is the most infamous bug you know?
Mine is the YouTube view count bug which took them way too long to fix.4 -
Is anyone able to help me fix a bug?
The wakeup function keeps throwing an error and reverting back to sleep mode, unless there is an alarm nearby. Does anyone know the fix to this?2 -
Its my birthday and people are asking me about the party and I wish I can tell them that I have a production bug to fix3
-
Spent 2 hours in frustration trying to fix a bug in my code. Then i found a > where a < should have been.
-
I've looked at code I've writte and on average I fix one bug (minor) every 10-20 lines.
Is this normal, subpar, or good for a beginner?8 -
That moment when you've been investigating one particular bug, then stumble upon the cause and fix for another bug from 6 months ago that had left your vendor stumped...1
-
When working through a 3rd party over the last 3 weeks to fix a bug when you know that you could fix it in half the time if they gave you access.1
-
The Satisfying sensation to kill a bug that you have been trying to fix for 2 days. Thats what i code for.3
-
Either a very tired dev or a really really critical bug fix whose details cannot be revealed
I'll choose the first2 -
I felt so good after revisiting a project and everything runs ok
Code readable
Managed to pick off where I left off and fixed some existing bugs
Added new features and uploaded the update2 -
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.
-
class Bug():
def __init__():
self._fix = random.randint(1, 6)
def fix():
if self.is_feature :
return Feature(self)
else:
if random.randint(1, 6) == self._fix:
Bug()
del self
else:
return Bug() -
When the whole dev team goes out to lunch but you have to fix a bug before the release in an hour. 😒
-
My favourite bug fix was actually IT based and it was the first time my Eastern European, critical of my skills, family not only praised me but claimed that I was smarter than them.
My grandfather had changed from a telecom to a VOIP device for his landline. For some reason after installation, he could hear the other person on the line but they couldn't hear him. Me and my mother were away during this time so they called in the other family IT guy. This guy is no joke, he's one of the top in his company and makes a sweet six figures and lives in a mansion.
So he started looking things up, googling forum, etc. Couldn't find anything. Started calling the tech support and tried to deduce what it was and their tech support had never heard of such a problem. He takes his lunch breaks to help out my gramps. Keeps escalating, escalating and nothing. His conclusion is that they need to send him a new VoIP stick and they're not giving it to him. At this point, he's so frustrated that he screams at my grandfather to go back to paying 60 bucks a month for landline and to stop bothering him.
At this time me and my mother return and they have concluded that they need a new stick. My mom is great at intimidating people into free stuff so she and I go over to do so. At this point everyone is convinced of the problem and even I don't think I could fix it. But I decide to check if that's the case because I don't want my gramps to get a new stick and it still doesn't work.
I go through the typical forum hunting and there's Nada on the problem. I look at the stick and all the lights seem to be working, no error lights. And I wonder maybe the problem is not the stick, because usually you can't do anything at all if the hardware is broken. So I start thinking, maybe my gramps accidentally muted his handset while talking or something dumb like that. That wasn't it.
Then I decided to see if the problem was recreated on the other handsets. I tried one out and my mom could hear me but I couldn't hear her. What?! That's different! It was the opposite with the other phone. I conclude that it's working and there's something up with the handsets. So I go and do a reset on all of the handsets to make sure.
Lo and behold, the problem is fixed. It took me 25 minutes to solve. That guy gave up after a week of trying. My mom who assumed my IT skills were on par with other kids and nothing special had finally seen me up against an opponent, and not any opponent, a six figure high ranking IT specialist. And I didn't even use any secret, complex software knowledge that wasn't accessible to her or any other normal user.
That's when she finally said that I was smarter than her, that I just used my common sense. She would've needed some kind of prompting, hint or direction to solve the issue but I did it without any.
It was a very satisfying bug to fix. -
"I'm nearly done. Just one last bug to fix."
Time passes, coding happens ...
"No, not quite done. Just three more bugs to fix."1 -
Who here does a little dance when you’ve been stuck for hours on a stupid bug and manage to fix it?4
-
That feeling when you fix a bug after you've been working on it for an hour or two.... Ahhh.. Sweet relief.
-
House got flooded, need to fix an urgent bug, doesn't have enough sleep, toothache, heartache... Does God hate me?6
-
When I fail at a Rant and have to delete it out of shame and repost 😢
bug fix: 01101100 01101111 011011002 -
When I added that bug fix to my code a few weeks ago only myself and God knew what I changed - now only git knows...
-
* Customer reports bug.
* I fix the bug.
* This highlights another issue that I haven't got enough resources to fix.
* I revert the fix.
* <insert hacky workaround here>
We have code that invokes undefined behaviour (freeing memory twice), but somehow people have managed to build around it and now it depends upon it to work.
FML. -
Hate those bugs, where you stumble upon a fix but have no idea why it fixes it or what is causing the bug!2
-
Day and a half trying to fix a bug in a deprecated library :) thinking about commiting suicide right now (yes I stolen that quote back there)1
-
Boss always asks how long it will takes to fix a production bug. I just say 2 hours no matter what.1
-
Spent the last 3 days on a jQuery scrolling bug that has been in the product for 3 years. It was a 5 line fix.
-
TL;DR: There was a Steam bug and I fixed it locally.
Some months ago, Steam had the problem, that if you tried to add anything from the Steam Workshop to a collection, you would get an error like "Process failed: 2", while it was loading the collection list.
I realized, that it would work, but there was a bug in the JS (Watched the network tab in chrome while trying to add to collection). I searched after "Process failed" in each js file and after 30 seconds I found the buggy if. It said something like
if (json.success != 2) {
//do error
} else {
//show list
}
After I changed that if condition to
if (false)...
it worked perfectly, although it would make problems if there would be a server side error.2 -
Fixing a bug under Drupal 8 has a bright and an other bad side
The bad sight is that you slowly get insane trying to fix a bug.
The bright side is that you get to see the lead the lead dev, who assigned you this bug, to get insane too 😁 -
I'm starting day three trying to solve a Dependency Hell issue which is preventing a bug fix being deployed.
Please help.4 -
I swear this is the PM's first time experiencing a scenario where you fix a bug and two more pop up.
"ThIs ShOuLd Be SuPeR sImPlE, gUyS" -
Tfw you're done with dealing with idiotic bug reports ("Game crashed pls fix", "Not working pls fix", like that) you force the bug reporters to read a copy-pasted version of Simon Tatham's Bug Reporting Guide (https://chiark.greenend.org.uk/~sgt...) on a page before going to the bug reporting page and set a minimum of 100 words in the bug report filter just to filter the BS.
EDIT #1: Spelling errors1 -
You have to understand why the bug exists before fixing it. Covering it up hides the symptoms -- IT DOESN'T FIX THE BUG.
-
Fix for bug x
Fix 2 for bug x
Final fix for bug x
Really final fix for bug x
Another fix for bug x
...
Fix 59 fit bug x
....
As the gf egg bf egg Jr DG DG r
Rf we j RF at uh xD egg GB g2 -
11 pm: Me: I'm going to go to bed after I fix this bug!
3 am: *Pulling my hair out trying to fix the bug*
Me: HOW IS IT 3 AM ALREADY!1 -
Ahhh, When the apprentice asks you to have a look at a bug and they haven't even attempted to fix it themselves.4
-
Fixed a bug, spent 4 days procrasrinating, or as I call it, celebrating the fix.
oh and the NEW bug that got created because of the fix ? Will look into it in another 4 days. -
Today is one of those magnificent days for my code. One of those days where I stumble up on the weirdest bugs and pull a fix out of my hat barely looking at any doc. One of those days where I find out there is a very tricky flaw in our project design and yet I end up finding an elegant solution to circumvent future problems. One of those days where I find the informations I want even though the documentation is the worst I've ever seen.
I love that productive feeling.random efficient docs efficiency i actually don't like tags bugfix bug fix doc bug documentation productive -
> merging feature 20155
> Removing debug messages for previous commit
> Fixing bug from feature merge
> Fixing bug from previous fix
> Merge fml -
Product owners not testing/validating bug reports and just passing us the email like
"Here, now fix it"1 -
When you have to fix a bug that's just happening in IE11 on Windows 7... 😧😩 well, nobody should even be using that shit!!!4
-
I love it when I manage to fix one bug and then 9 new appear, like a Hydra. Mythology at its finest.3
-
Why does our boss think that there is "fix it" button for every bug.. which will magically solve the bug in 1 minute.1
-
When the product designer ask me to move my bug fix Jira ticket back because there's a style change.
-
Me when I am trying to fix a bug and I skip the part of the code where the bug is, because I am sure it is correct. https://media.giphy.com/media/...8
-
Was stuck on a bug, took 2 days still couldnt fix it. Dumped all blame on backend guys. Came out it actually was an API issue 😂
-
If you tried to fix a bug
And put it on stage, but still not working!!!
MAKE SURE HAVE HAVE REBUILD YOUR SOLUTION3 -
The best part about working on Someone else's UI bug fixes is that you get to look like a hero when you fix the bugs and make all their work look like a sham - asshole 101
-
When was the last time you fix a difficult bug and you make a crazy lunar laugh that makes you lost control of your saliva?
~ I can tell, you code fiercely.2 -
Nothing like trying to fix a product breaking bug in someone else's code that just ran off on vacation for a week. 😒1
-
The quick and loud bang of someone slamming their hands on my desk. I was trying to fix a bug and suddenly forgot what I was thinking about. :(
-
Was to lazy to fix a bug. Waited some months and then realized the bug magically was gone. Happened not just one time...2
-
Most satisfying bug, it was something with good old $.ajax, way back when Axios wasn't a thing and SPAs weren't so widely used.
I was somehow able to fix the call params for a file that would not load with any other setup. Maybe it was just setting async to sync or something like that, however the thing is I was not familiar with AJAX at all, but I managed to get it run.
Then I googled, why its working and figured out all the answers on SO and other pages were the exact thing i set up for my call. I was so proud
some context: I was struggling with this bug for days and asked more experienced web devs, everybody answered, your code should just work fine.
Maybe thats why I have a positive relation with SO, because the first thing i searched there was something that I figured out myself, haha -
The time when you NEED to go to bed but you got a bug to fix or a feature to add, and become a BAT!1
-
Comments throughout code with things like "changed to fix bug #". And commented out code all over.
We have source control, why the hell are you doing this? -
"Hey, can you check this ticket, and fix a bug on a Drupal module written 2 years ago, making you rewrite almost everything, please ? You have 30mn"
-
I can't attach any image now and it keeps on loading forever. :/
(Is it just me? Maybe because of slow connection?)1 -
FMF! .NET Core's F# REPL depends on a bug. For two years the testing and building issue referenced as a reason for depending on the bug has not been resolved. Since 2016, no one has been assigned to fix the bug though the producer of the bug hates himself. Only the self-hating deserve love2
-
I don't get the bug "joke" that's flying around. If you have 99 bugs and fix one, why would you have more? Do you not have automated tests?5
-
only programmers can tell what this feels like sometimes it not funny expecially when trying to fix a bug.4
-
Releasing to production while knowing there's a high chance there maybe a bug that may require a hot fix
-
My head of products idea of an urgent bug is a feature that he really wants in the app.
Guess who’s got 22 ‘bugs’ to fix by Friday 🙁2 -
when you're burnt out and you question whether or not you really did fix that bug or your mind is playing tricks on you.
-
I've just spent 4 hours trying to fix a bug on prod. that can be fixed in 30 secs. At the end I remembered that I should check the error log. FML (error reporting turned off, logs only)
-
Life of a web developer: Find a bug at the end of the app, fix a bug at the end of the app, time to test the bug? Sorry service is down for the rest of the day on the page right before the bug.
-
Working. Finding a bug. Quick-fix. New bug. New bug. New bug. Spending 1 hour looking for Quick easy solution. Getting distracted with a more complicated solution. Spending 1 hour researching. Back to problem, one more hour bruteforcing the problem. Finding it was just about a configuration problem. Fix in 5 minutes. Repeat everyday.1
-
The production bug conundrum:
The new release that's going to fix the problem isn't ready yet, but hotfixing it means merge-hell for the new release. -
I installed Linux and ended up on Ask Ubuntu trying to fix a bug. From there it kind of snow balled into learning Bash and got interested.
-
A client just replied to a two month old email telling him that the next release will contain a fix for a bug asking whether this release will fix that bug... Mkay then...
-
There is a bug.
I know where the bug is.
I know what the bug is.
I tried to fix it.
Fixed a cometely different bug instead.
This repeats 5 times.
I don't call it bad luck, just talent -
That feeling you get when you enter in a piece of code for a bug fix...#aweekofbangingmyheadonakeyboard
-
most satisfying bug fix = getting Android MediaPlayer to PAUSE AUDIO PLAYBACK WHEN IM NOT INSIDE THE ACTIVITY
gosh how many of you here have experienced this before1 -
Finished my programming quiz but couldn't fix the bug.
Right after submission, found the solution to fix the bug and it was just to remove "-1" -
! Rant
When you have to change your desktop app because of a bug in iOS app and its fix on web service! -
Do you think the "Fix one bug, two more shall take it's place" is a real thing? Have you ever experienced it?6
-
Try to fix things yourself before you bug your seniors. But dont spend too much time if you're stuck.