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 IDIOT

As a long-time iPhone user, I am really sorry to say it but I think Apple has completed their transition to being a company that is incompetent when it comes to software development and software development processes.

I’ve grown tired of hearing some developers tell me about Apple’s scale and how software development is hard and how bugs should be expected. All of those are true, but like most rules of law, incompetence and gross negligence trumps all of that.

I’m writing this because of the telugu “bug”/massive, massive security issue in iOS 11.2.5. I personally think it’s one of the worst security issues in the history of modern devices/software in terms of its ease of exploitation, vast reach, and devastating impact if used strategically. But, as a software developer, I would have been able to see past all of that, but Apple has shown their true incompetence on this issue and this isn’t about a bug.

It’s about a company that has a catastrophic bug in their desktop and mobile platforms and haven’t been able to, or cared to, patch it in the 3 or so days it’s been known about. It’s about a company, who as of a view days ago, hasn’t followed the basic software development process of removing an update (11.2.5) that was found to be flawed and broken. Bugs happen, but that kind of incompetence is cultural and isn’t a mistake and it certainly isn’t something that people should try to justify.

This has also shown Apple’s gross incompetence in terms of software QA. This isn’t the first time a non-standard character has crashed iOS. Why would a competent software company implement a step in their QA, after the previous incident(s), to specifically test for issues like this? While Android has its issues too and I know some here don’t like Google, no one can deny that Google at least has a solid and far superior QA process compared to Apple.

Why am I writing this? Because I’m fed up. Apple has completely lost its way. devRant was inaccessible to iOS users a couple of times because of this bug and I know many, many other apps and websites that feature user-generated content experienced the same thing. It’s catastrophic. Many times we get sidetracked and really into security issues, like meltdown/spectre that are exponentially harder to take advantage of than this one. This issue can be exploited by a 3 year old. I bet no one can produce a case where a security issue was this exploitable yet this ignored on a whole.

Alas, here we are, days later, and the incompetent leadership at Apple has still not patched one of the worst security bugs the world has ever seen.

For less than a second, I thought I found a bug on devrant

A rare bug appeared. It was my duty to finish it.

SH = Manager

SH: So when do you think you can finish the task?
Me: I still have to analyze the problem. Give me a moment and I'll get back to you.
SH: Alright.

*An hour later*

SH: *Approaches my desk* Have you found the source of the problem?
Me: Not yet. Please give me some more time.
SH: Ok.

*An hour later*

SH: *the approach* You found it yet?
Me: Yes, I've found the the source of the problem, But... *explains the problem and thus concluding that it's a complicated bug*
SH: Can you finish it by tomorrow?
Me: I'll do the best I can but I am not entirely sure if I can finish it by tomorrow.
SH: OK great!

*The next day*

SH: *Le approach* Hey I have a colleague here that may be able to solve the problem, he has skills with XYZ. Ok, I will leave you two at it then. *the leave*
Helper: So can you tell me about the issue here?
Me: *explains the bug and the source of the problem*
Helper: Have you tried solution A?
Me: Yes sir, but it yields a different output... *explains what happened with solution A*
Helper: Well, that won't work. What about solution B?
Me: I've tried that, too. *Another lengthy explanation*
Helper: Welp, ok. I'll get back to you on that.

(...But he never came.)

*A few hours later*

SH: *A.P.P.R.O.A.C.H.* Hey I have this team lead from another department. I think he can help you out on this one. *L.E.A.V.E.*
Helper 2: What seems to be the problem?
Me: *Explains again with all the solutions I tried but failed*
Helper 2: Wow. That really seems to be a complicated problem.
~~
Me (In my head): -_-
~~
Helper 2: Listen, I need to get back to my team. I'll keep you posted if I happen to find a solution for your problem alright?
Me: Alright thanks.

*Towards the end of the day*

SH: *APPROACHHHH* Have you resolved the bug yet?
~~
Me (In my head): You made me spend half the FUCKING day explaining to these people who didn't even give a piece of FUCKING SHIT to contribute to the problem and you are asking me if I am done with this FUCKING BUG? FUCK YOU, YOU SON OF A -
~~
Me: No, it is not finished yet..
SH: You have to finish this because we don't have tomorrow.
~~
Me (In my head): SHDIFHWISGSIFGSISBAUDBEIQBDIWGFIEBWIDHWIQBDOSBCISBDOSHDIAGSUSVDIFBDKDJWIQKDBDIDGSUWVDIABDIXBSIDBDIDBWUWGUSVDUWVDJQBDUDVWISHDUWVFG
~~

I went home for the day.

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 easier

So I decided to give Linux a try again.

Created live usb. Prepared myself to go through all the hassles at the beginning.

Booted in live USB. I can't see mouse cursor.

Searched in google, apparently a common problem with GTX 1070/1080 graphics cards.

Installed proprietary nvidia drivers with keyboard only. Took me about 20 minutes.

Finally managed to get the mouse cursor and install ubuntu. Time to boot and smell the fresh air of linux again.

Sound card doesn't work. Even the integrated mobo sound card doesn't work. Looked for a solution, found the bug in lunchpad but not solution yet. Everyone recommending to buy an external sound card.

I can't code without music. Decided to remove linux.

Booted back to Windows and removed linux partition. That fucked up my bootloader although I installed linux's efi loader completely separately.

Now I am sitting in front of my computer, with black grub screen, while trying to make a Windows 10 usb with my 7 years old broken laptop.

Next time I see a rant about Windows 10 that glorifies linux, I swear I'm gonna smack your face over standard TCP/IP

Bill gates found a bottle in his garden.
He decided to rub it thrice (whyever) and a geany surged.

Bill gates: h.. He.. Hello?
Geany : hi, im willing to give you one wish as you saved me
Bill gates: I WANT WORLD PEACE, HERE IS THE MAP WITH ALL THE WARS ON THE WORLD!!
Geany: thats impossible. Other wishes?
Bill gates: fix every bug in windows vista!
Geany: gimme that world map

I was newly hired to company. A customer came in yelling saying "there's a bug, this should do this but it's doing that..."
PM came to me and told me to "urgently fix this as this is an important customer".

So I started debugging for hours and asking around and all follow devs agreed that this is a bug. Then I found it!! And it was clear that it was not doing what the customer wanted.

I decided to look through this code history and found out that this part of the code wasn't changed for a year but the code commited before it did actually what the customer was expecting (whaaaa....)

Gathered the devs and the PM showing them what I found. They all looked at each other and then one said "ouuhhh right...yes it was doing this but we changed it to that..."

Turns out it's a feature not a bug, and everyone forgot about it.

FML

Me and my team in middle of our first hackathon-
a girl who is our class topper is my team mate, trying to write some Android Code.

I am writing nodejs Api, she calls me saying there's a bug in my code,so for saving time I decided to fix that small thing on her laptop,so when I went to the backend folder to open the js file,I see no default text editor set for it. After searching,I found out she had no atom,sublime,vs etc.
I asked her - "Do you even have notepad++ ?".
She - "I have notepad,but not ++".

That day I had to edit my code in Wordpad. I am still shaking.

LONG RANT AHEAD!

In my workplace (dev company) I am the only dev using Linux on my workstation. I joined project XX, a senior dev onboarded me. Downloaded the code, built the source, launched the app,.. BAM - an exception in catalina.out. ORM framework failed to map something.

mvn clean && mvn install

same thing happens again. I address this incident to sr dev and response is "well.... it works on my machine and has worked for all other devs. It must be your environment issue. Prolly linux is to blame?" So I spend another hour trying to dig up the bug. Narrowed it down to a single datamodel with ORM mapping annotation looking somewhat off. Fixed it.

mvn clean && mvn install

the app now works perfectly. Apparently this bug has been in the codebase for years and Windows used to mask it somehow w/o throwing an exception. God knows what undefined behaviour was happening in the background...

Months fly by and I'm invited to join another project. Sounds really cool! I get accesses, checkout the code, build it (after crossing the hell of VPNs on Linux). Run component 1/4 -- all goocy. run component 2,3/4 -- looks perfect. Run component 4/4 -- BAM: LinkageError. Turns out there is something wrong with OSGi dependencies as ClassLoader attempts to load the same class twice, from 2 different sources. Coworkers with Windows and MACs have never seen this kind of exception and lead dev replies with "I think you should use a normal environment for work rather than playing with your Linux". Wtf... It's java. Every env is "normal env" for JVM! I do some digging. One day passes by.. second one.. third.. the weekend.. The next Friday comes and I still haven't succeeded to launch component #4. Eventually I give up (since I cannot charge a client for a week I spent trying to set up my env) and walk away from that project. Ever since this LinkageError was always in my mind, for some reason I could not let it go. It was driving me CRAZY! So half a year passes by and one of the project devs gets a new MB pro. 2 days later I get a PM: "umm.. were you the one who used to get LinkageError while starting component #4 up?". You guys have NO IDEA how happy his message made me. I mean... I was frickin HIGH: all smiling, singing, even dancing behind my desk!! Apparently the guy had the same problem I did. Except he was familiar with the project quite well. It took 3 more days for him to figure out what was wrong and fix it. And it indeed was an error in the project -- not my "abnormal Linux env"! And again for some hell knows what reason Windows was masking a mistake in the codebase and not popping an error where it must have popped. Linux on the other hand found the error and crashed the app immediatelly so the product would not be shipped with God knows what bugs...

I do not mean to bring up a flame war or smth, but It's obvious I've kind of saved 2 projects from "undefined magical behaviour" by just using Linux. I guess what I really wanted to say is that no matter how good dev you are, whether you are a sr, lead or chief dev, if your coworker (let it be another sr or a jr dev) says he gets an error and YOU cannot figure out what the heck is wrong, you should not blame the dev or an environment w/o knowing it for a fact. If something is not working - figure out the WHATs and WHYs first. Analyze, compare data to other envs,... Not only you will help a new guy to join your team but also you'll learn something new. And in some cases something crucial, e.g. a serious messup in the codebase.

I found a bug in my sleep...what has programming done to me !?

My little brother (still in school , learning security and pen testing): i found a bug in a website , it returns an xml file instead of the web page , i reported it to them and i think i'm gonna get rewarded like 2k $ for it .
Me : cool ! Show me .
Him : shows me his phone ...
Me : wait , gotta rant this .

Client: “Hey this thing isn’t working correctly.”
Me: “Hmm, looks like there was a bug in the last update. The team and I are going to work on a fix. In the meantime here’s a tool to help you get what you need.”
Client:”Yay!”

*A little while later*
Same Client:”Hey this thing isn’t working.”
Me:”Hey, yeah, it’s the same thing. That bug I told you about? Yeah, we’re still working on it. We’ll let you know when it’s finished I promise but we’re trying to fix it without introducing more bugs.”
Client:”Ok sounds good.”

*A little while later*
Same Client:”Hey this thing isn’t working.”
Me:”Bro...we just went over this...”

*A little while later*
Same Client:”Hey seems like there’s a bug in our system that was found by -insert random coworker’s name here-. Are we looking into to this?”
Me:”Wtf dude.”

*A little while later*
Same Client:”Hey this thing isn’t working.”
Me: -smashes my face against keyboard-

Hey, @google! I found a bug. The last 3 choices are missing.
The lack of balance is disturbing me.

!rant

Programming is a huge blessing i believe we all should be thankful to. For me, it literally turned my life around.

