TLDR : I left a company which doesn't understand the concept of email id and passwords.

Me (trying to login to the alumni website) *no register user option*

Customer support - you've to click on forgot password to create an account.
Me - Wonderful

*clicks on reset password*
*enters employee id, name, email, father's name, DOB, date of joining , date of leaving, current city because apparently if I just enter my employee id it is as if they never knew me. Sigh*
*your password will be sent to your email id*

Me - okay. *waits for two weeks because I assumed someone will manually go and create my account and email me, considering the state of system. *

After two weeks,

Me - I still haven't received my password on email after I created my account. Can you please check?

After one week,

Customer support - you need to click on forget password if you forgot your password.

Me - *inventing new curse words* I have not forgot my password, I never received it in the first place!

After one week,
Customer support - yes you'll receive your password on your email id.

Me - *runs out of curse words* seriously dude?
* proceeds to reset password*
System - your password has been reset. Your new password will be sent to your email id. *apparently anyone can reset passwords if you have the employee id, which is an integer*

After a week

Me - Am I going to ever receive the password? I've tried generating passwords, resetting my password. I never get my passwords. What should I do!!

Customer support - yes you need to click on Forgot password.

Me - are you fucking kidding me!!!
You fuckers need to be fired and replaced by a FAQ page which has no question and just a single answer, because a peanut has higher IQ than you. For any questions you may have, just reset password. Goddammit idiots!
Also, which email id are you sending my passwords to?

Customer support - myname@oldcompany.com

Me - you do realize that this is the alumni website for the company. Alumni means ex members.
Being ex members, you can assume we don't have access to our company email ids obviously?

Customer support - yes.

Me - how am I supposed to get the password using my old email id then?

Customer support - you need to click on forgot password option.

I think I should probably move to the Himalayas for my anger management issues. Plus it'll be probably easier to throw idiots off a mountain.

My code *may* have anger management issues.

Got annoyed by hitting f11 instead of f12.
("step into" versus "go to definition").
Solved the problem :)

Wrote my friend Sam a letter when I was still working in support. I think it still holds up today.

---

Dear Sam,

I understand that you will join us in our overseas office. Congratulations on landing that job. It’s good steady work. I’ve been doing it for the last ten years.

Your still young so maybe I can give you some little wisdom that will help you in your working years to come.

Let me begin by shedding some light on phone calls.

I try. I really do try Sam. But it is getting so hard for me to hold back the rage that builds up during certain phone calls. Especially the ‘Sorry, I just don’t know anything about computers! -giggle-’ ones.

Those are the times that I have no access to what they see. I’ve no team-viewer, can not take over that screen in any other way. And why-oh-why can I not take over that terminal session dear Sam? It’s because the caller can not double-click an icon or find a terminal session number.

And what is the reason for this? Because they ‘just don’t know anything about computers! -giggle-’. This is a sort of get-out-of-jail-free card. Beware of these callers Sam.

There is nothing so nerve-wrecking then finding yourself at the mercy of people describing Internet Explorer (do not even get me started) as ‘the big ‘E’, if they use Chrome for their webmail then they most likely will say ‘Mail’ if they mean Chrome. There is no logic Sam. That is just the way these people work.

They will suck all enjoyment out of your work. They will make you want to hunt them down in dark office hallways and show them your tears Sam. Because cry you will.

Sure, I understand that not everyone can be tech savvy. Why, if everyone would be, where would that leave us? No. I love the technologically challenged. They put the fiber in my internet. They make me LOL for real. After the initial anger subsides anyway.

But just below that well-willing folk, on the other side of that border… there they dwell: Management.

Nice cars, suits and iphones Sam. First thing a new manager will require is a brand spanking new business-card. It will hold his/her new title. Then an iphone or overpriced android model will follow suit.

Then they will barge into your office, holding it like it’s the next best thing since sliced bread.

Any manager will automatically assume that you will drop anything you are doing at the present moment to acknowledge the presence of greatness. Failing to do so will result in awkward yet fulfilling situations. I recommend that you do not take your hands of the keyboard and give only the slightest of nods after 5 minutes of complete silence and glaring.

