Working overtime

Just learned that my employer withhold part of my salary every month the past 5 months! I did not notice it as it was overtime compensation.

I first thought maybe it was a mistake so I asked, the reply I got was: Oh you know that compensation we agreed upon? I wasn't having it anymore so I decided to half it and been since then editing the hours you billed every week to reflect that and accedently forget to tell you.

Accedently?! My ass! One week is believable but not 20 weeks. The only reason I found out is that they tried to lower the compensation even further which caused these hours to show up differently in the hour declaration software we use.

So currently on my way to return company's property and quit.

In the darkest of days, I discovered how to remote login to my computer at work through the company vpn. I then proceeded to work overtime at night in secret for a week or so, writing documentation and refactoring code.

I finally woke the fuck up and realized that I shouldn't be obsessing over proprietary codebases that do not belong to me, and I should put this misguided energy into my own projects.

So yeah, as a bad dev habit I'm working on fixing, this fits the bill.

So one year ago I was working at this company from the US, me being in Europe, which automatically implies there is several hours of timezone difference.

The eng. manager decided we would have a release tomorrow (decision was made one month earlier), and stuff was being prepped up to make that happen.

In the US the workday was about lunch time and in EU it was one hour before finishing. The manager gets us in a meeting and asks me and another dude to do some testing that would take several hours to do. This testing could have been done several days or weeks earlier.

40 minutes after that meeting I get a private message from the PM asking for the status of the test...

Me: aaa.. well I started it and will continue tomorrow

Manager: wait what? we have launch tomorrow, this testing has to be done by tomorrow

Me: it's the end of the workday here, I got personal errands that I have to attend to

Manager: uhm ok ... I see...

I was just messaging something in the public chat right before calling it a day and the manager writes "thanks for the input, your day is over now", completely out of context to the conversation I was having with whomever.