11 months ago i was fighting a losing battle with depression, and contemplated suicide constantly. I would use a self remedy of smoking weed and sleeping all day long. I was depressed because i felt my life had no real value. I was doing nothing, and its kind of an infinite loop.

You don't do anything, so you feel bad, so you don't do anything, and so on.

That was until i finally took the step that changed my life. I searched and wanted to learn something. I always liked web pages so i thought id get into web development.

Did some research, found out that the fastest way to go was to learn ruby on rails. I followed a tutorial i found online, and literally pushed myself through it. There were times when there where things i didnt understand, and when it was really bad, but i pushed myself through it and i finished the tutorial.

Just finishing the tutorial and learning something new helped me alot. I had already quit smoking and was feeling way better, but after a while i started feeling bad again since i wasnt doing anything after i had finished learning, so i started working on a personal project, creating it from scratch, and just working on it day and night. I worked 14 hours a day, never really leaving my room ( this was during summer vacation ) for a month.

There were many things i didnt understand, but i never gave up and always searched for the solution and read about it until i understood it better. Looking back, there were things i knew could have been done in a better way, but as a first project, im proud of myself, not because it rocks, but because i did not give up.

In the process of starting a new life, i was really lonely. I cut all ties with everyone i knew, since they were all toxic, all i had in my life was ruby on rails and my web application. I wanted to launch it but couldn't due to personal reasons.

Not being able to launch and see something live, something that you worked so hard on, that you put so much effort into, that was devastating to me. I felt as if all my efforts had gone to waste.

And here is what i love most about programming, NOTHING EVER GOES TO WASTE. All that effort you spent on something ? All these all nighters you pulled ? All that frustration from that bug ? It will pay off later. It always does somehow. You get more knowledge and become a better programmer, and sometimes it even gives way to new opportunities and chances you never even expected.

I included my web application in my resume and it helped land me a job as a junior developer in a really nice company. A job that i wouldn't even have dreamed of several months earlier.

Programming and creating something new and learning something new everyday, creating something that people use, that someone else will benefit from and be grateful for, i think we should never take that for granted !

Tl;dr : learning how to code and web development saved my life

My boss literally spends half an hour finger-fucking his phone on the mobile site to find "bugs", that I can't replicate. A combination like: swipe, pinch, landscape, portrait, back pinch, open new tab, close tab, ash cigarette on phone, dunk in toilet, dry, double tap... Aha I've found a bug, there's 0.5 pixel line of space between the bag header and the browser bar.

Rant! I found a bug in payment provider's api. The bug involves sending an invalid (!) Stripe ID to that API, (which I send on purpose btw) Which causes a complete white page when you login to their systems and view the details of that customer. Btw the API will accept that invalid Stripe ID without questioning and returns a 200 status code back.

So I send a mail to there support saying "look I found this bug by accident, this is how you can reproduce it"

And the support team send me a message back saying "then don't send an invalid Stripe ID"...

You don't freaking say... *sigh*

You guys ever spent a longer period of time on finding a bug and once you found it, first go grab a coffee/snack to allow that bug some final moments?

Like some sick kind of power play along the lines of “I will fix you at a time and location of my choosing”

Junior dev: I found the bug
Senior dev: I found a bug

Junior dev vs senior dev? Anyway?

Dev: Hey I found a bug in your PR

Manager: YOU BROKE IT ON PURPOSE!

Dev: … yes?

IBM

I have replied to them with scripts, curl commands, and Swagger docs (PROVIDED TO SUPPORT THEIR API), everything that could possibly indicate there's a bug. Regardless, they refuse to escalate me to level 1 support because "We cant reproduce the issue in a dev environment"

Well of course you can't reproduce it in a dev environment otherwise you'd have caught this in your unit tests. We have a genuine issue on our hands and you couldnt give less of a shit about it, or even understand less than half of it. I literally gave them a script to use and they replied back with this:

"I cannot replicate the error, but for a resource ID that doesnt exist it throws an HTTP 500 error"

YOUR APP... throws a 500... for a resource NOT FOUND?????????!!!!!!!!!! That is the exact OPPOSITE of spec, in fact some might call it a MISUSE OF RESTFUL APIs... maybe even HTTP PROTOCOL ITSELF.

I'm done with IBM, I'm done with their support, I'm done with their product, and I'm DONE playing TELEPHONE with FIRST TIER SUPPORT while we pay $250,000/year for SHITTY, UNRELENTING RAPE OF MY INTELLECT.

QA: Hey I found a bug.
Me: Okay, can you log the bug and assign to me?
QA: <audible sigh> sure

My first testing job in the industry. Quite the rollercoaster.

I had found this neat little online service with a community. I signed up an account and participated. I sent in a lot of bug reports. One of the community supervisors sent me a message that most things in FogBugz had my username all over it.

After a year, I got cocky and decided to try SQL injection. In a production environment. What can I say. I was young, not bright, and overly curious. Never malicious, never damaged data or exposed sensitive data or bork services.

I reported it.

Not long after, I got phone calls. I was pretty sure I was getting charged with something.

I was offered a job.

Three months into the job, they asked if I wanted to do Python and work with the automators. I said I don't know what that is but sure.

They hired me a private instructor for a week to learn the basics, then flew me to the other side of the world for two weeks to work directly with the automation team to learn how they do it.

It was a pretty exciting era in my life and my dream job.

I was just trying to fix a "bug" for 2 hours and then found out I only had to "clean" to project..

So I found a bug in Bootstrap 4 today that was causing responsive tables to break. I looked at it for a while and threw a bunch of potential fixes at it, to no avail.

I was about to open a bug report when I stumbled upon the cause...

I spelled “table-responsive” wrong 🤦‍♂️

8:50am aight alarm clock, give me 5 more minutes

8:55am ok lets round it to 9, wake me up then

9:00am aight enough. lets just sleep for 1 more minute since 9:00 is too round

9:43am fuck

9:44am ok its time to finally study for the upcoming college exam

9:45am nothing but a fresh day to start studying for college

9:46am eh i dont have a lot to study so I'll do it in 2pm, I'll code my project instead

2pm hold on 5 more minutes until i finish coding this feature and then I'll study

5pm where the fuck is this bug coming from

5:504pm goddamn i found it

6:36pm holy shit its already over 6pm, I'll study at night

7:42pm ok its night now, time to study but I'll do it when i fix all bugs

8:14pm ok bugs fixed, commit. lets study

8:15pm you know what, im way too tired and exhausted from this coding, I'll take a short 30 minute break and then I'll study

10:15pm ok im feeling fresh bois lets study now theres not too much

1:31am damn this movie was good

1:32am fuck i forgot to study, I'll do it tomorrow

2:10am *posts this rant*

Boss: I wrote some tests and there is a bug in your code but I cannot find it. Fix it
Me: Sure. I'm on it.

Narrator: 5 minutes later

Me: Boss, I found the bug. It's in your testcode...

Seriously... WTF?!

(before someone suggests that my code should handle all test cases... He tried to measure the time the program needed to response and fucked it up...)

So just about to head to the pub and I got the dreaded call from my boss.

The support team had developed some fixes. They "tested" and deployed without letting us know... And you guessed it there was failures all over the shop!

So it turned out their testing was running on a local base install with no integration compared to the live system with 15 years of customisation and complex integration. My they thought this was acceptable I don't know...

And the best part was the developers who made the changes didn't understand their own code (I found the tutorial they copied online) they just blindly copied it without understanding how it worked!

So 4 hours later we found the bug, nothing like having a query and s SQL connection but not executing the query....

There goes my Saturday evening. Now we're was my beer!

The ultimate "I am vegan" guy will be arch linux user, vegan, trans, crossfitter and cryptocurrency investor. I've just met guy like this in my job. He did not shut up for a while. I am not sure whats he doing and whats his job but my guess is that hes paid for spreading cancer, sucidal toughts and eatig your will to live and talk with people...

R - retard
M - me

R: Hey CopyPasteCode I found this bug, it does 'this' insted of 'this'. *spreads arms to see his "muscles"*
M: *headphones off* Ok, I will look into it... *headphones back on*
R: Btw you invested something in the crypto, didnt you? Ive invested... ...bitcoin... ...crypto... ...litecoin..., do you think that... ...something... ...bla bla bla?
M: *tries not to kill myself after his 5 minutes of monolog* Ye sure
R: By the way Ive found this awesome vegan restaurant that accepts litecoin, would you like to come sometime?
M: *10 minutes monolog about vegan food and shit. At this point I want to die* Ok, I will now work on that back, see you later.
R: ye sure bro (wtf, "bro"?)... *looks like hes walking away* *teleports on my otger side touching my monitor*
WOW you are also a Limux user? 😮 Ivr installed arch linux this weekand and its so awesome, *another 6 minutes of monolog*
M: *smiling and preparing to kill him or myself* Nice, awesome *fake smile*
R: Anyway, I gotta go (FINALLY!!!), btw, I am going to the *name of local trans and gay club*, wanna go with me?
M: *after a month after a breakup with my GF (because she was cheating on me) which everyone in the office knew...)* Not really *trying to thing how to say "fuck off" without having meeting with HR*, I cant, I already have somethimg.
R: Oh, ok. Btw, you are rly cool bro (again), we should hang. We should hangout more often...

I hope someone is paying me for loosing 27 minutes with this guy.

Hunted a bug for 8 hours, thinking it was a problem in my code....

Found out it was someone else's code generator that injected the bug...

Contacted the concerned dev... Had to convince him for another 3 hours that it was his change to the code that caused the issue. He is still sure that his change can't break the code...... What the fuck are you..? A fucking God programmer who never makes mistakes??

I mean how hard is it to just accept when I just proved it to you??

just overhearing someone in my office,
he found a bug with someone's code who sits beside him,

I have now listened to him tell everyone in the team, blatantly pointing out the simple mistake he made, (parameter order)

In my mind im thinking this guy is a CUNT making himself look better,

End of second week at a new job. Found what I thought was a bug and wanting to impress I fixed it. The dev reviewing my code had just started a week before me so he also had no idea what was going on. It went live Friday afternoon.

Come back Monday morning and turns out I completely broke everything and nobody could use the site all weekend. I thought I was done for sure. Was shitting myself all day waiting for the call.

TURNS OUT NOBODY EVEN NOTICED

Overheard 2 colleagues having an interesting telephonic meeting late night at my room.
Dev 1: Wait. I am trying to fix it.
Dev 2: Ok. Take your time
Dev 1: Shit. I found it. I knew I was doing something wrong here.
Dev 2: Oh. Nice. What was the bug?
Dev 1: It was a super silly mistake. Don't want to tell. Folks will laugh at me.
Dev 2: Don't worry. It happens with everyone. Come tomorrow at office, and whisper it in my ears. Noone will know.

Me at QA, talking about a nasty bug I found in legacy code.
QA: what was the root cause?
Me: pos code.
QA: pos?!
Me: piece o' shit.
QA: ...

2:30 am: Okay, I think I found the bug. I'll try a last compile then I go to bed.
...
4:30 am: sh*t

I just had a rather stressful morning. I should've known something was up by the sounds of thunder as I walked into the office.

I sat down and checked my emails. There was an email from the boss who was away on a business trip. The subject read, "CRITICAL BUG" and my name was mentioned. "Great...No time for coffee", was my first thought.

