Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "coolest bug"
-
Once I was frustrated by a Javascript bug
So I Googled "Retarded JS'"
And holy fuckkk
I found a npm module 😁
Then I Googled "Asshole JS"
Holy mother of all fuckkks
I FOUND THE COOLEST JS LIBRARY EVER 😁😂9 -
This probably isn't the coolest bug I've ever solved, but surely the one with the biggest faceplam
So I was building a Bluetooth smart watch that pairs with your Android device for the final year bachelor's project. The submission was in a 2 days and it was all ready and it suddenly stopped working.. Spent hours trying to fix it, even tried to get a replacement Bluetooth module (was out of stock -_-).. After a day's worth of freaking out I discovered that Android phones (at least the OnePlus X) don't connect to Bluetooth modules when their battery is below 15% -_- and since I was freaking out I would let the phone charge a bit and get back to debugging and it never crossed 15% so it never worked.. One day of debugging attempts later it suddenly struck me that low battery might be an issue.. And voila! It worked after charging the phone
Shouldn't such things be clearly mentioned in documentation :/
(Btw, got full for the project, got a 10/10 GPA for the semester)1 -
The coolest bug I ever found:
was a simple button on my first website ~2002 that said "Don't Click Me!" and was supposed to popup a dialog saying "I told you not to click me!" When pressed in IE on my middle school network it would spit the message out of the library printer... Oh to be young again3 -
Coolest bug I ever found was the temperature sensor connected to a raspberry pi giving me -40 as a value.6
-
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. -
#wk6 coolest bug: it was first year CS and we were learning data structures. the assignment was a maze solver using stacks. I couldn't figure out the issue I had and went to sleep. my dream that night was in code (one of a few times it's happened) and I woke up mid-night and typed it in and it worked. slept like a baby after that.
-
Coolest bug is less of a bug and more of a feature. I've been working on a medical app and I used an open source backend which had almost everything I needed. To be hipaa compliant you have to encrypt all sensitive data - full db encryption was not something this backend was capable of.
So my solution was to encrypt the data on the client side and create a secondary server - that can only be accessed on my app server - to store and retrieve the keys.
If anyone's thinking of working on a HIPAA project - you're welcome -
Late for the "coolest bug" party. But: I helped migrate an organization from proprietary software to FOSS and they found a bug. They were used to being "the only ones who ever encountered this problem" (along with a few hundred other customers). Now we sat down and had a look at the code. Found out that the Perl script didn't pass the value in question to the template. An easy fix but it was an eye opening moment for them of the benefits of the FOSS path.
-
My coolest bug fix was fixing XSS and CSRF vulnerabilities. It was the starting of my IT career and when I hear these big names, I used to think that it takes a big brain to fix them. But the solutions were rather simple. My architect told me how to solve them and I made my version of the solution and sent it for his review. He just rejected it and told some enhancements to it. The to and fro of these reviews happened for a week.
At some point I felt, why don't he f*****g do it himself. It would take him about 5 minutes.
Finally my code was approved.
Now when I turn back and think about it, I feel I learned a lot from that exercise. -
the coolest bug happend to when developing games, when i get some weird artifact with the characters
-
When I changed my attitude and stopped feeling like a righteous prick for fixing a few hard bugs. Fixing that one bug in my own software was the coolest and opened the most doors for me by far.