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 bug"
-
When you "fix" a bug not by actually fixing the bug but by disabling the user's ability to cause the bug.14
-
"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 😩*24 -
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
-
The Linux kernel team working on the Intel bug considered naming their fix:
Forcefully Unmap Complete Kernel With Interrupt Trampolines, aka FUCKWIT.
😂😂😂1 -
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 -
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 -
I was just trying to fix a "bug" for 2 hours and then found out I only had to "clean" to project..6
-
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
-
> make a change
> PR gets rejected
> IHATEFORALIVING! YOUR CHANGE IS NOT WORKING! EVERYTHING BREAKS!
> 3 hours long debugging session
> We find out a whole bunch of bugs
> Suddenly, everything works
> None of the bugs had ANYTHING to do with my change. In the instances where the app broke, my code wasn't even being called at all.
> My change was literally the one and only working thing
I wish life was like in The Office, when you just stop what you're doing and you drop the Jim stare at some camera3 -
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
-
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 -
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: …1 -
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 -
That moment when you make a bug fix on your local dev deployment and keep refreshing PROD web page hoping to reflect the change.1
-
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 -
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
-
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 -
Sex feels good and all but have you ever felt the pride of submitting a bug fix to software you use on GitHub?3
-
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 -
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 -
There was a bug that I ignoring to fix for past 8 months and finally Client found the bug and reported back to me. All I said to myself "Motherfuck".
So from tomorrow I will be rewriting a piece of code.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 -
Just spent an hour trying to fix a bug on my Xamarin app that only affected the android project. Finally decided to Google it and figured out it's a Xamarin bug. FUCK YOU XAMARIN GO FUCK YOURSELF WITH A BROOMSTICK WITH NO LUBE.7
-
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 .-.3 -
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!4
-
-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 -
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
-
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
-
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 -
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...?11 -
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)
-
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 🤔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!11 -
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 message that I hate:
1. "Adjustment"
2. "Improvement"
3. "Fix Bug"
4. "I commit it but there are bug in this code"
5. "Client request"
YOU KNOW BE MORE SPECIFIC ON YOUR COMMIT MESSAGE!!!9 -
Most satisfying bug to fix...
Literally any API bug that returns JSON. Nothing quite like seeing that JSON blob come back correct.1 -
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"3 -
Love the feeling of closing all those open tabs when you finally fix that bug and finish that task.1
-
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
-
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
-
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
-
Today while trying to fix a bug, an actual bug came flying through the window and sat on my laptop. When I tried to make it flee, it went inside my laptop through the vent.
I guess now I have two bugs to deal with.1 -
I'm the happiest person alive!! Finally!! Fvck this bug! Everytime I fix a bug it turns out creating another bug itself -_-5
-
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 -
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 -
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
-
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 -
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! 😃
-
"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" -
So, I'm feeling a real programmer right now XD
Tired af and with a bug to fix.......
How's your day?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 -
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
-
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
-
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
-
In a hospital bed and in my cellphone, web app went down, sended a bug fix while mildly conscious, typhoid fever btw1
-
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.2 -
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." -
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
-
Lets fix this bug in production on a Friday afternoon. (did that three times on the same project). Never went wrong :)3
-
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 -
Job security:
- Create bugs purposely
- Discover the bugs after a while (if you discover it too quickly it will look suspicious)
- Fix the bug1 -
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
-
Follow up to my other rant https://devrant.com/rants/4994932/...
I have finally fixed the bug i couldnt fix for over several weeks. I was just missing a fucking if statement check. Not expecting this to work, i compiled, tested and it worked perfectly on the first fly.
Immediately i shit you not have i broken down crying. Sobbing in tears. Uncontrollably crying down on my table for several minutes and cant refocus to continue coding. I have NEVER cried because of a fucking bug fix! But i have also NEVER had a problem so much difficult that i needed several weeks to fix it!
..1 -
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 -
I was wondering why my td wasn't the correct size so I opened dev tools... Now I need to fix another bug...
-
What is the most infamous bug you know?
Mine is the YouTube view count bug which took them way too long to fix.4 -
Immediately after I fix a big I'm super happy.
Then I think about how it got there I'm the first place and realise it's because I made a stupid mistake and I'm super angry with myself.
I didn't choose the bug life, the bug life choose me.3 -
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!
-
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 -
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
-
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 -
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. -
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 -
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() -
Either a very tired dev or a really really critical bug fix whose details cannot be revealed
I'll choose the first2 -
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.
-
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...5
-
When the whole dev team goes out to lunch but you have to fix a bug before the release in an hour. 😒
-
Spent 2 hours in frustration trying to fix a bug in my code. Then i found a > where a < should have been.
-
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
-
"Just put a 3 seconds sleep in your system init process, it will fix the showstopper bug we are getting on customer systems."
-
When I fail at a Rant and have to delete it out of shame and repost 😢
bug fix: 01101100 01101111 011011002 -
"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 -
Hate those bugs, where you stumble upon a fix but have no idea why it fixes it or what is causing the bug!2
-
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...
-
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.
-
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
-
* 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. -
Trying to sleep. Looking at devRant. See a f ew rants about bugs which reminds me of my bug. Get out of bed and now behind my computer trying to fix the bug. Hope it's a quick one so I can go back to sleep
-
I'm starting day three trying to solve a Dependency Hell issue which is preventing a bug fix being deployed.
Please help.4 -
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
-
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
-
Ahhh, When the apprentice asks you to have a look at a bug and they haven't even attempted to fix it themselves.4
-
Boss always asks how long it will takes to fix a production bug. I just say 2 hours no matter what.1
-
> merging feature 20155
> Removing debug messages for previous commit
> Fixing bug from feature merge
> Fixing bug from previous fix
> Merge fml -
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. -
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.
-
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 😁 -
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 -
pros of working on a full C++ project:
Time to browse XKCD while it is building to fix a small bug my predecessor made. -
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 -
You have to understand why the bug exists before fixing it. Covering it up hides the symptoms -- IT DOESN'T FIX THE BUG.
-
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 -
House got flooded, need to fix an urgent bug, doesn't have enough sleep, toothache, heartache... Does God hate me?6
-
Nothing like trying to fix a product breaking bug in someone else's code that just ran off on vacation for a week. 😒1
-
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. -
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
-
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.
-
If you tried to fix a bug
And put it on stage, but still not working!!!
MAKE SURE HAVE HAVE REBUILD YOUR SOLUTION3 -
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
-
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 -
After inputting all of the defect info into the bug tracking tool, QA writes a quick summary of their findings and goes home.
Love explaining to mgmt why developers could not fix bugs because they had no access to the bug tracking software.
1 day.... X number of bugs... 0 progress -
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
-
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
-
Releasing to production while knowing there's a high chance there maybe a bug that may require a hot fix
-
When you're trying to fix a bug in your project and realize the problem is a bug in the platform your project is built on.... FML
---
Searches mailing lists for the problem
-- Hours later --
Finds that bug might be fixed in the new unreleased build.
--
Installs release candidate of new build.
--
Still broken.... *Facepalm*
Now to try an old build and see if that works...2 -
I love it when I manage to fix one bug and then 9 new appear, like a Hydra. Mythology at its finest.3
-
only programmers can tell what this feels like sometimes it not funny expecially when trying to fix a bug.4
-
Was to lazy to fix a bug. Waited some months and then realized the bug magically was gone. Happened not just one time...2
-
More health problems. Great. Health is like a single bug. Once you fix the bug you create 10 new ones. My lips are swollen and bleeding internally. Fuck off2
-
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...
-
Product owners not testing/validating bug reports and just passing us the email like
"Here, now fix it"1 -
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.
-
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'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)
-
I can't attach any image now and it keeps on loading forever. :/
(Is it just me? Maybe because of slow connection?) -
Any tips on what to do after 2 days of trying to fix a bug in a published project cos I'm losing my mind right now??13
-
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
-
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.
-
Working for a little SharePoint-Company while studying.
Have to hunt bugs.
Found a major bug which kills one of our customers SharePoint-Site completely because of code pasta.
Told my supervisor about the bug and reported it.
"yeh. we will fix it now"
2h later they started to go live.
"Did you fix the bug?"
"No. Wanted to have the system live asap."
On my way home I got a call.
"We need you back here in the office"
"Why?"
"It crashed. Is not reachable anymore. Help fixing it"
fuck off -
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" -
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
-
rant. Tried to fix a weird bug in gamemaker, with some unfamiliar technic, resulting in another bug. Then one hour later, still no solution to that bug until I look around in the code seeing that I already used the exact solution that fixes the first bug.
In gamemaker there are scripts. I tried to forcefead the fucking script with a variable when calling it. Inside the script, there where already variables working fine with the extension or what-to-call-it:
other.(insert variable).
And that pisses me off. -
! Rant
When you have to change your desktop app because of a bug in iOS app and its fix on web service! -
What interesting projects have you guys worked on as a junior/entry level engineer? I mostly do bug fix and enhancements😕13
-
Do any one feel so lazy to start write test especially for a complicated bug fix?
My problem is with starting2 -
So I had this bug where my csrf tokens weren't working and I spent hours on end trying to fix the bug and in the end it wasn't working because I set a default route to load the same page which was resetting the tokens when chrome requested favicon.ico ...
-
Try to fix things yourself before you bug your seniors. But dont spend too much time if you're stuck.
-
Do you think the "Fix one bug, two more shall take it's place" is a real thing? Have you ever experienced it?6