Well… you feel the glare. You do not glare yourself. You do not break eye-contact with the monitor. It does not even matter if you are typing for real or not. I once clicked away happily for 5 minutes. I just typed ‘he is still there’ over and over again. Do not break down Sam. This moment will decide your relationship with this individual.

After the nod there will be a flood of words aimed in your general direction. You can disregard anything that is said. It boils down to ‘can not operate device’.

You then take the device from this person and put it next to you on your desk. You’ll ask the name of this simpleton, write it down on a sticky-note, slap that on the phone. Then you’ll write a random date in the not so near future on another sticky and hand that to the bewildered person in front of you.

It will usually utter some incoherent words about ‘needing, time or but’ (I find that ‘but’is a word they like. They tend to use it three or four times consecutive before you usher them through the door).

Now you’ve won Sam. Well… not really. But it will feel good, I can guarantee that.

This must do for now. A new suit is glaring at me for the last five minutes.

Felt good to do something productive with this time.

Take care,

Baltasar

P.s. I just noticed that there is some foam around his mouth. So if you encounter this, don’t worry: it seems to be perfectly normal.

In the school we were using slow PCs for learning MS Office things. Every single step we did took ages. There were one guy who was an informatics antitalent: he never were able to work fluently with any electric machine from a microwave to anything smarter. In addition he was a semi-pro athlete and he had some kind of anger management issues, sometimes yelled to the teacher after a bad mark or with us when we lost a in-school soccer match. You know, he was that competitive guy.
One time on computer science class he was very focused. He tried to follow every steps precisly and his machine seemed faster than as usual. He felt like he broke some kind of wall which was between he and the machine.
When we had a break and he went out we tought that we should make a prank. We made a fullscreen screenshot from the desktop and set it as the wallpaper, then killed explorer.exe. As a result the icons and the start menu was only on the screen by the wallpaper.
When he came back he said that there were some bad news from some of the sport event he wanted to go, so he was angry. But then... You know the gif when the guy first hit the side of the screen multiple times then throws out the machine? Yeah, we saw that in real life, but not in that office. First he was just clicking everywhere, we just watched how his face just transforming. Then he started to talk just in himself as the machine could understand. After two minutes he just yelled to the machine why did it freeze, but the last drop was when the teacher said: You'll have to send me your work and it will be marked. In this moment he was just roard a huge and droped the CRT out of the window from the second floor. Luckily the window was facing to a brushy part of the garden so no one was there. He just standed there, looked out to the CRT sitting in a brush for a while, then he turned to the teacher as "Mr, I think something is wrong with my machine"

The following meeting occurred at a client between a recently added client PM and our team, we'll call her Shrilldesi, previously from one of the main consulting vendors.