I began searching commits to see when and how the bug came to be. "SHIT! It was my fault", I said aloud.

(A bit of backstory, I am Irish, working in Germany with a B2 level of the German language.)

I now had to communicate the problem quickly with a senior developer who is Russian. He can't speak English well and I would not expect him to speak it. We are in Germany after all. I tried my best to communicate the issue, but I found it so difficult to understand his German in a Russian accent. Normally, in the office I speak German except when it is urgent and I must explain a problem in greater detail through English. I got past that obstacle, however, the real challenge of fixing the bug awaited.

After 2 hours of coding, I had a solution and committed it to the master branch. All the while, I had been replying to the bosses emails with updates, probably with many grammer mistakes.

We have no dedicated testers here and the code is written in a way which makes it very difficult to test (i.e. it was written many years ago). When I had initially written the code, I tested rigorously and found no issues.

Just needed to rant. I need a coffee break now...

when they found a bug on production right before i left the office.

My code review nightmare part 2

Team responsible for code 'quality' dictated in their 18+ page coding standard document that all the references in the 'using' block be sorted alphabetically. Easy enough in Visual Studio with the right-click -> 'Remove and Sort Usings', so I thought.

Called into a conference room with other devs and the area manager (because 'Toby' needed an audience) focusing on my lack of code quality and not adhering to the coding standard.

The numerous files in question were unit tests files

using Microsoft.VisualStudio.TestTools.UnitTesting;
using System.Collections.Generic;
using System.Linq;
<the rest of the usings>

T: "As you can see, none of these files' usings are in alphabetical order"
Me: "Um, I think they are. M comes before S"
T: "The standards clearly dictate system level references are to be sorted first."
Mgr: "Yes, why didn't you sort before checking this code in? T couldn't have made the standards any easier to follow. All you had to do is right-click and sort."
Me: "I did. M comes before S."
T: "No You Didn't! That is not a system reference!"
Me: "I disagree. MSTest references are considered a system level reference, but whatever, I'll move that one line if it upsets you that much."
Mgr: "OK smartass, that's enough disrespect. Just follow the fucking standard."
T: "And learn to sort. It's easy. You should have learned that in college"
<Mgr and T have a laugh>
Me: "Are all your unit tests up to standard? I mean, are the usings sorted correctly?"
T:"Um..well..of course they are!"
Me: "Lets take a look."

I had no idea, a sorted usings seems like a detail no one cares about that much and something people do when bored. I navigate to project I knew T was working on and found nearly all the file's usings weren't sorted. I pick on one..

using NUnit;
using Microsoft.Something.Other;
using System;
<the rest of the usings>

Me: "These aren't sorted..."
T: "Uh..um...hey...this file is sorted. N comes before M!"
Me: "Say that again. A little louder please."
Mgr: "NUnit is a system level nuget package. It's fine. We're not wasting time fixing some bug in how Visual Studio sorts"
Me: "Bug? What?..wait...and having me update 10 or so files isn't a waste of time?"
Mgr: "No! Coding standards are never a waste of time! We're done here. This meeting is to review your code and not T's. Fix your bugs and re-submit the code for review..today!"

Once the system "lost" a user_id var that says who started a batch, but it was a mandatory field that was filled at the beginning of the process.

I tried to find the reason, failed, called a senior for help, he also failed to find the reason.

After a couple of hours I looked to him, he looked back and I said,
"Let's call it a solar flare bit flip?"
"It's the only logical explanation"

So it became a bit flip issue to the PM, we had a good laugh, we send as "system instability" to the client.

The bug never happened again, no one ever found the true reason, maybe it was really a bit flip 🤔

Today someone was testing a website for me.

Tester: I've found a bug this button doesn't work
Me: It works. I tested it in Firefox and Chrome.
Tester: I'm using Edge
Me: Oh yeah. Forgot that was even still a thing...

You guys made my whole day for the first time since I joined. (yes all of you!)

1) I had a 'fight' with a guy I'm making a startup with. Had to explain some of the story of my life, just to clarify that I'm not evil or generally unwilling to understand - regarding me, having the need to keep using practices

2) I've found that a whole niche-community of people seems to ignore the rest of the community and won't tag along. Having spent several months to be able to help, and receiving shit or absolutely nothing, for finally trying

3) Was in a bad mood the moment I woke up, because I fought with my girlfriend last night because she fails to communicate simple things and won't realise it.

Sorry for the bad punctuation, I tried and smartphones aren't a nice way to edit such things.

So my rant is basically a thank you! Not a rant.. But still, I think you people are the best for being so relatable and making me laugh, and feel like there's more of 'my kind'.

I also just fixed a bug in my app by (finally!) asking the framework maintainer what's up, and got a response which made no sense in a logical manner.. That's a rant for another day, I'll aggregate all the 0 fucks given, when I'm finally able to leave this thing behind, and give you a proper curse-filled shit stack of the nonsense I'm experiencing!

The bug would still live if I weren't so energized by devRant

EDIT: '!' != ','

While writing up this quarter's performance review, I re-read last quarter's goals, and found one my boss edited and added a minimum to: "Release more features that customers want and enjoy using, prioritized by product; minimum 4 product feature/bug tickets this quarter."

... they then proceeded to give me, not four+ product tickets, but: three security tickets (two of which are big projects), a frontend ticket that should have been assigned to the designer, and a slow query performance ticket -- on top of my existing security tickets from Q3.

How the fuck was I supposed to meet this requirement if I wasn't given any product tickets? What, finish the monster tickets in a week instead of a month or more each and beg for new product tickets from the product manager who refuses to even talk to me?

Fuck these people, seriously.

MFW I found a bug that has been dragging me for several hours....and it turns out to be a typo

So today, I managed to make one of my colleagues feel like an idiot. In this contract, I work mostly for ui integration, while he build the pages with angular before I add all the html structure and fancy css.

We are building the front-end/ui for an industrial device with a touch screen. For that last 2 days he was blocked on a bug that when you click the confirm button on a delete popup, it would somehow select an input in the page before it was deleted and would lock the ui when showing the virtual keyboard (the poor thing didn't know what to do and wouldn't close).

During those two days, he asked all the other devs for help, trying to find a pattern or anything that could help, while I was focused on writing my css and stuff since it was my priority and I was hired specifically for that (I was aware of the bug and gave my input but I never saw it being reproduced)

So today, he start his new routine of raging at his desk and he decides to show me on my device for some reason. I immediately notice a pattern. It would always select one of the two fields behind the popup, in the click area of the button (it's a big button). Then, I noticed that I could press a random spot on the screen, drag my finger on the button and let go and nothing would happen.

It's at this moment I knew I had found the bug. The button was set to emit an event on mousedown while the inputs behind it were set to emit an event on mouseup (like it should be everywhere). So the popup closed when you placed your finger on the screen and the input was selected immediately after when you removed your finger (which was usually faster than the page code which was not yet optimized)

After that, it was just an easy fix to change the listener and I had a free beer.

!rant

Yesterday I got a pretty straight-forward task of fixing SASS linting errors from our project. I thought, "How many errors could there be?" Turns out there were just around 2000 errors across 109 files!

I was almost like, "Man, this is going to take a lot of my time!"

So, I started fixing the errors one-by-one with my headphones on and switching music genres after every 2 hours.

After almost 6 hours of continuous bug-fixing, my mind kind of became repellant to the possibility of the outer world and my fingers automatically fell on the right keys in almost no time. My brain was functioning like a computer itself.

And after the end of 7 hours, I reduced the number to less than 1000 errors.

Today, I continued the task and found out that there were some scoping errors I made yesterday (web developers would know this pain of '&').

And after working for almost 6 hours today, I got the number down to 500.

Not a rant, but I felt extremely content with what I did today.

I guess every day is not just about programming, sometimes, it's also about making your code better.

Thanks for reading! :)

Well... I found the bug...
Thanks Sun/Oracle for the clever API design. ;)

Also... I feel like a noob now :D

Cool, I found a bug in Ruby!
And it’s preventing my debugging from working!
Asjfkladfsj

It’s 2:30am and I want to finish this crap.

No, I’m not doing any work tomorrow. I’m taking the day off to sleep.

I've been looking for a bug in my code the whole day. I randomly found it in 2 minutes today. That seems about right 😑

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 free

As much as I love opensource I hate really hate some of its actvie community members (read this as "freetards" <-- see urbandictonary). As a .Net + web devloper with minimal C experience (I just started learning it) and literally no Python experience its not really easy to contribute for me to many (most) opensource software for linux. I am using some <unnamed software> and I found a <critical bug>, it was easy to reproduce and I wrote for list of possible solutions, found it in a code and linked and basically wrote a docummentation longer than any other I ever wrote for every single project I did ever, combined. This <software> was critical for my server and since owner of github repo and few other people there were really active, I hoped that this bug with pretty good documentation will be solved fast, I went to my bed with a heroic feeling of an open source community contributor that helped saving world. I was horribly wrong. Tomorrow, I got 3 passively agressive responses from owner and other 2 freetards that summed up said <other1>:"oh thats nice, fix i yourself and commit it", <other2>:"have a sex with yourself" in a nice way, and <owner>: "fix my softwate and create mrege request". After replying that I have no experience my Python skills are not on a level requied for such an action, he messaged me on twitter I have linked to my GitHub profile saying even less nicely that I am a "retarded c*nt" and that I should learn Python and fix it myself. This makes me stay with my Windows based Server for some time now, fuck this. I googled his github nickname and guess what. Our main freetard is admin on an <unnamed linux forum> and mebmber of many other "computer help" with literally half of his posts just slightly toxic posts about how everyone should use linux and how supreme it is ober anything other, the other hals was crying why linux has only 1% of market share. Oh boi I am not sure why but ITS MAYBE BECAUSE OF FREETARDS LIKE YOU.
And the funnies thing is, hes not only freetard, he is just fullstack retard. One of his posts is "helping" to some <noob windows user> installing Linux. tl:dr for this las part: Freetard basically wiped all data of that <noob>.

PS: Bless everyone who do not respond "oh nice, now you can do it yourself"

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 😁😂

I found a weird bug where the output wasn't what I expected to be. After a few tries to fix it, I typed in something I expected was not going to work. It worked....

Another real-world argument for why I always say git is worth learning properly.

Had to track a really weird bug down today. Had no idea where it came from, how long it'd been in the code and hadn't the foggiest what was causing it. Realistically it could have been introduced any time in the last year or two, and that's tens of thousands of commits in this repo.

Git to the rescue. Knocked up a quick script to test the case in question, fed it into "git bisect run", and 30 seconds later git found the exact (small) commit that caused the issue.

It's a brilliant part of git, yet it seems like almost no-one I know uses it. Some use "git bisect", but using "git bisect run" and passing a script to it seems to be alien to most - yet it's probably my most used tool when it comes to tracking down bugs like these.

Yesssssssssssssssssssssssssssss, finally!

After months of searching for a damn bug I've finally found it in a 5h session. People increasingly started to worry whether this bug has been introduced because of a recent update of the programming language, but I finally found the bug in a dependency. Nobody thought it would be the dependency, because it wasn't updated in 9 months, but it seems like the update improved the networking a tiny bit, whiche caused a buffer to load a second mesage sooner than expected.

I can finally work on my side project again!
Fucking finally!

Some of the penguin's finest insults (Some are by me, some are by others):

