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 - "patronising"
-
Social let's-help-female-programmers warriors piss me off.
The other day a massive email thread at work on how women are misrepresented in tech and how we need to help them and how using words such as "guys" is intimidating and generally patronising shit like "let's advertise jobs on websites like femaleprogrammers.com instead stackoverflow because there's too many white males on stackoverflow."
99% participants in this topic were guys.
One girl sent a message saying she doesn't want to be helped and she wants to know she has been picked for her skill and not filling in diversity numbers.
...would you believe she has been schooled on problems women in tech face by those lads too.
Like "woman, please... we speak diversity here"
So annoying....!!24 -
So my ISP decided it was ok for them to log into my router remotely and re enable the wifi.
I turned it off for a reason and no your excuse that it will improve my upload speed is bullshit you stupid patronising fucking shithead.
I'm now seriously looking into cancelling my service with you because you don't respect your customers or their wishes.
Also I'm guessing there's a default backdoor password into the router as I changed all the passwords I could find. Meaning the whole thing is horribly insecure.11 -
Playing email tennis with a client trying to get to the specifics of a vague initial request. Difficult to do without being patronising and condescending. Having to read and edit my emails to make them believe that I don't think they are a useless fucking incompetent twat.2
-
I fucking hate stupid accountants!
Yesterday we went to a customer to talk to the accountants because we want to remove one of their unused PC's in the office.
First, just the way they think (and talk if) they are the most important and it's absolutely critical everything works 100%. I see they are important but not 100 times more important than everybody else!
They called us their EDP-guys (EDV in German, that's the translation I found). That insulted me a bit. I'm rather called IT-guy, I don't know anything about the fucking EDP systems nor want I to. I'm there to make sure the hardware works. But whatever, fine, call me what you want.
Then they straight up threatened us, because their work is so important, they can't afford to have downtime in their systems. They don't really care, but the bosses of us both do and if we fuck up they (the bosses) will hold us responsible. There is a fucking update for your piece of shit software (datev)! I don't do the update, I'm just responsible that the update can be deployed on the hardware. I'm not responsible if this update fucks your system and frankly I don't care!
I could tell them all of this but they won't listen. They always talk in this patronising arrogant voice, because they are so important and we better don't fuck up the update.
I'm there to help. I don't want downtime for your systems. I want you to work with our systems the best you can.
But fuck you, I hope the server burns down!13 -
Got a senior dev at work.
The guy is good at his job, no doubt, but his insecurity drives me up the wall.
- Constantly double checks work done by non-seniors.
- Setup a policy where only seniors can code review.
- Tells non-seniors not to give out advice as they don't know what they're talking about.
- Edits pull requests for you.
- Demands unobtainable quality for insignificant pieces of work.
- Patronising teams messages on the regular.
We're all just trying to get work done and he's always acting like we haven't got enough stripes on the badge.11 -
I've been working on the ecommerce website from hell for over a year now. I should have heard the alarm bells when the studio who were running the project took a month to pay my deposit but still expected me to start working, but I explained that I wouldn't start without some form of security and they were cool with it, so I carried on.
It started off as a simple build with simple products, no product variations etc and a few links on the designs which appeared to lead to external links, and checkout and cart pages were nowhere to be seen. It wasn't a big money job so I just build them in as plain and straightforward as I could, in line with how the rest of the site looked. They then changed their mind about how they wanted these to look, and added loads of functionality to the site throughout the build, so by the end of the line, the scope of work had completely changed. I also had loads of disagreements in terms of design and useability, as their designs straight-up weren't going to function otherwise, plus every round of changes meant that I had to prolong the job further and fit it around work for other clients.
Fastforward a few more months and I get sent a really angry email with some of the client's complaints, including one that raised an issue with the user journey, and the finger of blame was pointed at me. The user journey had been a part of the designs from the start, and this was never raised as an issue for A WHOLE YEAR. They then said that it had to go live on Monday (three days after they sent email with these huge new structural changes). I told them I could no longer work on the project but was happy to waive the rest of my fee (3/4 of the total fee, when I had essentially completed the site, minus 2 minor bugs), so they could find another developer in the limited time they had. At first they refused to hire another developer, claiming that it would be too expensive, which made no sense, as for a few minor fixes and out of scope additions he could get paid a wage that would have otherwise paid for the majority of the work I had done on the site. I stood my ground and finally they found someone, so I sent over all of the files and database to their new developer and asked him to give me a heads up when I could remove the staging site from my server. The next day, I received an email from the studio asking me to fix some bugs the developer was requesting I fix so he could carry on with the site. They were basically asking me to work more, for free, to enable him to walk off with the majority of the money and do less work. They also forwarded a suuuuuper shitty, condescending email from him, listing all the things he thought was wrong with the site (he even listed 'no favicon' although they'd never supplied a graphic for this). He also wrote a paragraph at the bottom EXPLAINING MY JOB TO ME and telling me:
I get the feeling you like to write Javascript, while being one of the easiest languages to learn, it can also be one of the hardest to master. While I applaud you for writing Vanilla JS, it looks like you have a general problem with structuring your application.
Not sure if I'm being oversensitive here but it felt so patronising, and i couldn't even go for an angry walk to get it out my system because of social distancing lol.
Let a girl quarantine in peace!!!!!!2 -
When you get a freelance dev who thinks he is a superstar dev and he is trying to prove he knows his stuff by throwing his 2 cents at everything and shits all over every architecture and code style decision of the project, even though he is not even familiar with the framework used by the project...1
-
Just remembering that time Britain started clapping for the NHS on a weekly basis, rather than giving them more money.
The longer ago in history this becomes, the more patronising it feels.4 -
Project leader did no work on our project (mainly due to not knowing how to do it), so he dealt with the problem by asking me to explain the entire infrastructure and setup to him five minutes before our call with the Director where he attempted to state all the things that "we" had done.
After his spiel of detail-less crap I explained exactly what was going on, and how I had done it, and the Director seemed far more interested to speak to me.
I'm an intern and the PL has been there full-time for over a year.
I said "I think that meeting went pretty well! He seems happy" after the call and was totally ignored 😂
Intern 1 - 0 Lazy, patronising, rude full-time employee.
TL;DR: If you do fuck all, let the person speak who knows the project inside-out; don't try and get in there first or the hard worker will then go into way more detail than you under to prove their worthiness!1