*Meeting begins after 15 minutes of bullshitting, waiting for people to file in*
Shrilldesi: "Ok everyone, let's get started
TeamMember: "We're still waiting for Z and W, not sure why they're late."
SD: "We can start there. It was decided had to lay off Z and W, because we didn't have enough work."
Moi: "Wait, what. Who made that decision? Why weren't we consulted on this? We have another project starting next week that they were needed for. They just delivered the entire public facing rewrite, why would we let them go?!"
SD: "It was decided by myself, pajeet, and venkata looking at the backlog. Not enough work, week gap."
Moi: "This is going to hurt our ability to deliver the next phase. When are we going to start interviewing new people, the project begins next week?"
SD: "We will interview new resources as needed."
Moi: "Who is we? And 'as needed' is yesterday, or realistically several weeks ago as the. project. starts. next. week. Also, we're obligated by federal law to bring back anyone we lay off before we hire anyone else for the same position."
SD: "Interviews will be done by myself, Mohd, and Pajeet."
Moi: "...can I point out that there's only one modestly technical person in that group, they're an admin, and none of them are from this team? How do you conduct an engineering interview without any engineers?"
SD: "That does not matter, I have watched enough to be able to ask your questions."
Moi: *anger intensifies* "I have to respectfully disagree. I don't feel it's appropriate to cut us out of the process of interviewing our own team members."
SD: "It is decided, we will take care of it, let us move on. Next, we need to find work for the Manasa, she doesn't have anything to do."
Moi: *sharpens baseball bat* "...shouldn't we just fire her then?"
SD: "Oh that is so mean, why would we fire her? We were thinking she might be able to do some of my project management work."
Moi: *sharpening intensifies* "You do realize it's a violation of H1-B statutes for someone to be employed in work other than what is stated on their contract, and Project Managers are specifically listed as not specialized skillsets per federal law."
SD: *ignores question* "We also need to find work for the offshore team, they don't have enough to do. Please find them work for the next period."
Moi: *checks how long the wait period is for ar-15s*
SD: "We also have a new person rolling onto our team, he comes from the xyz team, Dikshit *gestures to person we all figured was lost*. He will be handling our front end development."
Moi: *seething hatred* "WE JUST LET TWO EXCELLENT FRONT END DEVELOPERS GO. WE DO NOT NEED DIKSHIT."
SD: "Please calm down. We will be replacing the other two shortly, there is no problem."
Moi: "Have you heard nothing I've said? Did you even run this by legal and HR? Why did we let them go in the first place? Why do we even need Dikshit?!"
SD: "I said it before, please listen. There is not enough work for them. Dikshit will do front end. What is unclear?"

Note: There's not really any dramatization here. It's almost verbatim what happened. Eventually, the next project was cancelled, they incrementally rolled the rest of the local team off. They then had the cojones to express aghast anger when I notified them I would not be renewing my contract, and open hatred when I explained to them I was not a slave, and I refused to be a bag holder for the inevitable failure of a project without any chance of success. I don't really care what happened after that, they can all burn in their own little nepotistic shitshow of perpetual failure.

!!rant
!!ANGER

Micromanager: "Hey, Root!

Since you're back, and still not feeling well, we have an easy ticket for you: Rewrite the slack integration gem! Oh, you don't have to re-implement all of it, just make sure it all works the same way it does now. That bitch you worked with once over a year ago who kept throwing you under the bus to management and stealing credit for your work? Yeah, she wrote the original code like four years ago. It's perfect, so don't touch it. but she can fill you in on all the details you need and get you up to speed on how to test it.

But yep! It should be simple. and I just knew you would love this ticket, so I saved it just for you. Nice and quick, too, to get you an easy win.

You know, since you have to repair your reputation with product. and management. and the execs. and the rest of the team. and me. Yeah, product doesn't trust you so they don't want to give you any tickets. They just can't trust you to get them out and have them work. So you have a lot of hard work to do."

Spoiler: The bus-thrower wasn't much help. (Surprise.)
Spoiler: The ticket was already in my backlog -- one of a grand total of two tickets.
Spoiler: I don't find the ticket fun. Maybe if I was to write the entire implementation with a nice DSL? but no, "don't touch the perfect code." Fuck you.
Spoiler: It isn't going to be nice or quick. But, she (micromanager) is looking to lose me, so that really is an easy win. for her.

And. just. argh. fuck you. i've been exhausted and dying for well over a year, but you've kept ignoring that (and still are, despite me providing goddamn legal forms from fucking doctors stating it in plain fucking english, which you also fucking ignore), and you just keep piling on the work and demanding the ridiculous of me despite it. Yeah I can pull it off sometimes. No, I really shouldn't, and I'm surprised I can. (also, "Time off? What, and lower your productivity even more? ____ doesn't even take vacations. And how are you doing on that ticket?") And no, none of my tickets have ever had any fucking problems. Not even when there are upstream service outages. Not. a. single. fucking. one. Ever. And the only things I've ever missed were things that bloody product never put in the fucking ticket, so fuck you with your "repair your reputation" bullshit.

god, i fuckiNG HATE THESESTUPOID ANWETLJAF SAJEWTKW BITCHFACEDUCKFUCKERS

Why the FUCK am I still fucking working here?
Right, because I've been burned out and dying so much I can't pass a fucking interview so I can fucking leave.

jasdkl;fk