Disclaimer: We all make mistakes and I typically don't give people that kind of treatment, but sometimes, when someone is really thick, arrogant or just plain stupid, the aid of the verbal sledgehammer is neccessary.

"Yeah, you do that. And once you fucked it up, you'll go get me a coffee while I fix your shit again."

"Don't add me on Facebook or anything... Because if any of your shitty code is leaked, ever, I want to be able to plausibly deny knowing you instead of doing Seppuku."

"Yep, and that's the point where some dumbass script kiddie will come, see your fuckup and turn your nice little shop into a less nice but probably rather popular porn/phishing/malware source. I'll keep some of it for you if it's good."

"I really love working with professionals. But what the fuck are YOU doing here?"

"I have NO idea what your code intended to do - but that's the first time I saw RCE and SQLi in the same piece of SHIT! Thanks for saving me the hassle."

"If you think XSS is a feature, maybe you should be cleaning our shitter instead of writing our code?"

"Dude, do I look like I have blue hair, overweight and a tumblr account? If you want someone who'd rather lie to your face than insult you, go see HR or the catholics or something."

"The only reason for me NOT to support you getting fired would be if I was getting paid per bug found!"

"Go fdisk yourself!"

"You know, I doubt the one braincell you have can ping localhost and get a response." (That one's inspired by the BOFH).

"I say we move you to the blockchain. I'd volunteer to do the cutting." (A marketing dweeb suggested to move all our (confidential) customer data to the "blockchain").

"Look, I don't say you suck as a developer, but if you were this competent as a gardener, I'd be the first one to give you a hedgetrimmer and some space and just let evolution do its thing."

"Yeah, go fetch me a unicorn while you're chasing pink elephants."

"Can you please get as high as you were when this time estimate come up? I'd love to see you overdose."

"Fuck you all, I'm a creationist from now on. This guy's so dumb, there's literally no explanation how he could evolve. Sorry Darwin."

"You know, just ignore the bloodstain that I'll put on the wall by banging my head against it once you're gone."

Found a bug, reported it to the maintainer.
He then tells me to ignore it since no one noticed it (besides me).
I tell him i can't do it since it's just wrong and he can simply fix it.
Turns out he's just lazy as hell and got mad at me, so i go and fix it.
Next day boss is mad at me because i'm wasting time on tasks that it's not of my concern even knowing all my tasks were completed.
Not even a "thank you by the way".
What did i miss here?

Watch out for these fucking bug bounty idiots.

Some time back I got an email from one shortly after making a website live. Didn't find anything major and just ran a simple tool that can suggest security improvements simply loading the landing page for the site.

Might be useful for some people but not so much for me.

It's the same kind of security tool you can search for, run it and it mostly just checks things like HTTP headers. A harmless surface test. Was nice, polite and didn't demand anything but linked to their profile where you can give them some rep on a system that gamifies security bug hunting.

It's rendering services without being asked like when someone washes your windscreen while stopped at traffic but no demands and no real harm done. Spammed.

I had another one recently though that was a total disgrace.

"I'm a web security Analyst. My Job is to do penetration testing in websites to make them secure."
"While testing your site I found some critical vulnerabilities (bugs) in your site which need to be mitigated."
"If you have a bug bounty program, kindly let me know where I should report those issues."
"Waiting for response."

It immediately stands out that this person is asking for pay before disclosing vulnerabilities but this ends up being stupid on so many other levels.

The second thing that stands out is that he says he's doing a penetration test. This is illegal in most major countries. Even attempting to penetrate a system without consent is illegal.

In many cases if it's trivial or safe no harm no foul but in this case I take a look at what he's sending and he's really trying to hack the site. Sending all kinds of junk data and sending things to try to inject that if they did get through could cause damage or provide sensitive data such as trying SQL injects to get user data.

It doesn't matter the intent it's breaking criminal law and when there's the potential for damages that's serious.

It cannot be understated how unprofessional this is. Irrespective of intent, being a self proclaimed "whitehat" or "ethical hacker" if they test this on a site and some of the commands they sent my way had worked then that would have been a data breach.

These weren't commands to see if something was possible, they were commands to extract data. If some random person from Pakistan extracts sensitive data then that's a breach that has to be reported and disclosed to users with the potential for fines and other consequences.

The sad thing is looking at the logs he's doing it all manually. Copying and pasting extremely specific snippets into all the input boxes of hacked with nothing to do with the stack in use. He can't get that many hits that way.

While writing a raytracing engine for my university project (a fairly long and complex program in C++), there was a subtle bug that, under very specific conditions, the ray energy calculation would return 0 or NaN, and the corresponding pixel would be slightly dimmer than it should be.

Now you might think that this is a trifling problem, but when it happened to random pixels across the screen at random times it would manifest as noise, and as you might know, people who render stuff Absolutely. Hate. Noise. It wouldn't do. Not acceptable.

So I worked at that thing for three whole days and finally located the bug, a tiny gotcha-type thing in a numerical routine in one corner of the module that handled multiple importance sampling (basically, mixing different sampling strategies).

Frustrating, exhausting, and easily the most gruelling bug hunt I've ever done. Utterly worth it when I fixed it. And what's even better, I found and squashed two other bugs I hadn't even noticed, lol

Boss, yesterday: hey, we just got you a Windows 10 machine. Test the app and make sure it works.
Me: kay. (Fast forward20 minutes) I found a hell of a bug.
Boss: what?
Me: the SA disabled scripts on the machine so I can't build.
Boss: Are you serious?
Me: yeah, and he's out until January.

There was a bug that I ignoring to fix for past 8 months and finally Client found the bug and reported back to me. All I said to myself "Motherfuck".

So from tomorrow I will be rewriting a piece of code.

Coworker made a tool to automate part of our job and she sent it to me. After 5 seconds of using it I found a bug... she has been using it for weeks. Now I don't trust anything she has done around here. (It's a financial tool and the bug is changing certain numbers to negative so it subtracts instead of adds...)

My internship is coming to an end and I think my boss is testing my limits.

So, in the beginning of this week, he assigned me a non reproducible bug that has been causing trouble to the whole team for months.

Long story short, when we edit or create a planned order from the backend, once in fifteen, a product is added to the list and "steals" the quantity from another product.
Everyone in the company has experienced this bug several times but we never got to reproduce it consistently.

After spending the whole week analyzing the 9 lines of JS code handling this feature, reading tons of docs and several libraries source code. I finally found a fix by "bruteforce testing" with selenium and exporting screenshots, error logs and snapshots of the html source.

This has been intense but was worth the effort, first, I fix a really annoying bug and second, I learned a lot of things and improved my understanding of Javascript.

There was a pretty big bug that I spent all day trying to pinpoint. It was getting really late, so I called it a night and went to sleep.

That night, I dreamed that I was still at the computer, debugging. I kid you not, in the dream I both found the bug and realized what the fix needed to be. In that moment, I woke up.

I ran straight to the computer down the hall, and sure enough, that was the issue and that was the fix.

Shoutout to the capabilities of the human brain.

Thanks, brain!

Me when i found a bug ..

The only serious, as in customer affecting, bug I never git fixed was an indexing bug that caused an exception requiring manual intervention by one of us.

Despite going at it for many years I never found the root cause before I left the company.

The reason it was so difficult was that it only occurred every second month or less and with different customers.
It was also not triggering directly when the error occurred but a while later once the error had caused accumulated errors until one value got negative.

Also, it was a combination SQL, backend code and frontend js and the time from initial error until an invalid value could be hours, days or even weeks.

And we never ever managed to replicate it our self and found no common pattern between occasions.

We think it was some kind of race condition when updating the db that caused duplicate values or a hole in the index series (db transaction or db index was not an option for various reason that would require a redesign of the central tables and most if the central code).

This then grew into multiple error on consecutive updates until one f them resulted in a negative number that then caused a regex in js to fail.

my dad bought me my first computer at 8, when I was 12 he thought I was always playing video games. at 19 he wouldn't pay for me to go get a bachelor's degree in computer science even though I was dual majoring with computer science and business. but he wonders how I always have money, he's 79 years old so not really unexpected.

my mom never understood what I was doing on computers but knew I was making money when I needed it, she's 61 years old and getting in bad shape so she's living with me and my wife. but she can tell when I'm thinking hard on a project and leaves me alone.

my wife doesn't know what I do and thinks I found a fucking magic money tree and she'll bug me after I spent 30 minutes planing a function out and I have to start over.

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".

Here's a real tip for people new to the industry.

It's one of those things that's been said over and over again but very few can really seem to employ. I suggest you learn it /well/.

You are not your code. Criticisms of your code, ideas, or your thought processes, is not a criticism of YOU. You absolutely cannot take criticisms of your work personally.

We are engineers. We strive to seek the best solution at all times.

If someone has found a problem with your code or with an idea or whatnot, it is coming from a place of "this is not the best solution", NOT "you're an idiot".

It's coming from a place of "I'm closing this PR because it is not a change I feel suits this project", NOT "I'm closing this PR because it's coming from a woman".

It's coming from a place of "This feature request is ridiculous/this bug is not actually a bug", NOT "you're a fucking idiot, fuck you".

It's coming from a place of "I've already had to address this in a number of issues before and it's eaten up a considerable amount of my time already", NOT "I don't even know you and this I don't have time for a nobody".

You do not get to be bitchy to maintainers because they denied your request. It's not a reflection of you at all. But if you're arguing with someone who has maintained a piece of code for almost a decade, and they're telling you something authoritative, believe them. They're probably smarter than you on this subject. They've probably thought about it more. They've probably seen their code used in many different places. They have more experience than you with that codebase in almost all cases.

Believe me, if we cared about who was behind all of the issues, pull requests, etc. we get, we'd get NOTHING done. Stop taking shit personally. It's a skill, not a defense mechanism. Nobody has the time to sugar coat every little thing.

Let's normalize directness and stop wasting time during technical discussions into opportunities for ego-stroking and circle-jerking and back-patting.

Unsurpisingly, an in-house client reported a visual bug in IE. So I candidly asked him which version of browser he was running. He told me with confidence: 11. As I couldn't reproduce the bug I asked him where he found the version number. He answered: "below the laptop on a sticker".
Well, it happened to be the year of construction of the computer.

TL;DR: At a house party, on my Phone, via shitty German mobile network using the GitLab website's plain text editor. Thanks to CI/CD my changes to the code were easily tested and deployed to the server.

It was for a college project and someone had a bug in his 600+ lines function that was nested like hell. At least 7 levels deep. Told him before I went to that party it's probably a redefined counter variable but he wouldn't have it as he was sure it was an error with the business logic. Told him to simplify the code then but he wouldn't do that either because "the code/logic is too complex to be simplified"... Yeah... what a dipshit...
Nonetheless I went to the party and He kept debugging. At some point he called me and asked me to help him the following day. Knowing that the code had to be fixed anyways I agreed.
I also knew I wouldn't be much of a help the next day due to side effects of the party, so I tried looking at this shitshow of a function on my phone. Oh did I mention it was PHP, yet? Yeah... About 30 minutes and a beer later I found the bug and of course it was a redefined counter variable... My respect for him as a dev was already crumbling but it died completely during that evening

Alright, seems like I have to buy this.

Ps: I believe to have found a bug in Devrant's Android App: if you attach an image to your rant and tab out afterwards it crashes for me