There was no question of "can you stay extra hours and do this?", there was no "hey, I know your day is over we will pay you premium hours with this amount as according to our contract, could you do this now as we have release tomorrow?" ..no ..just .. "do it!". I automatically assumed that ..hey, maybe he wants to do this during and after the live launch (and yes I do admit my mistake of not asking just to be clear, but I assumed the manager knows that there is a timezone difference ..like it's a no brainer).

I can not tell you the heat sensation I had after that last reply from the manager ... it was completely uncalled for, and unreasonable.

I mean why not make a pre-launch phase where you put stuff on the staging server, and perform all the necessary tests and then when you get all the green lights from testing you then proceed with the actual deploy? ...no ... mention this like right at the end of the day before the launch....

And another thing that scratched my neuronal cortex is, how does he know exactly how long the tests would take?

I'm a tech lead for a digital agency.

Digital agencies are universally known for being shite. Why? Because they typically push through sub-optimal code with very little testing over tiny deadlines for maximum profit. Maybe I've just had bad experiences but this is the 5th digital agency that I've worked at that does this bollocks.

I am currently sitting on a Teams call at 8:39pm because the fuckwit project/account managers are unable to face up to the big scary client and ask them terrifying questions like "Is this bug a blocker for the deployment?" or "We don't have enough time to fix/change these things, can we delay another day?". They just assume that A - We will work into the evening, and B - that all the issues are P1 and that we should all 'pull together' as 'team players' to get this done in time.

No, Me and my team have to work into the evening for seemingly free because these pricks can't do their jobs properly.

The funniest thing of all? When I speak to the CTO about overtime payment he tries to make me feel bad about "we don't typically pay for overtime..."

Fuck Everyone.

Time to find a new contract.

TM: Hey, do you have a moment?

Me: not really, I'm already overtime and have enough work for the whole year.

TM: Yeah, we know. Just a quick meeting to discuss something awkward.

Me: Hmkay.

...

Later that day:

TM: Yeah. To make it quick - we're confused and bit dissatisfied with how project X turned out. The staging server is blazing fast, but the devs machines seem to be extremely slow... Some devs complained.

Me: No wonder. I said from the beginning that the devs shouldn't do X and Y, and that the dev machines need to be redone after staging is done - as we need to gather hands on experience first, cause no one could explain to me what resources the project actually needed.

TM: Oh. I wasn't aware of that.

Me: I guessed so. You were on vacation at the beginning and I didn't had the time to lead another team...

TM: Yeah... So the dev machines get replaced?

Me: They _could_ be replaced, but the devs would need to reset up their environment, as I and won't transfer the environment of the dev user.

TM: Ah... So they would have to retransfer their personal modifications, if they made any?

Me: Yes. As always, the basic setup just provides the necessary services, settings etc. - stuff like remote IDE settings on the machine, configuration etc is left out and we don't transfer it as it is usually too much of a hassle and risky, as every dev does have his / her own preferences, and we don't want to support every possible configuration out there.

TM: Just out of curiosity... Staging was ready like... Last year?

Me: Beginning of December, yes.

TM: Sigh.

Me: The jolly of having a kinder garten full of toys that no kid wants to clean up...

TM: No comment. The kinder garten Kids might make me a Pinata otherwise.

Me: If only they'd fill us with chocolate first instead of just beating us.

...

Tales of lazy devs, to be continued...

By not having them. Seriously, every job I had was more than average paying and I was overqualified for the tasks. Sure I didn’t develop oh-so-important software but I never had to do overtime, lose sleep because of workplace difficulties.

Pick your fights well. This profession is unfair. No need to endanger yourself for idealism.

Manager: Can you stay late as fuck today? One of our bitchiest vendors is gonna update their piece of crap and I'm pretty damn sure shit is gonna hit the fan

Dev (inner voice): no fucking way, I have kids to watch and chores to do!
Dev (outer voice): can't we just check everything in the morning?

Manager: No fucking way! If there is some fucking "challenge" when our "people" try to log onto their shit, I'm gonna look like a chump!
Let's talk silvers, I will sign on that bloody commie bullshit for your hours tonight.

Dev (outer voice): Fine. Until how late?
Dev (inner voice): Wait, I was supposed to do it without getting overtime bonus?

Wish me luck. I HAVE to launch 10 websites (yes, ten) this week and half if not all of the clients don't know their DNS accounts or log ins. I foresee a lot of long nights in my near future. Story of our life, right?

Our boss did always the same thing. When there was a BIG potential customer who indicates a small interest in our software, then he lied constantly about features. After the customer bought our software we got a deadline and should develop the missing features. I could remember two features: The first one was a quote tool for a car transport company. The tool should estimate a price for a transportation from an email with no structure and the other one was an API which should be possible to write dynamicly to MySQL, MariaDB, Postgres, MSSQL, DB2, Mongo or better said any possible dbms. The API should guess the structure of the dbs and offer CRUD actions. The funny thing is must write the api with go. Yeah dynamic and GO.

At some time, we told him we wont make any overtime and if the deadline is not possible we told that immediatly the customers, so that they call him. Thank god I don't work anymore in this company.

git cd ..

*stares at terminal*
...

Is that a sign that I should get some sleep?

Please deploy on Fridays I get paid overtime when I have to stay late to fix whatever untested microservice broke as a result.

So...Just got moved from salaried to hourly for an already extremely overworked, underpaid position. Lost our flexible hours and our platform is moving to drop and drag...Watch them say no overtime now. Beyond pissed!😡

FML or how I made myself unhireable

TL;DR: Working as a QA.
Changed jobs.
New job sucked.
Left after three months.
Got laid off from the next one after 4 months (not my fault).
Got depressed.
Got a Dev job back in the first company.
Job sucks, cannot leave… (5 months in)

Full rant:
I was doing pretty well as a QA Enginner. Started with internship, then junior in company A, then big pay rise moving to company B, where I quickly got promoted to Senior. As I was nearing 3yrs of exp, I decided it’s time for a change, as things were getting worse project-wise and felt like I was regressing. Also I was constantly bombarded with offers of +50% of my salary I could easily land, while company offered 10%.

Moved on to company C. This is where it started getting rocky. I was told I would be working on this one project, strictly test automation, nothing exciting but an easy gig. However week in, I was told to work on this other project 50/50. This was a startup kind of thing. It was a nightmare. Only manual testing. Most tickets had only a vague title, no description, no requirements, nothing. How do one test something without any knowledge how it should work? Besides that, the project lead on the client side was aggressive sometimes.
The workload was immense - 4 devs, 2 of them doing heavy overtime, so the output was like 6 devs and half of a tester….
Despite raising the problems, nothing was going to change, nor I could switch projects. The job began to heavily affect my mental health. Decided not to prolong my contract and left after 3 month probation period.

Quickly landed a job in company D. As my burnout as a tester kept bothering me more and more I decided that this was going to be my last job as a QA and next one will be a Dev. You see, I never enjoyed the tester part, I always enjoyed the automation part more. The plan was to learn in free time and after 18-24 months start applying for a dev role to see if I can land one (switching inside D was not an option). All plans went to hell, as I was handed a one month notice by the end of my third month. A month before my wedding… I was told the company was having financial issues and was laid off with about 30% of people in the company (mostly new hires).

I got depressed. I wouldn’t get out of bed for a few days. I never thought something like this would ever happen to me. Standing by my decision I was applying for development jobs, but most recruiters seeing either only QA experience or my recent 3 and 4 month employment periods weren’t responsive. Applying for testing jobs was a bit better but still nothing like before C and D.

Since company B I stayed in touch with my former manager, and he kept telling me that a new team has taken over most of the shitty work, and they are now working on cooler stuff and have more coming. He encouraged me to come back, as he has always thought highly of me professionally.
Looking at my options, I could probably get another testing job with lower pay, maybe I could land a junior Dev with like 1/3 of my salary or I could go back. So in my dark time I have reached out to my manager and just like that he got me a Senior Dev position, same pay as in company D.

Finally what I wanted right? Yeah… As soon I as joined all the new initiatives were being dropped one by one, and backlog got flooded with bugs and sh*t again. Five months in I hate my job again. Cannot leave cause no one will hire me…

Where I made the mistake?
Shouldn’t leave B despite facing regression and being underpaid?
Shouldn’t leave C no matter what?
Shouldn’t come back to B?

I think I've reached some kind of job nirvana. My coworkers and I all complain about our work. We're overworked, underappreciated, underpaid, and and have to deal with all sorts of bullshit all the time. Pretty much everyone who has been on the team longer than a year is talking about quitting.

But I started at this company as a level 1 tech support phone technician before I transferred into the DevOps side of things, and that tech support job was SO much worse. Way more stressful, way less pay, mandatory overtime, horrible scheduling, being forced to remain calm while people hurl insults at you over the phone, and it was a dead-end job with a high turnover rate and almost no opportunities for advancement of any kind.

And every time I think back on that job, I realize that what I have now is actually pretty great. I'm paid well (still underpaid for the job I do, but catching up really fast due to my current boss giving me several big raises to keep me from quitting lol). I deal only with other tech people like developers and data scientists so no more listening to salesmen insult me on the phone. I'm not in any sort of customer service role so I can call people on their bullshit as long as I'm professional about it. I'm salaried so they can't make me work horrible shifts. 99% of my days are a normal 9-5 workday. I actually have a reliable schedule to plan around.

People treat me like the adult that I am.

I'd get a similar experience at other, better-paying companies, for sure, but what I have now is still pretty great.

I'm sure I'll be back in a few days to rant about more nonsensical bullshit and stress, but for now I'm feeling the zen.

Regain work life balance.
The last few years especially with COVID I've started to do way to much for the company's I've worked for. Working while I was coughing my lungs out when I had COVID. Working during my holiday because it was finally a fun feature to develop. Working in lunch breaks because people would call me all the time (remote there are no boundaries)

I left that company on a good note, started actually healthy as the new company actually understands flex working. However as I gained responsibly more meetings started to appear also causing rushed lunches no more walks of sport activities. Than I was lead in a project and because of some personal circumstances (death in the family) that was running long. Again started to work overtime trying to catch up.

I need to stop doing this. Caring is fine but I just give to much when I feel responsible. Good thing is that my current company actually wants to help me with this.

Well here it goes,

I started out in customer support (A lot of stuff to tell here).

1.
One of my colleagues would come to work drunk, like every day he would smell of boze (the hard stuff 80%+). When a customer got on his nerves he endet the call and threw his Keyboard across the room. He worked in the company 3+ Years after I left.

2. Another colleague would connect to his Personal Computer at his home and play WoW while at work ( Allthough the man was a genius with a lot of free time, until a new task was assigned to him)

3. My Boss at the time did some really shitty things. I worked 17 hour days (while I was 18) for a week, and at the end of the week he shredded the accrued overtime with some Bullshit Explanation. (I did not stay long after this shitshow happened).

4. A dispatcher who sent our technicians out scheduled their tasks so that they were on the road for weeks and did not see their families. This led to a very strong turnover among technicians.

And yes, this company still operates today.

Old old organization makes me feel like I'm stuck in my career. I'm hanging out with boomer programmers when I'm not even 30.

I wouldn't call myself an exceptional programmer. But the way the organization does it's software development makes me cringe sometimes.

1. They use a ready made solution for the main system, which was coded in PL/SQL. The system isn't mobile friendly, looks like crap and cannot be updated via vendor (that you need to pay for anyway) because of so many code customizations being done to it over the years. The only way to update it is to code it yourself, making the paid solutions useless
2. Adding CloudFlare in the middle of everything without knowing how to use it. Resulting in some countries/networks not being able to access systems that are otherwise fine
3. When devs are asked to separate frontend and backend for in house systems, they have no clue about what are those and why should we do it (most are used to PHP spaghetti where everything is in php&html)
4. Too dependent on RDBMS that slows down development time due to having to design ERD and relationships that are often changed when users ask for process revisions anyway
5. Users directly contact programmers, including their personal whatsapp to ask for help/report errors that aren't even errors. They didn't read user guides
6. I have to become programmer-sysadm-helpdesk-product owner kind of thing. And blamed directly when theres one thing wrong (excuse me for getting one thing wrong, I have to do 4 kind of works at one time)
7. Overtime is sort of expected. It is in the culture

If you asked me if these were normal 4 years ago I would say no. But I'm so used to it to the point where this becomes kinda normal. Jack of all trades, master of none, just a young programmer acting like I was born in the era of PASCAL and COBOL

During the interview I was told that overtime will be paid. I'm working on a project which requires a lot of overtime so we can meet deadline. I was told that there is no budget for overtime.

I have also done 50 hours of overtime so that means 50 hours of overtime will not be paid to me.

I recently graduated from university and landed a job as a junior devops engineer.

There’s so much tech stacks to learn and I’m in the process of converting a legacy CI system composed of only bash scripts to Python and I feel that 8 hours a day isn’t enough and I often feel that after working hours, I should be reviewing more so that the next day I can be more productive.

I am given tasks to do but I keep feeling the pressure that I need to prove myself.

Is this normal? I’m not used to this learning pace.

So this month I had to do two major features which required unexpected refactors and I had to handle unexpected edge cases all over the place. Since I work in another timezone and time was of essence, I was kinda working around the clock to complete refactors as fast as possible because it was "important and critical". I have 7 other devs in my team but only half of the team are actually competent and even less are motivated to push through. Most of the team prefer to sit on low hanging fruit tasks and cant even get that fucking right.

So that resulted in me doing at least 100 hours of overtime this month. Best part all I got for pulling it off was a thank you slack message from teamlead and got assigned even more work: to lead a new initiative which seems to be even bigger clusterfuck...

So today I had a sitdown with my manager and I asked for 3 paid days off and told him that I did 50-60 hours of overtime. He okayed it as long as my teamlead was happy.

So I created a chat, adder manager and teamlead to it and explained my situation. That Im feeling burned out, I need 3 days off and combined with the weekend that should allow me to finally relax.

My fucking teamlead told me that these days are mine and he cant take them away from me. But then he started guilt tripping me that no one else will be working on the new initiative these days so we will have a very tight timeframe to deliver this (only until August).

Instead of having at least a drop of empathy that fucker tried to guilt trip me for taking days off for fucking unpaid overtime. What a motherfucker. Best part is Ive talked with manager and we actually have until end of August to deliver the new initiative, so fucker teamlead is gashlighting me with false sense of urgency.

I guess a hard lesson learnt here. Waiting for my fucking raise to be approved for the past 6 weeks (asked for a 43% bump which is on the way since I got very strong positive feedback).

So Im done. I proved myself, will get the salary of which I only dreamed about few months ago. Not putting any overtime anymore. If something is very urgent, borrow fucking decent devs from another team. Or replace half of our useless team with just one new decent dev. I bet our producticity would increase at least by 50%.

Its not my fuckint fault that 2-3 people are pulling the weight of 8 people team. Its not my responsibility to mentor retards while crunching under immense pressure just because current processes are dysfunctional. Fuck it. Hard lesson learned. If you want overtime, compensate with extra days off or pay. Putting my 7-8 hours in daily and Im not responding to your bullshit slack messages or emails after work. I dont give a fuck that you work in another timezone and my late responses might result in stuff getting done postponed by a few days or a week. Figure it out.

Seems like the company is going through some trouble. The sheer anxiety of having to deal with recruiters and interviews if it kicks the bucket gives me the shivers. Made me force myself into overtime.

I still enjoy developing . The part I'm finding difficult these days is that, if I'm under deadline pressure and need to work overtime; instead of being supported by my family, my wife moans and blames me for doing this job; saying I just want the money (which isn't true) and guilt trips me for not spending time with the kids. So, I get it from both sides. As if life isn't hard enough.