ugh. Anyway. If you ever find yourself starting work at a Cali fintech company whose internal mascot is a very fine duck? Just run. I absolutely guarantee you will be miserable.

When I opened my digital agency it was me and my wife as developers, I had no savings and I needed to get long contracts ASAP which luckily I did straight away.

Lovely client, had worked for them before as a consultant so i thought it would be a breeze. Let's just say the project should've been named "Naivete, Scope Creep and Anger: The revenge".

What happened is that when this project was poised to end I naively thought I would be able to close the job, so I started looking for a new full time consultancy gig and found one where I could work from home, and agreed a starting date.

Well, the previous job didn't end because of flaws in my contract the client exploited, leaving me locked in and working full time, for free, for basically as long as he wanted (I learned a lot the hard way at that time) and I had already started the new agreed job. This meant I was now working 2 full time shifts, 16 hours per day.

Then, two support contracts of 2 hours per day were activated, bringing my work load to 20 hours/day.

I did this for 4 months.

The first job was supposed to last one month, and I was locked into it, all others had no end in sight which is a good thing as a freelancer, but not when you are locked into a full time one already. I could've easily done one 8 hours shift and two 2 hours jobs per day, but adding another 8 hours on top of it was insanity.

So I was working 10 hours, and sleeping 2. I had no weekends, didn't know if it was day or night anymore, I was locked in my room, coding like a mad man, making the best out of a terrible situation, but I was mentally destroyed.

I was waking up at 10am, working until 8pm, sleeping 2 hours until 10pm, working until 8am, sleeping 2 hours until 10am, and so on. Kudos to my wife for dealing with account and project management and administration responsibilities while also helping me with small pieces of code along the way, couldn't have survived without the massive amount of understanding she offered.

In the end:

- I forcefully closed the messed up contract job and sent all the work done to another digital agency I met along the way, very competent people, as I still cared about the project.

- I missed a deadline on my other full time contract by 2 days, meaning they missed a presentation for Adobe, of all people, and I lost the job

- The other two support contracts were finished successfully, but as my replies were taking too long they decided not to work with us anymore.

So I lost 4 important clients in the span of 4 months. After that I took a break of one month, slept my troubles away, and looked for a single consultancy full time contract, finding it soon after, and decided I wouldn't have my own clients for a good while.

3 years since then, I still don't have the willpower or the resources to deal with clients of my own and I'm happily trudging along as a consultant, while still having middle of the night nightmare flashbacks to that time.

Every time you feel anger, instead of explosion you write a new rant and make people smile.

=> devRant is behaviouristic therapy.

Dear Atlassian Support,

In my life I had a lot of experiences...

But your software manages to replace all these experiences with a unique feeling of depression, hatred, anger... Only negative emotions.

Not once have I said anything good about your software - not once in > 5 years.

Whenever your chum bucket of mismanagement and misanthropy stops working, it's never the fault of the end user, the administrator or someone else.

It's entirely your fault.

Fucked up upgrades, lack of documentation, catastrophic handling of logging, lack of support of current database systems, lack of proper migration and clean up of plugins, ....

I could go on. But it's really just and endless tirade.

I wish I could stop management for even giving you money for the pile of poo you call software, but sadly they don't listen.

But there's hope on the horizon.

Thanks for making people go cloud only.

No one wants that.

It would mean entrusting that pile of poo to the craptastic hands of your irresponsible people.

No one really wants that.

Not even management who blindly paid the license fees all the times.

Thank you for your cloud only movement.

Maybe we can finally find an alternative and I can finally start a therapy for the PTSD I have thx to your software.

The exit interview with an ex boss.

While working there, we had regular meetings every other week. Discussing current work, equipment requests, technology, sometimes office politics. At some point we discussed that our team was moved to an open-plan office and how I regarded this as detrimental to our productivity and satisfaction. Of course we sometimes had different opinions, but it was an amicable atmosphere. My boss also always carried a personal organizer and sometimes wrote notes during these meetings.

Later I resigned. Him becoming more and more abusive was a major reason, and I think he knew he had crossed a line. So the day of the exit interview came...