At one of my former jobs, we devs had to do all sorts of non-dev work, such as writing quotes and even contracts!

The CEO of that company had this naughty habit to contact devs directly without delegating through the CIO. Sure, if it's really urgent like when some system is down because of a bug, go ahead and disturb a dev. But interrupting coders to write some freaking quote? Come on!...

Once, that CEO asked me to stop everything I was doing to write a quote to a customer ASAP, as this was really urgent.

I spent several hours writing that quote. It had to be done right as any specifications in our quotes were used in our agreeements and were referred to in the case of any dispute. So not only were we devs and salesmen in the same time; we also needed to be lawyers.

When I was done and delivered the quote to the CEO, he told me he had no intention to take on that customer in the first place. Instead, he wrote a polite we-are-not-interested e-mail to the customer and cc:d it to me just so that I could read for myself how very sleek a businessman he was.

Me: why did I have to write that quote when you knew all along that you were not going to use it anyway?
Him: It's for your own personal development.

Another naughty habit of that same CEO is that he made "jokes" and remarks that I found inappropriate, such as "You walk like a drunken sailor".

Later, he decided to discontinue our team/product because "it isn't proftable". Well, what do you expect when devs are forced to waste half day completing pointless tasks?!

It was for the better anyway, and I was actually relieved when I left the company. I'm still thinking though, that the real reason he sacked me is that I am too honest and not the docile kind of employee that would be ideal for him. I did question some of my tasks, and worst of all: I didn't laugh at his stupid jokes.

I recently found a vulnerability in a food delivery app where i can add credit to my account. as some of u suggested I decided to report it. Here is their response of me asking (before explaining the bug) if i will be legally prosecuted and if ill be rewarded. this was their response. I feel they were mean. Thoughts ?

Oh man. I have been waiting for this one. Gather round lil' chil'rens it's story time.

So. I was looking for a new project because my old one was wrapping up and that's what my company does. So I was offered some simulation type stuff. I was like "sure why not, I want to make a computer pretend it isn't a computer no more." Side note I should not be a psychiatrist.

So, prior to coming on to this job I felt stifled by my old job's process. This job was a smaller team so I thought the process would be a little smoother. But it turned out they had NO process. Like they had a bug tracking system and they held the meeting to add things to the system, but that was just fucking lip service to a process.

First of all, they used the local disk on the test box as their version control. and had no real scheme as to how they organized it. We had a CM tool but gods forbid they ever fucking use it. I would be handed problem reports and interface change requests, write a bug to track it, go into the code and about 75% of the time or more it had already been worked. However, there was no record of it being worked and I would have to fucking hunt that shit down in a terribly shitty baseline (standardize your gods damned indentation for fuck's sake) and half the time only found out it was done because when I finally located the piece of code that needed changing, the work was already done.

Then, on top of all that, they ask me what time I want to come in. I said 10am, they said okay. One day I roll in at 10 and my boss is mad. Because I missed a meeting. That was at 9. That I wasn't told about. He says I can keep coming in at 10am though (I asked and volunteered to help get him up to speed on the things I was working he said it wasn't necessary) so I did, but every time I missed a 9am meeting he would get pissed. I'm like PICK ONE!!! They move the meeting to 9:30am (which is not 10am).

This shit starts affecting my health negatively. Stress is apt to do that. It triggered an anxiety relapse that pushed me back in to therapy for the first time in 7 years. On top of that the air quality in the office is so bad that I am getting back to back sinus infections and I get put on heavy antibiotics that tear up my stomach along with the stress and new meds tearing up my stomach. So one day as I am laid out in pain, I call out sick. Two days in a row. (Such a heinous crime right.) Well I missed a test event, that I wasn't even the primary or secondary on.

So fast forward to the most pissed off I have ever been. I get called in to a meeting with my boss's boss. As it turns out, my coworkers are not satisfied by the work that I'm doing (funny because I thought I was doing pretty good given that my only direction was fix the interface change reports and problem reports. And there was no priority assigned to any of them).

And rather than tell me any of this, they go behind my back to the boss and boss's boss. They tell me I need to communicate (which I did) and ask for help when I need it (I never did). That I missed an important event (that I played no part in and gods forbid I be sick) and that it seemed like I didn't want to be there (I didn't but who WANTS to work a corporate job).

They put me on a performance improvement plan and I jumped to another project. I am much happier now. Old coworkers won't even say hi, not even those I was friendly with, but fuck them anyway.

I love GDB on CLI!

I'm using an OSS tool for multi-threaded testing stuff, and it's nice but segfaulted after 30 minutes.

I was too lazy to set up an IDE project and click through tons of stupid shit, so I just compiled the tool with debug symbols, fired up GDB on CLI, let it run until a crash, got a strack trace and quickly found the problem.

I sent a bug analysis to the author, plus a patch which got accepted, done.

After three hours of emailing with a customer I can confirm that programmers are the worst customers.
Customer: We've found a bug in the system... <details>
Me: Thank you for letting us know, a ticket has been created and the issue is most likely to be fixed in the next release.
Customer: Please grant me UPDATE privileges in the live(!) database so I can fix it myself
Me: I cannot allow that. You have to use the client software for maintaining your data.
Customer: No, I don't want to spend my day clicking. I want to write queries.

We didn't reply to the last one yet...
If we give him access, then I would charge them at least 3x for fixing issues caused by him.

I'm currently developing an integration to an API and I found out a bug.

So I asked the contact person for the API if this feature was intentional. I did this on their forum for the API and I sent it as a private message to him.

I got a response telling me that they dont have the "sufficient details" to answer my question and that they would investigate the feature "comprehensivley".

5 minutes later I see a post on the forum in the developer section from the contact dude and it was my fucking question.

So now he's asking the users of the API if his and his companys own bug is intentional.
What the actual fuck?!
Is this how you investigate things "comprehensivley"?

My most satisfying bug fix?

I found a core concurrency issue in this gnarly homegrown ORM and reported it to the lead devs, who (very defensively, having written the damn thing) argued that it would never pop up in a prod environment and I was stupid for even bringing it up. Theoretically, this bug could cause pretty much every foreign key to be assigned to the wrong parent, but only if multiple instances of the application were open/running at once. They were so certain it would never happen on live that they explicitly instructed me not to fix it. After all, this bug had been active for many years on a previous project and nobody complained.

Problem was, that previous project was something that only a single user had open most of the time (think: a manager). The new project was something that would be used by multiple people at the same time (think: all the employees). Once we released this new-project-with-old-orm, it didn't take long at all for our customers to start complaining.

After that, they let me fix the bug. :)

mangodb's rant reminded me of smth.. Folks from my country might remember this story.

So we have a national e-health system. Millions have been invested, half of the money have never reached the project [disappeared smwhr in between] and its quality is not shiny. It works, sometimes even fast enough. But boy does it have bugs... Let's not get into that. It's politics.

So some time ago one IT guy spotted a bug that allowed him to get sensitive info of other patients. He informed e-health folks and waited for a fix. He waited for a few weeks but the fix had never been released. So he published his findings in soc media [yepp.. Stupid move]. That caused a national scandal. Not to mention he had been pressed with charges.

That guy and our health minister were invited in one of the tv debates. The guy was asked to explained how he found all this sensitive data. And he explained that he hit f12 in his browser, opened a network tab, issued a network request by clicking smth in the webpage analysed received data in the dev tools.

The minister looked somewhat happy, maybe a lil proud of himself - a person who has a "gotcha!" moment has that very glow he had. And he said: "what you did there was obvious hacking. I reckon you should know that true developers do not do those things you have just explained to us" [he was talking about dev tools].

I died inside a little bit.

When you think you've either found a bug in Python, or you're going insane, so just to double check, you make two mutually exclusive assertions that could never both be true, and yet, your tests still pass.

I think it's time to find a new job.

Took me 6+ full days.

The feature does not work. Repro is unknown, so only prod is experiencing the issue.. Which rules out the debugger option. Sometimes there's an entry seen in logs: "java.lang.StringIndexOutOfBoundsException". Nothing more - just that. No stack, no class, no nothing. Is it my code that's buggy? Is it some config? Integration? Unexpected response...? A bug in a lib? Is dimm faulty ir maybe server's shared libs are off?

Turns out I used a closing parentheses instead a closing curly bracket in an error message that's supposed to be interpolated...

String message = "{some-business-rule-related-error-message-key)";

took me 6+ full days... But I found it. Took the rest of that Friday off to walk in a park and enjoy my life :)

!$rant

