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
-
When you "fix" a bug not by actually fixing the bug but by disabling the user's ability to cause the bug.
14 -
"This is not an application: it's a bug pretending to be an application." (This comment was left as an app review on Google Play Store)3
-
Today I received the best bug report I could've ever asked for..
Received an email from a member of our customer service centre containing a description of the bug they'd found and not only did it contain the steps to reproduce the bug, but a goddamn video of him reproducing the suspected bug!
The greatest feeling when the client decides to take time to make your life that little bit easier24 -
Leaning Tower of Pisa being a wonder of the world is basically "It's not a bug, it's a feature" example.1
-
Receiving a bug report from the manual tester “numeric input does not work”.
He accidentally disabled Num Lock on his keyboard.16 -
Today, I finally had the opportunity to say to a client: "It is not a bug, it is a feature".
No, seriously, it is a feature.2 -
What's the worst bug? Schrödinger's bug, one that only appears when the debugger is not attached, and your test instruments are disabled.12
-
I love how "minimal" devRant is.
No username, no time... just the number of likes and number of comments ..
*it's a feature not a bug*
✌(◕‿-)✌3 -
Turns out, double tapping the rant too fast will not ++ it, but open it (sometimes twice even).
Not certain if it's a bug or just my shitty touchscreen, but make sure you tap more slowly if you have similar problems.3 -
When you hit run after an hour of powercoding:
Old Mcdonald had a bug,
E I E I bug.
And on that bug he had a bug.
E I E I bug.
With a bug bug here and a bug bug there.
Here a bug, there a bug, everywhere a bug bug,
Old Mcdonald had a bug.....
E.....I.........E............I.................
[FATAL ERROR] : Program has ended for a simple reason...not telling why though...here's a completely unrelated line of code you may want to take a look at :) -
Every week is the same. Wake up, new jira ticket. “Build us a pink house”.
*i build a house*
Next day, “URGENT BUG REPORT!!! CRITICAL ISSUE IMPORTANT IMPORTANT IMPORTANT”, click on ticket, “bug report: the house doesn’t have sprinklers”
They didn’t ask for sprinklers. This is not a bug. *i add sprinklers*
Next day, “URGENT BUG REPORT!!! CRITICAL ISSUE IMPORTANT IMPORTANT IMPORTANT ASAP ASAP ASAP”, click on ticket, “bug report: the house is pink.”
HOW IS THAT A BUG TWO DAYS AGO IT WAS LITERALLY A REQUIREMENT
Meanwhile management makes triple my salary6 -
Oh yeah that.
That's a known bug.
It's been there for a long time now and the customer knows about it.
We ship it as expected behaviour now.2 -
My application closes, but with an error, but it technically still closed. Soooo, no problem, right?
5 -
Our product owner's equivalent of "It's not a bug, it's a feature" seems to be "It's not a new requirement, it's a clarification."
:-/2 -
All the ++ counts are showing in binary... If this is an error I vote we keep it as a feature not a bug.3
-
Tester - The app has a bug when I try to buy a ticket
Me - okay, what's the bug ?
Tester - it shows an error
Me (trying to not high-five him with a chair in the face) - What's the error message?
Tester - ah nvm it works now!!
Fuuuuuuuuuuuuu. Explain the issue you dimwit, don't just say it doesn't fucking work!2 -
Appreciate how lucky we are. We get to say "It's a bug" instead of "I've made mistakes". Suddenly it's not our fault.3
-
Having to deal with stupid testers who think your app should be resistant to water and black magic and report a bug if it is not5
-
Been working on a bug fix for 3 hours. Literally nothing I do will fix it. Finally I realize I'm not even calling the function.5
-
STOP BREAKING FOR NO FUCKING REASON YOU FRAGILE PIECE OF BUG-INFESTED SHIT
I’M NOT EVEN TOUCHING ANYTHING WTH10 -
You know your getting deep in trying to figure out a bug when you start discovering bugs not even reported yet.1
-
Team leader: hey why this bug is taking too much time? You could fix it hours ago let me try to fix it. I really fuckin hate juniors ...
*Hours later*
Me: could you fix it ?
Team leader: ....
*Couple of years later*
Me: ah i see it's not an easy but could you find any solution bro?
Team leader: no it's not a straight forward bug. You are right am sorry i shouldn't prejudge5 -
Easy cop out for people who wrote code vulenerable to SQL injection: It's not a bug, it's a feature that let's users search using SQL syntax.1
-
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 -
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 -
PM: Ok Android, i've reviewed the latest build, you are good to release. Waiting on iOS's build to test.
Me: ... are we not holding all builds until we hear back from backend about that bug?, as we likely have to change something on our side?
PM: Which bug?
Me: ... the only one we discussed yesterday in the team meeting.
PM: How many customers is it affecting?
Me: that we know of, one ... the CEO of our company
PM: oh that one, yeah were not doing that anymore.
Me: WHAT? i've been waiting all day / night to hear back. Why are we not doing this?
PM: ¯\_(ツ)_/¯ ... Everything is too messy at the minute anyway, the release plan is changing every day. Need to keep it back in line.
Me: ... the plan has changed exactly once. We had a plan at the start of last week for the last release, we changed it YESTERDAY to include 2 critical bug fixes. The only issue with the plan changing is nobody telling us these aren't bugs anymore
PM: We can discuss tomorrow in the team meeting.
CEO: oh hey guys, yeah we pulled that bug fix. Its not really a bug, more like a missing feature. No way it will get done before xmas. Going to live with the way it works for now and fix it properly next year.
Me: Ok, fair enough, but we really need to be told these decisions.
CEO: sure, sorry, didn't think anyone was blocked by this. What was the blocker?
Me: ..... you asked me yesterday to get this bug fix in the build ... you asked for the final build to be made today so we can go through the app store review. As we all discussed yesterday, today is kind of the last day we can really do this.
CEO: ok, its late, we can discuss this tomorrow in the team meeting.
Me: ..... ..... ..... ..... sure7 -
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 -
Description of a Bug in JIRA:
Hi guys, there is "another" bug :-))))))!!!! :-((( with the customer list:
- The list of Customers (**which one? we have 4 fucking lists **) is sorted by Name, not by Birthday date (**wait, it's a sortable table, with a sortable name, city ,zip column, it's not sorted by birthday because the birthday column was not even required **)
- If I click on the details I see some data missing (**which data? which customer? there are thousands of them and most work**)
- In addition the arrow on the right is too small, can you make it a little bigger (**excuse me**)?
- I also need to export everything in excel.
Categorised as: Bug
Moron. You are part of a League of Morons...2 -
That feeling of reilef and rage when you find out the crippling bug in your code is because you are passing the wrong variable and not because the function is broken.3
-
It's not a bug if a feature is working how you told me it should work but not how you wanted it to work.6
-
my boss asked me to log in 1h30 after i logged off because "a user has been experiencing this bug the entire day and i should fix it because we're on maintenance tomorrow " but a) it's a known bug that we can't reproduce, he should've notified sooner the issue; b) it's not a big deal, i can fix it tomorrow, it's just not ticking a column in the database; c) I'm off work, go cry about it2
-
Overheard a conversation between programmers:
.... Your dirty hack finally caught up with you!
.. it is responsible for bug A, B , .. E ... F..
That "temp" code was not touched in years.3 -
Not even YouTube descriptions (Which, I guess, are automated by BuzzFeed...?) are safe from this little joy of a bug.
3 -
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 -
Who else questions the Apple QA team?
Effective power to the letter "i" not working to the root bug and now this?
Jesus Christ they need to get some help lol
10 -
!rant
Double tap-like is not working properly on my Oneplus 3T while on list view. I'm wondering if it's just me or if it's a bug in the Android app...18 -
Just used my first "It's not a bug, it's a feature" explanation 😂. However, the irritating part is, I had to explain it to another person from IT industry (I mean testers) who is from another company.
And it's really a feature and not a bloody bug. Stop reporting it on the bugs list 😥3 -
WHAT THE FUCK.
I have to deal with a fucking bug that crashes my app only when I'm NOT looking for it.
I investigate another bug? Then BAM, here it is and crashes the app. And I have to start over again find the right conditions to not trigger it again.
I investigate that bug? Nope, everything runs as smooth as velvet.
It's like a Heisenbug, but the cat is dead in the box AND pissing all over the lab at the same time.3 -
Dear people who leave bad reviews...
Do not use a review as a bug report, saying something crashes on your device and telling the developer to "fix this" isn't a review.
It is barely a bug report but a review is on quality, not individual issues .-.3 -
Life as a developer:
Yesterday I could reproduce the bug everything I ran the program, but I could not debug it. Visual Studio would not break at my breakpoints.
Today Visual Studio works fine but the bug cannot be reproduced at all.
I should have become a florist instead...4 -
- "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 -
> I didn't brought any condoms
> Just pull out Anon, we'll buy some later
You could say I went straight to production and now I'm considered "legacy"3 -
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 -
When the client decides not to do a feature because he finds your estimate unreasonable, then tries to add the missing functionality as a "bug" to another feature that's already estimated.3
-
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 -
Whenever I'm stressed out on a bug or what not...
I find some of my best ideas have come from sitting on the toilet4 -
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 -
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 -
Successfully wasted 4 hours then realised jQuery was not inserted..
jQuery inserted..
Bug Fixed.. o_O8 -
Finally had a "it's not a bug, it's a feature" moment today and called bullshit on it. I feel like a real developer now.
-
I feel so bad for the Devs of this app, they can't make up bullshit excuses and not bug test their code like other Devs can
-
I just want to make it clear to all of us here...
Not every goddamn thing is a bug from X or a bug from Y most of the time I, Us, We as programmers fucking make mistakes or don't know the issue because it's vague!!! IT'S NOT A FUCKING BUG!!!2 -
Gotham...
why, oh God, why do you have a scene in SE01 E17 at 9:20 min into the episode, where
J.Gordon uses reading glasses to a screen of an old B/W TV and magically is able to read a logo brand of a jacket.
How did the glasses add hundreds of more pixels to the resolution behind them.
This has ruined it for me, not watching now. Even Mission Impossible where they say "use DDOS to take over their systems" is better than this.7 -
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.
-
Current Job Title:
Hoarder Bug Exterminator
Details:
Fixing code for projects that have not been refactored ever in 20+ years. -
I reported a bug and the PM replied "It's not a bug, it's just an outcome of how the button was coded. Although that's not how we want the button to behave so we'll prioritise this next sprint planning."4
-
Fucking facebook researcher that make underfitted neural nets and fuck Mark that it's a marketing genius, the only idiot that can make news from a failure. The CEO of Tesla knows it and said Mark is not an AI expert. Bug not feature, it's only a poorly trained and poorly designed neural network having a bad representation of concepts, not a new language and not the fucking apocalypse. Google faced and solved the same issue when start ed using neural nets for zero-shot translations without using english as a translation bridge.
-
When we had to implement urgently a small project estimated in two weeks. Took me an afternoon. 3 years later, still works, not even 1 bug.1
-
Client: "I found a bug on your website. Its not possible to submit the contact form."
Me: "No bug. Its a feature"
#answerforeverything4 -
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 swear I NEVER hated PHP before, but after seeing this shit, I just can't love it anymore, I feel betrayed
I mean, WTF? Just bc I'm using the variable as a reference in the NEXT loop the LAST element changes? What even is the fucking reason?
Yeah, I read the answer on StackOverflow, but seriously...
SO ref: https://stackoverflow.com/questions...
12 -
https://thehackernews.com/2019/11/...
Facebug secretly opens a camera on iphones: a bug or a malicious behaviour?
OFC IT'S A BUG!!!! FB DOES NOT UPLOAD ANY PICTURES W/O AUTHORIZATION!!! FB IS GOOD!
/s7 -
Getting "bug" tickets from customers complaining about EXACTLY WHAT I DESCRIBED WOULD HAPPEN. THATS NOT A F&)$*(%$(*# BUG, THATS LITERALLY WORD FOR WORD WHAT I WROTE IN THE TICKET LAST WEEK YOU F&#*(@#$() NEANDERTHAL PIECE OF SH$%*(#(*)!!! WE AGREED ON THIS EXACT BUSINESS PROCESS WEEKS AGO. DO YOU EVEN READ THE WORDS THAT I WRITE AAAAAAAAAAAAAAAAAAAA5
-
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 -
Closing a bug with "Let me know if it's still happening for you" when it's been three years since the bug was filed and you haven't looked at it at all since then be all like...
-
!rant
We were talking about Kafka's "metamorphosis" and a friend said "what if the parents were programmers and did not want to have a bug in the family?" -
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 -
One thing I learned early on was...
"If the bug is not where you are looking...look somewhere else."
I just spent 2 hours looking at 50 lines of code pulling my hair out why it wasn't working. Guess what...those lines were correct. The bug was somewhere else.4 -
Come back from a week's vacation, 3 apps in review. Sit down, set up Xcode, pull latest changes. Run code for the first time, tap through two screens, find a critical bug and I have to reject all 3 apps and resubmit.
5 business days away and I found an obvious bug in 5 minutes.
Someone's not doing their job... -
Did you know that you can't up vote your comments/rants on devRant? Wish it was implemented on other platforms.2
-
Note to self, don't fix a minor bug that will not effect the demo right before the live demo. My program that was working great didn't work anymore during the demo because of my quick bug fix I figured I had a few minutes to add to my code.1
-
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 -
🎶 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 -
Product Owner: There is a major bug with your code it's not working.
I then spend hour looking at code to find out.
It's a content problem! -
I was considering starting a business with a coworker something like dfox-trogus duo...
But damn he can't even stop pushing unfinished changes ... Its not bug... Its bug+unfinished... Bugs I can handle...
Now I really think I might be better alone4 -
1. Push a bug with a bug fix.
2. Fix the bug created during previous bug fix.
3. Push the bug fix which solves the bug created during previous bug fix.
Try not to cry...
Cry a lot 😭 😭
1 -
jim :"this is not a bug.. you just can't use localhost for developing on your machine.. it is forbidden.. things break"
1 -
>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 -
The moment you sit down to try to fix a bug and you just stare and the screen for an hour not understanding how this even happened1
-
coolest bug our team had was not a actually a bug but a feature that is misused and abused.
tldr: its a feature that became a bug
we have an app that has a "test print" feature to test the printer and the format of the document to be printed. it has the word TEST for fields and all that.
it became a bug when suddenly, the users use that feature to print documents, instead of using the app with the business rules and all, and just manually strike off the TEST words with a pen.
the feature became a bug because it has become a security risk. -
One fucking week I was trying to solve a bug where I could save data to neo4j but not retrieve it.
I thought there has to be a bug within the library. But it turns out, I referenced the wrong class.
I need ducks...2 -
Dealing with a Salesforce (what else,heh) bug that caused batch payment requests to be fired off at seemingly random intervals. Pretty big consequences to that one.
Of course, the problem is that no-one assumes it's a Salesforce bug, and you have to spend an eternity proving that it's not your fault...1 -
So,
Acer has a corrupt BIOS,
Lenovo is a bug fest,
HP supposedly also sucks.
So which brand of laptop does not suck?40 -
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!! -
Tis was the night before Christmas
And all through the house
Not a creature was stirring
EXCEPT THE BUG IN MY SOURCE
🎅😡
Merry Christmas and Happy Holidays everyone!2 -
Looking for bug bountry online and trying to find sqli bug.
I tried using sqlmap but no success.
Is it about WAF they're using or sqlmap is not complete ?
(I set the level and risk to highest possible)
Thanks
@ExGetMessage6 -
"Working as designed" : slang. The acceptance criteria were too hard, so we only completed half of them.
synonym: "not a bug" -
Today I heard my first "This is a feature, not a bug" from a enterprise which gives us a SaaS.
They were damn serious, and never in my life I wanted to punch an IT guy so hard in the face more than today -
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... -
I'm not a beefy dude, But I consider myself as a terminator 🔫 because when I find a BUG I fucking console log the shit out of it !
-
Today, a customer complained about a bug. I checked their account: yup, there was a bug. I checked it on my machine... nothing. It took me about an hour to figure out that they were actually just not using the feature correctly. I'd understand this from a stupid customer, but me?! FML2
-
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
-
So my boss thinks of debugging as a guessing game. As in you just say random things that have not even the slightest relation with the code where the bug is ... now i know why it take days to fix a little bug...5
-
when 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 -
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 -
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.
-
I am not a PHP dev but this back end error message when accessing /notif looks weird.
Is this a security bug?
7 -
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 -
MFW
me: debugging an issue from a customer for three hours and ask my colleague for help
him: oh, that's not a bug, it is a user error
me: 😶 -
I am not a math expert but I am almost 100% sure that 617 comes first (this is a bug that happens a lot when searching for top and all)
4 -
I've sat with this shitty bug since 9:00 this morning. Just finished fixing it. What could causing such a fatal problem you may ask? Not pinning fucking dependencies.
*facepalm* -
As some of you might know I am currently working in a QA Team.
One of my "colleagues" asked me to help him with the automation of a simple page.
The tool we are using could not determine if a checkbox on a mask was checked or not so he decided to open a BUG!
This is not a bug the page is working fine (the checkmark is visible and the server handles the data correctly)!!
When I asked him why he opened the bug he said "Because I want the developer to make that easier for me!!!"
WTF This is your job! JUST GET IT FUCKING DONE!
I work my ass of to close the gap between testers and developers...
BUT IF I SEE THINGS LIKE THAT I UNDERSTAND EVERY DEV WHO WANTS TO PUNCH HIM INTO HIS FACE! -
How did they manage to come up with such a bug? The only things there should be numbers or an arrow, not meaningless Hebrew letters.
1 -
Me: There is a bug in the most recent "standard global software" release that causes data not to send properly to the device. There are 3 ways to send the same data to the device in the current release but they apparently don't do the same thing like they should. (Sent screenshots of the issue)
Standard Dev Support: "it's not a Bug it's a feature. So the development found out, that there are several problems with sending data to devices using "x" method. So they decided to stop "x" function in the latest release. Use "y" method instead."
Me: "X" and "y" methods are both still there. You didn't remove it in the latest release. So it is a fucking bug moron?!?
Wtf!!!!!1 -
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 and your senior push to production well knowing there is a bug in there but you do not care because you are the company's dark lords
1 -
I'm supposed to find why a pdf is not generated correctly. But here is the problem :
I don't have access to the production to see the bug and the pdf they gave me is different to the ones I generated myself. But ! It's not over :
My local version does not generate the same pdf as the acceptance testing version !
So here I am, with three different pdf and only the possibility to modify the local one, where the bug isn't.1 -
When your bug fix corrects an issue that is a year old and customers freak out because they do not not how the feature is actually suppose to work. Management: you should of wrote a test to detect the reverse effects of your bug correction. I told them what the effects would be and to have customer support on stand by with the corrective actions to take if they were concerned.1
-
TIL that rants not loading when there's no internet is not a bug but a feature. A friend was going through the phone, and I don't keep mobile data, so he wasn't able know about the wk13 rants. Which is good because that would have destroyed him.
-
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.
-
get bug
find slack context
senior describes some stuff as magic and it's unfortunately not working as expected
fml2 -
Bug handling advice #1337:
Do it like Pöttering at systemd:
- Bug incoming[1]
- "That's not a bug!"
- Wait for CVE with 9.8 critical score[2]
- "Ok, well...might be a bug..."
[1]: https://github.com/systemd/systemd/...
[2]: https://nvd.nist.gov/vuln/detail/... -
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 -
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 -
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 -
I have some really satisfying bug fixes in one particular project but it's under NDA.
So I'm not allowed to tell you guys any of them :(1 -
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. -
When a major bug fixad recently by you reappears on production environment 'cause someone else (not you of course...) merged old branch content to live branch...
-
"Bug: IE 10/11 open silverlight when trying to view a MS Office PowerPoint link online"
"Bug: IE doesnt play this 1 video"
The problem is IE right? Not the website or the links? Am I crazy? -
I dont know which one is more frightening!
Having a bug on the first run or not having one until production...3 -
Whenever you change your Instagram username it becomes unavailable completely even tho it's not taken. Not possible to get it back after changing.
Not sure if this a bug or a feature that they intended to have in their app...8 -
If you tried to fix a bug
And put it on stage, but still not working!!!
MAKE SURE HAVE HAVE REBUILD YOUR SOLUTION3 -
The moment where you can prove the senior that the bug was not because of you but of him..
If you have absolutely the need of make someone feel guilty about a bug, then at least be sure you find the right person!!! -
Have you ever been stuck with CSS for weeks? Being stuck in an algorithm bug is thrilling. Being stuck in CSS is surely not fun.1
-
My new feature has a bug in it, but not in Internet Explorer..
Huh? This is new! I know this the other way around! -
!rant
If your manager does not add undue stress on you even if there is a bug in production, then probably you are working for the right company.3 -
That moment when you find out, after lots of reading documentation and debugging, that the damn external library has a not yet reported bug -.-
-
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 -
Was to lazy to fix a bug. Waited some months and then realized the bug magically was gone. Happened not just one time...2
-
I spent 3 hours without find the bug on my code. I just found, I installed the library but not the plugin
Django + Django excel + pyexcel_xls
:( #WIN1 -
I don't get the bug "joke" that's flying around. If you have 99 bugs and fix one, why would you have more? Do you not have automated tests?4
-
Not sure if someone reported this or not ..
But after I post my rant, and try to write new one .. I find my previous rant already there with the tags.
It might be a bug in the autosave2 -
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 -
only programmers can tell what this feels like sometimes it not funny expecially when trying to fix a bug.
4 -
FMF! .NET Core's F# REPL depends on a bug. For two years the testing and building issue referenced as a reason for depending on the bug has not been resolved. Since 2016, no one has been assigned to fix the bug though the producer of the bug hates himself. Only the self-hating deserve love2
-
That feeling when you've done TDD but there's still bug because tests were not good enough..
I guess every day is a school day.. -
Don’t have any Laptop Stickers but do have stickers on my Roller Derby Helmet, and my fav has to be:
“It’s not a bug it’s a feature!”1 -
odoo keeps showing nameerror: name 'id' is not defined.
like bruh, 'id' is in default, the primary key of my fucking model. why the hell cant i reference it
fucking bug3 -
After inputting all of the defect info into the bug tracking tool, QA writes a quick summary of their findings and goes home.
Love explaining to mgmt why developers could not fix bugs because they had no access to the bug tracking software.
1 day.... X number of bugs... 0 progress -
Am I the only one not being able to open up an image from a rant in the detailed preview 😐 hate dat shit
-
sorry about this, Feedback does not allow images. little bug I really don't know how but happens sometimes... sound like dumb client, see screenshot . Padding for filter without filter. iphone 5c
4 -
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. -
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.
-
Product owners not testing/validating bug reports and just passing us the email like
"Here, now fix it"1 -
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!!!
-
It took me 48 hours ( not continuously) to fix a bug by going through a cluster fuck code of multiple modules. Tracing the error through 5 or 6 layers. And u dont get error logs right away. You need to recreate that error and see the logs on a kubernetes pod. Just to find out the bug was a duplicate.
Yes jokes are on me. I fucked up by not checking for duplicate. I steered right away on that shit dipped bug like a hungry/zombie hound. Fuck me. -
when you're burnt out and you question whether or not you really did fix that bug or your mind is playing tricks on you.
-
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
-
I love spending my night not being productive because I spent the whole night looking for a bug. A bug that ended up being an eensy-teensy missing letter
-
Hate it when people say a bug is weird. Your not having enough information to know what's going signifies either a problem in your approach or determination. It's not weird.2
-
I'm currently making an internship at a medical software company and today i found this gem in a js file:
/*
the server does not check if the element was deleted or not; it will return success, no matter what; **it's not a bug, it's a feature**
*/ -
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
-
Images are not loading! Not even if I open a rant. Profile pics also. I have to open the image itself to see it.
Bug?2 -
Work load, bug fixes, plenty of errors, back and neck pain and eye strain does not irritate me as much as HRs not responding to your emails.
-
Not even funny when QA is testing a module -> they find a bug -> report the bug and forget rest of the functionalities that are actually working!3
-
most satisfying bug fix = getting Android MediaPlayer to PAUSE AUDIO PLAYBACK WHEN IM NOT INSIDE THE ACTIVITY
gosh how many of you here have experienced this before1 -
if you somehow/accidentally make mobile youtube play on the background on a free account, then that's not a "that's not a bug, it's a feature" but a "that's not a feature, it's a bug"1
-
"DevRant is not even close to being as popular as it should be" - I say that's not a bug... (you know the rest)1
-
Never thought an underscore could bug me till today. Took me three hours to find out if I removed the underscore the form field would be required. Thanks stupid formhandler
-
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 -
Yes, the bug is always on our side. Other teams are immaculate and they write the purest, most perfect code possible.
-
A guy asked me today why his code wont run and it didnt even have a single ; or endl; i straight up ignored the guy later he was all hyped he told me that the huge bug had beeb not using ; this noob literally taught he solved some huge bug....4
-
Everytime my qa says "it's a bug"
Me: You saint, it's not a bug, it's a feature...
*Awkward silence* -
Not sure what's worse, finding a bug in my code or waiting in a garage for 3 x tyres to be fitted and tracking to be done on my car! 😱1
-
Fixed the bug tested multiple times the build. When uploaded on stage not working. Debugging, debugging ... i forgot to push.. blah
-
Just a Thought
We are not creating any feature
We are just directly implementing bug/error at first place and resolving/fixing that thing with adding more code to it1 -
It's not a matter of simply "unlocking it". It's a bug that needs to be researched, fixed, tested, and released.
-
Today " It's not a bug it's a feature" became true. Had an escalation where user reported as a bug. Team came up with an answer they couldn't resist to accept it as a feature. 😎1
-
nice read:
https://lukasa.co.uk/2016/12/...
(would love to know what happens to radar/bug report, but could not retrieve it) -
Seriously.. CSP for a bug tracker site.... not really a good idea....
http://bugs.chromium.org/p/...
Site is TOTALLY broken due to CSP.... -
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