I’ve had a good amount of incompetent co-workers in the past. One that stands out was this junior developer who worked at one of my previous companies. He was incompetent, but that wasn’t even his worst attribute. He was incompetent, and worse, he had a piss-poor attitude.

Myself and a few other devs at the company tried to help him, but he would literally get mad when people tried to help him. Sometimes he would even call one of us over and start getting snarky with us as we tried to help him. He was a piece of shit and a shitty developer. I don’t think he built one complete feature or fixed one bug in the year he was at the company before he was eventually fired.

Oh, and aside from his incompetence and shitty attitude, he had no sense of humor. It was so annoying. My friend and I made a little song based on his name and a group that sounded like his name, and he got pissed. We always used to sing it anyway after that and it always riled him up. I feel a bit bad about that now but he pretty much got mad at everything so whatever.

One of my favorite memories of him is when he was leaving one day, my good friend/co-worker and I were having a Nerf gun battle. The junior was leaving the office, and my friend tried to get him involved in the battle and shot him, but accidentally hit him in the back of the head. He said nothing, didn’t turn around, and just walked out lol. He was not happy about it.

Me doing CSS:

Improvise. Adapt. Overcome.

Fixed this guy's code and he spent the whole day thanking and explaining to me how sad and depressed the bug had left him. I felt really sorry for the poor dude. Lol.

"I am a fucking idiot"

These words ring loud when I'm stuck on a bug and the fix is so simple that I can't help but hate myself lol 😅

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

iNNOVATION

Support has today gotten the bug report that a user cannot make phone calls from Antarctica

lol

Who else questions the Apple QA team?

Effective power to the letter "i" not working to the root bug and now this?

Jesus Christ they need to get some help lol

Tldr; my "this is not bug, its a feature" moment actually turned my bug into a feature.

Today we were presenting a project which has imposible deadline. I am developing this small project alone (which is probably good). I implemented core features first but I know project still have bugs and a lot of tech debts. Another friend started to presenting our demo and a wild bug appeared as expected. He was adding rows to a table. To add a new you gotta open new modal by clicking + button and fill the form. One of the fields had a bug. When you add row by clicking Ok button, the value of the field stayed there after you open modal again. So its basically a state problem in React. I forgot to clear previous state of modal. When they see that and my friend said "oh we got a bug there". Then I enabled my mic and said "thats not a bug, thats a feature. I didn't want to enter that field again and again when I adding multiple rows and made it persistent." and you know what? They liked the idea! They requested to add that bug to two more fields. I was just joking and my "this is not bug, its a feature" moment actually turned my bug into a feature. Instead of fixing it, I'm creating more of this bug. LOL!

Drove my colleague mad with console.log("you cant find me"), that stare he gave me across the room when his stuck with a bug. made me lol in the office literally

!rant

How easy is to get fired from a Dev job? 😛 I'm afraid of that happening every time I introduce a bug lol

I can’t help but wonder who programmed the firmware for this.

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

Go home iOS, You're drunk

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

I just remembered a weird fix in a bug, some old developer hide the error message using css, placing it in a div then just used display none. LOL

Lol I'm starting to learn the bug-life

TLDR: Walmart bug 😠

As a dev, I know that bugs happen. But as a dev from a small shop that has many clients and very few devs, I absolutely despise when a large company with many devs has a bug in a product that millions of people use.

WalmartContacts.com. How many devs do they have? And how many dedicated to this 1 product? How many people in QA? (how many on DevRant... lol)
And yet I can't even place an order using their reorder functionality. Seems like they should have this shit down. Seems like they should have all their regression testing ducks in a row. Seems like they should at least show some kind of error message so the user knows what's going on. Instead, no message at all, just the final checkout payment page reloading when I submit leaving me to wonder if my card has been charged or not.

Ask Google Assistant "What's the second tallest building in the world?"

Maybe it's a bug or something
Or it just loves the tallest building lol

lol nvidia-bug-report.sh

it collected an xorg log that is not the current one.

For some reason, my arch openbox logs to $HOME/.local/share/xorg/Xorg.0.log.

What a goddamn trainwreck. I'm not necessarily saying it's nvidia's fault. But it is a trainwreck.

Reminds me of some of our testers, who raises similar bugs, if they don't get any issues in regression testing.

Speaking of JS gotchas. Why is there a null and undefined? I guess undefined doesn't exist, but null is it exists, but is null? Had a bug related to this. I was checking for null, but undefined was getting in there even though I defined the variable as null beforehand. All I can guess is some assignment shoved undefined in there. But that just doesn't make sense to me. So an existing variable can be undefined as well? lol