So I'm getting closer to finishing my devrant-widget project but ran into an issue because some people use emojis in their about, skills, website, etc *cough @alice.. cough* and well.. it creates internal server errors because emojis dont magically convert themselves xD But I think I found a fix. On to the next bug.

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 :(

Working on my Google Foo Bar level 4 challenge.

9 days past figuring out how to solve this problem..

And finally reached on a working solution. When started compiling my solution.

And then i Find out, the fucking Google tool is facing some bug and not allowing compilation. Tried hard to do everything but still getting errors...
And after searching on Google just found I'm fucked up.. It's on Google's end and they are not fixing it since so many days..

Just 5 days left to complete.. And i have no idea what should i do...

4 month work just fucked up

I'm curious, how did you all start to like programming?

Mine was when I was in grade 7 or 8, which is around 13 years old. I watched a movie called "Hackers", Angelina Jolie was in this one (I think, it was a long time). I was curious on how to be a hacker, then I googled and found an article which said something about learning to code.

I wasn't sure I would enjoy it at first but after a while, I started enjoying that thrill you get when you solve that pesky little bug that took you days to get rid of. Haven't stopped learning more about programming and computers since.

*At the daily status meeting*
Manager: I don’t have anything to table or anything I want to ask about. I honestly don’t know what the point of this meeting even is.

*Throughout every other living breathing moment of time*
Manager: Hey, I had an idea
Manager: Hey, I wanted to get your thoughts on something
Manager: Hey, what do you think about…
Manager: Hey, what are you currently working on?
Manager: Do you think you could just *sneak* in this new feature request and have it to me by EOD?
Manager: Hey, I just sent you an email
The email: Hey I think I found a bug, it’s with image alignment in Microsoft Word and it’s pretty breaking to my productivity report. Do you think you could take a look right now? Thoughts?

Rant!!!!!!!
When you work hard on building frontend and suddenly, you realise whenever you restart your localhost, some URLs don't work. And it's random. Error logs also seem meaningless as the latest error report keeps changing the error location from file to file. Wasted hours to identify the abnormal behaviour.
I always had the mentality to keep its programmers fault in order to always consider all possible flaws.
But realised later that it was the OS setting issue. Did a stacktrace about 300 lines and found out the root cause(hopefully as no issues till now). The bug was related to total allowed open files at a time.

Hey so found another tiny bug, well more like a typo, if you're​ a subscriber and you go to edit a post more than it's time limit in this after 57 mins you get the old can't edit after 5 minutes alert dialog message, super easy to fix (I guess lol) and not too important

Management Double standards...
At a previous employer, the manager had me doing some QA testing for a updated version of some customer facing UIs. I spent 3 days constantly testing, except for my lunch break.
Every bug that I found I sent to a Sr dev.
Now this Sr dev was a coding savant. I mean awesome coder, but he had the personality of a rat and snake combined. If he wasn't coding he was brown-nosing the manager, talking about how he was doing all the work, or trying to rat on us other devs.
Anyway this dev has spent the 3 days of bug fixing alternating between watching videos and fixing bugs. Don't know what the videos were, don't realy care. I do know that he did not like to be disturbed while watching them...
On the third day, on my lunch break, I decided to watch two fifiteen minute videos on VSTS feeds and linking node packages.
As soon as I started Sr dev came over and asked me if I was focused on the teams priorities. I told him that it was my lunch break and since this was related to an upcoming sprint I thought it was worth it.
This S.O.B. goes full out hissy fit. He was flat out throwing a tantrum like my small daughter would. He made such a noise that my manager walked over and asked what was going on.
This shitbag Sr dev smirked at me and asked to speak to the manager in his office. When the manager called me over I knew what was up. I was lectured on not focusing on the teams priorities. I tried to explain that the videos were relevant to an upcoming sprint but was shot down. When I brought up the fact that the Sr dev was watching videos, the manager told me flat out that he didn't care. I was mad and told the manager that this was bullshit. All the manager cared about was keeping the Sr dev happy. I was told to "treat <shithead sr dev> with respect or else".
It was at that time I decided to look for another job. Less than a month later I left, for a much better paying job with awesome benefits. Sr dev acted like he was hurt I was leaving. Manager couldn't have cared less.
When some others on the team heard what he did, they started looking for work elsewhere too.
A month after I left another Sr dev on the same project left. At the same time a BA and QA tester demanded to be put on another team or else they would leave.
Manager started out with a team of 6 was left with only two people.
When the last one left, manager had the nerve to ask me why I didn't let him know anyone was unhappy. I told him if he cared so little for me, why would I think he care about them.
Ultimately, leaving was one of the best things I could have done.

So I had this conversation with my boss yesterday...

Me: Hey, I found this bug in the other team's code that has a major impact on what we're trying to do. Can you ask them to look into it?

Boss: No, I don't want to be the one who has to tell them there's a major bug in their code. Find a workaround.

M: But... It isn't really a major bug, it just has a big impact on our side of things.

B: Workaround!

Fuck bosses who value how they think they look to other devs over a day of my time. Fuck.

ATTENTION @dfox!!!!

I found a bug in the devRant REST server. When you upload a rant with a vertical image (when the height is bigger than the width), the server seems to flip between the width and the height (I don't know if it happens all the time), and when I fetch the rant, the JSON data for image width and height is flipped! (in the JSON, the attached image section contains width and height information about the image, and they are flipped in their values, meaning that the width key is equal to the height, and the height key is equal to the width).

An explanation on the image below:

The small window on the left shows the real info about the image. Notice how the height is 800 and width is 600.

The window at the bottom shows the data fetched from devRant servers. Notice how the width returned from the server is 800 and the height returned from the server is 600.

Help. I'm drowning in spaghetti code

I've been working at a working student (15 hours/ week) at a local software company for about a month now... and with everything I learned at college I'm kind of getting eye cancer here.
We still use SVN
We don't have any coding guidelines. No checkstyle, no overview over the program. When I started there I was just giving a ticket and they said good luck.
We just have some basic RCPTT Tests inside Eclipse and most of Themen don't work in the trunk because the gui got changed...
At least we have a ticket system but it doesn't get used by most of the working students.
I found 10 other bugs while reproducing and trying to fix 1 bug.
And I've never seen Java raped so badly. Today I saw a line that started with 6 brackets because whoever wrote it wanted to cast like there was no tomorrow. I see more instanceof in one day than in my whole devlife before.
The only thing we have is two normal employees that review our code before we are allowed to commit it into the trunk.
So yeah... I'm drowning in spaghetti-code.

I just found a new WhatsApp Crash Exploit. Full denial of service right there. An attacker could send a message to a Chat (be it private Chat or group Chat) and everyone who receives the message has no chance of starting WhatsApp again. It crashes and won't restart.
Tested on latest version on Samsung Galaxy S6 and S8. Don't know if it works on other versions but I am pretty sure it does. (It's midnight here, noone online to test)

The fun thing is, I knew this Bug for a long time but when I last tested it, nothing happened. Which means this Crash is only possible because someone at WhatsApp programmed a new Feature...

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! :D

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 again

So I found this consulting job a while ago thinking that some extra cash while studying would be nice to have.

I meet with the guy, a researcher trying to start a business up, good for him I think, maybe we'll hit it off, continue working, why not? Except he has no clue how to write working code, all he ever did was writing matlab scripts he says, thats why he hired me he says.
Okay, fine, you do your job I do mine.

He hands me the contract, its about comparing two libraries, finding out which one is better suited for his job, cool, plots and graphs everywhere.

Except this is an unpaid job. YOU WHAT?! It's a test job. FINE. At least it'll look good on my resume.

We talk about the paid part where I'm supposed to scale the two libraries, looks good, as expected from an ML engineering perspective. It comes to payment. The dude has no idea how taxes work, says he has a set amount to pay and not a penny more. I explain with examples how taxes are paid, how you get reimbursed for them and so on. Won't budge. Screws me over.

Opens the door for other jobs I think, he'll learn next time I think and take the job.

Fast forward a month, 90% of the job done, he adds a third thing to compare. Gives a github link to a repo with 2 authors, last commit a year ago. There are links to a 404, claiming compiled jars. Fuck.

Not my first rodeo, git clone that shit, make compile, the works. The thing uses libs that ain't in no repo, that would be too easy. Run, error, find lib, remake all the things, rinse repeat.

The scripts they got have hardcoded paths and filenames for 2 year old binaries, remake that shit.

It works, at least I get a prompt now. Try the example files they got, no luck, some missing unlinked binary somewhere, but not a name mentioned. Cross reference the shit outta the libs mentioned on readme, find the missing shit, down it.

Available versions are too new, THE MOLDING NUTCRACKER uses some bug in an old version of the lib.

I give up. Fuck this. This ain't worth the money OR time. Wanker...

This is a short tale that can be summed up as "oh fuck meee".

After finishing an API the night before I settled in for a day of bug fixes and tidy ups. Until slack went off.

The front end dev was getting an error, a code breaking error. After doing the standard process of request checking i went okay must be me. I find the script that is has the error and the line that it is failing at.

Que 2 hours of the full cycle of anger, sadness, pleading, and finally acepting that it had finally happened I had gone insane. The code was to documentation best practise correct and it still had the same error.

I the cheaked the DB on a whim and I found that my code was not wrong and it was doing exactly what I wanted the data however had a single record that was old and the schema had change juuussstt enoigh to break everything at that record. One 3 secound deletion later code ran perfectly.

Coolest bug I ever found was the temperature sensor connected to a raspberry pi giving me -40 as a value.

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.

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.

I always thought i could use some extra hours a day, but 40 seems a little excessive...

This is also the first time i encountered such a bug in the wild, and i'm way more excited than i should be, hehe.

I found a post in the depths of the steam forum about borderlands 2,that if you open the steam-overlay's browser while in-game, go to youtube, start a video and paused it, you would get +10-15% FPS. Tried it and it worked.
I can't even start to imagine the causal chain that causes such a... bug? feature?

12pm : "I found a bug!" - "ok I'll fix it"

5pm : "I found a bug!" - "call pest control"

'Hey I found a bug in your code, it's probably a typo, see here.'

Me: Oh right, yeah. How stupid of me. Thanks, I'll push it.

'It's okay. You can push it or I can do it too after you push the changes we just discussed. I actually simplified one of your methods.'

Me: You, what... ?
(You crammed multiple lines in a single line with your stupid as fuck, rigid constructs, removing my error handling, loosely coupled service, in the name of simplification?)

' Yeah it's just four lines in a single function now, no need to call the function again and again.'

Me: (No... Just no. This totally undos whatever little I could do to avoid supporting your idiotic object in the first place.)
Oh... okay, we'll see. I'll let you know.

What life.
Life in a company full of ignorant, inflated egos is no joke.

Details:
I created a service that reads a configuration file and returns the configuration. This person needs five entries for his app logic. He collected them in a object. Quite alright. Except that the class prototype is shitty. I, like a normal person, made my service return a value based on input. I was asked to incorporate this awful object so that I can return the five entries together, which is awful because the service is not supposed to know about how the entries are clubbed. It should most certainly not know about the data members of the object!

It took a while ... but I found the bug

I’ve noticed a bug in HR that I would like to report. Steps to reproduce:

1. Get offer on LinkedIn/Email
2. Respond politely and optimistically that you’re interested but would like to scale down you’re hours to 32 per week, changes in pay are accepted.

Result: 404 Not found

Expected result: I’m only human let me work part time pls

After a long work, I finally found the bug!!!

Got a weird bug report, 6 red bull later i'm a energizer bunny on speed. But have found and fixed a severe underlaying bug. Can't believe noone had noticed for years.

Now i'm afraid to report it to my boss cause it most likely costed us a lot of money over time. And I just got shafted in the pay raise so my loyalty is low.

Spent 2 hours last night (leaving an hour late) with the IT guy hunting down a problem that affected at least 12 other teams. It didn't crash the app, but did prevent MANY scripts from working, and thus nothing could be committed.
I found the culprit, made a solution, and posted in the email chain my solution. (it required a code review and a client-side update)
Someone responded asking for another dev to confirm my report. That dev did and them dumbed it down for those who can't understand programming talk. Then EVERY EMAIL after that thanked that dev for "fixing the root problem" and "solving their scripts".
And just now, the PO for the bug was replaced to that dev's team. (previously was my team's PO)

Client: "I found a bug on your website. Its not possible to submit the contact form."

Me: "No bug. Its a feature"

#answerforeverything

Today I found a critical bug to our software and wrote a fix and tested it locally.

Common sense would dictate that especially when it is critical you test said fix on a real release and not with a debugger attached and running onna different device altogether.

I was denied this request because the afflicted machines engineer would not be able to finish the machine before the factory acceptence test.

I stood there with glassed over eyes for a second and then to no avail tried to explain that without this fix he wouldnt even pass the internal acceptance test......

Back when I used be a junior fresh out of school, my senior used to say, when releasing a first version or a major version of any software, app or website always implement easy to fix bugs.

End users or clients, especially the ones that tasked you with the creation of it, will look for a bug until they find one, if it isn't one you will spent hours trying to figure it out, instead give them one.
You know how to fix it and the client is satisfied they found one.

To this day, i still do that, although mostly not even aware of it. Eg: I know that's a bug but i'll fix that when (not if, when) they complain about it.

I even find myself telling the juniors, i develop with, giving them similar if not the same advice.

And that is what experience means, skill is something they teach you in school.
Experience is what makes you a senior or a junior, not your level of skill or the amount of keywords on your Linked In profile.

I found a bug in my computer.

I was working on a bug in a legacy application and I was the first person to open the project in 10 years.. Found all the variables named with swears.. It was hilariously difficult to figure out what was happening lmao..

Not really a hack but still worth telling:

I was working in the QA team for a big project. I tried to do some automation when I realized some radio button behaved weird... out of curiosity I checked the source and saw that there was a hidden option for a unimplemented payment option.

I was like: Let’s see how the system behaves if I just submit that form with that hidden value...

Well I was very surprised when I received the email that my order has been processed successfully.

During the investigation we found out that this bug was in prod for over two years. And it requires a one liner executed in the browsers console to skip the payment.

