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
-
Will the bug in my code please stand up?
I repeat
Will the bug in my code please stand up?
I think we have a problem here.
*music intensifies*11 -
*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 -
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 -
Manager: This code you wrote violates the single responsibility principle!!
Dev: How so?
Manager: You have one function that you call in *MULTIPLE* places. That’s too much responsibility for one function! Functions should only have one responsibility!! Creeping the scope of a function beyond that is a TERRIBLE way to write code!
Dev: But why spin up multiple functions that all perform the same thing?
Manager: Well if a function has a bug in it and you use that function multiple places then that bug exists everywhere you use that function. If a function only has one responsibility then if it has a bug that bug will only exist in the single place it is called! You really should think first before asking questions like that.
Dev: …26 -
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 -
Victory!
Today I finally closed a 'Nessy' bug (A scary bug you can't reproduce typically only sighted by one person). Below is my response...
"There were no errors in the error logs because writing to the error log was causing the error."
5 -
"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 -
Me becoming responsible:
Help in household chores ❌
Help siblings ❌
Finish college work ❌
Report every bug i encounter in Pubg ✔️
5 -
When your in apprenticeship and find a bug that allows the user to skip the payment... that was in production for multiple years...3
-
Tester raises bug:
"Error when loading application in Opera 11.1"
Current Opera version - 48
No tester. Just. Fucking. No6 -
Finding the bug. The usual flow:
"Omg! I think it's a bug in the compiler"
10 minutes later:
"OK, it surely is a bug in the runtime"
20 minutes later:
"I'm certain this is a bug in the core library"
2 hours later:
"Oh, it's a bug in my code. Again, as usual, I'm the idiot. Stupid world."1 -
My Boss: When are you going to finish?
Me: There is a bug, I'm solving it, I need more time.
My Boss: Why have you introduced a bug in your code and now solving it? It were more simple if you didn't created any bug!
Me: WTF!!!8 -
I have been 6 hours trying to fix a bug in more than 3000 lines of code.
Removed one line and bug fixed...
WHAT THE FUCK
I will pack my things and go home...4 -
- there is a bug in the code.
A: I have searched everywhere I can't find the bug
B: What was the last thing you wrote?
A: I called this function
B: did you check the function for bugs?
A: no, I just coded it, there can't be any bugs there3 -
What I would define as a critical bug:
- System doesn't respond
- Functionality is broken
- Client data is all wrong
What QA defines as a critical bug:
- Typo on this page in the QA environment2 -
I hate having moments where you realize the bug was caused by a bug in the framework after scratching your head for hours......2
-
When abandoning a midnight bug hunt in the middle of a particularly nasty bug, always remember to leave kind words for your future self to see, so that they're not as disappointed with you for leaving this work for them.
2 -
That feeling when you find the bug breaking the application in production and you are just an intern :)5
-
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 -
I found a vulnerability in a food delivery app api that allows me to add credit to my account. I ate my first free meal today but i feel bad about it. What should i do 😞.
1- continue hacking free credit and eating free food.
2- stop and forget i found this bug
3- report the bug in exchange for money/credit
4- report the bug for free24 -
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
-
Not a software bug but an organisational bug...
Employees holding the door to other people so they can come into a secured building without using their identity badges.
I look like an asshole everytime I refuse to let people I don't know in because most people let them in...12 -
>>>> Followed link to a post
* Do you Accept Cookies?: Yes
* Our customer supports online: Okay, I know
* Subscribe to Newsletters?: Click Click Accept
* Website wants to turn on Notification?: Okay
* Seen Our New Product?: No, not today
* We require you to be over 18?: Yes, I am
* We value your privacy?: I Agree
* Looks like you're using ad-Blocker?: Turn Off
* Don't forget to follow us on...: Okay!!! I get it already, just show me the f*cking post!
* What next
***** 1 million ads appear around a single post broken to bits having (1-2-3-4-5-6-7-8-9 next>>) *****
Just wondering who invented this money making strategy.8 -
Just noticed that the Firefox mobile browser plays YouTube video in the background.
I am curious... Bug or feature10 -
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 -
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 -
When I see a bug in somebody else's code (Gnome):
- "can you please not write bugs!"
When I see a bug on my code:
-"whatever, I'm only human..."
😅2 -
I'm struggling with a bug. It's not my bug, it's in a lib - in an assembly function commented as "this is where the magic happens". After 27 hours of trying to determine what triggers said bug my best guess is it's a relationship between the position of Mimas and the mood of my neighbour's chonker. If it's not triggered by the Saturn's moon and a pet animal... I'm out of ideas.
Now how do I break it to my PM that we have to kill a cat?7 -
1 little bug in the code
1 little bug in the code
put a little ; in now
compile it around
991 little BUGS IN THE CODE1 -
One of our customers calls everytime when he thinks he found a new bug. Then he literally yells "I found a new bow" since he thinks "bug" is a german word, so emphasizes it like that. In german "bug" means "bow of a ship".1
-
Tldr; my "this is not bug, its a feature" moment actually turned my bug into a feature.
Today we were presenting a project which has imposible deadline. I am developing this small project alone (which is probably good). I implemented core features first but I know project still have bugs and a lot of tech debts. Another friend started to presenting our demo and a wild bug appeared as expected. He was adding rows to a table. To add a new you gotta open new modal by clicking + button and fill the form. One of the fields had a bug. When you add row by clicking Ok button, the value of the field stayed there after you open modal again. So its basically a state problem in React. I forgot to clear previous state of modal. When they see that and my friend said "oh we got a bug there". Then I enabled my mic and said "thats not a bug, thats a feature. I didn't want to enter that field again and again when I adding multiple rows and made it persistent." and you know what? They liked the idea! They requested to add that bug to two more fields. I was just joking and my "this is not bug, its a feature" moment actually turned my bug into a feature. Instead of fixing it, I'm creating more of this bug. LOL!5 -
Have you ever heard the story of the first bug in software development?
The first documented bug was actually a bug. There was a moth trapped inside the computer causing the bugs.
source: https://commons.wikimedia.org/wiki/...8 -
- "Hi A, we had a bug in production due to a changed category ID which we were not informed of."
- "Oh but my API just proxies the content from team B."
_____
- "Hi B, we had a bug in production due to a changed category ID."
- "Ah, I have nothing to do with category IDs, you should talk to my colleague C."
_____
- "Hi C, we had a bug in production due to a changed category ID."
- "I wish I knew anything about that, you should contact person D!"
_____
- "Hi D, we had a bug in production due to a changed category ID."
- *changes status to "Absent" on IM*
ERROR_TOO_MANY_REDIRECTS1 -
When you find a bug in a "min" js file and you don't have the not minified version anymore... ok, it's not a bug it's a feature.
6 -
on the first day of christmas my PM send to me
There's a bug in your B-tree
on the second day of christmas my PM send to me
two threads deadlocked
and a bug in your B-tree
On the third day of christmas my PM send to me
Three servers crashing
two threads deadlockd
and a bug in my B-Tree
on the Fourth day of Christmas my PM send to me
Four clients angry
Three servers crashing
two threads deadlocked
and a bug in my B-tree
on the Fith day of Christmas my PM send to me
Five SCRUM meetings
Four clients angry
Three servers crashing
two threads deadlocked
and a bug in my B-tree
On the sixth day of Christmas my PM send to me
Six deadlines waiting
Five SCRUM meetings
Four clients angry
Three servers crashing
two threads deadlocked
and a bug in my B-tree
on the Seventh day of Christmas my PM send to me
Seven machines learning
Six deadlines waiting
Five SCRUM meetings
Four clients angry
Three servers crashing
two threads deadlocked
and a bug in my B-tree
on the Eighth day of Christmas my PM send to me
Eight repos compiling
Seven machines learning
Six deadlines waiting
Five SCRUM meetings
Four clients angry
Three servers crashing
two threads deadlocked
and a bug in my B-tree
on the Ninth day of Christmas my PM send to me
Nine interns asking
Eight repos compiling
Seven machines learning
Six deadlines waiting
Five SCRUM meetings
Four clients angry
Three servers crashing
two threads deadlocked
and a bug in my B-tree
on the Tenth day of Christmas my PM send to me
Ten Features requested
Nine interns asking
Eight repos compiling
Seven machines learning
Six deadlines waiting
Five SCRUM meetings
Four clients angry
Three servers crashing
two threads deadlocked
and a bug in my B-tree
on the Eleventh day of Christmas my PM send to me
Eleven products deploying
Ten Features requested
Nine interns asking
Eight repos compiling
Seven machines learning
Six deadlines waiting
Five SCRUM meetings
Four clients angry
Three servers crashing
two threads deadlocked
and a bug in my B-tree
on the Twelve day of Christmas my PM send to me
Twelve DBs updating
Eleven products deploying
Ten Features requested
Nine interns asking
Eight repos compiling
Seven machines learning
Six deadlines waiting
Five SCRUM meetings
Four clients angry
Three servers crashing
two threads deadlocked
and a bug in my B-tree3 -
Trying to find a bug. Found a possible line in the code where it might be originating from.
Not I put a breakpoint in there. I can't reproduce the bug anymore.
Sometimes I think I should just go home and play games :(2 -
Reported a security bug in Chrome two years ago, got the response now -
Moral - even google products are fucked up.
5 -
Me: *deploys site*
Someone: Hey, there's a bug in your site's css.
Me: ...
Me: *rewrites css with sass* -
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 -
our tester arguing with software house about blocker severity bug
SH: "No, this bug is not possible. It's possible only when you are logged as admin in other tab"
T: "I managed to replicate it in another browser in private mode"
SH: "But you can't replicate the bug now"
T: "True that I don't know steps to replicate it and it occurs just sometimes... Let me check right now"
...
T: "Okay, I managed to replicate it right now in private mode in other browser on normal user account"
SH: "Because you are admin"
They are pretending to be idiots or just are?6 -
"always think of a bug as a feature"
-Someone I used to know in a hckathon, 2012, colorized, minified -
Dear Client,
Mentioning "Dear Friend" in email won't make your bug as top priority.
Seriously,
Developer4 -
Client writes a bug report: This and that doesn't work.
Me: This functionality never was implemented. Please open a feature request.
Client: But this is a bug. Without this feature, the service won't work as we expect.
Me: But this wasn't in the requirements for release. So you have to contact the PM for a feature request.
Client: THIS IS A BUG! FIX IT!
Me: GO FUCK YOURSELF! THIS IS A NEW FEATURE AND YOU HAVE TO PAY FOR IT!
Unfortunately, I never sent the mail. But I kept it in the drafts. Maybe someday...1 -
Current Job Title:
Hoarder Bug Exterminator
Details:
Fixing code for projects that have not been refactored ever in 20+ years. -
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
-
I hate myself so much right now. I just spent an hour finding the bug in the following:
var counter=0
while(1){
if(counter%2==0){
doStuff()
counter++
}
}
Because I thought it was a bug in doStuff().8 -
Love it when you try to fix a bug and realize the bug only occurs in debug mode.
No clue why, but also not my fucking problem, users ain't gonna debug :D7 -
I 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! 😃
-
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 -
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. -
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 -
In a hospital bed and in my cellphone, web app went down, sended a bug fix while mildly conscious, typhoid fever btw1
-
This is what they teach in management schools apparently
0 bugs - Dev doesn’t exist
1 bug - There’s a bug!
2 bugs - There’s many bugs
3 bugs - There’s so many bugs
4+ bugs - The app is full of bugs5 -
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
-
My reaction when a bug I fixed reoccures after another developer merged in his changes: http://m.imgur.com/vyez0MS?r1
-
99 little bugs in the code, 99 bugs in the code, 1 bug fixed...compile again, 100 little bugs in the code. 🐞
-
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
-
Windows: restarting in 10 seconds
Me: probably just a bug or something like that *click OK button*
10 seconds later
Me: it's no a bug! IT'S NOT A BUG! let me save my stuff
(I don't now why windows did that it made some kind of update without warning except for the 10 seconds and then I had some problem s like I couldn't connect to a SQL server and the computer was super slow)6 -
I found a bug.... it's in production for a long long time... I wrote it while optimizing some legacy code....
FUCK.... how do you feel when you discover a bug in production created by you?6 -
In an encryption-module, I had a bug, that caused my PC to crash, every time I tried to encrypt something.
Turns out, the loop, that appends
0-Bytes to the string, to make it Block-Cipher compatible,
Had an logical-bug in its exit-condition, that caused it to run infinitely and allocate an infinite amount of memory. -
Ever have a bug that *only* occurs in your production environment? How do you test potential fixes? 😜5
-
>makes a bug report about the JS linter in Eclipse Che not working
> makes it a P2 bug (moderate severity)
> confirms in their current implementation it doesnt work
> escalates to P1 (high severity)
wow for once Eclipse is actually making their shit better -
When you realize that the solution for a bug in your code is putting
if (somecondition)
but then you put
if (!somecondition) by mistake and try to figure out why is the bug still there :-(1 -
Had an odd bug today. No rubber duck in sight so I started using my friend (who is not a dev) as a rubber duck. He was *not* amused.
But I did figure out the bug!! -
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 -
Chased a bug for nearly a week. Huge code base, over 2mn lines consisting of a mess of C++, Python and Lua glued together.. Wrote a very complex distributed computational framework. End up with a elusive compiler bug in GCC.. FML
-
Another fun thing. This morning one of the first mails i read was a issue about a bug in our software.
This was a bug i mentioned months ago but there was nog evidence where i searched like mails chats or tickets.
If people would just listen to me this bug was solved months ago but back then i got a reaction like: "works over here" while i tested it on two different instances with buggy results each time. -
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 -
Did you ever take advantage of clients that has less computer literacy? Like have you ever escape a bug in the system by telling the client heavy technical BS! 😋
PS - fixings that bug later obviously!!6 -
Just had a bug reported that only happens in Chrome. Works in IE and Safari. This is going to be an impossible bug to squash.2
-
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
-
Sometimes I think that my computer is possessed.
The story goes like this (typical): adding a new feature creates a bug with something that worked perfectly until now. I find and solve the bug in a few minutes. Now the spooky part: with that sort of bug, even the code that worked up to now shouldn't have worked. But it did. Does someone knows a good Ghostbusters service?1 -
Happy days, yesterday we updated form 16.3 to 16.4 and thanks to them fixing the bug in 'getDerivedStateFromProps' my broken code is now breaking.
Don't you just love it when features inadvertently depend on bugs. The entire component ONLY worked properly because of a react bug.3 -
Sherlock Holmes' "It's never twins" translated for programmers is "It's never a bug in the language"2
-
i spend now 5 hours of searching a bug/typo in between 200 lines.... either my eyes are shutdown or my mind goes like ace ventura.
i didn't found that fucking bug....3 -
Why everyone in management wants to know how i solve the bug if you do not even know what is Bootstrap. All that matter is fucking bug is resolved PERIOD
-
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 why I'm doing this but when I go to websites that aren't mine and found that there's a bug in their site or system, I kinda happily report these bugs and issues to their email with screenshots, findings and steps to reproduce the bug.
Just recently, I just went to a site and found a peculiar timeout error, eventhough it was less than a second to respond back. Only to find that there was an undefined JavaScript variable in their code.
Is there a bug bounty for fixing code?6 -
The feeling of fixing an annoying bug is much better, than the feeling of finding something good in the fridge.
-
The worst bug?
Skipping a payment with 20 chars of js
System was in production like this for two year... -
Soo insyde BIOS got a big bug via 17.10 ubuntu iso
- Settings not getting saved in bios
- USB booting is a no-go.
- suspend never wakes up without battery removal
Infected systems mostly include acer, LENoVO and hp mainly
I am surprised it took them this long to notice the bug.8 -
Couldn't sleep this morning, so at 6am I tried to tackle the bug that gave me a hard time yesterday... at 10am I found the bug, and so I remembered the number one rule when coding.
KISS? Nope.
The number one rule is that your past self is dumb and he probably created the bug in the easy part of the code... you know, the one you didn't even check because of-course-the-bug-cannot-be-there-Im-not-stupid.2 -
My stress ball has been stolen!
I came in to work to an email alerting me to a bug in production. I copied the site to staging to work on the issue but I was unable to replicate bug. My rubber duck wasn't helping so I went to go bounce my ball off the wall when I realized I don't have a stress ball anymore.
I spent 7 hours working on the bug without a stress ball before finally fixing it. And now I'm ready to deal with the theft the old-fashioned way.3 -
when you spend more time in JIRA explaining the client that their bug is not a bug but misconfiguration on their side than actual programming. :-/
error between chair and keyboard.1 -
Not sure what is going to be worse. Fixing the bug in this code. Or removing all of the code I added in the name of finding the bug in this code. I have found myself asking myself why I chose coding when I come have picked something less stressful. Like flaming bull fighting.
-
Finally solved the most elusive bug I have ever encountered.
It only occurred in chrome and the reason I could never recreate it is because it didn't happen when developer tools was open WTF!
Try solving an apparent JS bug without your console - I've never been this happy/relieved!2 -
@dev-rant @dfox @trogus
Feature+bug
I think it would be better for the development of of the app to include a feedback/bug option.
Bug-> I changed my password on a different phone but the current phone didn't ask for the updated password, and logged in.7 -
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 -_- -
Why shouldn't I clone production DB locally in order to debug an issue / recreate a bug? What is the alternative?5
-
Slacking off in Hawaii or running for my life.
Depends if that three laws thingy was implemented bug free.4 -
When you have a bug filed for a feature you created to spec, questions it, and then they state the the bug shouldn't exist as it is "common sense" even though it's not in the spec.
-
In the process of fixing a bug, have you ever made your program better without actually fixing the bug?
I feel like it happens a lot to me. -
When you're trying to find a bug in your parser/interpreter but it's working fine and all this time the bug was in the code you were feeding to the parser/interpreter. Smh2
-
Program: Meets a critical bug, potentially crashing the whole system.
Administrator: Presses the "Emergency stop" button.
Emergency stop program: Meets a critical bug in itself.
Admin: X . X -
This feeling when you finally fixed an annoying bug in your code that gave you headache for days... :)
-
Why does our boss think that there is "fix it" button for every bug.. which will magically solve the bug in 1 minute.1
-
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 -
My new feature has a bug in it, but not in Internet Explorer..
Huh? This is new! I know this the other way around! -
That moment when you are deep in the zone, focused and solving that damn bug, and the managers began a loud meeting a couple of meters from you, throwing away all the chances to solve the bug, even with earbuds on...
-
So you find out a bug in your own code... a bug that nobody noticed in the month it was out and about... because nobody used that feature the manager asked for in one of those mood swings... that yet you so had so carefully built with love...2
-
testing feature: that is not what the specs say this how this is suppose to work. so, I write a bug report.
conversation with developer goes as follows
developer: this is not a bug. sends the bug report back.
me: the specs say it is a bug. I resubmit the bug.
developer: sends it back saying that it has been changed in the new specs.
me: how do I get the new specs?
developer: it is on the server, go ask your boss on where ecaxtally on the server they are. then, he closes the bug report.1 -
You know that feeling you get when there is a bug in Prod and to identify the cause, you setup your dev environment with the exact same codebase as Prod. But the bug won't show it's ugly little mug in devo...
Yeah, Fucks me up too... -_-2 -
I received the following e-mail today:
Hey, XYZ! Could you please check the following in your web application. The data do not show correctly. Could it be a bug?
[insert attached screenshot with said "bug"]
My reply:
Hey, ABC! It is not a bug. You uploaded the data into the wrong table. 😊
[insert attached screenshot with the incriminating evidence]
-----------------------------
I felt a bit savage and I liked it. 🔥4 -
Today I had to fix a bug and it took me about 2 hours to find out that it related to a bug in a component which doesn't belong to the bugs component. In development everything where fine. But after deployment the bug occured. Found out that when running Vue webpack projects in dev it handles errors different, kind of a global try catch block. After deployment the application breaks.
This teached me again that we should not ignore any red error line in console. -
There is a bug that causes a second notch to appear in the pixel 3xl. On the right side.
https://androidpolice.com/2018/10/... -
It just came to me.. an error in a computer program is called a bug.
A listening device used to spy on people is also called a bug.
A computer bug can be used to spy on people. IT ALL MAKES SENSE NOW, PEOPLE! 🤯
(yes, I know the story of why it's actually called a bug. Still, I find that very entertaining.)1 -
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. -
There's no bug free program on earth, they say. Well show me a bug in my program
<?php echo"hello world!";?>
😂 😂6 -
Yesterday I wasted 2 hours because a bug in EF Core (https://devrant.com/rants/2323794/...)
Today I wasted another 2 hours because of a bug in Android Studio 3.5.2, which had a report only available in AS 3.6-alpha channel.
Dev life is wonderful huh?
https://issuetracker.google.com/iss... -
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 -
Fuck when your client find a bug in production, but you can't replicate in your developmment environment. So sad 😣2
-
Q: What will be left in your code if you remove all the bug causing statements?
A: print("Hello World!") -
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 -
Y'know, there are some things that are timeless. Like bug severity arguments. We don't have a "likeliness of occurrence" parameter in the bug database. We just have "severity if it occurs". You have to classify it as such. The bug database IS NOT FOR RISK MITIGATION ACTIVITIES IT'S FOR FIXING THE FUCKING SOFTWARE!!! STOP MAKING THESE DAMN MEETINGS TAKE 30 YEARS BY QUESTIONING THE SYSTEM THAT WAS ESTABLISHED IN THE BEFORE TIMES BY PEOPLE WHO ARE ABOVE YOUR PAY GRADE!!! TINDER BOX!!! MATCH!!! GODS DAMMIT!!!
-
I wrote a cellular automaton in university (elementary game of life). It was generating shapes but it just didn't work. It seemed like the shapes would degrade as they went until they caved into some mesh of pixels.
Turns out that when counting the number of neighbours around a cell, I was counting from 2 because of an earlier bug.
The really interesting thing about this bug though was that it made sense. There were too many people and the resources ran out, which meant the patterns that would normally survive were dying off early.
It's a bug, but not a bug. -
Thanks past developer for not only one bug but also the bug in your exception handling attempting to catch this bug which resulted in confusing the hell out of us for way too long due to output that made absolutely no sense
-
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
-
Man, at the rate I'm going, I'll have to put a bug I found back in April on my new years resolution list...
Sad thing is, as we all know, new years resolutions never work out... So maybe this bug will never be solved :S -
Marketing in other companies: we found a bug, let's make it a feature!
Our marketing: We found a feature, let's report it as a bug!1 -
Why the fuck does Visual Fucking Studio SSIS delete scripts in script codes? A completely bullshit bug in VS 2017, completely in fucking excusable to find my fucking scripts GONE when I try to run the package. Download it from TeamCity? Still gone.
How does a business like MICROSOFT let this sort of bug even happen?1 -
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. -
Working with microcontrollers is like another level of frustration.
Beside the code not working you are on another level, which is the hardware not working...
Once spent 6 hours searching for a bug and in the end the "bug" was swapped cables for communication.2 -
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 ...
-
It's almost all the time but specially when there is a stupid bug i find out in production after all the efford i put on testing before release, or even worst, when the bug is not stupid, is random and just hard to tell why the fuck everything is fucked up
Top Tags
Weekly Rant
View