I am glad this is not my primary language for heavy lifting. Fuck this noise.

I was going to do this as a rant. But it turned into an ironic joke. I am adding an old meme, but it checks out for accuracy.

First time me ranting about PHP.

First time. I still really like the language.

But what the fuck.
I am debugging, I narrowed down bug to my validator.
I played with php console and debugger and narrowed down to that one offending line.

Narrowing down to smaller and smaller examples when it dosent work, confusion and tension grows in me.

And then it hit me.
Confusion got to apogeum.

Anyone, if you know the anwser, please tell me.
WHAT THE FUCK?

maybe thats task for stack overflow? Hrm...
No, I dont have time to explicitly tell what I tried to google and spend 4 hours to have all checkmarks ticked before asking lol

So I got a job and on the first day I was giving a task to fix a bug which they said it was urgent that the software is been used by the financial department, so if I don't get it fixed soonest they would be loosing money.

I completely don't know how the software works, so I thought they would give me some time to get familiar with the code base but fu*k I gat to fix this if not they would See me as a person who does not know his stuff.

Some minute later, the CTO messaged me asking me how I introduced the bug in the first place, I was like I have not even cloned the repo, I have not pushed any code lol. At that point I know I'm gonna be so f**ked in this job .

So after sometime I fixed it but I had to get permission from the lady that manages the database because I was not given access and I need to update a field name in a table for everything to work well. I asked the lady to help update the field since she is the only one that has access to it and its urgent and every body is waiting for me. She told me to wait for 1hr and remind her that she's busy right now, after some hrs I reminded her but she kept telling me she will update it later.

Nobody wants to hear that I was not the one delaying the fix, so since I can push some code to the report and it's get deployed, I wrote a script to update the field and I removed the code later. With that done the fix was live and everybody was happy!

The next day, the lady came to me and was like I tried to update the field when I went home but it has already been update but I don't know why. I told her I don't know too :p😃

Fixed a bug today that I created over a year ago.
It made a machine start doing really fucked up things like running motors when it shouldn't. My boss, an expert on the system and the code, gave me some ideas to check. He couldn't understand why it was doing it either. So I started checking things and comparing to another piece of code that does similar things. I finally found a place where I had used a really sketchy pointer. I even knew it was sketchy at the time and put a ? mark in the comments next to the line of code. I changed the code to match another system that explicitly creates the object. Then I started testing the system and boom everything is working as it should. I talked to my boss and explained everything. He said it was an easy mistake to make. Internally I was saying, "But I don't make easy mistakes. I make hard mistakes!" LOL

Got to walk away from work for the weekend knowing that my other code is a lot more solid than I was thinking earlier this week. I was starting to second guess what could possibly cause this problem and thinking there could be culprits everywhere. Boss was happy problem was solved as he is going to be showing off the system I am working on in a month at a show.

I hate leaving work late, stuck on a bug and 10 miles down the road heading home, figure out a solution and then argue with myself do I go back and fix it now with no distractions or write it down ... then in the morning I’ll do it but bear with distractions... or not write it down .. hope I remember and then do it in the morning

But I’ll probably get distracted.: forget .. then remember after everyone leaves and implement it tomorrow night .. lol

So we have this project that we are hosting on our testing server for presentation purposes ( already provisioning prod server ).

Our boss was presenting it to investors and my superior committed a bug there and was asking me help to figure out how to fix it (yeah.. he doesn't know how to checkout last commits in git... fml), and I realised the presentation might still be going on... so I asked: isn't boss showing it to investors?

superior: lol, idk maybe.

me: right... ( I proceed to roll back changes ) bye, have a good lunch.

And here I am having lunch considering my life choices.

Fixes 1 bug, creates 3 more-__-

FML. Lol

Asked junior how did they find out the location of the bug, got a copy-paste reply from chatgpt explaining the code.

AI is allowed at work, and idgaf if they use it or not. But the whole situation, including the fact of not just replying “I used it to understand/solve the problem”, makes me wonder if SE as we know will end not because AI will replace us, but because AI will make all the fears people had with stack overflow, come true, but worse.

At least with stack overflow people needed to be able to form the question or to search on the website lol.

Started work in the morning, after a couple of hours was 90% done and would be clicking the checkbox on trello that task is completed.
Lol.
Found a bug.
OK, debugging time.
Spend an hour on trying to fix the simplest bug ever,( php was creating a file that had the contents but the wrong name)
At this point I was starting to get super pissed of cuz in 30min I need to go meet up with some friends.

LOL ok, fuck this shit, I don't want to do this anymore.
Made the bug into a feature that now you can have multiple authority(admin) accounts.

My teamm8 was like lol ok, we didint really need this but it will be useful so nice job.

👏GREAT MORNING:))))