In a professional setting, you'd thank each other for the good collaboration. Maybe laugh about one or two points from the past. And then wish each other success for the future and say farewell.

Not there. Not with him in the exit interview.

Instead, he apparently went through a list in his personal organizer. A list of every single thing we ever disagreed at. And roasted me for each. single. item. "Back when you said x... you can't really say it like that". Or "remember that time when you were against open-plan offices? Let me tell you, that's just your opinion. There are no actual arguments against them, it's just a matter of taste". And that went on and on and on. Like a final reckoning. Like he needed to get revenge. I hope that carnage made him happy, because it made *me* happy to have had resigned.

And it was fucking unprofessinal, because this is the management equivalent of stomping your foot in rage and anger, shouting "no no nooo I'm right! I! am! Riiiiiiight! *stomp*".

1. Manage my time better.
2. Find motivation to wake up and go to work.
3. Fake more smiles.
4. Kick ass hole (L)users in the throat when they piss me off...
5. Attend anger management.
6. Stop making shit lists.

In all honestly I need to dedicate more time to my personal clients and stop allowing my primary job’s frustration to drain my motivation to take care of their needs. It’s not fair to them that I chose the life I have. Find myself and attempt to love myself again. Create more time to focus on my health and goals. Surround myself with people that have goals and want to better their life. Find someone to share life with.

Then, with my luck; throw it all away and repeat these steps like a broken record.

I was asked to fix a critical issue which had high visibility among the higher ups and were blocking QA from testing.

My dev lead (who was more like a dev manager) was having one of his insecure moments of “I need to get credit for helping fix this”, probably because he steals the oxygen from those who actually deserve to be alive and he knows he should be fired, slowly...over a BBQ.

For the next few days, I was bombarded with requests for status updates. Idea after idea of what I could do to fix the issue was hurled at me when all I needed was time to make the fix.

Dev Lead: “Dev X says he knows what the problem is and it’s a simple code fix and should be quick.” (Dev X is in the room as well)

Me: “Tell me, have you actually looked into the issue? Then you know that there are several race conditions causing this issue and the error only manifests itself during a Jenkins build and not locally. In order to know if you’ve fixed it, you have to run the Jenkins job each time which is a lengthy process.”

Dev X: “I don’t know how to access Jenkins.”

And so it continued. Just so you know, I’ve worked at controlling my anger over the years, usually triggered by asinine comments and decisions. I trained for many years with Buddhist monks atop remote mountain ranges, meditated for days under waterfalls, contemplated life in solitude as I crossed the desert, and spent many phone calls talking to Microsoft enterprise support while smiling.

But the next day, I lost my shit.

I had been working out quite a bit too so I could have probably flipped around ten large tables before I got tired. And I’m talking long tables you’d need two people to move.

For context, unresolved comments in our pull request process block the ability to merge. My code was ready and I had two other devs review and approve my code already, but my dev lead, who has never seen the code base, gave up trying to learn how to build the app, and hasn’t coded in years, decided to comment on my pull request that upper management has been waiting on and that he himself has been hounding me about.

Two stood out to me. I read them slowly.

“I think you should name this unit test better” (That unit test existed before my PR)

“This function was deleted and moved to this other file, just so people know”

A devil greeted me when I entered hell. He was quite understanding. It turns out he was also a dev.

My boss said ignore CI-CD let's just diploy it as it is localhost.

First off murphy is a bitch. Week started off good, nothing bad happening then friday night came and i get an email about a site being down. Ok check it out real quick, cert is expired. No real big deal just a 20 minute fix, didn't bother me that i didn't get an expiry alert. Now is where murphy decided to be the biggest fucking bucktoothed cocksucker, generate a csr for a wildcard domain using an existing key and sent it off when i get it back the private key doesn't match the cert. Again ok maybe i fucked up, generate a selfsigned cert no fucking problem. Contact support to see if they have an idea. Oh now is when it gets fun, the fucking dumbass preceded to tell me how i didn't know what i was doing and how i just had to generate a csr and private key at the same time after i explained to the bastard that I've already tested it with a selfsigned cert. (How does this fucker have a job) By now apparently i was pissed off enough to scare murphy's pansy ass away cause i told the fucker to refund my money, got a list of 30 subdomains and setup letsencrypt on it. Now the part on this that is fucking hilarious is that it took me damn near 24 hours to be called a fucking idiot from a guy that doesn't know his ass between a hole in the fucking ground and 30 minutes of being pissed off more than i have been since i took anger management classes in the 9th grade to say fuck it and switch.

