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 - "coworker"
-
*me and a bored coworker
me: bored as hell dude.
him: i have a fun game in mind.
me: shoot.
him: *brings his keyboard
him: type the string you can type the fastest. we will time it. i will start.
him: *types his name
him: your turn.
me: Scanner scanner = new Scanner(System.in);
him: the fuck is wrong with you?16 -
me: "ah, my scraper is nearly done - just need some final tweaks"
coworker: "JuSt FrOm LoOkInG aT yOuR ScReEn A fEw TiMeS tOdAy, I cAn TeLl YoU iT wOnT wOrK"
me, infuriated by his idiot mentality but not trying to start anything: "ah, its fine, I've already scraped 3000+ entities"
coworker: "but it wont work."
me: "but... its working..."
coworker: "but it won't work."
me: "ok."
sometimes its just better to just affirm the narcessistic assholes. make sure they are right.6 -
I got assigned approximately 20 tasks, all are high priority.
Coworker got assigned 2 tasks, (“like fix button sizes and padding”, “localisation “)
He completed.
I got questioned: “are you sure you are a senior developer? Are you doing your work at all? If your coworker can finish low priority tasks in a day , why you as a senior can’t? “
Me :”if you have the ability to see , please tell me how many tasks I have that are in high priority.”
“Exactly, I need you to complete it now , I expect more from you as a senior. “
Me: “why not you tell me which tasks are higher priority? Because can’t be all are urgent. If everything is urgent , nothing is urgent.”
“Stop giving excuses, be a team player.”
Me :” how is it making excuses for asking urgencies of the tasks?”
“Hahaha you called yourself a senior. What a joke”
Me:”likewise, you called yourself a Project manager yet can’t manage. What a joke indeed.”20 -
So today the Manager told my coworker that "going to the toilet" is an excuse. We all work from home, "eating", "shiting", and anything other than work is considered excuses.
What in the bloody fuckery fuck is this?36 -
Coworker: "can you help me with this thing?"
Me: "sure, what have you tried so far"
Them: "nothing yet"
Hdhajsgrbeiry JUST TRY _SOMETHING_ AT LEAST BEFORE ASKING FOR HELP.
It's literally your job to solve problems, not get other people to solve them for you.
Asking for help if you don't understand something is one thing, but constantly trying to get people to show you exact examples is not doing your job.
This has been a chronic problem with one of our devs and despite advising them multiple times on it, it continues to happen.12 -
Week 278: Most rage-inducing work experience — I’ve got a list saved! At least from the current circle of hell. I might post a few more under this tag later…
TicketA: Do this in locations a-e.
TicketB: Do this in locations e-h.
TicketC: Do this in locations i-k.
Root: There’s actually a-x, but okay. They’re all done.
Product: You didn’t address location e in ticket B! We can’t trust you to do your tickets right. Did you even test this?
Root: Did you check TicketA? It’s in TicketA.
Product guy: It was called out in TicketB! How did you miss it?!
Product guy: (Refuses to respond or speak to me, quite literally ever again.)
Product guy to everyone in private: Don’t trust Root. Don’t give her any tickets.
Product manager to boss: Root doesn’t complete her tickets! We can’t trust her. Don’t give her our tickets.
Product manager to TC: We can’t trust Root. Don’t give her our tickets.
TC: Nobody can trust you! Not even the execs! You need to rebuild your reputation.
Root: Asks coworker a simple question.
Root: Asks again.
Root: nudges them.
Root: Asks again.
Coworker: I’ll respond before tomorrow. (And doesn’t.)
Root: Asks again.
Root: Fine. I’ll figure it out in my own.
TC: Stop making it sound like you don’t have any support from the team!
Root: Asks four people about <feature> they all built.
Everyone: idk
Root: Okay, I’ll figure it out on my own.
TC: Stop making it sound like you don’t have any support from the team!
Root: Mentions multiple meetings to discuss ticket with <Person>.
TC: You called <Person> stupid and useless in front of the whole team! Go apologize!
Root: Tells TC something. Asks a simple question.
Root: Tells TC the same thing. Asks again.
TC: (No response for days.)
TC: Tells me the exact same thing publicly like it’s a revelation and I’m stupid for not knowing.
TC: You don’t communicate well!
Root: Asks who the end user of my ticket is.
Root: Asks Boss.
Root: Asks TC.
Root: Fine, I’ll build it for both.
Root: Asks again in PR.
TC: Derides; doesn’t answer.
Root: Asks again, clearly, with explanation.
TC: Copypastes the derision, still doesn’t answer.
Root: Asks boss.
Boss: Doesn’t answer.
Boss: You need to work on your communication skills.
Root: Mentions asking question about blocker to <Person> and not hearing back. Mentions following up later.
<Person>: Gets offended. Refuses to respond for weeks thereafter.
Root: Hey boss, there’s a ticket for a minor prod issue. Is that higher priority than my current ticket?
Root: Hey, should I switch tickets?
Root: Hey?
Root: … Okay, I’ll just keep on my current one.
Boss: You need to work on your priorities.
Everyone: (Endless circlejerking and drama and tattling)7 -
My most f*cked up client process I ever had to deal with:
Digitalizing E-Mails.
I seriously asked if they were joking on me… Wasn't the case.
The process was: Get E-Mail, print out, scan, archive (digitally).
Nobody could explain to me the necessity for this bullsh*t.
"Hmm... Kinda always worked this way, I guess"
The client was a big company. My coworker aged 5x faster during that project. I swear to god, I'm not joking.16 -
I actively avoided looking at my coworker code because i didnt want to micro manage. God i was so wrong3
-
The code is a freaking mess. Shared behavior, terrible variable/method naming, misleading module naming, dynamic polymorphic spaghetti, whitespace errors, no consistency, confusing even if you understand what the code is doing, ... . It should never have passed code review. It probably wasn't code reviewed.
The comments are sparse and useless. Quality level: // This is bridge.
The documentation does not exist.
Testing steps for QA are missing several steps, including setup, so actually using the feature is bloody challenging. If one thing is wrong, the feature just doesn't show up (and ofc won't tell you why).
The specs for the feature are outdated and cover only 4 of 19+ cases. And are neigh useless for those 4.
The specs for the report I'm fixing don't even check the data on the report; it just checks for one bit of data on each row it creates -- a name -- which is also the same on each row. gg.
The object factories (for specs) are a mess, and often create objects indirectly, or in backwards order with odd post-create overwriting to make things work. Following the factories is a major chore, let alone fixing or extending them.
The new type has practically zero test coverage.
The factory for the new type also only creates one variant -- and does so incorrectly.
And to top it all off: the guy who wrote the feature barely ever responds. If he does, he uses fewer words than my bird knows, then stops responding. I've yet to get a useful answer out of him. (and he apparently communicates just fine, according to my micromanager.)
But "it's just fixing a report; it'll be easy!"
Oh, fuck off.8 -
$work is migrating to a new HR performance review service (15five). Instead of a private (ish) review once a quarter, it'll be public (and uneditable) reviews due every friday. Better make sure that review is perfect.
also, praising a coworker is required.
<sarcastic thumbs-up>13 -
I applaud my coworker who titled the business analytics dashboard showing end user feedback and CES values projected onto the 6 meter high wall of the office lobby.
"International Normalized Customer Effort Score Tracker"9 -
There's this guy who randomly make sexual remarks. Not the usual guy's talk kind sexual remarks, but more of "I am going to rape this girl infront of her boyfriend and her father " kind of remark. Also he sexual harassed women coworker like take video of them in the toilet.
What we did was gathering every rape case possible (which is not related to him, but somehow the victims don't know who the rapists were) , all the evidence of him taking nude video of girls and report to police . We launch the statement that "maybe" the rapist was this phallus.
And the authorities got his arse and tracked. Well he asked for it.
Always remember "with great power of boasting bullshit, comes with a fat shit of consequences". The difference between the actual Spiderman and this phallus is that Spiderman think with his senses and shoot webbings from his wrist, but this phallus don't have any actual thought involve and shoot webbings from his micropenis.
I resigned after that.15 -
Not a coworker, but this guy who I went to uni with and was a real life saver when I was really down. (we played minecraft together)
... So, he is a real genius. One of those guys who I legit couldn't keep up with. His brain works, he doesn't bullshit his way through, he's not pretentious, he is legit a down to earth rare genius. Yet, he doesn't use his talents enough, he likes to work or go home to play minecraft. And he doesn't politically care enough, so I am almost sure that he will end up getting stuck in the defence force.
We're still friends. And I try my hardest to not be nosy and nag at him that he can do better. I mean, he is happy the way he is, and he is not ambitious. But the memory of him is a reminder that not everyone who gets somewhere is the best and brightest.41 -
I've told the same story multiple times but the subject of "painfully incompetent co-worker" just comes up so often.
I have one coworker who never really grew out of the mindset of a college student who just took "Intro to Programming". If a problem couldn't be solved with a textbook solution, then he would waste several weeks struggling with it until eventually someone else would pick up the ticket and finish it in a couple days. And if he found a janky workaround for a problem, he'd consider that problem "solved" and never think about it again.
He lasted less than a year before he quit and went off to get a job somewhere else, leaving the rest of our team to comb through his messy code and fix it. Unfortunately, our team is mostly split across multiple projects and our processes were kind of a mess until recently, so his work was a black box of code that had never been reviewed.
I opened the box and found only despair and regret. He was using deprecated features from older versions of the language to work around language bugs that no longer existed. He overused constants to a ridiculous degree (hundreds of constants, all of which are used exactly once in the entire codebase, stored in a single mutable map variable named "values" because why not). He didn't really seem to understand DRY at all. His code threw warnings in the IDE and had weird errors that were difficult to reproduce because there was just a whole pile of race conditions.
I ended up having to take a figurative hacksaw to it, ripping out huge sections of unnecessary crap and modernizing it to use recent language features to get rid of the deprecation warnings and intermittent errors. And then I went through the same process again for every other project he'd touched.
Good riddance. -
how to become a true scum master:
- formulate jira tasks for your inferiors as vague as possible, best they don't make any sense
- before sprint start, ask the subhuman being to estimate storypoints, and if they say they can't really tell with this description and choose the highest estimate, say "okay, let's estimate it to one sprint length", so they can actually work on it within one sprint (which makes total sense)
- if the scum dares to question the content of the ticket and begs for more details, be like teflon and give no useful answer at all. if they continue asking for a meeting to discuss the ticket, tell them to have a meeting with a coworker about it (who also has no clue). don't be available for them because you have more important stuff to do.
- bully them during daily standups that they didn't create clear subtasks from this task and criticize them because you have no idea what they are doing. tell them they are having performance issues and suspect them to sit on their lazy asses all day.
- criticize the team in general for bad performance, bad item tracking and never say something nice, to make sure everybody loses even the last bit of intrinsic motivation for the project.
stay tuned to learn how to make yourself a skull throne out of those filthy dev smartasses ^.^7 -
We do infra as a code, and one of my coworker worked on the project alone. Few months down the road, when shit hits the fan, he just message me this is not working.
First of all, I did not write that shit, and also I was never part of the conversation during the decision making. So when shit hits the fan what do you expect me to do? Do some black magic and fix it magically???1 -
Just a friendly reminder to fellow developers to take care of yourself.
If your system is constantly pumping out cortisol, even when threats are minor, it gets desensitized to the stress signals. We used to react to cortisol with the fight-or-flight response when our lives were in real danger. Nowadays it's produced when you disagree with your coworker or there's a deadline coming up. So your cortisol rises but you neither fight nor run. The result is a stress response that isn't functioning properly. This is when burnout symptoms develop. Same goes for testosterone, dopamine and some other hormones and neurotransmitters. Read up and start proper work hygiene that includes workouts, fresh air activities and manual hobbies.
Your back, wrists and eyes aren't the only things you have to watch out for when coding long hours. Cheers and have a fun weekend!8 -
So I was talking with a coworker about a difficult situation I had with a manager years ago. It came down to how to interpret the company rules. The issue was about schedules and not being allowed to modify those schedules permanently. Say always leaving at 3pm on Friday every week kind of thing.
It came up because I wanted to work through my lunch to make up an hour. So my manager went pouring through the company rules and found this one phrase "you are not to modify your work schedule on a continuous basis". I was like what does that have to do with me working through lunch. He then told me that would make my work schedule during the day without a break to be a continuous day. Which to him was not allowed. I was flabbergasted at how insane the interpretation was on his part. It was not worth fighting it at the time.
Back to my current coworker. We keep talking for a while and he says to me: Was that manager an adversity hire?
I have been chuckling about this all day.1 -
!Dev
Not all Asians are the SAME. Let me explain, I got a coworker who goes by the name "Lau Dum Fuk" (which I learnt that it is pronounced "loud doom fok"). I was so stupid that I pronounced his name as "Loud Dumb Fuck" very awkward. I am Asian but I pronounced Asian name wrong . Who started with the idea that all Asian are the same?16 -
I created our login system to be secure and reliable.
One coworker hardcoded the roles a person who is logging in receives and built a backend to just assign roles you want. He pushed this to prod...
Yeah...1 -
At this point, I just feel bad for my coworker.
No, I am not frustrated or angry, just feeling terribly bad for her as how difficult life must be for someone so dumb.
We are introducing a new method to track some data in our product, like total number of sign-ups, DAU, etc.
Now the implementation is already WIP and this is known to all.
The dev has documented the approach where he has mapped the screen name, a screenshot, and a snippet of the schema that tracks that particular screen.
I kid you not guys, this coworker somehow landed on that document and started some scientific study to try and extract data.
Yes, she looked at the schema screenshot and spent like few hours trying to decode it to figure out the sign-ups and DAU.
Data via a screenshot in a document. I can't even express it.
And then texts me in panic mode that she isn't able to access the data because the file is . jpeg within a document.
I asked where is she executing the schema, because I thought she is joking initially. She said she doesn't know and asked me where she should execute it.
My mind is numb. Life must be real hard when you are so fucking dumb.21 -
Not ONLY does the new code a coworker wrote straight up not work (and they somehow managed to merge it to master) but it also broke an entirely unrelated endpoint due to an abstraction they tried to make. Very clear they didn't even run their code at all.2
-
In my last rant (https://devrant.com/rants/5523458/...) I regaled you lovely folks of how I had to diplomatically yet firmly defend my work/life boundaries during off-work hours for non-life threatening affairs (a frustratingly common occurrence), and concluded the thread by mentioning that I still had a job, but would make a note of my frustration of that for whatever exit interview happens.
Well, no need for those notes any longer.
I and half of the engineering force, along with several senior managers were laid off this morning in the form of a "mandatory on-site all hands".
I live and work in NYC. Several people took trains and booked rooms from as far away as Boston to be here (or at least I know of specifically two people who commuted up here on Sunday to be here for the "all hands"). I presume those people used their travel benefits to get here and back.
We were dismissed before the meeting even took place, and according to a coworker I became friends with (yes, despite my snarky comments in other threads, I *do* actually have coworkers I became friends with lol) who survived at least this round of layoffs, once the actual all-hands commenced, the company first disclosed the layoffs, then announced being awarded a major contract with the very client the entire org had been working on overdrive to win for the last nine months. He had already been looking for a new job and got an offer last Friday, had been mulling it over, but told me once we were off the phone he was calling them up and accepting. He had three people reporting to him, and lost two. Even he had no idea it was coming until one of his now-former subordinates asked him to come outside and told him they'd just been let go.
I knew going in to this startup that "it's a startup, anything can happen, just mind the gap". That's why I asked on numerous occasions and tried to get time with our CFO to ask about revenue and earnings; things that in my years at this place were never disclosed to the rank and file, I'm not a professional accountant or CPA by any means, but I did take a pair of corporate accounting classes in community college because I like the numbers (see my other rants about leaving the field and becoming a math teacher), and I was really curious to know how the financial health of the business was.
It wasn't so much a red flag as it was an orangish-yellow that no one ever answered those questions, or that the CFO was distant but not necessarily cagey about my requests for his time; other indicators were good while interviewing--they had multiple fully integrated, paying customers (one of which being a former employer from years ago, which aided me in having strong product familiarity during the job interview), but I guess not enough to be sustainable.
Anyway. I'm gonna use the rest of the week to be a bum, might get out of the city and go hang with friends Pittsburgh, eat some hoagies and just vibe for a while. I've got assets and money stashed up to float pretty easily for a while, plus a bit of fun money so losing the job isn't world ending. Generalized anxiety because everything is going to shit worldwide, but that quickly faded into the backdrop of the generalized anxiety I always have because existentialism or something like that.
Thanks for reading. Pay the teachers.5 -
Got a text message from a former coworker who was spared the layoffs from $last_job.
"Go look at the status board, they left it up after the layoffs".
The 99% uptime is now down to 80% and you can practically pick out the exact week when the company laid off half the engineering team.
But hey, they redesigned the homepage and got a new logo.1 -
Coworker: hi
Me: hi
... 3 hours later ...
C: hi
M: how can I help?
...
C: hi
M: HAVE YOU EVER USED COMMUNICATOR IN YOUR ENTIRE LIFE? JUST TELL ME WHAT YOU WANT IN FIRST MESSAGE, DONT WAIT FOR ME TO HI YOU BACK, WHAT THE HELL HOW MANY TIMES A DAY YOU NEED TO GREET ME12 -
!rant Scheduled Slack message from myself after hours to myself during work hours:
“Hey idiot,
The thing you need to do is [solution]. Trust me.
Sincerely,
Past you
PS: Drink some gd water.”
*followed by panicked double-checking I’d actually sent it to myself and not a coworker*2 -
ITT: Best/most professional ways to ask your coworker "What the hell are you thinking?!"
I'll start: "Whats the reasoning behind that?"7 -
Coworker was adversarial from the get. He would always bully me by saying “You better do [BLANK]!” whenever we’d discuss tasks to be done. He eventually pushed my buttons too many times. I responded to his bullying tactic by yelling back, “IF I DON’T, WHAT ARE YOU GOING TO DO ABOUT IT!? Stop bullying me and let’s work TOGETHER on this!” I realize now he was fucking with my head.3
-
When I see a coworker is having their anniversary at my company, I don't know whether to congratulate them or give them my condolences.1
-
It’s been so long since I posted but this time it’s juicy again.
I got a coworker, no prio experience but already a year and few months into the job. He’s bad.
Magnitudes of bad!
We’re trying to teach him but to no avail. Everything about him sucks, major ballsack to be exact.
His attitude is to avoid every task, finishes nothing and then starts something new.
„Did you do X like we told you to?“
„No I started on Y, because I thought it [looks better, seems more interesting, thought that X is useless…]“
When you ask him much is done he is always „almost“ finished and needs your help on the „last 5-10%“. Yeah fuck that!
But that guy has a talent, his talent is to always give you technically correct answers which actually are complete bullshit.
„What are you doing at your job?“
„Staring at a screen and typing things.“ dude what?
That guy used the excuse „I can’t do maths“ on everything.
For an exam he had to calculate how long it would take to reach a certain amount if you would get some interest in that every year.
He asked the teacher for the formula. During the exam! And when the teacher didn’t want to give it to him he wrote plainly „can’t do maths“ on the paper and left
His code is of a quality as if he would write his first line in a week and then has the audacity to blame me and the colleagues for not explaining it right.
Ok you might think now we’re teaching him bad, or are too impatient. But honestly if you have to explain how to do a for loop for over about 15 months and get that attitude I think you get the right to be angry. I don’t mind explaining on how things work, even for the hundredth time, but then don’t tell me you understood, go behind my back, complain at a colleague how bad I explained, get explained by him and then do it again until you whored yourself through the whole staff!
It’s like he got the mind swiper from Men in black at home. Every day he hits the reset button.
He had a week of just changing indentation on a html file. Why? Because he wanted to find his style.
Yeah his style
if(a==b){
console.log(a);
}
else {
console.log(b)
}
And to produce code like that it takes him atleast 4 hours of trial and error.
And at the same time he goes arround and boasts what a super good programmer he his and that he can do some project work for them.
How we found out? Because he started working in those projects during work time at the office and asked us how to do things.
And he does so like a complete bastard!
Broken sql query? “No that query is perfect as it is, it’s supposed to show no results! But, just in theory, if I wanted to show some results, what would I need to change?”
I’m so mad about it and pissed on a personal level because he goes around blames everyone and the world for his short comings8 -
My coworker became super restless and incompetent during the initial 2020 Covid lockdown. Like playing hours of video games during work hours restless.
For one project, my coworker was working on the backend and I was working frontend. Coworker also wanted to be overlord of the epic branch.
My coworker merges the epic to our test branch and our code is broken. Coworker didn’t pull my FE changes before merging. Dude, I shouldn’t have needed to tell you to pull. You changed the api response that your BE code delivers so of course I had to update my FE code so it could work with this change.
I had to resolve the conflicts because coworker left work early to “rescue/pickup” their girlfriend from work.
You bet I leave this person on read when they try to text me on Signal1 -
I can't believe this happened. I thought i would never witness this. A coworker dropped the entire production database. And no backups because its the first day, were way past beyond the deadline and no one thought we would need it this soon. Now we manually have to enter the entire backlog. He was supposed to delete just one tables rows. Im amazed by how dumb he is. How much trust we put in that we wouldnt fuck up the database this soon if at all in this way. Im beyond words. I am so glad im leaving this place at the end of the month. Hes so lucky i will never see him again after that.5
-
Coworker who mostly works from home: "Who took my keyboard?"
Me: "Someone needed it for testing yesterday. It's over there"
Coworker: "Why does it always have to be my stuff when I'm not around"9 -
them: welcome new project members, this is our CI/CD pipeline which is completely different from the rest of the company, there won't be any great knowledge transfer, we just expect you to be able to know and use everything. but also, we expect you to work on your tasks and don't waste any time.
me: okay, so my tasks aren't going as fast as expected, because I need to invest some learning so i can set up my project correctly.
later: some help would be nice, i'm stuck right now
coworker: *helps me to fix my problems, which were partly due to misconfigured build servers* i know it's a lot, and unfortunately, for this topic sources on the web aren't so good. i can really recommend this book, this will give a deeper understanding of the topic.
me: okay, yeah i mean, tbh, i'll read the book if the project invests some time for me so i can learn everything that's required, but this won't happen. also, some initial workshop on the topic or anything would have been nice.
coworker: well, i mean, i am a software developer. for me, it is normal that i learn all that stuff in my free time. and i think that's what the PM expects from us.
me: okay, that's fine for you, i mean, if i'm interested in a topic, i will invest my private time. but in this case, PM would just expect me to do unpaid labor, to gain knowledge and skills that i can use in this specific project. i'm not willing to do that.
coworker: ...
me: ...
it's not that i don't want to learn. the thing is that there isn't any energy left by the end of the day. i'm actually trying to find some work life balance, because i don't feel balanced right now, haven't felt since i started this job.
also, this is only one of several projects i'm working on. it's like they expect me this project has top priority in my life. if it wasn't so annoying on different levels, maybe i'd have a more positive attitude towards it.
also, at the moment i find it fucking annoying that i have to invest so much time in this dev ops bullshit and this keeps me from doing my actual work.
if they are unhappy with my skills, either they can invest in my learning or kick me out. at this point, either is fine for me..12 -
A few months a couple of my colleagues, a business consultant and a developer, worked on a big project. The project capsized because the client is an A-hole and the developer was way over his head.
To save the project I was brought on board. The entire code base was a fucking mess of duplicated code. Shortly after, the developer called in sick with stress, simply because the whole thing was too much.
Fast forward to now; we just launched. The client is expressing concerns about the quality of the work because of the bumpy road (rightly so). I try to explain why my way of doing things is better, but to "paint the picture" I had to compare my approach to my predecessor. This results in the business consultant shooting me down, right in front of the client.
I fucking saved your job, your project, and about $1M in profits. I'm allowed to tell the story of why my incompetent coworker messed everything up.
I'm so done walking on egg shells because some just don't realize they are not cut out for software development.2 -
I share a large room with a coworker who incessantly burps.
And I do mean incessantly.
I normally keep my ear buds in to override the sound, but I swear to god if I take them out, in as little as 5-10 seconds he'll let out another one.
God grant me grace.5 -
So, I got this new coworker of mine, he's 5 years older than me and says he's got a loooot of experience with html, css und javascript. Nice. Boss wants us to blur some text on a website, I show him how to do it with css "filter: blur(4px)".
5 minutes later he's all proud and says "done". I think nice, check the code - and see this moron having put an <img> png in there, having blurred the text with photoshop. Short memory, anyone?2 -
Honestly, I think this one is yet to come for me.
I've had a few bad experiences, but the worst ones are the ones where I couldn't find the time or brain to get some work done properly and therefore did bare minimum, so I basically was driven to shame because my teammates did almost everything.
Second to that, are times where I had to go through drama because teammates were absolutely incompetent or power hungry or inflexible.
Otherwise, it's "live and let die".
Note: I use "teammate" in general sense, equaling "coworker", "colleague", "the guy who's supposed to give me details or access" and "those in on the project" in this rant.2 -
I hate people who think they are always right.
A coworker who seemed to be a friend turns out to be an emotionally needy narcissist who seems to think that he is a perfect human being and is the best example of how to live.
Long story short is that we did some bonding via alcohol and smoking cigarettes. Especially when I was in a bad period in my life where I had little self confidence, was in a bad financial situation and overshared many details abound my personal life.
And yeah we also work as software devs in the same team but I started avoiding working with him directly, because due to his seniority he overcomplicates things a lot to the point where stuff gets postponed for months. Meanwhile I am a simple guy, I do my tasks and if they are not up to the standard I just work on the feedback until Im up to the standard, thats it. Its just a job for me, for him its a way of life and he considers himself to be basically an artist.
Hes always trying to prove me something, showing that the "long way" is the best way and so on. In reality I dont give a fuck about him. I live my own life and I have my own priorities. I work fulltime in one job, also I work part time as a freelancer and in total I make about 20 percent more than he does. Previously before this job I owned my own company where for 2 years I ran my own projects which generated a decent revenue. I know what is hard work and how to sacrifice myself in order to achieve results. I am more pragmatic and I have some limitations of what I can be good at (since I have a shitty working memory due to my ADHD). So I have systems in place and bottom line is that I earn a decent living and my skillset is different. Yeah I agree that in some ways he is better than me, but dude has such a massive inflated ego that now he thinks that he unlocked some sort of universal wisdom and now hes suddenly experienced in every field of life and his opinion is the right one.
This guy takes a massive pride in how good software engineer he is and in every topic or interaction he tries to one up me. Which most of the time is just his preference or in order to gain a 0.0001 percent performance increase. Dude is basically a big walking ego and since "we are close now" his ego started bleeding into personal relationship.
In my personal life, Im in a stable relationship, thinking of proposing soon and getting married. I already co-own an apartment with my current girlfriend. Everything is serious and planned, Im soon to be 30 years old. He is the same age but he still thinks hes young hot shit and all he cares about is getting shitfaced a couple times a week after work and he doesnt really have any other hobbies. He has a girlfriend but I dont see any future in there TBH.
So what I did now is I started putting some distance between us. No more drinking every week with him, maybe maximum once in 2 or 3 weeks. I started working from home more. Also I stopped sharing my personal life with him. Each time when he thinks he is right I just go along with it and dont even pay attention to his emotional manipulations. I just hope one day he fucks off completely and I wont give in to his gaslighting. Maybe in a few months I will be leaving this job, so I will never have to deal with him again.
Lesson learned: dont be vulnerable to coworkers who you bond together only via alcohol.3 -
Have you ever encountered a situation like this before?
You worked in a team, made many adjustments in the codebase, and all the changes you've made are the best practice (after some research or asking the community).
But the team leader decided to go with the "messy" version of the code and the team leader does adjust the principle of "bad code" in favour of your coworker, just because he/she is a friend of the team leader.
So, whatever you adjust or contribute is simply nullified but any adjustments made by your coworker are considered "new updates".5 -
All of those painfully incompetent coworker stories I could share are mostly about me, if I’m being honest. Most of the people I’ve worked with have been much more talented than I was.2
-
Just had a discussion with a coworker. I noticed he was storing dates as string in mongodb, saying it was better for comparison and because he stored them in UTC. WTH, mongo already stores all dates in UTC and a string date is imposible to compare. I wasted 8 hours finding that last part out.6
-
One of my coworker change the code from
```
void foo() {
if (condition)
{
}
else
{
}
}
```
to
```
condition ? ifTrue : ifFalse;
```
and add it to changelog
```
- fix bugs // yes with an "s"
- feature added
- some list of the bug fixed.
```
I refer back to the commit, only one Fucking commit and on changes. Bro, what the fuck?8 -
Me: I just know there's gotta be a better way to do this.
PM: No I think it's just a problem of inexperience. You and $coworker just haven't spent enough time in WordPress.
Me: no you're right. I'm just trying to get a better handle on the code and make things as less error prone as possible.
PM: well we really don't have very many errors.
Me: wait, what about the (list off other issues)?
PM: those all have been resolved already.
Me: Oh. Ok. I guess it's just me.
PM: See, I make changes and nothing breaks. You guys just need to continue working on this.
Me: ... 🤨
Me: (weird flex but ok) hey! Look at this guy over here!
PM: (Laughs)3 -
Currently at my work they are making everyone assist to the office at least 1 day of the week, some people live in other cities, there is even one coworker that has to take a flight once a month. We don't even do anything different on the office, same work, nobody likes to come.4
-
Friday, forced deploy day for last & current months work. Been stockpiled due to holiday.
Yesterday boss demoed the product to clients so they expect to test today.
Early o'fuck this morning, a coworker managed to drop all secrets and env vars from CI pipelines and trigger a deploy leaving production broken...
It's gonna be a long and busy Friday... -
As a keyboard enthusiast I can’t help but cringe when my coworker slaps and slams down on his 10 year old gross disgusting Logitech membrane keyboard.7
-
I wish I would have picked faster shipping for my first mechanical keyboard I ordered this weekend... The wait is killing me and I have to wait a whole week until it comes in lol. Hurry up Fedex! I need to annoy a coworker.
-
Why comment on the same thing during code review??
I submitted a PR and had to make a design choice that propagated throughout the module i was working on.
During code review, my coworker commented on every...single...line that this change effected asking "why are we doing x here?" instead of just creating ONE SINGLE THREAD with this question for discussion. There were at least 10 review comments on github from their one review that said "why X?"
Is this normal? Ive only had a few programming jobs and this is the first time this has happened to me.
personally, when someone makes a choice like that, i just make a comment and save the rest of the review until that is addressed.6 -
I hate these Mondays. You start really motivated after a nice weekend of seeing lots of old friends, but instead of your own work, you have to pick up the mess a coworker left for you while fleeing into holiday and because that's not frustrating enough, you try to review code from that new senior developer and get confronted with the probably most awful commit history someone ever managed to create.
Of course he also needed handholding and multiple trys to stop breaking like every coding convention we have for branch management...
I am still a junior and I feel pretty disappointed when being confronted with people being so..confused with stuff like git even though they have like 10 years of experience.
While I was still studying, I somehow imagined this industry to be much more...sophisticated?2 -
Do some of you somehow internalize the rants of people here and wonder if your workmates feel the same?
Or have you encountered someone rant about a coworker but that’s also something you do/did and now you wonder if your workmates think the same about you?5 -
the gross feeling when
you and your friend both leave your company which pays poorly
then an old coworker tells you they've hired 3 new people
this feels worse than hearing about your ex doing well after you broke up, for some reason4 -
!rant
Good Morning! (it's morning here in my area) My coworker gave a good word today "Don't work for an arsehole until forgot to work for yourself" and "Working for a company who under appreciate you is like having sex with a zombie , the more you remain inside, the more part of your penis disappear"
hahahahaaha and today is his last day..6 -
What to do when you want to strangle a coworker, but he is probably just trying to do his job, the way he thinks , is the right way to do it ?3
-
If u you don’t have empathy towards me as a coworker, you are my enemy and I will laugh at your failure and defeat.5
-
me: builds a python-script to transport data in .json-format into a config-file written in .xml for a coworker
my boss: "I am glad you have earned yourself a reputation as the 'programmer' in our team" -
how to deal with toxic coworker? everybody hate him, he hates everybody, but this piece of shit is only backend guy here. and I need to create tasks for him. so cant really ignore.9
-
when your coworker wants help on something but they can't seem to explain the problem or you fail to understand them explaining the problem
also not sure if i had to show them how to set a debugger breakpoint in the web browser debugger
fml1 -
So a coworker is having a conversation about travel:
Ted: I need a microwave in my room so I can cook food.
Coordinator: Okay, we can try and arrange that.
They finish talking about a couple of things. Coordinator is walking out of room.
Me (loudly): Cat's not gonna cook itself!
Ted: <nervous laughing>1 -
When my client asks my team for a simple script and my coworker spends an entire sprint writing a C++ application and complaining about how difficult it is.1
-
Am I right? Is this micro management?
So, in my new team, I have another coworker is my buddy, we are same level and I doubt here coding techniques as I have seen very bad code written by her.
The thing is, whenever I need to pick up a new jira, she starts telling me what code I need to change, without me understanding the ticket or the code.
She forced a code change which was obviously a bad one.
She asked me what did I do yesterday and said that I could have worked on this jira.
Although this is a start but I don't want yo waste my time working with someone who is trying to micromanage when I clearly have the potential to be working without her micro-managemnt.
The problem I see is that her priority is not learning but I don't know what is that but she worked on the tasks which are clearly not our teams work, in the initial informal chat she was too concerned with people being young in the company like who is married who is not etc.
I don't see her as a good developer.
Should I move to other project? or am I overreacting?7 -
Me: What algorithm prioritizes food no matter how you use it?
Coworker: Idk, never heard of that one.
Me: Bread-First-Search1 -
!rant .
Interesting conversation between coworker 1, 2 and 3.
1 : “ hey do you know if you want to sounds like Australians , start eating spiders. Alternatively you can try to eat kiwi to sound familiar to Australian but isn’t.
2 : “ I fancy myself sugary juices and burgers everyday, but yet I am not becoming American.”
1: “No pal you should start drinking petroleum and yell FREEDOM and ‘this is my right!’ every chances you get. That’s how you become a US citizen without the green card .”
3: “bro, you are taking you are what you eat too literally and stereotypically. Let say if you guys would to suck my dick and drain my semen down your throat, won’t me you my son . But I will get the pleasure.”
John : “Yo what the fuck?”
3: “the real question is ‘yo wanna fuck?’”
1 :”you sus bro”
2: “I’m going to pretend I didn’t read that one .”
John :” 1, which ‘you’ you are referring to? 2, of course you didn’t with that amount of sugary juices.”
2: “hey this is my right!”
John: *mute the off-topic channel *
Yo like what the fuck .14 -
Did someone already thought about how color highlight can be better? It's been 4-5 years now that I'm coding on a virtual console that run on iPad with a monochrome code editor. Despite the fact that's remind me the old days when I was 8 years old, that doesn't stop me for coding with it.
I mean, is it really important to know that strings are red and numbers are yellow? How does that help me? They are both literal and behave to the user-content categories.
I was talking with my friend, and he says he likes to know if something is a keyword or an identifier. In C++, a lot of common keywords to define stuff and control the flow are often the first word and easy to spot.
A couple of months ago, I tried Flutter, and the editor can highlight ident blocks and give them different colors, but with Flutter, it's easy to get 10 or more ident levels, Does the color help? Splitting the code does.
I think, there is so much stuff that is more important than coloring the grammar of a language. For instance: knowing if an identifier belongs to which Rust Crate because, It's easy to stack 10 or more dependencies in one file that as better chances of names collisions.
Knowing if an identifier was recognized, if it used, if it's a local, a member, a global, a compiled value or a macro seems more important.
I would like to color block of code that is important or sensible. That will help my coworker about the severity of a particular place in the code.
What do you think?1 -
[ Thread ]
👇
Let's share what psychology tricks you used on your coworker when working for a team?
👇
👇
👇
👇
👇
👇8 -
"Good job coworker X for making a hotfix, that fixed crashes".
I don't get it. Poor code, no tests, bad QA and at the end of the day people get praised for fixing the crash. Cool, I guess I know how you get promoted.6 -
My best coworker was probably my last boss and team. We always were able to help each other out when needed and really worked as a team. It was great except no one worked onsite so it's not like we could go get drinks or lunch.
-
Was asked to do a peer review on a coworker who I barely worked with. When I say barely, it’s like maybe 1 hour out of 8760 hours in a year.
Can I just ask them what to write?2 -
People all over the world own dogs as pets. In some places in the world people eat dogs.
Is it okay to feed your pet dog the scraps left over from eating dog?
I also pointed out to a coworker that New York has huge rats. I then said: "street steak".
The response was: "Why?!"2