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
-
Finally I found a webpage related to my bug.
The page is from 2004.
*keeps reading*
"Yes, yes! This is exactly the problem I'm having"
*Carefully reading each comments*
*Looking at scroll bar with stress*
*Almost coming to end, no signs of solution*
At the end the thread creator say: "Ah finally I've fixed the problem. Thanks everyone for helping"
*moment of silence*
WHY U NO SHARE THE GOD DAMN SOLUTION? YOU FUCKING IDIOT17 -
A friend asked me to test a program he made
So i downloaded it, and i noticed that i crash when you try to minimize the window
After i tell him about the bug, he send me a new version, and said "I fixed it, it was pretty easy"
He just removed the minimize button
"to remove a bug, remove the feature"4 -
"Sir, I fixed the recent bug"
"Great, what did you do?"
"I commented out the code that was causing it :)"
"Brilliant! You didn't forget to push the code to production, did you?"
"No Sir, I pushed it immediately"
"Marvelous! I'll arrange a promotion for you next month"5 -
Why am single 😂😂
On a date with a girl:
Her: Tell me what you do for a living
Me: I create my own stress and worries, sometimes these worries follow me in my sleep.
Her: Did they follow you here?
Me: Yes! Infact, I got it now. I think I forgot to install curl, that's why my API queries wouldn't work.
Her: Excuse me?
Me: I mean, I out of here, bug is fixed bit*h14 -
I've always made this joke, but it happened for real.
There was a existing bug in our machine for a very long time. So long that the validation engineer now treats it as a feature and they raised a issue when the bug was fixed :/7 -
Me: *finds severe bug in school-contracted software, emails teacher about who to talk to to get it fixed*
Teacher: "should I report you on grounds of computer misuse and hacking or...?"
thanks fucker, school-contracted company it is.28 -
Dev: Ok issue fixed, you just need to log out and back in again on your end to receive the fix
User: It’s still not working
Dev: Did you log out and in again?
User: No why would I want to do that?
Dev: It’ll reset your locally saved login information which is causing the issue
User: I thought you said the issue was fixed?
Dev: On our end yes, we just need you to reset your end in order to receive the fixed version
User: Look I have been dealing with this issue for 6 months. Fixing bugs are your responsibility. I have too much to do, you have to get this fixed. *click*.
Dev: Yeah you submitted the bug ticket yesterday night though
Email from users manager later that day: <User> is saying you are refusing to fix this bug. This is unacceptable. Fix it or else I will escalate this. Also there are other bugs we noticed today too, fixing them is absolutely critical!
Dev: …
Dev: What other bugs did you notice?
*no response for 2 weeks and then:
User: Hey you can close this ticket, the issue seems to have resolved itself.
Dev: ….muppet.17 -
A guy who doesn't work on our project anymore, but still checks on us regularly just did this:
- reported a bug
- started explaining what's causing the issue
- realised the problem was in a piece of code written by him before
- fixed his own mistake, committed it and created a pull request
We all had a good laugh.6 -
Reasons why I update a software to the latest version:
1% - I'm glad that they fixed the bug
4% - I want the new features
95% - To get rid of reminders that don't allow to tick a "don't remind me later" field.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 cache
5 -
User: There’s a bug in the app
Dev: How do I reproduce it?
User: I don’t want it reproduced, I want it fixed!
Dev: …7 -
I just fixed a bug with the ticketname "Sometimes, There is a strange behaviour when opening the app on some devices"
Feeling heroic now8 -
I had been trying to fix a bug for the whole day, I decided to sleep for a while. During my sleep, I dreamt I was working on the code and I fixed the issue. I woke up, tried what I did in my dream and it Worked! I was so confused and happy
17 -
#6
My client tells me there's a new bug with to-www-redirects. He yells they don't work properly anymore and tries to blame me. But fact is I know, they are well configured in the Nginx conf and therefore work like a charm.
I told him I fixed it and charged an hour. Motherfucker.
😓🔨 -
Ex-coworker of mine fixed this bug a week after the site was launched and has gathered several thousand users in database.
Yep its exactly what you think it is, each time one user would update its infos, it would update his infos to all the users in the database.
Luckily I was not in charge of the project in that time, so it was really fun to watch how everyone's name was changing every couple of minutes for a whole week :D
12 -
2 Days.
Thousands of lines of code analyzed.
Dozens of log files across 6 servers.
Countless pots of coffee.
Much power metal.
...
One line of code.
Bug fixed.8 -
Gooooood morning devRant! Fucking friday, fuck yeah.
Hereby a rant which @dfox asked to make to test if a possible bug is fixed.
Have a great day everybody and thanks to dfox for keeping me in the loop on this!14 -
My day in a nutshell:
Fixed the app.
Broke the app.
Fixed the app.
Broke the app.
Reverted all changes from repo.
Fixed app.
Found new bug.
Ugh....1 -
!rant
Yesterday I upgraded VS Code (insiders version, i.e daily/beta/etc) to the latest version and ran into a minor bug. I reported an issue in the Github repository, and 40 minutes later got a reply saying It was fixed and I can upgrade to the newest version.
Kudos on Microsoft and the VS Code team!5 -
Client: There’s a bug in the app
Developer: How do I reproduce it?
Client: I don’t want it reproduced, I want it fixed!
Developer:🤐🤐🤐5 -
So apparently two "senior" "laravel-engineers" spent a total billed 35 hours trying to figure out a "critical bug" which "doesn't happen locally".
I went to the dev-console, saw it is generating http urls (fronted by cloudflare https, running on http server-side) and fixed that in maybe ~15 minutes, fucking morons.9 -
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 -
Multiple weird ones but one specifically where I fixed a bug over and over again and the second I pushed and deployed, the fix was gone both locally and remote.
I kept going more and more crazy and had rage attacks and such.
"Wait what, I changed and fixed this.. Let's try again"
"Huh, I definitely changed this..."
"Oh no, I fucking changed you"
"Go fuck yourself, I fixed this and pushed already, you can't just fucking disappear on me!"
"Oh yeah no of course, disappeared again, totally fucking logical. GET BACK HERE"
"I FIXED YOU A GAZILLION TIMES ALREADY, DON'T YOU DISAPPEAR ON ME AGAIN"
*NO. NO. NO. NO. NO. I. FUCKING. FIXED. YOU"
It went worse and worse for a while and then I woke up with a "....ahh" feeling 😅2 -
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."9 -
And then there was this big review...
DEVs:" this bug is hazardous and needs to be fixed quickly! It could crash a productive system completely!"
CTO and DEV teamlead:" shut up! This big exists more than two years! No customer will ever klick this button!"
--exactly twelve hours later--
Customer:"so we clicked on this button and our system crashed! Can you help us quickly? We are losing money!!!"
CTO in the meeting:"who programmed this shit? Are you insane?"
Teamlead:"you are useless !!"5 -
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 -
Fixed this guy's code and he spent the whole day thanking and explaining to me how sad and depressed the bug had left him. I felt really sorry for the poor dude. Lol.
1 -
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 😞82 -
I fucking hate it. Clients writing impolite emails about bugs I didn't make without telling where this fucking bug is and demanding it to be fixed yesterday.5
-
Coworker: There's clearly a bug here, this thing just says OFF and doesn't work!
Me: Well, did you try switching it to ON?
Coworker: OH SHIT that fixed it!3 -
Just Fixed a major issue in my code and the Sun came out at the same time! I feel like should I go out and scream on my balcony!4
-
Boss: "How much time do you get this bug fixed?"
Me: "Give me 20 minutes"
*4 hours later*
Me: "fixed is in the repository"
Boss: "You're getting to much time to do your assignments"
Me: *Damn it*
I suck doing estimates 😥7 -
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 -
Was feeling like a boss in new office after fixing a major bug.
Yes, the bug was fixed. Only half of the program doesn't work anymore.1 -
One day I created a bug issue for intellij to the JetBrains guys. After some days this ticket got closed with status 'fixed'. That was kinda satisfying.1
-
I just had a dream about how to squash a bug I was encountering in my app. I immediately woke up, fixed the bug, and cleaned up my code. I thought this only happened in movies.3
-
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.16 -
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?11
-
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...4 -
My project at work (an electron/angular desktop app) has an exceedingly rare bug that causes it to crash-to-desktop while loading. Nothing about the bug makes sense, and there's no way to catch or detect it until the next run, and it happens 100% of the time for affected users.
There have been six confirmed cases so far (out of 500k+ users), and nothing linking them together. None of the fixes discovered by those users have worked for other affected users.
The worst part?
I was the first of those cases. I inadvertently fixed it for myself and haven't been able to reproduce it since.
I'm stumped!19 -
.... And it appears my Atom has Entered the Matrix. Full time.
In other news, I successfully completed the E-Commerce App I was working on, even though that Stripe Verification was a ball ache and the bane of the entire project giving me a stupid bug in jQuery whereby it was infinite looping over adding the token and not actually submitting the card charge. Somehow changing my button from using an id to using a class fixed my problem :/ (# -> .)
11 -
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 moments2 -
git commit -m "fixed bug where div wasn't resizing with window size change. Next I'll work on new bug which makes it so the pages won't load at all"
3 -
Finally fixed a major bug.....
FUCK YOU C# AND YOUR FUCKING CASE SENSITIVE BULLSHIT.
DAYS
THAT TOOK FUCKING DAYS AND AT NO POINT DUD VISUAL STUDIO BOTHER TO MENTION THAT FUCKING ERROR.
1 CHARACTER, ON ONE LINE, EFFECTIVELY BROKE THOUSANDS OF LINES OF CODE
fuck this, I quit. See you next time you contact the Microsoft live support chat!13 -
Fucking Edge. I fixed a "bug" and now the bug-pointer tells me a line with only a comment causes a problem. Yea. Genius browser.
It's an "UNKNOWN" error btw, great debugging!
8 -
"Dont jump. The bug has been fixed!"
(Plot twist: I'm actually that guy who's gonna jump) lmao
Whats yours?
49 -
When you work for hours to solve a bug, and finally you fixed it, only to have 2 new ones show up to replace it:
3 -
Just found a humongous bug in production. The customer relation number, which should have been unique was shared by ten customers.
So instead of 400,000 relation numbers we only had 40,000 unique numbers.
The system is live for 3 weeks now, and we just fixed it on a friday at 5:30PM
If we had found out a week later every customer would have gotten a plastic card with the wrong number, because the cards will be printed in four days...8 -
So the CEO called me down about a super urgent bug that needs to be fixed or we will loose several hundred thousand pounds of business.
I rush down to his office and there he has a graph "look the values are barely moving i would expect the values to be more erratic this time of day"
*i look at the graph*
"Errrr your looking at 02:00 in the morning, it's 14:00"
Boss: ahh good spot *looks at 14:00* yea that looks good, great job.5 -
That awkward moment you go from being the developer of an online store, to being the customer of said online store, and pray the ordering system behind the scenes doesn't fall over due to a bug you haven't fixed yet 😅
Here's something I never thought I would do, I just returned this weeks pay check back to the company!6 -
Thanks to @sain2424, we found a really weird bug in devRantron.
One of the user that commented on or upvoted his rant has deleted that account. So when the notification component was trying to fetch the user's avatar to show the notification, it was failling and causing the app to crash.
@Cyanite the bugs you reported is fixed as well. Please update 🙃 🙃3 -
We have a 15-machine cluster that went down last night because one machine in the cluster went down. Apparently having a cluster for redundancy is just a nice idea and doesnt actually work in practice.
Also I shouldnt have to go to a vendor's forums to find out the bug that is causing my cluster to go down is fixed in a future version. It should be in the goddamn patch notes!!! -
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.1 -
That moment when you want to sleep and suddenly your brain says “hey buddy I know how to solve this one crazy bug you tried to solve the whole day”
03:00 fixed it
06:30 on my way to college
#Error404SleepNotFound -
My nipples are hard, as hard as diamond. For no fucking reason at all.
But aside from that important update, does anyone just get this absolute light-headed euphoria whenever they realize they've fixed a bug?
Like my god, its the best feeling. I've only fixed other people's bugs a few time, and even then I experienced it.16 -
Two of them, both are not very extrem.
Positive one first:
Meetings were usually not dead serious (unless there was a problem), everyone just joked around a little, made their actual points and got back to work.
Now the other one:
A client's QA staff commented "this bug is still occuring" on 5 tickets, without checking if they ever deployed the new release candidate.
They didn't deploy the new RC, so of course, the bugs couldn't have been fixed on their side.2 -
I hate when a software update changelog looks like this:
The latest update is now available, update your software to get the most out of it.
I want a fucking changelog before updating my things. Like: fixed a bug, new button with cool new feature. Just something. I have to know. Can't just install something blindly that could ruin my software, especially when it's not reversible..1 -
Google: buys Android
Makes tons of $ from Ads
Meanwhile 7 year old bugs
Are still not fixed
A bug reported in 2012: recently created files are not visible when using MTP protocol.
Guess what? I still have this bug on my 2017 phone, like many other people.
Probably has something to do with file cache.
Because obviously 7 years is not enough to fix a stupid bug. Especially when Google is busy implementing all the other features nobody asked for except marketing department4 -
To all you fuckers out there giving bad app rating because some shit does not work on your shitty phone and you are to fucking lazy to report the bug via the fucking "send log to dev"-button that pops up with the exception.
Go fuck yourself.
And to all the user whose bugs I fixed and did not change their Bad rating - fuck you too.
And oh.. The fucktards that did not even install the app and give a Bad rating because i am your competitor - guess what...fuck you.8 -
There. I fixed the bug. Tested every way possible 10 times and it won’t break. I’m awesome.
Tells a tester I have a phone with the new app-version installed for testing on my desk when he has time.
He just... came to my room. I gave him the phone. He looks at it, does SOMETHING and just ”Ya man, I broke it”.... whaaaat O.o2 -
Don't you just hate when your boss goes like:
"Why isn't this feature working?"
SHIT FUCK, IF I KNEW THE REASON, MAYBE I WOULD HAVE FIXED THAT SHIT, INNIT?
WHAT KIND OF FUCKING QUESTION IS THAT?
"Well you should have tested better"
IT TOOK A MONTH FOR 1 USER TO SEE THAT BUG, WHAT DO YOU EXPECT? YOU EXPECT ME TO SEE THAT BUG IN THE FEW HOURS OF TESTING I CAN ACTUALLY DO FOR THIS PROJECT?
"There also are other 15 project to get done"
FUCK THIS SHIT -
When your company buys a third party solution and you spend all your time emailing them about bugs in their system.
Seriously, I even sent you the exact line of the bug in your JavaScript with a suggested solution, and deployed a new stack with your latest (broken) fix so you can test out that solution. Then you email back saying it is fixed but it is clearly still broken. If I email you a fixed version of your file will you deploy it? OMG!1 -
See another of this git commit message :
"Fixed bugs and added new feature"
Fixed what bug?! Added new feature what?!4 -
!rant
just wanted to share with you guys,
instead of spending 1hr writing shitty code to fix a bug quickly, i just spent tha last 10 fucking hours and finally fixed it
I'M FUCKING PROUD OF MY CODE, IT BELONGS TO A MUSEUM8 -
Fixed a bug in my emulator that was completely breaking almost every program I ran on it.
Turns out the virtual ALU set its arithmetic flags (zf, nf) even when a non-arithmetic operation was run. -
Successfully wasted 4 hours then realised jQuery was not inserted..
jQuery inserted..
Bug Fixed.. o_O8 -
Most of the work we do is committed into various branches. Everything is merged into the master branch.
Colleague was on vacation. I was working on a bug that was fixed by him some time ago. All I had to do was find the commit and merge it into the relevant branch. I didn't know which branch to search so I just looked into master. Search all commits on master made by colleague.
All I see is:
"Merged into master"
"Merged into master"
...
"Merged into master"
MERGED FUCKING WHAT INTO MASTER?4 -
POV: You fixed a hairy bug at a FAANG as a:
L3: "You're a technical wizard!"
L4: "Good job."
L5: "Why did you allow this into your team's code base?"
L6: "Why didn't you delegate that?"1 -
I started a project at high school 7 years ago, I had no idea what's clean code or design pattern, just learn while keep coding. I eventually stopped because my code is so terrible I cannot understand it anymore.
Now, after 1 year of working, I look back those dirty codes and think it is actually not that bad. Within hours I even fixed a bug with concurrency.
I start to think, instead of learning to how to write good code, maybe I should learn how to read bad code. That's just much more practical.5 -
I just found out I had used, for over 4 months, the wrong function to encode/decode url strings, which caused a lot of issues with my app...
I refused to believe that the problem is there, so I was looking elsewhere.
The longest search of a bug in my life finally over. Fixed! :D2 -
My coworker "fixed" a bug. Then an issue was reported to me. He refactored something that we both used(And my code was already working right). I asked him about it. He didn't care about it and also was upset about my question. A question that I didn't ask in a "rude" way.. The worst: the refactor only required 30 seconds to do!!!
What!!!
Please guys if you refactor do it right or don't do it at all. Have a nice day9 -
A bug which takes 6 days to be found/fixed. Screw you financial data. 👹
🏀on the good side: whole class was de-constructed and re-factored + no other bugs were found! 😀🔥1 -
When you're helping someone with a bug for ages and then try something random and it's miraculously fixed so you have to spend another hour figuring out why...1
-
Today, I had a segmentation fault in a data structure, so I wrote a function to test the integrity of the data structure. It worked, and I found and fixed the bug. However, the test still complained about the integrity. After debugging some very strange errors for 5 hours, I discover that there was a bug in the integrity test. The data structure works just fine. FML.1
-
It was my first month as a driver developer fresh out of grad school, at a semiconductor company. There was an elusive memory alignment bug that had eluded the experts on the team. Of course, they had to assign it to me.
I was looking at the code where alignment was being calculated for nested structures case. I saw something funny: "size_t(object)". I asked the expert where it should have been "sizeof(object)". And, sure enough it was!!
I was super-thrilled to have fixed a bug in my first month, which had troubled the team for a long time! ^_^6 -
Blaming someone and giving them a lecture on a bad code/bug then realizing it's not a bug or that I fixed it incorrectly.
-
Fucking people, why the hell are you reading into things instead of asking for clarification if something is unclear?
So much time, sweat and tears wasted on miscommunication.
When I said, "there might be a problem in the way component X method Y was implemented", i didnt mean go refactor the entire code of the component. Why waste 2 days of work on unnecessary refactor that nobody wanted and breaks changes + the bug is not fully fixed 😤13 -
A mail I got two days ago started out like this:
"Hello Mr. $myLastname,
I know the Internet Explorer is quite old but we found some errors[...]"
My mind: "NooooOOoOOOO"
They find a lot of weird stuff too, dropdowns, carousels all that major stuff didn't work.
Turns out it was a bug with bootstrap 4.1.0. It's fixed in 4.1.1 and until, release we can use 4.0 just fine.
My feelings in those 15 minutes resemble a sine wave.2 -
"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" -
When your non-programmer boss asks how exactly some code/bug was fixed.
"You sure? I mean, alright... "
It's not like every time something doesn't work right, this will be the fix. We're not going to have a conversation in the future where you help me troubleshoot something by remembering parts of this conversation.1 -
I've fixed the bug... After 3 fucking months...
If I worked on this in one go, non-stop, it would've been over 5 days.
Bring on the next one. 🤘🤘🤘1 -
So we're seating in our small dev room where nothing else and no one else can fit in. I'm sitting next to the door so whenever anyone want to get in or out I need to do it first.
It's middle of the day and one of our dev friends. You don't believe what he did.
He fixed bug. So I pushed the red button to signalise that the bug was fixed and at the same time the alarm siren has launched and red lights starts to blink. Next minute couple of strippers wants to enter. Since the room is small they started dancing on our desks. Waitress opens champagne that's pouring on my leg and then I woke up and my dog is pissing on me.2 -
Does anyone notice that when you go to a 404 page on Google that the title has a "1" at the end, like someone was trying to put three !s but let go of shift to early.
I was going to submit a bug report, but I kind of like that 1 there, for some odd reason.
(If me posting this rant gets it fixed, I will be upset)
4 -
You know how my 'about' here says I create features from bugs?!? Well if you didn't before, now you do.. :P
Anyhow, today the most bizzare thing happened.. Customer played 'reverse uno card' on me..
Meaning?!
They reported a feature missing on uat env, when in fact I fixed a bug they have on prod..
Not sure how I should feel about this, but it sure made my day! (: I just hope they will not open a bug report for this missing bug..4 -
Fixed a bug in a code wrote 11 years ago.
It took 11 years for a user to find a bug.
The user must have a prize: a Bug Bounty.
My Boss does not like Bug Bountis
4 -
Had to fix a bug in flask App built by 3 ppl !
So I some how roughly figured out the code and was trying to fix.
The bug was
I click on submit, two times the record was entered into database.
(Second time, duplicate error).
So to figure out ,I just commented the code which inserts to DB!
Whola!
Now only one record is inserted!
I still don't know where it's actually inserting !, And IDC , problem fixed
Shall I boast about my skills!?😂3 -
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...1
-
Bugs fixed, bugs have been fixed, bugs removed, daily bug fixing, bugs have been weekly fixed, update, daily update, weekly update, ...
9 -
My reaction when a bug I fixed reoccures after another developer merged in his changes: http://m.imgur.com/vyez0MS?r1
-
I could kill someone. My boss occupied the whole cluster for 24h yesterday, so that I had to wait until today to see that I had a small bug in my code. I wasted a whole day waiting around for something I could have fixed in 5 minutes yesterday if I only had 1 free node on the cluster 😠
Worst of all, if anybody else had occupied the whole cluster for so long without asking, he would have sent an angry e-mail to the whole institute 😠4 -
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 fixed4 -
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 -
I downloaded somebody's GitHub code to use for a project. It had a bug that broke functionality, so I fixed it and started running it to gather data. Then it stopped working for a different reason. I rechecked out the code fresh, same (second) issue occurred. It was a second bug, that once I fixed it, everything worked. But I didn't need to fix it the first time! There weren't any commits in the last two months! I blame ghosts.
-
Most satisfying bug I fixed?
Indentation bug in python after searching hours for the bug. Yes, indentation bugs still happen in 2018. Thanks to TDD I failed fast otherwise it would take way longer to find the bug. -
A big project in my company. Had some annoying race condition that caused data to get deleted when two processes finished in the wrong order they hit the dB and override each other’s work.
Long story short. Fixed the bug and in the process the codebase shrunk by 60%. I didn’t have to delete the rest of the code, but the bug was due to a function in the legacy section of the code, and found out that it was the only function used in that section.
So I deleted it. Rewrote the function so it upserts. And bam. Smaller, cleaner code :)1 -
Bug fixed! Commit, close ticket.
Ticket reopens. Dang.. let me test it. Still fixed, wtf? Send message to QA guy that opened it again.
"Read my comment." Comment has some entirely different yet slightly related bug.
Leap out window.1 -
+++ Windows 10 NTFS file system corruption 0-Day will be fixed soon +++
https://bleepingcomputer.com/news/...2 -
> Moment you thought you did a good job, but ended up failing
> Times the bug wasn't actually your fault
> Times you took the blame for a junior or other dev
> Times someone took the blame for you
> Times you got away with something you shouldn't have.
> Most valuable data loss
> The bug you never fixed
> Most satisfying bug to fix
> Times where a "simple" task turned out to be not so simple
> Debug code left in production?
> Moments you wish you could undo
> Most satisfying optimization
> Have you ever been ranted about? -
Damnnn, have u ever found the solution to problem while u were sleeping cause i found the way how to fixed a bug in my dream maybe cause i was thinking about it before i went to sleep but its really weird when i think about it. 😬🤯1
-
I accidentally fixed a CSS bug that has been bugging me for weeks. I wish it was always like this.1
-
Worked with a team on a mobile app project. The system needed to contact a system coded in php.
When a call was made to php, it would be stored in a variable $call. Weirdly it never worked. After spending days trying to find the bug, it turned out that a junior Dev had created a variable $call in another file that was being included into the api file.
We partied the day the bug was fixed 😎 -
Brave Browser was found hardcoding referral links to partnered Crypto sites, even if you manually type the URL.
Since then , they have fixed the bug but it's hard to trust Brave again.
Privacy is built on trust. I have recommended Brave to my friends and family and seeing news like this , makes me skeptical about the company.8 -
Finally fixed a bug that's been bugging me for weeks, but now friend wants to commit suicide. What a world we live in.6
-
99 little bugs in the code, 99 bugs in the code, 1 bug fixed...compile again, 100 little bugs in the code. 🐞
-
Okay, we fucking get it guys, you wish that you'd get changelogs with every app update and they'd tell you everything and blah blah blah.
Fuck off
We're the only people who even check, it's not worth the effort. Unless a major feature was added or a well known bug was fixed, the "fixed bugs" is more than enough for the general public.3 -
Proudest bug squash experience?
Fixed a N+1 pattern bug on our web site. Wasn't a deeply technical problem, but I was proud to shove the fix up the arse of the developer who blamed me (and even got a VP involved) for the web site crashes (the N+1 involved his code calling a service I wrote) and none of the half-dozen other devs found it.
I really wanted to make a t-shirt with his initial 'blame' email outlining all the 'technical problems' with my service, and the fix was literally moving the service call outside 5 (yes 5) level deep for..each loops.2 -
Last summer we went camping but it was raining for 4 days straight. The first and second day we all went to a nearby mall. On the second day I bought a new mobile router with the only carrier that had reception on the camping grounds. The third day I stayed in the tent coding along while the rest went for the mall. In the fourth day I got angry messages in slack telling me to enjoy my vacation instead of working. Fixed a major bug that day the team had trouble with. It was a very nice vacation and on the fifth day the sun came out and never left until the vacation was over.
My lesson learned was: if it's raining, fix the production bug to get sun again -
Holly crap..... Just fixed a 7 months old bug in a system i worked on and had to leave it for 7 months coz i just wasn't seeing what i did wrong and today..... everything simply unraveled
It's a flask app and i got stuck on updating a column in the database and also it created duplicate configs on one of the configuration functionality
Figured out what was causing duplicates
A different function was creating new configs instead of updating...bypassing duplicate checking in the config function2 -
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'sfinger : hey I fixed that finger but still got 2 critical fingers and 4 small ones7
-
🎶 It must have been a bug,
but its over now-ah-ow...
🎶 I'm not sure what I did...
but I fixed it somehow 🎶4 -
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/ -
Me: Hey, I looked into the bug, *explain what it was, how I fixed it, when it will be pushed etc.*
Boss: *calls immediately* How are you doing with the bug?
Me: ... I sent you a message?7 -
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!4 -
>end of the work
>me tired and want to go home to pet my cat, dog... and fishes or whatevs
>while shutting down monitors I was asked to help fix the bug
>fml
>ok, though I was not working on that part of the project
>fixing it and feeling proud
>today I got angry messages that it wasn't a bug and I shouldn't have touched it
>the person who asked me to 'fix' it did not understand why it worked in the way it worked (and I fixed it in the way he wanted it to work)
>ffs...
>I guess next time when I feel tired I should just be avoiding helping people
>time to think of prepared excuses3 -
I remember when my module lead left a bug... he immediately went to the client location. He managed to go in the room where only restricted people were allowed.. (even I need to take many permissions to go inside) he confidently asked to check some logs to get the access to the machine, fixed the bug and came back in heroic style.
I was really impressed. -
Had a very productive day today:
1. Fixed a small bug
2. Ordered Tab S6
3. Watched the entire season of a Netflix show4 -
One of my coworker change the code from
```
void foo() {
if (condition)
{
}
else
{
}
}
```
to
```
condition ? ifTrue : ifFalse;
```
and add it to changelog
```
- fix bugs // yes with an "s"
- feature added
- some list of the bug fixed.
```
I refer back to the commit, only one Fucking commit and on changes. Bro, what the fuck?8 -
Sent a company-wide email with changelog of an internal tool. Front end guy made some simple UI fix while i fixed a nasty bug that was causing data loss in the back end.... Everyone praises the UI fix...
Kill me now 😫3 -
Bug - if it is reproducible, then it can be fixed with no time.
But it is never gonna be that easy 😂
-
?rant
We bought an expensive middleware which helped development speed and stability a lot. Something did not work and after a week I located the bug in the middleware. Support was adequate and the bug got fixed after my report.
I'm not mad at the developers, because bugs happen, and this one was hard to catch, even with tests.
On the other hand I have to explain my boss what took so much time.
It really wasn't my fault, but I also don't want to shame the middleware company, because it will make it harder for me to buy their stuff (and I quite like their products) or even any software at all. -
I had a ticket to enhance the loading of a page.
So instead of doing 40K requests to a MySQL DB in order to generate a tree and display it to to the user on each page visit, the initial query was optimized and moreover, the results are saved in a MongoDB which will then are served to the user on each page visit.
Long story short, after a code review the code got shipped to production and there was a bug which got fixed in a Hotfix shortly afterwards.
I got all the blame for the bug.
I don't deny I have a responsibility for the bug.
Do you guys think the code reviewer also has a shared responsibility for the bug?4 -
Today on "fuck Firefox": elements with display: inline and position: relative completely mess up z-index and nested fixed / absolute positioned elements. It's a known bug, it has open issues on bugzilla since 2005, but still no fix. IE 8 can get it right, but not Firefox...9
-
I came home about 1am and saw a bug in a small (unpaid...) project that had to do with timezones (see some earlier rants). Fixed it, got to bed.
A few days later I realized that a feature I implemented before was gone. Going through the git log I found out it was me in that night who removed it, by accident I suppose.
Not the end of the world but I was quite intrigued by my own drunk ability to remove a feature that had nothing to to with what I was doing and not even noticing it.2 -
The Hydra regrows three heads for every head chopped off. Just like fixing bugs. For every fixed bug three new pop up.
-
Me: Alright, new week, back from vacation fully rested and focused, lets get productive.
Apple(safari 10.3 update): Fuck you.
Basically the change log was:
*fixed critical security bug.
*added more bugs to fix later.
Well fuck you too safari... You disgust me.
The least the fucking imbeciles, or monkeys, behind safari can do is add a fucking css prefix. For fucks sake. -
Working on this bug for a day. Frustrated Friday afternoon. Decided to explain to my manager and senior why I can't find a fix and while explaining it to them, I eventually figured out the problem and fixed it.
I just realized I used my manager and senior as rubber ducks. -
Finally, fucking finally I fixed a damn bug that seems to be freaking popular on asus machines. This damn bug captures the fn keys needed to regulate the screen brightness.
All tools that display your keypresses didn't find them at all and I had a pretty tough time find the source of problem.
You can create as many arch memes as you want but you cannot deny that the they are truly MVPs imo.
Today I also:
* Fixed and refactored a bit of code
* added shortcuts for volume and keyboard backlight control
* Installed lots of fonts
* Got Steam to run
* Found out the meaning behind the Arch linux
* Felt disgusting using windows 10. Learned that 10 stands for the number of minuts before I must vomit 🤢
* Learned a bunch of linux stuff
But most importantly
*installed sl -
I found xss on the software the my school and many other schools use it. The bug is on every page of their website.
I reported the bug to their team, they fixed it and didnt even reward me.
What do you ranters advice me to?
7 -
most memorable bug I fixed
Line 1:
- throw new Error(‘test’)
+ // throw new Error(‘test’)
yes, this was committed code in production4 -
bug comment in the tracker, from the new junior dev, during her first week:
"probably fixed by [other dev]".
Among the unhelpful comments, this was a special gem. really special. a What the Fuck did you mean by that special. Was it fixed or not? who fixed it? [other dev]? someone else?
it was better not to have any comment at all.
later that junior became a really good dev... -
My thumb hurts / is exhausted from lots of typing (phone) and writing (school). Any tipps besides seeing a doctor? (I will if this bug isn't fixed 'till friday or so)2
-
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.3 -
I don't know if this is really much of a rant
So I fixed a huge bug in a standalone tool I'm writing for my team. Took care of some personal stuff, i.e arranged a long weekend away, booked leave for that, arranged a dentist appointment, felt so productive. Ready to go home, looked at time, 10:00...
Fuuuuuuuuuuu- -
Omg I have to check 2350 svn commits.
We have 2 seperated frontends, one for maintaining old UI and one for new UI which is going to production in one month. So now I have to check if any CR/bug was implemented/fixed only on old UI. Frontend2 was created last year on july. Fuck my life2 -
had an incredibly productive day today on the ultradark blockchain. wrote a bunch of tests, updated documentation, split the repo into 3 seperate ones because it got too big and had too many different things in it, AND accidentally fixed an annoying, deep-recursion bug that ive noticed for a while now.
seems too good to be true...1 -
JoyRant build 18
I fixed a bug which would "break" links when editing a rant or a comment.
The links broke because devRant shortens them.
So now I’m "resolving" them by replacing the short links with the full links when editing.
Here I used the good old trick to start from the end and replace in reverse so that the ranges don’t get messed up with multiple links. 🙂
TestFlight:
https://testflight.apple.com/join/... -
Don't you love when there's a teeny tiny little bug in your code that's not very important but you want to get fixed because you're a perfectionist so you start inserting log statements and it magically fixes itself and stays fixed even after removing the log statements? So now you have to live in constant fear that the bug will appear again and you will never be able to fix it.
Abfjancnancnamxhajd fuck this, fuck js, fuck webpack. It was probably a fucking cache issue but who knows, fuck everything.8 -
I was deploying a fix for a bug (for a hotly-anticipated feature) with a really strict time limit (there was literally a countdown clock). Our senior dev couldn't do it, and threw it out for the masses. I fixed it with about 1m30s left on the clock.
That felt pretty great.1 -
To fix a bug I added a few log messages to trace what gets executed and in what order (very new to the project). Fixed the bug, pushed PR and the only comment was to remove the log files. 🤦♂️🤦♂️
Please tell me this is normal or should I start looking for a new place that hires "only the best" 😭10 -
QA: * reopens the bug I fixed *
Me: hi, whats up I thought I fixed that?
QA: *proceeds to explain totally different issue from totally different module* ... andd April fool.1 -
I just fixed a bug I've been trying to fix for over 10 hours. "Email not sending in laravel notifications but sending with Mail::send". How did I fix it?
Changed "email_address" to "email" because that's what the framework was expecting.
How do I explain this to my client? 😂😂3 -
Fixed a shitty fucking shitfuvk bustard bug yesterday night at 4 am ...
Switch off the system .
Went to sleep
Woke up in the morning and boom !!
That same bug but in another form came up .
End of my fucking love story -_- -
Thursday: Made an appointment with doctor for (painful because no anesthesia) outpatient procedure. Sent message to team slack saying appointment would interrupt part of my day.
Friday: Boss decides to launch website. Launched.
Saturday: Fixed many broken things.
Sunday: Fixed more broken things.
Monday morning: Texted team about fixing more broken things WHILE BEING OPERATED ON!!!!!!!!!
Monday afternoon and evening: STILL WORKING ON MORE BUG FIXES!!!!!!!5 -
I fixed a bug properly... Took down an entire application systems, sometimes you just gotta monkey patch that shit.
So it was a 15 year old cold fusion system and chrome had deprecated some window pop up feature, so I tracked it to the shared function that triggered this, fixed it there, tested it and even got it all past qa.
Turned out some of the other modules on the app had some other logic around this that made it not work there, they had implemented the fallback check without any fallback logic.
Time to rollback a 3 week sprint...1 -
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 -
I was working on an annoying bug in my genetic algorithm for about two hours when i realised it's late and decided to call it a night. Turned off my pc, shut everything down. Just as I was brushing my teeth I got enlightened by the code gods and suddenly i knew exactly how to fix the bug. Toothbrush in hand i booted the whole system again and successfully fixed it in 2 minutes.
Thank you code gods, i may now sleep in peace.1 -
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 😁 -
Fixed a 9 month old bug today which couldn't be reproduced in debug and the stack trace from the release was utterly useless.
Total fix..... 4 lines of which two with only brackets1 -
The bug I never fixed isn't a bug in code I wrote, but rather an OS problem I've given up on fixing.
I dual-boot Windows and Linux on my desktop PC. Every time Windows updates, it switches from grub to the Windows bootloader, making it impossible to boot into Linux. I've fixed it three times (each time requiring a different fix, from disabling fast startup to reinstalling Grub from a live USB), then gave up. My desktop PC is now a Windows machine. I'm upgrading some parts soon (including replacing my boot drive with an NVMe SSD) so I decided when I do that, I'm just going to reinstall Linux on the new drive and see how long I can last without installing Windows at all.3 -
Asked my teacher for help in 10th grade, she came up to my computer, looked at the code, zoomed in to 350%(ctrl+), mentioned that in C# we use upper cased functions names and then disappeared.
Not only the bug was not fixed, I couldn't even execute my code now.2 -
The most satisfying bug, the fucking mosquitoes at night, after buzzing around my head or hours. Fixed them by fucking smashing them on the wall with a shoe.
Oh wait, you meant a dev bug.
On my previous job, any problem that my egocentric idiot that i had as PM couldn't solve and i could, was satisfying to solve. -
!rant - it's a THANK YOU!
Had the problem so far that I could not start some apps in docker containers with GPU support (e. g. Chromium).
After a long search and a lot of help from the community, today's update of xf86-video-ati (1:7.8.0-2 -> 1:7.10.0-1) has finally fixed the bug. Yay!
Thank you very much Arch Linux and all the great maintainers. You're doing an awesome job.2 -
After merging 2 branches, Git randomly decided not to merge one particular line (the place where my newly defined function was called) and that caused a fixed bug to reappear. First time in 4 years I am witnessing Git do something strange like this— probably an issue in the “merge by ort strategy”.5
-
As much as I enjoy working with Magento 2, (No really, I actually do) the amount of times I come across a bug that is reported on GitHub and labelled as 'Fixed in 2.2' or 'Fixed in 2.3' without any commit reference or backport to 2.1 is pretty infuriating. Upgrading to 2.2 would probably break many more things than it would fix, too.
-
During my internship, I fixed a bug in android app related to user data updation..
BUT I didn't knew it's root cause and I have no idea how I fixed it.
Also, it was satisfying.1 -
These goddamn fuckers who every week spam people because their CI or code is broken. Apparently it's more important than other projects. Douchenuggets send an email and CCs the whole department and all the bosses and basically says "It's all broken, the whole company needs to work on this asap, it's possibly x other person's fault".
Then when you try to troubleshoot it because bosses want it fixed, the dumb pieces of fuck made a bug in their code that they could have easily fixed if they took the time to troubleshoot themselves instead of panicking like jackasses. Or better, have good tests and actual error handling.
I swear some day I am gonna get into a fistfight I started because of this bullshit. -
Only for the fact i had my earphones turned off I overheard the BA saying the ticket im working on is no longer a problem as the external vendor has fixed the issue.
What the Actual Fuck is going on, if i didnt ask what the story was i would have been working on a fucking bug that wasnt present in live or ever will be,!!
Get to Fuck you God Damn Ass Clown -
My last commit:
git commit -m "This better f*ing work or I will make everyone's life a living hell tomorrow morning... btw, I fixed the ie 10 display bug." -
Guys. Guys. Guys.
I went to sleep last night, after hunting a bug the whole day that showed up towards the end of my simulations (after several hours of simulations) and that crashed my program.
The crash was due to a bounds error in a fixed size vector, that worked on all the other thousands of iterations but for some reason randomly crapped out late into the sim. So I gave up and went to sleep.
Booted up my program today, 10x speed gain and no bug. Please send help. My brain is playing games with me, I'm sure. This shouldn't happen. :(1 -
This feeling when you finally fixed an annoying bug in your code that gave you headache for days... :)
-
Hello god, I'd like to report a bug.
this.IsSocial is true, but this.BeSocial() throws a NotImplementedException.
I'd like this fixed ASAP, at least by changig this.IsSocial to false since the BeSocial method is not implemented, but this mismatch is killing me...
Anybody know the URL of gods issue tracker? I really need to file this bug...4 -
I had a bug in my code, I was sure I fixed it but when I tested it nothing was charged. I asked my friend to take a look, and when he looked over my code I found out what the problem was: I tested with the older version.
-
!rant
Borrowed our designers desktop figurine / mannequin , i read somewhere that there is something called rubber duck debugging so i tried it but on a mannequin , honestly it works like a charm i have fixed a bug in the code thanks to talking to a inanimate object. -
"Hey before we launch, can you reintroduce that bug you fixed on Friday? The other team needs it for debugging."
Why the fuck would you need debugging code in production and why the fuck do we want to readd something that was causing problems? Shaping up to be a great week already. -
I build a project for internal team around a year ago. QA did sanity and we released. Product wasn’t used and suddenly they decided they want to use project. They forgot almost everything about project feature. I had product doc and ask them to follow. Still they kept making mistake. And finally they found an edge case bug. Now these idiots making noise that product is buggy we are blocked. We are not able to use.
After I fixed it is working but these idiots are asking why there was bug and made us blocked to use product. They couldn’t follow doc to use their own product. They are just trying to pin blame on me and wash their hands. I was really pissed . I told there was bug but why the fuck it took a year to know ? And yes there is bug but it’s edge case and it happens when you guys make mistakes from your side then only it happens. Even if it is bug. What the fuck you want. Have you never made any mistake in your life? Go fuck yourself. There was bug but I don’t care. Bugs are part of release.1 -
How can someone be applauded like a hero for fixing a bug when he’s the one who caused it in the first place?
Gosh Bill, thanks for saving the day! The least the guy could do is acknowledge he fixed something HE broke. But that’s wishful thinking on my part, isn’t it…6 -
Just fixed a bug I was working on for the last 2 days.. I have set a variable to 1 and everything is working now.
-
Caused an outage on production because of a bug in the make file that hasn't been fixed for years. It hasn't been fixed because everyone knows to side step it. Except for me. Unit now. So the bug shall continue to live until the next newbie gets smacked in the face by it.
Kinda feels like an initiation. -
You are definitely a dev when: it's 5:30, you and your coworker are in the parking lot, both about to get in your cars, and...he calls you over to ask about how you fixed a bug1
-
Never fixed? lol.
Maybe I took hell of a time, maybe I've ignored it for long but at least I've always fixed bug which I came across and will fix if I come across any new (as there might be many hidden :P ).
As I mostly work on eCom and integrations, it's way too risky keeping bug.
Cheers!! -
Fixed obvious bugs.
Tests started to fail.
All error messages read similarly—“Feature XXX contains an obvious bug blah blah blah. It’s supposed to fail, but it’s not.”
F____!!!!!2 -
Was to lazy to fix a bug. Waited some months and then realized the bug magically was gone. Happened not just one time...2
-
"Please provide steps to reproduce" seems to be the catch-22 when people try and kick up a fuss about a bug I'm certain doesn't exist.
It's funny because then they report the bug, they word it like I've ruined their life, that can simply cannot continue to function until this error is fixed, yet those simple magic words "Provide steps to reproduce" seems to put their prioritise back into perspective or at the least scares them back into the void from which they came. -
When you can't understand a compiler warning, try to reduce the problem to a minimal example, and the warning goes away...
... and you realize two hours later that you weren't compiling the minimal example on the same machine as the original. Different versions of g++, one with a bug fixed 😩
(assigning {} to a struct member) -
Damn I hate js in the browser. I fixed a bug, but I don't understand what caused it or how my fix works.
I have 2 semantically identical elements that do the same thing, one of them crashes, while the other doesn't. Screw it!3 -
the worst person I worked with was back in school. he would make no contribution to our work and would have a go at me if I did something wrong and whenever I fixed a bug he would act as if he knew the solution the entire time. it was so frustrating2
-
Hey look at these awesome features we offer in the new version!
*carefully upgrades servers*
*app runs smoothly for few hours*
(Docker container exited with code 137) x 100
OutOfHeapMemory errror
Another dev: "I can't see the data flowing through the pipeline"
Boss: "Hmm, why did we upgrade again?"
*checks jira issue for the software*
Bug Report #125 fixed in the next version.
Aha!
Fuck this shit!1 -
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 -
When it's been one month you don't see that bug always worried you and you realize it fixed itself :)))1
-
Today I spent almost a full hour after office hours debugging my code for an issue only to realise that the local process responsible for live reloading my code did not pick up changes after git branch switch.
So in retrospect, if I had left the bug for the day it would have automatically got fixed tomorrow once my laptop restarted.
But no...I just had to figure out the issue on my own today which wasted a complete hour and I won't get it back 🤦🏽♂️ -
Same user. One profile was loaded, one was not. Look and see. A reload of the rant fixed it. Idk if it's a bug. I'm reporting it anyway.
-
Today, I found a bad bug. I fixed it and tried to understand what happened there. Story description was ok, dev was done on time, review performed (1/3 of the time needed to developed), testers were happy: story was DONE.
I feel uneasy as all protocols had been respected, and still, the code was bad and features were broken :( -
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'm so happy today. Fixed a bug that was haunting me for weeks. My ionic app was working on Android, the browser, the toaster,... Everything but an iPhone. I thought it was an issue with iOS and this bug really messed with me.1
-
Every freaking time I think I've fixed my bug and can continue, I see a secondary bug showing up making me revise the code that I previously fixed..
At least I keep myself busy I guess. -
We had a bug with our Karma test (JavaScript unit tests). The headless Chromium crashed after test 272 or 273, every time since a week. I fixed it, but I even don’t now, we Chromium crashed 🤷🏼♂️
-
Debugging a feature that has a reciprocal effect on an other feature is like being given the task to make a toggle switch perfectly flat.
"Oh look, I fixed that bug in feature A. But fuck, now there is a bug in feature B. Perfect, now the bug in feature B is gone. Ah crap now feature A is broken again"
FML -
Yes today I learn ma lesson about deleting projects in Linux. jst deleted a project which had a fixed bug which took me two sleepless nights. I can only recover jar files... wow.
-
That one bug that is always elusive, only happens once during development, you can't seem to reproduce it and think its fixed, and only reoccurs on production or during a demo 🤔 damn it
-
Long standing PhotoShop bug in Wine FIXED! It's stated that it was for CS5, but I've heard one report that it's also fixed a CC version, but not sure if it was the latest CC or not. I don't miss much from Windows, but the Adobe workflow is one thing I do miss. Possibly the ONLY thing I miss at this point. https://bugs.winehq.org/show_bug.cg...
Has anyone got around to trying this yet? Maybe I can test tomorrow and report back!14 -
Why am I feeling that QA always have some attitude?
I observe this for quite sometime now that they can’t communicate! They are mean , sarcastic and passive aggressive. Couldn’t they just have explain the bug and why needed to be fixed.
Why there’s a need of condescending people? Couldn’t people just FUCKING COMMUNICATE?!11 -
Have you ever felt like your smart just because you fixed a bug on someone else project, that bug you did not tell the team you happen to cause it accidentally, but after finding how is everyone stocked about it u pretend to fixit hoping no one will notice , haha , just felt like posting today , super bored,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 -
Apple denied the bugs that I reported , stating it's a duplicate of a future bug😂😂 I guess bug report id are on a rolling basis nd they jus said 1>2 🤣🤣 WTF!! over it they fixed the bug...heights of cowardly acts😕
-
I just fixed some weird bug in legacy code which was caused by UI that contained text input fields embedded inside of text input fields.
How can anyone even think of this as a good idea?!
Needless to say, the UI was just broken. Maybe not a few iOS versions earlier. But definitely on the current iOS.2 -
When you fixed p1 bug in the production and waiting for the release is like watching the conjuring movie all alone in the night. It makes you scare out of shit.
-
It's not a matter of simply "unlocking it". It's a bug that needs to be researched, fixed, tested, and released.
-
Fixed the bug tested multiple times the build. When uploaded on stage not working. Debugging, debugging ... i forgot to push.. blah
-
1. More experience in programming to reach the next level!
2. A job in the USA!
3. Will leave it for a complicated bug to wish it be fixed lol4 -
Today i fixed a bug with which i've been fighting for 3 days. Messages from the device stopped coming through all of sudden. Turned out time needed to be exact 6 characters...
-
So I have been working somewhere around 35 hours straight, with 3 hours of sleep in between and 'breaks', because tomorrow is the deadline for my university project and every freaking time I fix a bug I make another. Most of the time it's something I just fixed...
I'm currently telling myself not to give up. *bangs head on keyboard*2
Top Tags
Weekly Rant
View