Coding has impacted my life as a way to quiet and focus my mind.

(Also, as another positive side effect I learnt a great deal about frustration and anger management along the way. :D)

Cooking.

Murderous cooking.

Anger management cooking.

Joke aside, I mostly have no clue what I'm doing.

Cooking and gardening (sadly no longer a possibility) are two thing where my brain goes out and I just do it.

It has happened more than once that this has failed... But most of the time it goes surprisingly well.

I'm absolutely not an accurate or refined cook.

I hate cutting stuff "even sized"… I hate when it looks perfect. I hate swiping off drops of the plate so it looks more refined....

So yeah, it might look like puke. But it's tasty. XD

The year was 2006. During the first half of my career, I use to work in the NOC. This was before I made my transition to software engineer. I worked on the third shift for a bank services company. The company was on a down turn. Just years earlier they just went public, and secured a deal with a huge well known bank. Eventually they entered a really bad contract with the bank and was put into a deal they couldn't deliver on. The partnership collapse and their stock plummeted. The CEO was dismissed, and a new CEO came in who wanted to "clean things up".

Anyway I entered the company about a year after this whole thing went down. The NOC was a good stepping stone for my career. They let me work as many hours as I liked. And I took advantage of it, clocking in 80 hours a week on average. They gave me the nick name "Iron Man".

Things started to turn around for the company when we were able to secure a support contract with a huge bank in the Alabama area. As the NOC we were told to handle the migration and facilitate the onboarding.

The onboarding was a mess with terrible instructions that didn't work. A bunch of software packages that crashed. And the network engineers were tips off, as they tunnel between our network and the banks was too narrow, creating an unstable connection between us and them. Oh, and there were all sorts of database corruption issues.

There was also another bank that was using an old version of our software. The sells team had been trying to get them off our old software for over a year. They refuse to move. This bank was the last one using this version, and our organization wanted to completely cut support.

One of the issue we would have is that they had an overnight batch job that had an ETA to be done by 7 AM. The job would often get stuck because this version of the software didn't know how to fail when it was caught in an undesired state. So the job hung, and since the job didn't have logging, no one could tell if it failed unless the logs stopped moving for an hour. It was a heavily manually process that was annoying to deal with. So we would kill the JVM to "speed" the job up. One day I killed the JVM but the job was still late. They told me that they appreciated the effort, but that my job was only to report the problem and not fix it.

This got me caught up in a major scandal. Basically they wanted the job to always have issues everyday. Since this was critical for them, all we needed to do was keep reporting it, and then eventually this would cause the client to have to upgrade to our new software. It was our sales team trying to play dirty. It immediately made me a menace in the company.

For the next 6 months I was constantly harassed and bullied by management. My work was nitpicked. They asked me to come into work nearly everyday, and there was a point I worked 7 days with no off days. They were trying to run me so dry that I would quit. But I never did.

On my last day at the company, I was on a critical call with a customer, and my supervisor was also on the line. My supervisor made a request that made no sense, and was impossible. I told her it wasn't possible. She then scalded me on the call in front of customers. She said "I'm your supervisor, you're just a NOC technician, you do what I say and don't talk back". It was embarrassing to be reprimanded on a call with customers. I never quite recovered from that. I could fill myself steaming with anger. It was one of the first times in my adult life that I felt I really wanted to be violent towards someone. It was such a negative feeling I quit that day at the end of my shift with no job lined up.

