Sometimes I wish people were Linux processes so that I could kill them for being so fucking useless.

Ruined my weekend for no reason. Get a fucking life.

Craziest bug, not so much in the sense of what it was (although it was itself wacky too), but in what I went through to fix it.

The year was 1986. I was finishing up coding on a C64 demo that I had promised would be out on a specific weekend. I had invented a new demo effect for it, which was pretty much the thing we all tried to do back then because it would guarantee a modicum of "fame", and we were all hyper-ego driven back then :) So, I knew I wanted to have it perfect when people saw it, to maximize impressiveness!

The problem was that I had this ONE little pixel in the corner of the screen that would cycle through colors as the effect proceeded. A pixel totally apart from the effect itself. A pixel that should have been totally inactive the entire time as part of a black background.

A pixel that REALLY pissed me off because it ruined the utter perfection otherwise on display, and I just couldn't have that!

Now, back then, all demos were coded in straight Assembly. If you've ever done anything of even mild complexity in Assembly, then you know how much of a PITA it can be to find bugs sometimes.

This one was no exception.

This happened on a Friday, and like I said, I promised it for the weekend. Thus began my 53 hours of hell, which to this day is still the single longest stretch of time straight that I've stayed awake.

Yes, I spent literally over 2+ days, sitting in front of my computer, really only ever taking bio breaks and getting snacks (pretty sure I didn't even shower)... all to get one damn pixel to obey me. I would conquer that f'ing pixel even if it killed me in the process!

And, eventually, I did fix it. The problem?

An 'i' instead of an 'l'. I shit you not!

After all these years I really don't remember the details, except for the big one that sticks in my mind, that I had an 'i' character in some line of code where an 'l' should have been. I just kept missing it, over and over and over again. I mean, I kinda understand after many hours, your brain turns to mush. and you make more mistakes, so I get missing it after a while... but missing it early on when I was still fresh just blows my mind.

As I recall, I finally uploaded the demo to the distro sight at around 11:30pm, so at least I made my deadline before practically dropping dead in bed (and then having to get up for school the next morning- D'oh!). And it WAS a pretty impressive demo... though I never did get the fame I expected from it (most likely because it didn't get distributed far and wide enough).

And that's the story of what I'd say was my craziest bug ever, the one that probably came closest to killing me :)

So I promised myself some down time this weekend since I usually end up working all night and in a blink my weekend is over. I also declined going out for better 'relaxation'. Here's how it's going so far...

>Gets home. Hmmm what should I do I can do anything! *thinking*
>Pours a stiff whiskey
>Trys watching something as well as playing a game, gets bored of each and abandons them.
>Opens a dev newsletter
>*blinks*
>Realizes I'm elbow deep in some repo... starting to feel inspired.
>Decides to code something "fun"
>Uses "Well as long as I'm not *working*" to justify his addiction.

I'm really not sure what I did for fun before I started coding. It ruined things by being so damn enjoyable and ultimatley many other things became well... less fun.

This is what addiction looks like.

Am I unlucky or perhaps in the wrong place if I’m always stressed as a junior dev coz too much pressure and they give you super tight deadlines and do languages that you never done before?

Or is what most people go through when they were juniors

my employer moved our company to the UAE. we were in a dying and collapsing country. Now we are in a stable and great place to be. We are even paid about double the average salary here.

But...

He now seems to believe we all owe him. so every time a long weekend / holiday comes up he tells us you have a week to deliver X or ur career will be in danger.

I have been living the past 2 months with those continuous threats. In utter anxiety over possibly losing a job i love because of him.

Before the weekend started he tagged us and said you have 48 hours to fix X. and here i am on a weekend working 10 hours a day as a result.

But i have been pulling 2 day shifts in one day. spending nights, weekends and holidays working on the project he wants fixed. and he still seems very angry at me and my team all the time. very unappreciative. and just very hurtful.

im just scared shitless because i have a family i support and have Just moved to a new country and paid thousands of dollars to rent and furnish my new place. If i get fired now i would be ruined...

Weekend ruined supporting legacy and poorly designed services coupled with poor architecture.

But "no project bandwidth" to refactor said services.

5 hours of data loss should now hopefully inspire a backlog re-shuffle.