Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "wk248"
HR sent around updated contracts asking everyone to sign them since the company changed its name, fair enough.
In the contract it stated "Your normal place of work will be X" - only X was many miles away, and I'd never worked there, never planned too. Assumed it was a mistake, sent it back. HR refused to change it, stating that the "normal place of work does not need to be the place where you normally work."
A lot of back and forth entailed, I refused to sign, I was reprimanded for not doing so, I was asked what my problem was as it made no material difference, and then I eventually replied with:
"Angela, I'm refusing to sign this as it's factually incorrect. No further explanation is required. I'll maybe consider signing this if you sign a piece of paper declaring you believe the moon is made of cheese, and you're the cow the milk came from to make it."
A very strongly worded email came back about how this was going on my record, I needed to offer a formal apology, etc. - all cc'd to my manager. I replied back, again copying my manager in, stating that this was ok, as I couldn't remain at a company who forced employees to sign dodgy contracts anyway.
Problem was (for them), I was a *massive* single point of failure for them at this point owing to some others leaving with no handover - hence I knew I wasn't going to be the casualty here. My manager flipped the lid at HR, got the CEO involved on threat of *him* leaving, and the whole thing massively blew up. Happy ending in that the HR person in question was fired, everyone else's contracts also had to be redone (I assumed everyone else just signed without looking which is worrying), and I actually got a pay rise out of it when higher ups realised the massive single point of failure I was.
But damn, I would've walked over crap like that. Walked pretty soon after anyway!17
I was hired as Project Manager.
After few days, I discovered that:
- I didn't have a team
- I was also the main and only developer
- all the projects I was assigned to were late
- I was also the account manager and I had to explain the delay to the customers.
And no, the salary didn't make up for the daily loss of reputation.
I lasted more than I thought, when I discovered that customers were not interested in delivery either, as it was a kind of money laundering scheme10
IT Manager: What kind if attachment did you send me in that email?
Me: A .zip?
IT Manager: ...?
Me: A zip file? Zipped Folder?
IT Manger: ...?
Me: Umm... the data file you needed has to be sent in a zip folder because 6 different file types combine to make it? Just download the .zip and extract?
IT Manager: I don't know how to extract the files?
Manager A : "You've done a great job, you'll get a X raise"
Manager A: "I was not able to negotiate it, but you'll get a X bonus to compensate for it"
*Manager A leave the society*
Manager B: "A bonus? Never heard of it"
Me : Resign.5
I ended up quitting my first job for many reasons, but this talk still haunts me:
"our workers need to input this data and they tab a lot because [...]"
Me: "ok... Where do they get the data from?
"A standard model compiled via web, sent via mail and then printed for them."
Me: "how about we make the import automatic?"
Them: "but then what will our workers do?"
To this day I am still impacted by this dialog... Not much for the stupidity from a business logic point of view (there are many bad companies, and this is not the only one I met in my career), but rather for the implications our job has and for the fact bs jobs are a thing because we are SO used to the capitalism that the bad guys are the ones removing boring tasks, rather than the shitty system which forces you to do a repetitive and automatable task and which reduces you to a shell doing a job a machine could do... And thanks for the wasted paper/ink, global warming ain't gonna get worse on its own!2
Job BS that made me consider quitting? If you find my previous rants, you find a lot of BS.
Here is one (attached is the actual email sent to me.)
TL;DR. The biggest BS part is the fact that I *got approval* from my boss to work on the migration and we already 'owned' specific project and no one else was working on it.
After I got the email (my boss sits right next to me)
Me: "Whoa..what's this!? Two weeks ago you gave me the green light to work on it."
C: "Oh yea...I forgot. Sorry."
<yes, the BS flags thrown all all over the place>
Me: "I'll schedule a meeting with everybody and straighten this out."
C: "That's a good idea, but I'll take care of it."
<10 min. later>
C: "Sorry, J said his word was final. You are not supposed to work on the project."
Me: "I never said I wanted to work on the project, it's already finished and with your approval. That's what I want straightened out."
C: "Yea..yea...I know, but J said to roll back your changes. I tried everything I could to change his mind."
Me: "I don't want his mind...never mind...I'll go talk to the boss if J won't listen"
C: "About that..um...the directive came directly from the boss. It's probably best you roll back the changes and forget this happened."
I knew then the well was already poisoned, so anything I said could be grounds for dismissal (the boss had an itchy 'firing' finger)
Time and karma took care of most of the rage. Not really a month later my boss was demoted back to developer and working on dead-end projects (porting data for reports).6
Everything is "critical priority" all the time. Every new project is the most important project in the entire company. Every request that comes in has to be handled immediately. I have a good manager now who fights back against the deluge of critical work, but for my first year in my job I had a different manager who would bend over backwards to appease everybody, over-promising constantly.
I eventually started asking questions like "Which project are we de-prioritizing to accommodate this?" or "Is X more or less important than Y?" and then I would focus entirely on whichever project he identified as being the most important, and not touch anything else until I was done. Basically forcing him to prioritize our work.
I almost quit over a few of these issues, but I stuck it out and eventually our team came under new management, and now our manager is the one asking those questions instead of me. As she should be. Her favorite response when someone says a task is critical is "How critical? How much money will the company lose per day if this is late?"
Most of the time, the answer is somewhere in the range of "nothing" until a couple months after the deadline. So we set a much later deadline and get the work done right.6
Not from a coding job: "Optional" after work social gatherings which I declined to attend. My boss told me I had to attend them. I said, "That means they aren't optional." He said, "They are optional insofar as I don't have to attend them but you do."
Satisfaction: I quit while he was on vacation and gave only 1 week notice
From coding job (and this has happened several times):
"We value your input! What do you think of ..."
And then NEVER listening. NEVER giving feedback as to why my ideas aren't useful/helpful. But continually asking for input.
Yeah, go fuck yourself.1
People telling me to talk more even when I have nothing valuable to say. On my first job, two people in our batch didn't get promoted. Guess what we have in common? We're both quiet. He's a good developer though, better than most of the people who got promoted. I'm not so sure about me. My senior back then told me that there's no place for quiet workers there. He didn't say it to be rude to me, more like "yeah, management is fucked up here".
This happened way too many times, in all the companies I worked with. I even received feedback from clueless motherfuckers that I should improve my "communication skills". It was clear to me that those idiots use words that they don't really understand. To them, good communication skill means talking non-stop even when you don't make any fucking sense and use words you don't really understand, but there were a few people who supported me. I speak clearly especially at work. I can articulate my thoughts better than these obnoxious motherfuckers.
But people don't care about that, especially in this country. I managed to find ways to make my efforts more visible. I don't mind attracting only the few who sees honesty instead of incompetence when I say I have nothing to say about a certain subject. They know I speak up when something's up.4
A manager who felt that it was okay to come and speak to me about something that they were unhappy with in my conduct towards a member of our team, in a public place, loud enough for others to hear.
The conduct that made the manager feel the need to do this was my response to something another team member asking me to do. I had a lot on my plate with work, and had been given at least 3 additional tasks already in that meeting and my response to having to do yet another thing for this other team member because they "hadn't any idea what to do" was simply that I was quite busy and if it wasn't high priority it could wait one week as I have 3 other higher priority tasks that week to do. This resulted in me getting a warning and in a very public place.
Shouldn't have let it get to me the way it did, but the stress I was under and the way in which it was conducted just broke me and I cried. That nearly pushed me to leave my job and industry entirely.9
Bossman kept giving me a new “high priority” every month. Which would’ve been fine except for the fact that the prior month’s “high priority” was always a type that needed several months to come to full fruition. So he was constantly pulling the rug out from under me just as I was starting to gather steam and make progress. Also, he was begrudgingly paying me only half of the market salary for my job title in my locale. Would have loved to have paid me less and worked me twice as hard. I endured about 9 months of that and then I quit. Now my job is the exact opposite. Paid nearly twice as much with no micromanaging and plenty of time to work on my projects.1
I made a functional parsing layer for an API that cleans http body json. The functions return insights about the received object and the result of the parse attempt. Then I wrote validation in the controller to determine if we will reject or accept. If we reject, parse and validation information is included on the error response so that the API consumer knows exactly why it was rejected. The code was super simple to read and maintain.
I demoed to the team and there was one hold out that couldn’t understand my decision to separate parse and validate. He decided to rewrite the two layers plus both the controller and service into one spaghetti layer. The team lead avoided conflict at all cost and told me that even though it was far worse code to “give him this”. We still struggle with the spaghetti code he wrote to this day.
When sugar-coating someone’s engineering inadequacies is more important than good engineering I think about quitting. He was literally the only one on the team that didn’t get it.2
They just... stopped paying me...
(Ended up recovering the money after going through the Department of Labor, but damn)4
Previous employer demanded I work on Christmas Day or risk being terminated. Wasn't the final straw (I was young and needed the work) but did start the slow spiral.
I'm grateful now, happy in my current job for about 9 years with plenty of career growth.2
1.5 million lines of undocumented spaghetti code. Think 500~1000 lines functions, 5k+ lines classes, string html concatenation. You name it, it had it. And complete unwillingness to improve it by the company. I eventually quit after considering doing it about 2, 3 times.5
First company I worked for, overall it was a good experience, but at one point they promoted a consultant to project manager, and their planning skills were about as good as their people skills, which is to say, appalling.
We had a project update for a huge client, that required, for political BS reasons, that most of the team spend several weeks on-site, 300km away from home.
Go-live was approaching, and the plan was: migration starts Friday night, shortly after midnight (so actually, Saturday) once the client’s IT confirms DB is backed up. Expected duration: 5 hours.
- So, you expect me to work from midnight to 5am on Saturday? And when do we start working on Friday?
- 9am, of course.
- 9am!? So you actually planned a 20 hour work day? (Note: legal maximum here is 10 hours in a day, 40 a week)
- And we have to be there on Saturday 1pm to recheck everything is running smooth.
wtaf were they thinking?2
- being sat at an office that didn't have chairs with proper back support. It would kill my back every day. Like sitting on a bar stool coding.
- not having access to basic resources (cafeteria, salary bonuses)
- being seriously underpaid ($200 under)
- not having an IT process pipeline (yeah, this is a huge one): no JIRA, no git, no VCS, no continuous integration, etc. I fucking spend 45% of the time fixing coding-unrelated shit.
Second company (very aggravating):
- dumb frontend bitch and privileged colleague who both kept telling me months on end to shut up and who wouldn't listen to my advice on anything, while my advice would actually help the company advance in productive ways. The key here is being told to shut up while stagnating. i.e. dead end job.
- people advancing in the company based on nepotism and favoritism, based on having tits and ass, rather than skills and independence.
- pointlessssssssss meetings where decisions are made solely based on the opinion of Mr. favorite senior dev. The rest just sits there like a bunch of sad saps and yay-nodders. Incompetent PO's who "would like to hear your input" but then when you give it, they completely dismiss you.
- pointlessssssssss monthly meetings with stakeholders, where the dev teams do nothing but clash and act like pussies in front of the PM just to get in his favor, but behind scenes continue to make the same mistakes and telling the CEO everything is fine. Goodness, how can it get more unproductive.
- completely antisocial and nepotistic 'colleagues' who won't even talk to you, let alone smile at you or be friendly. You saying good morning and them pretending you're vapor that doesn't exist. Go go company atmosphere! Especially during lunch, those are the worst times. Imagine sitting at lunch where everyone looks like you killed their dog and the rest is huddled up in little high school groups.
What else? The incessant and pointless smalltalk that makes me want to bang my head against the wall. Talking about dogs, kids, what show was on tv last night. The fuck man, do you have a brain?!
- HR bitches who think they are the shit and developers are antisocial, helpless misfits, but they work with computers and they don't even fucking know what a status bar is! The irony!
- forced socializing and stigmatization for the opposite. Imagine coming into a company and you don't say good morning. Should that be a problem? No. Instead, everyone starts dogging on you and hating you just because you didn't smile in their faces and said: hiiiiiiiiiiii how did you sleep? Did you feed your dog? Fuck you.
Elliot (Mr. Robot): "Wouldn't it be awesome if there was a mute button for life?" -boop, boop, boop, boop...- Ahh.. there.. that's much better."
- CEO's sucking up to you but when it comes to salary increase, they say shit like: "Ahhh ya know, it's kinda difficult." Yet another dead end job.2
A manager who asked me to research and produce documentation on findings on a new system upgrade we could apply. Report on the risks, the amount of resource and time that would be needed etc. And the benefits of upgrading. Then after recieving the documentation and taking 1 month to read it, refused to make any form of decision without asking managers 2 levels above them who respond with "It is your decision". Then deciding it's best not to upgrade at this time. Okay, no probs.
6. Months. Later. That thing I said I didn't want you to do? I want you to do it now, could you get that done by the end of the week seeing as you have done the research already? Oh yeah and I will be off for the next two weeks as I am off on a ski holiday, so good luck with that.
Manager who doesn't code makes all the technical decisions and doesn't listen to us, lowly developers. He only listened to the developer who has been the longest time in the company and had terrible ideas as well.1
Tried to reply to @Fast-Nop who had replied to someone wondering if C would be a good first language.
IMHO C should have been put to sleep ages ago. A few years ago I downloaded the latest, greatest C Standard. For a language billed as small and simple (by many) it was over 800 pages long. Still there's a lot that's unspecified like order of evaluation of function arguments. Int etc is implementation dependent. And error handling, let's not go there. The macro assembler throws away all the semantics leaving behind a cryptic value. It's a complex language due to the innumerable interactions possible.
It's been called assembly language for the PDP-11 minicomputer. Recently learned that even the VAX-1 was built from SSI chips like the 4-bit 74181 ALU. The VAX.
Anyway I had several excellent books on programming style written by Henry Ledgard. He despaired of making C look readable. I commend his books which are so old that the code is UPPERCASE A lot of he wrote had to do with program design, naming things, writing good comments and that the visual shape of a program assists mental clarity.24
I got two, both my internships sucked.
First one, I got hired for a C++ job, did JS for most of it. Half the team quit while I was there lol. I was in charge of the whole frontend when I left.
Second one, again half the team quit while I was there, leaving me with only ppl in Europe to talk to lmao.1
When the project lead gave a half hour speech for why our shitty web page was similar to Elon Musk’s rocket and how we needed to work extra to get it off the ground, to justify an extra 3 months of unpaid weekend work at 10 hours a day, after already getting 6 months of unpaid weekend work when I was a junior dev.1
Me: Hits blocking bug in someone else's code. Everyone's busy and stressed, I'll have a look myself. Find the problem, find associated documentation. In a language I don't really know, so pass this to appropriate dev.
Them: It's not a problem for me.
Me: ... Wut?
I don't work there anymore...
I joined in June to work on a project due to release in July. It released in December.1
Prepare for a long one.
There was this time when I worked for a company that made some patented proprietary software along with a device that measures some part of the body. Nevermind what exactly.
Then there was this major new customer. Bitchy and demanding as they want to deploy their own os/licenses onto the embedded computer aboard the device. I've told them that's not the way we do it as there's some proprietary software and technics involved that is of no concern to the client. They insisted, called the CEO, he then told me to make sure the customer is happy.
I go OK. I present the software, scripts to use to run the whole thing.. the works. Customer wants to run its own client software on the side, proposing they buy better embeded machines on their own - they want to use that instead of the desktop /imagine a nurse using an mri machine as her desktop if you will/.
I then call back the CEO and explain what's happening. I ask how far along this nonsense do we go.
After a word with CTO he demands I take back the software and explain why I exposed everything.
I "took" back the software /as if that is possible/ and made it work as it was supposed to, locking their sysadmin out. Then proposed I take the fall as though I did not understand the policy, so the client can save face and we get the deal.
Problem is, someone else should then proceed working with the client. They accuse me /as proposed/ but then have me clean the mess up. Client still bitching about adding devices to ad is their policy. Yeah.. like the fucking Tesla he rides is also joint to AD.
I quit that job soon after. This was not the only situation that blew my fuse there.2
Job BS that made me consider quitting?
Huh. so timely.
With my previous employer, it was the whole "we're doing Agile and sprints and all the things" with "finish the project in six weeks plus here are some more requirements" garbage. Plus my tech lead always let the business roll over her and add unplanned requirements during a sprint without adjusting the deadlines set by the project managers. In summary: a fuck-all combination of Waterfall deadlines, Kanban tickets and Scrum timeboxes.
At my current employer, it's our business partners who're a bunch of douchebags that don't plan for anything except making sure their bonuses stay intact. Recently they terminated support for a third-party product that literally drives 99% of their web application then says to us "Hey, we need to build our own replacement for the vendor product using an entirely new stack. You have 3 months or our clients will get pissed." Oh, and these business partners keep raising new issues without any documentary basis except "this doesn't feel right" when they test our in-progress work. So helpful <sarcasm />
On the bright side, I'm getting paid whether or not this project fails, so... meh.
Being denied the opportunity to work as a full time software architect instead of being a developer with a fancy title, speding 90% of my time just developing features and fixing issues. Then I hear stuff like how microservices are inherently bad because one of them is acting up and the whole reason for it was because a third party service had transient failures and the developer didn't bother to add a circuit breaker pattern there so it cascaded down to a critical process. Times like those I wanted to quit because those kinds of opinions are so dangerous, without any real basis, and senior developers even got the CTO on board in that idea.3
In a previous job, I was trying to organize a common repository with our shitty business partner so we could both be able to contribute our part so our work would not overlap. Not like they cared anyways.
One thing I quickly noticed is those fuckers would just straight up commit untested changes on master and cripples our whole testing and prod deployment at times because we were depending on a shitty IoT service they provided us onto which we had no control whatsoever.
I told my boss, who was often complaining about them being unreliable in the first place, I would simply restrict them from merging and commiting to develop or to master without my approval. We cannot keep working like this.
He told me that we could not impose on them our work practices and that I should not try to piss them off. To be diplomatic.
I politely and professionally refused to do it, but he did change his mind in the end. He and I left not too long after. I guess he felt obliged to respond that having his job at stake but you cannot condone voluntarily shitty work.
I had a week off. During that time nothing new was pushed to remote by my boss.
On the last day, before I started working again, literally Sunday night, a pile of garbage non-urgent changes were pushed directly to remote.
I guess it wasn't possible to wait another day for a review. I didn't really care much at that point, but it was just another confirmation, that quitting is the right thing to do.1
First or second week of my first job (internship) and my manager mentions that upper management has decided that a couple of engineers are being reassigned to the new technical writing team, myself included, effective tomorrow with no prior warning, before dragging us into a tech-writing standup.
A couple of hours later my manager apologizes to me for forgetting to tell me about this and asked how I felt about this. I basically answered "not well, this isn't what I signed up for", and credit to him, he pulled enough strings to get me out of that team and back to my actual job. In hindsight I suspect that it was more due to the fact that this internship was a three-way contract with the university and that if I complained they might get their intern supply cut off.
I used to work for a consultancy that specialised in a very niche area (I won't say what – this is traceable enough already!). We charged our clients a very high hourly rate, because demand and supply. All the time I'd get calls like the following:
"Please could you just make this small change to the deployment?"
"Yes, of course. You don't have any contract hours left, so I'll just forward you to our billing department so you can sort out the payment first"
"Ah okay, please can you tell us how to do it"
[Even if I explained it, you wouldn't be able to do it – that's why you're coming to us.]
"...or better yet, just do it as a quick fix outside of work?"
[So... work for no pay? No thanks.]
While my company always had my back on these requests (obviously, they wanted payment too), they were so frequent that I got sick of it.1
We have a lot of small projects with different domains that we maintain and develop. Most go into maintainence mode now and get no new features. Now our new department lead declared us the SWAT team bc there are no new good projects. This baiscally means we get pushed to other team's projects that have issues with deadlines and support there. So basically we get to projects with fire on the roof and as reward for extinguishing, we get another burning project.
Either that or in the first department meeting where our new boss introduced himself and managed to say in the same paragraph that due to corona we "shouldn't expect any salary increases bc these are hard times" and "his department has so much money and doesn't know where to spend it"
My job description is software developer, and that's the thing I do less because I have also been assigned tasks from other areas that nobody wants to do. Yeah sure, make the IT guy do it, he's not busy and doesn't do much anyway, right? Oh but wait until they do need something coded...3
Shitty legacy codebase made by shovelling pile of different shit by some 'cool dude' who left the company 3 years ago. Fixing bugs on this pile of shit all the time, but also I have to document everything as documentation wasn't there at all and fix the whole damn project in the meantime. No linters, no types, ancient libraries that have shitton of issues, hacky behaviours wherever you look, no tests whatsoever.
Except when we want to refactor/rewrite we don't get time for fixing the whole shit as it is worthless - there's no value for customers in that.
the other one was shitty HR talk which consisted of bashing on my technical competencies by computer illiterate troglodyte after which I left the company. They asked me could I stay for 2 more months.
That was that one single NO that felt so great that I will remember it for the rest of my life.
Context: Working in a small IT department of an SME that sells wine during my uni placement year.
Having the MD come into the office cubicle without notice or even knocking and always expecting people to work long hours (when his dad was more of a _work efficiently 3h per day_ type of person) and not hold his promise on getting me to work on projects relevant to my degree and the initial contract (where I was also paid less than promised).
Creating a ticket plus confluence page for every open source library I want to use to get approval to use it. Of course only to allow usage of the minor version, so in js Land the request is outdated after 2 days, before someone had to chance to approve it.1
Ok, I started a reply and realized that I forgot the dance of doom to verify my email address. So I copied the text and came back. Can't find my place.
AND how do you search for posts?2