I walked away from the job feeling very uncertain about my future, but VERY relieved. I paid the price, basically unable to find a job until a year and a half later. And even was forced to move back in with my mother. After I left, the company still gave my a severance. Probably because of the supervisor's unprofessional conduct in front of customers, and the company probably needed to save face. The 2008 crash kept me out of work until 2009. It did give me time to work on myself, and I swore to never let a job stress me out to that degree. That job was also my last NOC job and the last job where did shift work. My next few jobs was Application Support and I eventually moved into development full time, which is what I always wanted to do.

Anyway sorry if it's a bit long, but that's my burnout story.

Me: We need to have a developer on our core product

*We fork our core product from a private repo for new projects

Management: No.

Me: But imma die 5years early from stress and anger overdose of fixing the same problems over and over again in every new project we do and still hit deadlines which didn't account for them when we could fix them once and maintain our core product

Management: everything is fine. Lalalalalala

Me: *wonder why every senior dev has left in last few years*

Lost my temper at one of our volunteer moderators the other day. We had to do a test using live data, our sysadmin warned him, but not far enough in advance and not really by the right channels. So that was on us. sorry not sorry. But so then he didn't believe us. He must be a geek too cuz he responded with some stupid math problem for me to solve, as if that would prove we work here and aren't hackers or scammers. I replied "how about if i just kick you out of your own group and delete your account, would that convince you?" And so I did. Asshole. Of course I had to apologize later and get a lecture from the boss, but it was kinda worth it.

*Be project manager/most senior developer*
*Higher up tells you there is only enough money to hire recent graduates/internees, the cream of the pie, and that I can't hire fewer developers with more experience*
*Code is shit as result*
*Feels anger towards the developer that did it*
*Feels sorry because that developer is actually trying really hard and is diligent even if he is inexperienced*
*Change anger object to higher management*
*Repeat*

5 fucking days of Google search after Google search. Error after fucking error. Deadline getting closer by the fucking minute. teammates interrupting me every 10 minutes over discord asking for help on their fucking part of the project

and it turns out the solution was just one damn line

One fucking line in a forEach to iterate over the model data sending the necessary aspects to the Javascript function to create map pins for the database locations

5 fucking horrible days all amounts to 1 line

Really shows how much I still have to learn. And the yelling at my screen reveals my need to take an anger management class

Blindsided by a project meeting 5 mins to end of day when I was super busy and I've spent all day dealing with shitty hacked together legacy code, requirements changing everyday and still no business solutions to some areas of the project. We already have one booked in for tomorrow at 10. What the fuck. Needless to say I pretty much shouted about everything to everyone. Fucking joke. Now I'm just mad at me for letting my blood boil externally

Have you guys ever seen another dev at you work just completely lose it? How do you cope with stress, rage, frustration at work? (other than DevRant) Stories, please.

I got plenty of stories of yelling at co-workers before for assortment of reasons. But let me tell you a story of a time I almost yelled.

Think of Adam Sandler when he's a bit ticked. He says something nice with nice words but he delivers it in an upset and load tone but not actually screaming/yelling. That's me trying to hold back but it reveals how upset I am. I do try to stay courteous and gentlemanly (I'm really trying to manage my anger after so much BS I've been getting after a decade of working). But there are times where my patience is testing its limits and well, I implode.

And when that happens, I regret doing that to my co-workers as we are all trying to get things done and still get paid by the end of day. But they stoopid! UGH!

Co-workers, I can tolerate a little more. But clients are a completely different story. Ever tried fake smiling for over 3 hour meeting of ridiculous change requests and has the balls to make them free? It fcking HURTS!

In my first job another junior dev and I (junior at the time) were assigned the task of designing and implementing a user management and propagation system for a biometric access control system. None of the seniors at the time wanted to be involved because hardware interfacing in the main software was seen as a general shit show because of legacy reasons. We spent weeks designing the system, arguing, walking out in anger, then coming back and going through it again.

After all that, we thought we would end up using each other, but we actually became really good friends for the rest of my time there. The final system was so robust that support never heard back from the client about it until around 2 years later when a power outage took down the server and blew the PSU.

Good times.

!dev
Anger management is real. I just broke my PS4 controller coz of NBA 2k. My fucking players just cost me a game 7