A CPU intensive and pointless program to determine the font of text in a picture.

I didn't get past downloading every single google font. TTF drawing bug crushed my dreams. Will upload files to github if you want to see the mess

PS wanted to write it in Python lol

Starts search and replace.
Trys to replace a type in the whole Project.

Syntax Check: lol no, apparently everything is broken now, good job

(literally my whole project was marked red)
Reverts changes
(project still marked red)

Syntax Check: lol what? Your code already looked like shit before, won't let you compile this.

It was a bug which breaks the syntax check after big replace requests. Had to start a new project and copy my code step for step, so it didn't break again. However I've forgotten to replace the type before I copy...

Another story regarding this shit:
Renames Variable
IDE: oh, let me help you by replacing all old var names with the new one
Agrees
IDE: oh shoot, didn't know it could break things
Wants to revert
IDE: did you think I would go through this mess again?! Do it yourself!

That LOL feeling when incompetent backend wants you to fix their bug on the frontend!

How about NO!?

And why tf I know more about how backend works on this system than devs that are actually working on it???

Spent 1-2h (or it felt like so) fixing this one bug today. I'm still mad about it LoL. I knew exactly what was the problem, just didn't know where it was, and went over that piece of code time and time again and didn't see it... UGH THE FRUSTRATION. When I found the error I wanted to get inside a hole and die of how stupid a mistake it was and how it had been staring at me in the face, mocking me for being so dumb. ARGH!

Do you guys still see the relevance of using code freezing instead of just properly managing versions, repositories and branches in a cyclical manner, given how advanced software practices and tools are supposed to be?

To give some context, the company I work for uses the complete trash project management practice of asking teams to work on a sprint basis, but there is still a quarterly milestone and code freeze to commit to and it's where shit hits the fan.

Development teams rush features at the end of the quarter because they had to commit at the very least to a 6 months in advance planning (lol?) and turns out, not being able to design and investigate properly a feature combined with inflexible timelines has high chances to fail. So in the end, features are half-assed and QA has barely any time to test it out thoroughly. Anyways, by the time QA raises some concerns about a few major bugs, it's already code freeze time. But it's cool, we will just include these bug fixes and some new features in the following patches. Some real good symver, mate!

Of course, it sure does not help that teams stopped using submodules because git is too hard apparently, so we are stuck with +10Gb piece of trash monolithic repository and it's hell to manage, especially when fuckfaces merges untested code on the main branches. I can't blame Devops for ragequitting if they do.

To me, it's just some management bullshit and the whole process, IMO, belongs to fucking trash along with a few project managers... but I could always be wrong given my limited insight.

Anyways, I just wanted to discuss this subject because so far I cannot see code freezing being anything else than an outdated waterfall practice to appease investors and high management on timelines.

Lol. In the years that `const` and `let` have been in Javascript, not once have they ever helped me read the code better or caught a bug. They have not helped me understand anyone else's code, nor have they really helped convey any sort of meaning for other developers that I have heard.

Usually the rule is, const first, then change it to let if you need to. It adds nothing.

All this gold plating is weighing things down.

Never fixed? lol.
Maybe I took hell of a time, maybe I've ignored it for long but at least I've always fixed bug which I came across and will fix if I come across any new (as there might be many hidden :P ).
As I mostly work on eCom and integrations, it's way too risky keeping bug.
Cheers!!

Came across a bug in our code today where we were trying to store to large of a value in a database field. Turns out we intentionally set the value to a huge number just so that we could tell another process farther down the line that the object containing it needed to be deleted...Really??? Lol

When you don't find the bug lol

A: oh hey my commit is not in the master branch...
A: *seeing bunch of commit deleted activity in bitbucket by B
A: Lol B deleted commits in master branch
B: Wait, what?! I know I have rebased my branch.. but never have I rebased anything in the master branch.. how can this be *intense breathing
B: Are you sure you have pushed yours to master?
A: Sure I've rebased, squashed, and rbt landed my work to master, here look my local master has my commit
CTO: wait what? Is this related to this bug we have in production just now? Please don't panic, let us resolve it