It was kind of a big deal and although I was (and am) still a trainee (in apprenticeship) I got invited to meet up with the client and the bosses.

It was kind of a door opener! After that they trusted me more. I have more responsibility, more interesting tasks and more client contact ever since.

To make a long story short:
Validate everything on the server side ;-)

Found another bug, this one won't have a screenshot because that wouldn't explain much.

So I edited a comment that was 6 mins old and after hitting save the app refreshed multiple times and then went to a blank page.

Also for some reason in the settings screen I have the supporter banner thing that pops up to say to support again (I thought I already paid, lol would be buggy to be a double supporter lol).

Sent patient health information in a screenshot of a bug I found, unencrypted, through email. No one thought to mention the test DB had real patient info. 😐

Bug I had to fix today: some elements in our React app were being swapped with other elements.

We had `<foo>bar</foo>` on the component but on the html `foo` was being swapped with some other element in our app. It's contents ("bar" in the example) were being left in place, though, so we were getting `<baz>bar</baz>`.

This would only happen when running on production mode. On development everything was fine.

Also, everything seemed fine on the React dev tools. `foo` was where it was supposed to be, but on the html it was somewhere else.

Weirdest shit I ever saw when using React. I found a way to go around it and applied that fix, but I'm still trying to track this down to the source.

The worst part was waiting for fucking webpack to finish the production bundle on every fucking change I wanted to test. I didn't miss the change-save-compile-test flow at all.

What a shit day.

I was looking up for a bug in my code that caused a fail in one of the test.
Hours later I found that negative integer division in python is just stupid and -1 / 10 = -1.
The sad part is that -1/10 != -(1/10) contradicting the associative property of multiplication over the real numbers.
FUCK YOU PYTHON.

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 :)

@dfox in case you havent already discovered it i have found a bug with notifications in the iOS app.
Steps to reproduce:
1. open notifications
2. tap one of them as many times as you can really fast
3. It generates a new view controller for every time you tapped it.

obviously having to tap furiously is a bit obnoxious but i originally noticed it when the app was running slow and i tapped the notification a second time. It created 2 new view controllers instead of one so i had to actually go back twice to get back to the notifications screen.

Right now, I'm tracing a bug that causes some of our data to be lost.
and I found a table with 'xxx' field on it. ohhh. what is it for?

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...

This is probably VERY OLD, but why don't devRant supports Markdown? Having to upload (not paste or drag) code screenshots and having to UPPERCASE to yell or emphasize text feels... quite non-dev.
I found the bug repo and checked the Markdown issue has... almost three years.

I just came by the @highlight bot. Seriously? There are several layers of "wrong" with that hahah

Bonus: not very good UX to write a message, try to post it, and ONLY THEN get to know there's a time limit. This should show when you open the form, not when you submit it.... But I just sent a bug report on that, at least.

Bonus 2: if the char limit is 5k, why's the textbox so tiny on the web?

qa: so yesterday we found some bug, not really related to you but <boss> told me to put it on you
me: yeah, when he doesn't, this dick didn't work since I came

*later this day at ~15:00*
boss: so I'm going home, you **must** deal with this bug today, your algo doesn't work.
me: it did 2 days ago didn't it? did you even check the bug?
boss: yeah
me: did you check for regression or just said to put it on me?
boss: nope
me: did you check the changes of the new guy?
boss: nope
me : so why the fuck blame my code?!

*17:10 I'm going home no regression, new guys code deadlocks, not a single fuck thrown*

A dev found a bug I created where I set a SQL parameter name to @OrderID instead of the expected @Order. The standard is @OrderID, there is one stored proc where it's @Order.
Oops...I didn't catch it because the integration test didn't cover that area of the code. My mistake...I should have checked...I take complete responsibility for the screw up.

He let me know by email..
"When refactoring, from now on check the stored procedure parameters, there are a few that don't follow the standard."

I was like "from now on..."? ...wow....bold comment from someone responsible for code that doesn't check for nulls, doesn't log errors, and relies on exceptions for flow control. You wouldn't even have known about the error if I didn't modify your code to log the error (the try..except returned false)

I really wanted to reply ...

"Fixed. From now on, when you come across those easily found bugs, go head and fix it, write a test, and move on. Don't send a condescending email to me, my boss, your boss, all the DBAs, and the entire fracking order processing team. Thanks."

But..I thanked him for finding and letting me know...we're a team..blah blah blah..

Frack..people suck.

Once i worked on an application which has very long form and submit to a soap endpoint (post). I felt my life was so pointless when testing after i made changes. So I automated the testing by generating post request so i can just run it.

I filled the user name with Brandon Boyd, Alan Turing or Ryan Gosling. And it increments like Boyd1, Boyd2.

Once my colleague found a bug, the data never get saved but all the boyds persists. He knew it was me, who uses that kind of name

My barbaric manager (was involved) kind of pointed his finger at me. I sweat a bit though i couldn't find logical explanation why Boyds stay. but turned out someone changed the sqlscript.

I just wasted 2 hours together with a colleague to trace a bug, through several modules, functions, data, etc to find out it was usage of the wrong information in the wrong place. The data used was never intended to be used this way.

I HATE SUCH SOFTWARE ARCHAELOGY.
Carefully uncovering layer over layer, getting one detail after another, from which you don't know if it's really necessary to trace the bug, until you lose the sight of the whole picture. Then when you're confused to the maximum, try to figure out what's important and what not and reassemble the puzzle until you can see where the road is heading.

At least we found the cause of the bug, so it wasn't useless. Now we have to waste more time to develop a solution (...preparing for next rant 🙇)

Managers at my jobs for the most part leave me be. Though I often have no clue whether I'm doing OK. I guess no news is good news right?

My worst experience isn't that bad. At one place, I was the only tester working on things coming from 20-30 devs. After about a year+, the company finally hired more testers, but it was still only 3 of us.

We were in the final stages of releasing a build to prod. It was going smoothly, or so we thought. At the last minute, I found a buried bug that was a showstopper.

A lot of hatred on me that day, that once it was fixed, and the release was finally deployed, I just shut off my laptop and left. I took all the blame because I was the one who found it rather than blaming the team as a whole for not finding it earlier. Oh well. Stuff happens.

Let's knock on wood that I don't run into worse higher up stories.

So, this incident happened with me around 2 years ago. I was pentesting one of my client's web application. They were new into the Financial Tech Industry, and wanted me to pentest their website as per couple of standards mentioned by them.

One of the most hilarious bug that I found was at the login page, when a user tries logging into an account and forgets the password, a Captcha image is shown where the user needs to prove that he is indeed a human and not a robot, which was fair enough to be implemented at the login screen.

But, here's the catch. When I checked the "view source" option of the web page, I saw that the alt attribute of the Captcha image file had the contents of the Captcha. Making it easy for an attacker to easily bruteforce the shit outta the login page.

You don't need hackers to hack you when your internal dev team itself is self destructive.

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. 😬🤯

I have been debugging for like hours trying to figure out the cause an unknown bug spoiling my UI by making my elements overlap.
I'm working on a Unit Converter that takes kWh and then converts to mWh. (Logical Conversion: 1000 kWh = 1 mWh).
Just an easy shit i thought, using Javascript I just passed the dynamically generated kWh value to a function that takes maximum of 6 chars and multiply it by 0.001 to get the required result but this was where my problem started. All values came out as expected until my App hits a particular value (8575) and outputs a very long set of String (8.575000000000001), i couldn't figure the cause of this until i checked my console log and found the culprit value, and then i change the calculation logic from multiply by 0.001 to divide by 1000 and it came out as expected (8.575)

My question is that;
Is my math logically wrong or is this another Javascript Calculation setback?

Smashing on the keyboard
with 3 screens infront of my face
i spot a nasty bug,
In one of the features someone else made,
I called their office for aid,
But found no one is there to be
Of any aid to my sorry ass,
Now i have to debug the whole thing,
Oh,
Documenting code
Documenting code
Why didnt you document the damn thing
At least tell me you left some comments
To help debug thy algo tree
Oh ...

:'(

Had a bug that I just couldn't figure out. How did I solve it? Had to think like a user. Just started clicking options over and over. Not giving it time. Found my issue.

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.

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?

Are you worried about your development environment becoming more and more unstable?

Let me give you an example: I've been (mostly) a .NET developer for about 10 years now and yes Visual Studio crashed sometimes but not very often. Also whenever I found something that seemed like a bug in e.g. the MVC framework I always realized that the problem was in my code. However recently there is a VS update almost every week, and I more and more often bump into open GitHub issues without a fix.

Is this the same with other development environments? I also had a lot of issues with XCode/Swift but I never expected that to be stable...

!rant
Does anyone else derive great pleasure from creating quality of life/small utility programs?

So I'm learning python in between projects at work (plan on slowly moving new projects to it) and damn, my coding buddy and I have found a package/import for almost anything we can imagine. Heck, we canned ourselves laughing when we started googling random things and still found python packages that do it. I plan to use the language to automate a ton of things when I get a new PC.

Aside from that, I recently in 2 days (1 day building, 1 day bug fixing) made a tiny utility that shaves a good 5 minutes off a certain task for my colleagues at work, and in bulk use will save even more time. It's a textbox and a button only but it felt so nice to make something useful like that so quickly.

Well... I can think of several bugs that I found on a previous project, but one of the worst (if not the worst, because the damage scope) it's one bug that only appears for a couple of days at the end of every month.

What happens is the following: this bug occurs in a submodule designed (heh) to control the monthly production according the client requirements (client says "I want 1000 thoot picks", that submodule calculates the daily production requirements in order to full fill the order).

Ideally, that programming need to be done once a week (for the current month), because the quantities are updated by client on the same schedule, and one of the edge cases is that when the current date is >= 16th of the month, the user can start programming the production of the following month.

So, according to this specific case, there's an unidentified, elusive, and nasty bug that only shows up on the two last days of every month, when it doesn't allow to modify/create anything for the following month. I mean, normally, whenever you try to edit/create new data, the application shows either an estimated of the quantities to produce, or the previous saved data. But on those specific days it doesn't show any information at all, disregarding of there's something saved or not.

