Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "overpaid"
-
My employer has a dev studio in Cali.
The office is gigantic.
It has amenities.
It has a stocked fridge full of iced coffee, energy drinks, and apparently wine.
All the devs have totally enviable hardware.
And they probably earn twice what I do, or at least 50% more.
Yet they write absolute shit, never test their code, and push broken updates every day, often marked as "ready for final testing." Their codebase is full of hacks and guesses and stale cruft and worst practices. I wrote a rant recently about one of their fuckups, which involved 18 million Facebook errors per. day. So that should give you some idea as to the quality of their code, and their level of can't-be-bothered.
Again, they make 50%-100% more than I do.
Their whiny lead dev is bloody lazy when it comes to building things correctly, and totally prefers to half-ass everything and complain instead. He probably makes 150% of what I do, doing like 25% as much work, and maybe 10% as well. Doesn't quite compare though, as he's a Unity dev, not a backend dev. So his work isn't as critical.
akagdkdafavskakeuxbfh.
Bloody pisses me off.
"But their cost of living is higher!"
THEY SHOULDN'T EVEN BE EMPLOYED.rant root gets angry this is the short-short version overpaid crap-tier devs but i got too angry this was originally to be a comment22 -
Boss told me he couldn't raise my salary, since according to him, I was already overpaid. Months later they suddenly outsource some positions, including mine. I got 6 months with payment as a parachute. But I also got a new job that pays $15 000 more each year...!
It's nice to have double salary for 6 months...
:)9 -
Agile in practice.
I finished my story with 3 days left in our 2 week sprint.
Me: What story should I pull in next?
PM: Story <number> to add <new feature>
Me: ok, sounds good
PM: Will you finish it before our sprint ends?
Me: No, probably will take me 5-7 days.
PM: But it can't spill over, it will make our metrics look bad.
Me: I can't finish it in 3 days.
PM: ....
Me: Can't you just explain the spillover as us working ahead?
PM: It will look bad on our <automated-report>
Me: ....
Me: So don't want me to get started on <new feature>?
PM: ....
Me: <internally sighing> What do you want me to do?
PM: Maybe you can pair program with <Overpaid-Idiot-Programmer> to help finish their story
Me: ....
Me: feelsbadman.jpg14 -
Job Interview for a CTO role for a premium employer, a big law firm.
All is going well, I am telling them about my years of experience doing complex software integrations in business environments. Talking CRM/ERP, project management and development with external service providers. I tell them I want a salary of 100k and they nod in silence.
Then out of the blue one of the three stakeholders/managers leans over for a final question:
"Soo, we have this really big IT problem and if you would happen to know a solution to it, you would really prove your worth: I have these 10k+ E-Mails in my Outlook folder which doubles as an archive and Outlook keeps getting slower all the time. What can we do?"6 -
So, I'm investigating this flipping problem at work involving mbeans. Other than the fact that it's a fun fucking word to say, idk a damn thing about it, and the people who are having problems with them/it are looking at me like I'm a fucking pregnant triceratops... HOW THE HELL am I supposed to fix your shit if you aren't going to tell me why you need mbeans, what you do to cause the error, and what you do to make it go away. YOU'RE GIVING ME LESS THAN NOTHING... on a temperature scale, we're in negative Kelvin...
Also, anyone know what in the world an mbean in? Because right now, these overpaid idiots are making me think it's not a thing and just another way of saying "coffee"10 -
Finally bought a macbook for my android app development. Paid 1600 EUR for 2015 MID mbpro with 512GB SSD, 16gb ram, 2.5ghz quad core i7 cpu and dedicated gpu. I know I overpaid but I couldnt fkin stand working on windows anymore. I spent one year with fcking windows building android apps. Making apps on windows is fking impossible. And dont even get me started on new crap macbooks starting from 2016 :/19
-
What is it with networking guys refusing to do any kind of fault finding? Pretty much everywhere I've worked they seem to be overpaid address hogs who occasionally want everyone to be proud of them for installing a new switch.
Currently seeing a production issue that's clearly due to spikes in packet loss on a certain part of the network - but oh no, it's always "our tests are fine", "we can establish a route no problem", "this is an application level issue", etc.
No you morons, when a dozen unrelated applications hosted on different cloud services fail because none of them can contact anything in your particular subnet in your data center at the same time, it's a damn networking issue. Sort it out.14 -
You may be familiar with work philosophy known as "they pretend to pay us, we pretend to work."
Or a favorite of mine "in this together" and passove aggressive work place signs about safety, inbetween being told to operate machines that have faulty safety mechanisms and almost took a guys forearm off last week, when the machine was supposed to be locked out.
Also dont let them blather on about being a "family", or any of the worse horseshit they spew.
I knew a women who would take those "hang in their" and other inspirational posters and burn cigarette holes in the eyes.
I didn't understand what her motive was then but now I know she was a revolultionary, a visionary even.
It's all lies. It's all "Human resources" department brand managament by neurotic executives and glorified coffee secretaries with 100k student debts for degrees in "humanities"--while lacking any humanity themselves, let alone brains or a soul.
And in between an army of overpaid middle and district managers, checking for the fifth time that day, if you have finished that tps report, or that ONE task you just started or finished. As if a little internal robot timer has told them, not that a task needs managed, but that the task, having been started and done, awaits their preternatural ability to know, and arrive 'just so', and justify (barely) the continued existence of their mediocre job and their mediocre lives.
And out of the woodwork of generations, like a horde of oblivious fuckwit melonheads, comes a tidal wave of these brush-mustached fucks, speaking in aphorisms and happy turns of phrase, while people increasingly dont show up to work be cause inflation has all but destroyed the future so many saved and worked for.
And the shelves gradually empty.
And the wheels grind slowly to a halt.
Because we will not accept the bullshit anymore about being in it together.
Not when a floor guy makes 15k a year, and a district manager makes 120k.
Raise your wages, or say good by.
We were never in this together.3 -
You know what really grinds my gears?
Executive bathrooms. They get gold and marble and all kinds of fancy shit and the rest of us get a linoleum shit box. Who do they think they are? Are they too good to shit and piss with their developers. You know...the people who make the shit that makes them money?
Executives are just overpaid suits who do next to nothing while the rest of us carry their fat asses across the finish line and they are too good to take a shit with us common folk.12 -
So IBM finally jettisoned the cancer that was Virginia Rometty a few weeks back. They had an opportunity to move fresh blood and solid managerial background into the top slot with Jim Whitehurst (Redhat) and try and recover their flagging market share and do some sane business strategy. They passed on that opportunity and instead appointed the old guard bootlicker who overpaid for Redhat to the tune of 20x what it was worth, and signalled their intent to continue staying the course of the Titanic and it's slow inevitable trek towards the bottom of the ocean. The board wants a yes man, and they got one.
This is basically what I assumed would happen, but I have some other predications as well:
- Whitehurst will leave to a better company
- the redhatters that haven't already left will be replaced with commodity labor
- Redhat will be the least stable Linux offering 2 years after the last hatter leaves
- they will sell off most of their existing software assets to HCL/ similar consulting partners like they did with domino and websphere to stem the bleed
- the displaced in that move will either quit or be replaced
- their cloud initiative will collapse under the weight of its own stagnation and glacial pace of development
- they will attempt to salve these wounds by moving focus to global services, reducing profit loss by cutting salary costs, further diluting their eroding ability to innovate
- they'll buy at least one other trendy software company at ridiculous valuation, and sell it off within 2 years at a massive loss
- the CEO slot will start to resemble the late Roman empire with a new CEO every other week
- Redhat assets will be sold to Google inside of 5 years
Last prediction: I will be overjoyed being able to witness the death of IBM in my lifetime. Fuck them 🍻7 -
I applied for a position as an engineer for a nonprofit organization that helped kids across the country (and the world) and got the position. The people across the organization were wonderful and, without a doubt, mission driven to help kids and it felt good to do the work. The agile teams worked well together, every team had their roadmaps, and management always emphasized family first. The organization was making crazy money so we were given all the tools we needed to succeed.
Then, within a few months of my hiring, it was announced that the non-profit organization was being bought by a large, fairly well known for-profit company which had also been recently acquired by a venture capital firm.
The next thing we knew, everything changed all at once. We went from building applications for kids to helping this company either make money or build value for their owners. Honestly, I did not know what my day-to-day work was doing for this company. The executives would tell us repeatedly that we were expensive and not a good value compared to their other teams. It felt like we were only being kept until the systems were integrated and their had access to our decades of data.
You might think I'm being paranoid but a year after the acquisition, we still did not have any access to any of their systems. We operated on a separate source code solution and were not given access to theirs. When requests came from them that would facilitate them connecting applications to the data, it was to be considered highest priority.
The final straw for me was when I was told my compensation would be cut for the next year. We were strung along for the whole year leading up to it saying that the company was evaluating our salaries compared to others in the industry. Some of us figured that we would probably even go up knowing that we were underpaid for a for-profit tech company because we chose to work in a non-profit for a lower rate to be able to do worthwhile work. Nope! We were told that we were overpaid and they talked about how they had the data to prove it. One quick look at LinkedIn would tell you they must be smoking something that had gotten stale in a shoebox. Or they were lying.
So that was my rant. If you think you are protected from the craziness in tech right now just because you are writing code at a nonprofit, you might be wrong. Dishonest executives can exist anywhere.3 -
Did a presentation to the brass with data so summarized that no informed decision could conceivably come out of it.
They want it even more summarized.
Here is your messy-suit-that-cost-50-grand, version, your overpaid tool:
1) Client be dumb
2) Supplier be slow
3) Money be good
4) We be smart
5) We make money (if you stop meddling and eating my whole morning with a PowerPoint to a meeting you got an hour late to, your fiduciary sack of douchness) -
"A lot of people in this business develop huge egos. Why? None of us is curing cancer. None of us is saving babies from burning buildings. We’re just a bunch of overpaid knuckleheads who think up nutty stuff for some other knuckleheads’ products." - Paul Howalt2
-
Money or growth?
I'm mid level SE, looking to get promoted to Senior Level in January 2023.
(context: there are 4 levels before Engineering Manager or Software Architect in our company - 1 (or junior), 2 (or mid), 3 (or senior), 4 (or lead)...
But my total pay (way too good for my age at my place, but Software Engineers specially in FAANG and FAANG-like companies are overpaid here compared to the rest of the market.
My company, an Amazon's competitor in local market, earlier used to pay almost same as Amazon (or slightly higher to attract talent).
Recently, due to splurge of remote jobs, the MNCs started opening more offices (likes of Apple, Google, Amazon, Microsoft, Goldman, Morgan etc) hence the salaries increased even more.
Amazon for example, recently gave 33% increment on base pay recently.
Taking their base salary equal to my total pay (including stocks, bonus).
Should I switch for money or stay for growth?2 -
When the outside company that's testing your new site comes back with 10 problems:
2x are real issue
1x suggested wording change
2x them using bad data
2x are things that don't, shouldn't, and never existed on the site
3x can't be reproduced by anyone, including them
I'm thinking we way overpaid5 -
3 weeks back took a bug..
**long rant**
Looked into it and found that it is exist in older version(say V1) as well.
Sent mail to client stating i can fix this in current version (say V2). Since V1 is already released and our current code stream is V2 and so if we fix in V2 , the code will not reach V1 code base.
**explained to client**
Client : I mean if you fix why it won't work in older release.
Me: Explains how code streams will work.
Client : Okay.. but it will support the functionality in V1 , right ?
Me: (*internally* are fucking kidding me? It won't work dumb ass.) No. It won't work in older versions. I am fixing it in V2.
client: okay.. Let's proceed.
Me: Done code changes. Send code to review. (we have to send review to upper level manager).
Manager1 : I didn't liked this part. can you change this ?
Me : sure. Done.
Manager1 : Now i liked it. Sent review to Manager2.
Me: why the fuck ? Are you not sure about my changes are good?
Manager 2: I liked it, but need some log changes.
Me: Fuckkkk...... Let me change this.. Done. Now can I promote those changes?
Manager2: No we need to send review to client manager as well.
Me: Goddammit.. Okay.. sent review.
*After a fucking week..*
Client Manager : Looks good. Push the code.
Me: Finally..
(This process took 18 days which would have been completed in 3 days if there is only one peer review)
Now the other guy from client whose tracking the bugs reported why it took so long to fix it.
I think my client manager is over paid and can't even know how his company code stream works. Fuck you . why client has these lazy ass old fucking "I don't look into my email" type people. God I hate these "I am in rich country" people.2 -
Getting burn out right now. Filling in for departments with overpaid inadequate talent and poor management, it's driving me up the wall.
-
Open a youtube channel, create some tutorials. Build an audience and launch an unusually expensive course for them to buy.
this YouTuber is not selling course, they are selling dreams to people.
Shame3 -
I got my first developer job three years ago. I’ve always had a great eye for detail, and getting things done while following best practices. I learned that a few years ago from typography, which I think is a fascinating subject, which has a lot of shared ideas with software development.
In my first job, I immediately took a lot more responsibility than what I was assigned to. This job was as a React Developer, but I quickly got into backend development and set up kubernetes clusters, CI/CD.
Looking back, this was to me quite an achievement, considering I had never done anything even remotely close to it.
I did however, work my ass off. 18 hours work days without telling my boss, so only getting paid for 8. Plus I worked weekends.
I did love it. After a while, I got promotes to Senior Developer, and got responsibility for everything technical. I tried asking for help, but everybody else was either a student, or working purely front-end or app-development. Meanwhile, I was Devops, API-design, backend, Ci/CD, handling remote installations (all our customers are Airgapped), customer support, front-end and occasionally app-development when the app-developers could not handle their shit. Basically, I was the goto-guy for every problem, every feature, every fix. I don’t say this to brag.
I recently quit my job, started working as a consultant, because I almost doubled my pay. However the new job is boring as shit. I’m now an overpaid React Developer. And I really hate React. Not because it is shit, but simply because it is boring.
I’m thinking of going back to my old job. It was a lot of work, but it was really interesting. However, after I quit, they have changed their whole stack. No more Golang, Containers, Kubernetes, webRTC and other fun new technologies. Now, it is just plain, PHP without any dependecies. It is both boring, and idiotic. So I’m thinking of just quitting. Either doing some personal projects like game-development. I dont know.