Turns out rbt land just squash your commit to your local master branch and they thus A have not pushed it to the remote. And the bunch of commit deleted activity were bitbucket not informing from which branch the activity was happening. Almost gave us heart attack.

WOW! WENDY! YOU ARE THE BEST TECH SUPPORT EVER!
So on my assignment i see a glitch in the course where i cannot get access to the last button.
i contact tech support
me: Hello *explains the situation*
maddie: *please wait i will check on that*
maddie: *are you logged in?*
me: OF COURSE I AM LOGGED IN THEN HOW WOULD I BE TALKING TO U???
maddie: will it be okay if i impersonate as you?
me: w h a t
me: *session timed out* JUST WOW!
next support: > Wendy
me: explains the whole situation and sends screenshot
Wendy: ah i see. wait on that a second
me: *waits ONE HOUR*
Wendy: Please clear your cache and cookies.

what does cache and cookies have to do with a html course bug that blocks access to the last button...
well i guess you can say im stuck in the mud
i can't get out and im stranded i miss maddie the tech support because i got timed out and she was about to spill the real tea but dummy wendy popped up and is talking about cache and cookies LOL

So we now do continuous deployment to a development environment. Once a PR gets merged it gets deployed there. We then have to manually deploy to staging every so often.

We did this because QA wined that the Dev was constantly breaking Staging, when we contentiously deployed to that.

So now we have a staging instance that is always behind. Which isn't big deal, because its supposed to be stable right?

Well now the stupid fucking QA team is always making mountains of tickets and noise for stuff that is already fixed on the development instance.

Fucking shit that they message me about, or have to call me about. "Hey let me tell me about this thing I found." And then I'm like I already fixed that thing last week.

So it seems to be wasting everyone time to not just CDCI into staging. I have to wait weeks to retest my bugs on staging. To make sure that some other stupid fuckeshir on my team didn't undo or break my fucking fix. Shit keeps getting kicked out of QA Review. Fuck. lol.

Then there like I can update the thing on the database through the front end tool. Well tough shit buddy, your going to have to wait a week unti next staging deployment to see if that tool is fixed. This is your fault for fucking up our pure CDCI with your ideas. Now everything takes longer for everyody.

To sum things up. Some dumb bug makes it into the manual staging deployment and gets fixed an hour later. Doesn't get deployed until next fucking week. QA makes a bunch of noise about it. A thing that is fixed and in the pipe-line.

Also a dumb fucking bug will make it into staging, lets say a critical front-end back office tool that needs to send numbers to the backend, they send a fucking string instead of a number and break it. Now we have to redeploy the tool and backend to staging because there related. Then if we deploy backend we have to deploy the client facing site too. since it also depends on backend.
Its a fucking hassle.

Now if the fucking DevOps guy could do his job, and make a god-damn deploy button for all the staging servers that would be great.

so which job pays for improving an existing thing and not being a tool for your boss's whims? I guess the answer is a house-helper cause devs for sure aren't paid for clearing a shitty codebase.

i recently made a commit because i was do angry at the issue . this was the message "fixing a stupid bug from previous owner". it got squashed but i still felt better lol.
there are a few classes in our codebase that are so infuriating that i want to run a bulldozer on them and build from the ground up. multiple bugs ate caused from them, but we simply ignore because we know that our monkey iq QA won't be able to replicate them and we won't be answerable.
I hate to be in this position. the mgmt won't be giving me time to fix this shit but rather want us to add 2k more features to this Frankensteins monster.

adding to this, I can't get my satisfaction creating some hobby project and solving issues in that coz A) it won't be as massive as my company proj and B I won't be interested in building a dimmy project for a longer time, which does not attract any actual users :/

They're calling me the exterminator at work. I would take that as a compliment if it hadn't been me who introduced the bugs.

dude why there so many dum fuck in this industry like people who just graduated , and don't know shit about tech or anything but flex and complain about shit just can accept that they don't know any shit this many years fucking noobs nothing like why are they , this don't deserve jobs just make bug and always call for help like why cant they figure out their shit, its just cant just spoon feed they every time, like i dont know what happens to this people after or they just survives in it? just tired of getting my ass on whenever they suck dude they dont know how to commit git lol , but never accepts , i am not talking about one person its like a species now , they dont even try to learn even tho they get jobs for no way , itrsucks

1. More experience in programming to reach the next level!
2. A job in the USA!
3. Will leave it for a complicated bug to wish it be fixed lol