The worst thing is that such process involves both a very overcomplicated stored procedure, and an overcomplicated functionality on the client side (did I mentioned that it dynamically generates a pseudo-spreadsheet with the procedure dataset? Cell by cell), that absolutely no one really fully understands, and the dude that made those artifacts is no longer available (and by now, I'm not so sure that he even remember what he done there).

One of the worst thing is that at this point, it's easier to handle with that error rather to redesign all of that (not because technical limitations, but for bureaucratic and management issues).

The another worst thing (the most important none) is that this specific bug can create a HUGE mess as it prevents the programming of the production to be done the next day (you know, people tends to procrastinate and start doing things at the very end of the day/week/month)... And considering that the company could lose a huge amount of money by every minute without production, you can guess the damage scope of this single bug.

Anyway, this bug has existed since, I don't know, 2015 (Q4?) and we have tried so many things trying to solve it, but that spaghettis refuse to be understood (specially the stored procedure, as it has dynamically generated queries). During my tenure (that ended last year) I spent a good amount of time (considering what I mentioned on the last rant, about the toxic environment) trying to solve that, just giving up after the first couple of weeks.

Anyway... I'm guessing that this particular bug will survive another 4-ish years, or even outlive the current full development team... But, who knows ¯\_(ツ)_/¯ ?

Just got off the phone with a csr about a bug they found. No biggie, I said I'd fix it. Basically until it gets fixed I told them that when they do their process to make sure to do "foo" first, then "bar" second. As soon as I got off the phone, had to poop so I went to the bathroom, and as soon as I sat down I get a message from the same CSR, "Hey I did bar first, can I type foo then bar again?"

WTF DID I JUST SAY LITERALLY 2 MINUTES AGO ON THE PHONE. TBH IT WOULD BE BETTER IF YOU JUST DIDNT DO ANYTHING FOR 15 MINUTES BUT NOW I HAVE TO COMB CLOUD FUNCTION LOGS, FIND THE DOC UID YOU CREATED, FIND THE DOC YOU MADE, DELETE IT, DELETE THE ASSIGNMENT IN YOUR TRASH ASS WORKPLACE PORTAL, AND STILL FIX THE SAID BUG

I've tried so many ways for that at night or during walk spark of bug solving ideas:

- fluorescent ink on regular paper
- florescent mini whiteboards
- "alexa remind me.."
- writing down in my phone
- recording on my phone
-..

But all of those due to my short term memory made me forget half the things by the time I opened the fucking phone/app, found where to grab the pen or the whole dance for alexa, to remember the exact phrase I have to spell out, when it should remind me, what time,..

Earlier today I remembered how I had a little tape voice recorder I used to use a ton, thankfully that tech advanced by now and found myself a stereo mic setup little voice recorder that can also act as an mp3 player!

Went for a walk today, while listening to some podcasts, then it hit me as usual on how to fix and implement some things that were awkward at best on paper when I left home, pressed the record button, recorded it and went straight back to music mode, which remembered where I left off!

I'm so indescribably happy, I ordered quite a bunch of the same to just throw around everywhere, at the bed, in the bathroom, kitchen, for walking outside, everywhere haha

Today we found out that my brother has a condition, triggered by a stressful event, that causes his heart to try and shutdown.

The dev in me is screaming "fix the bug!"
The crazy in me wants to start punching doctors in the face til we find a solution.

But the rational side of me knows there's nothing that I can do because that magical asshole in the sky didn't commented his code...

And then, looking for the source of a bug in the code .... I randomly found this:

public bool IsOperationStarted { get; set; }

public bool IsOperationStartedTrue
{
get { return IsOperationStarted == true; }
}

public bool IsOperationStartedFalse
{
get { return IsOperationStarted == false; }
}

This weekend I was working on a fun hobby project with a friend of mine. While he was modeling items for the game I started with a dungeon generator.

This morning I got stuck at a bug which took me more than 12 hours and 4 developers to fix. In the end I found the issue. I was checking

If y > arraySize && somethingElse
DoSomething();

It had to be:
If y < arraySize && somethingElse
DoSomething();

After I changed that everything worked without issues... Day well spent...

What idiot uses 0 for a success response!!! Integrating with a 3rd party I found a bug in our code that uses the default value for an int when the external server can't be reached.

As it happens 0 is the default integer in most languages so no surprise when our system accepted the 3rd party as a success when it blew up 😒

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.

Check out my current scenario:

I have to show some progress in fixing a bug to management in the morning..

I tried to sleep early, so that I cud fix it before the standup..

but I couldn't sleep, so I thought of fixing the issue now itself..

Sat down to fix, got stuck with a stupid blocking issue, did all the wrong things to debug it, wasted 3 hours, found the issue fix (not related to the main bug at all)

nd now going to sleep..

It's like:
Distance covered = 1000kms
Displacement = 0!!!!

!rant && Android

I thought I found something on devrant app turn out it is an Android thing. Not sure if a bug or not.

I use Android 7.1.2 default keyboard . And Google place a small G logo at the top left corner of keyboard. Clicking that show the gif, emoji, language setting etc menu.

On devrant and a few apps I have tried, that G icon remains on the screen in a transparent and almost not visible state but at the same position after hiding the keyboard. Like a watermark.

At first I thought devrant app background has that mark. Even took a screenshot to share here. Turn out it doesn't show up on screenshot. Because when I zoomed in on the image, the icon remained at same position on screen. So it is showing on Google photo app as well.

Any of you guys have that issue?

QA: I found critical bug in your application. 😡
Me: Oh no, It's a feature! 😅

I fucked up...

I inadvertently fixed a bug which changed the behavior in another application. Weeks later had a seemingly unrelated issue which my initial assumption was to blame a 3rd part tool (which was wrong). I gave said assumption to my manager not thinking anything of it and putting a simple change in place.

Higher ups start asking my manager about it, he provides details...the more I thought about it the more I realized the changes I made did not make sense.

I dug deeper into it and found it was due to the change I made weeks ago. So my manager offers to cover for me but i told him I'd take full responsibility.

I'm not getting fired or any type of reprimand at all...I just hate fucking up and then it looks like we are trying to lie about it being our fault.

At a previous job I had, there was a bug in the payment code, we did not know anything was wrong until the customer support team began receiving some crazy emails stating that our company emptied their bank account. Then we investigated further and thousands of customers had their banks emptied. So the payment team went big hunting, found the problem to eliminate further chaos.

Unfortunately the person responsible for this huge screw up was not fired immediately, but did resign soon there after.

Boss found a bug, fixed it and told him it was commited. Replies couple days later with "you should really check your code better", after checking the live site. Told him that the code still isn't live, just commited (as I wrote), no reply. Admins...

I was almost 2 days in a task to find the reason of a bug in a client's process, then I found something really weird, that made all the team go to my desk to see wtf was happening, then a guy says, "wait, this was not supposed to be in there, I was editing this process in other environment (he knew it because of the number)" , what did we discover? Someone (they haven't told me who), was supposed to put a file in a folder, just it, but the motherfucker did put the file in the wrong environment folder. I lost 2 days chasing a bug that never existed '-'.

College came to me today with version 3 of an attempt for a bug-fix followed with the comment "This one should work, this time i tested it myself before commited it and came to you"

I just thought: then wtf did you do the previous two times? Just yolo commit it to the codebase?

Maybe its time i found some other place to work..

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 was kinda proud, when I released a new test version of my android app, since I had a couple of new features and bug fixes. As soon as I told a friend of mine about it he found a error that has never occured before in the method. This only happens in the release build. Why does it happen? BECAUSE SOME DAMM VIEWS WANT TO BE INITIALIZED AFTER DAMM THE APP HAS BEEN PAUSED/MINIMIZED

So management calls me at 1 AM. I have insomnia so I'm still awake... but I know I have to set boundaries, steer away from unhealthy and unproductive habits. I knew that this spontaneous meeting would not be compensated, and even if they wanted me to fix a bug, I'd be too sleepy to do anything really. I needed some healthy sleep. So I muted my phone and ignored them...

But I kept thinking on the call. What did they want? Did they found a bug on production? (We do have clients on the other side of the world.) Would this create a big fight? And of course, if they brought it up, what would I respond? I did feel guilty. I was worried about the company, since my future also depended on it... and my insomnia kept me awake for an extra couple of hours...

Yesterday was a horrible day...
First of all, as we are short of few devs, I was assigned production bugs... Few applications from mobile app were getting fucked up. All fields in db were empty, no customer name, email, mobile number, etc.
I started investigating, took dump from db, analyzed the created_at time stamps. Installed app, tried to reproduce bug, everything worked. Tried API calls from postman, again worked. There were no error emails too.
So I asked for server access logs, devops took 4 hrs just to give me the log. Went through 4 million lines and found 500 errors on mobile apis. Went to the file, no error handling in place.
So I have a bug to fix which occurs 1 in 100 case, no stack trace, no idea what is failing. Fuck my job.

Everytime I face a new bug, my innerself tries to convince me that I can never find a solution to this.
But my gut feelings know that sooner or later I've always found a solution.

Thanks to all the devs sharing their problems in the internet.

When you are very busy and got a tight schedule but some other team complains to their boss that your changes to a shared library completely broke their work and that is a "showstopper". They say it worked before so it must be their code.

So you try to figure out what happened because you sometimes make mistakes even though you took precautions. It takes almost 3 days of your time because you dive into your commits and into their messy codebase.

Turns out the fucking thing never worked in the first place and nobody took the time to validate this. Worst thing is I found the bug with someone else even though it's not even my job to do it. I wasted my fucking time.

I swear if I was not working remote I would have started a fistfight in the office.

My life was troublesome today, had to help a non programmer to run jar files.

The jar executed well from command line in Windows 10 but didn't work on double click.

Did all the tricks, registry edits, cmd commands and at last I found a miracle tool called Jarfix.

Just double click and all okay.

The root cause of the problem was 7zip.

This bug is reported in the Oracle bug reporting and they have closed it as " Will not fix" low-priority report.

So the other day, I was working on some Python project when there was this bug that kept transforming. Like seriously, I would turn from "bool not defined" to "function does not exist" to literally "file does not exist"... within the FILE. And when I fixed them, new bugs kept popping up, and I couldn't find anything that was a problem. Nothing. There was this one function in there that, if I changed even the comments in there, would break. And so.... I turned off Atom and turned it on again. ( ha ) Didn't work. I restarted my computer. I copy pasted the file into another file. I used another IDE. I restarted GHCI. I restarted Jupyter Notebook... and after 6 hours... I found that it was because an if statement has a comparison between a bool and a bool, with a = in the middle. (not ==). I swear I almost threw the computer on the floor.

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....

Spent 2 hours in frustration trying to fix a bug in my code. Then i found a > where a < should have been.

Is it OK to punch a game dev who codes stupid numeric bugs?

So my wife got into Stardew Valley, that admittedly awesome comfort game farming simulator.
She went pretty far in the game, and found some item that was supposed to highly increase the damage she could inflict onto cute little monster thingies.
It didn't work as intended.
Since equipping the piece of shit all her hits did 0 damage. She tossed the item away but the problem persisted. And on and on...
She took to the googles to try and find some explanation, and apparently that is a fairly common bug for mobile devs.
Then she called in the big guns (that is how I'm calling myself in this case, you will see why).

Apparently there is some buggy piece of shitcode somewhere in the game with a numerical insecure routine that overflows the attack modifier. I.e. if it was supposed to increase from 1.990 to 2.010, it actually went all the way down to -0.4.
She was lucky her attacks weren't increasing the monsters' HP.

We found a forum post where some dude said that he managed to edit the game save file and reset the negative-value attack increase modifier variable. Seems easy enough at first, but my wife uses iOS. Nothing is ever so straightforward with apple stuff.

We did get to the save file, she emailed it to me (the file has no extension and no line breaks in it, so we facepalm'd on a couple attempts at editing it directly).
I finally manage to get it into my personal 11-yo laptop... that won't open a single line file that big.

Cue the python terminal. Easy enough to read the file into a string var and search for the buggy XML tag. Edit the value and overwrite into a new file. Send it back to her by email. Figure out how to overwrite the file in iOS.

Some tense moments while the game reloads... and it works!!!! Got some serious hubby goodwill points here.
Srsly, this troubleshoot process is not for technophobes. It is out of reach to pretty much every non-techy user.

And now back to the original question: If I ever manage to find the kid who coded a game-breaking numerically unsafe routine and shipped it as if every test in the planet had waved it bye-bye, can I punch them? Or maybe buy them a beer, let's see how I get to cash that hubby goodwill tonight :)