How do you deal with quiet quitters that quit before they even started?
Posted by tinmanjk@reddit | ExperiencedDevs | View on Reddit | 280 comments
In a new company, new team. Have a colleague who's done ZERO actual work and manages to somehow fly under the radar. I know for sure that it's the case.
Should I tell anybody and get myself into some situation or just lay low and let people find out for themselves?
AdeptMasterpiece7054@reddit
Don’t mess with other people’s livelihood, that’s a good way to make an enemy for life.
badbog42@reddit
Maybe they’re one of those devs that do nothing then push a 300 ‘WIP’ commits that completely rewrite the core functionality and implement their own take on beat practices?
Adorable-Advisor-469@reddit
Plot twist: It's the company owner that loves lurking around developers.
iComplainAbtVal@reddit
The best advice I can give you is to worry about yourself. You’re different people with different circumstances and the world is not fair. You might find yourself in their position eventually but for now you have to grind. Ratting on him won’t improve your teams output or make yourself look good.
I’m sorry man, but it’s best to let it go.
Square_Baker_5460@reddit
This is insecurity , focus on your own work and watch that guy not get promoted and stay at that job for years and eventually get fired
Mystic-Sapphire@reddit
Why are you so focused on someone else? My advice is to just stay out of this.
skwyckl@reddit
Does it impact your work? Why are you burning so hard for being a snitch?
rubyruy@reddit
Some people are just assigned cop at birth
NoobInvestor86@reddit
Dev Karen, Hello
danielt1263@reddit
Here's the thing... If you know that by whatever analytics you are using, then your colleague's manager knows it too. Likely they know even more considering the probably have access to analytics tools you don't.
EmbarrassedSeason420@reddit
Mind your own business, genius!
lordnacho666@reddit
You may want to find out why nothing's been done before you try to crucify the guy. Maybe he's just finished something recently, maybe he's planning something, maybe he's going through some personal issue.
If you just go straight for getting him reported, you may run into people who are understanding of his situation and don't appreciate you trying to knife him.
You might also find a way where you can do nothing and get paid as well. Wouldn't that be better for everyone?
DestinTheLion@reddit
He should just, not try to crucify the guy? Is he like a shareholder?
ToughAd4902@reddit
It looks bad on the team as a whole and can limit actual dev resources being allocated to a team, that might actually need them, this take doesn't make sense.
FetaMight@reddit
Ugh. It might do a lot of things. or it might not.
Rather than act rashly based on an imagined threat how about properly assessing the situation first?
Itsmedudeman@reddit
Being professional is about delivering what you’re paid to do. Why do I need to do mental gymnastics to give him a million excuses?
BeerInMyButt@reddit
Flip the question: why do you need to go out of your way to light someone up when you aren’t even 100% sure it’s warranted? Is it loyalty to the company? Is it a sense of fairness that you’re trying to protect? Maybe look into that and the need to tattle will feel less urgent and perhaps a bit embarrassing. (Speaking from experience)
Itsmedudeman@reddit
Maybe because 99% of other hires don't do that? Like do you guys just work with a bunch of idiots?
BeerInMyButt@reddit
Does this explain the motivation to take it into one’s own hands to fix it? I’m suggesting introspection
ToughAd4902@reddit
I never said you shouldn't do your due diligence, or to act rashly, anywhere in my statement. I also don't think if it affects your team it's a "well his manager isn't doing anything so I shouldn't" situation.
My team is under constant pressure and any more amount of devs I could get, would help massively, but we are paid very well because of this. If I saw one of my teammates was doing literally nothing, and I could truely know that (none of these imagined situations that some people in this thread are coming up of of literally any dev - ever - not doing a commit in months), I will 100% sell you out as you are directly affecting me.
phil-nie@reddit
Does your company not grant RSUs, or options if it is not public?
Different_Pain_1318@reddit
go and check how employees at your local apple store work as you have 1 share + 0.1 thought index funds
caret_and_stick@reddit
What kind of dream world is this, where the assumption is people have a stake in their own company?
phil-nie@reddit
Like… every major tech company? Every startup offers options even if they mostly end up being worthless.
DrShocker@reddit
While it's true that stick incentives are common in the software industry, it's definitely by far not ubiquitous.
oldDotredditisbetter@reddit
new season of UNDERCOVER BOSS
Existential_Owl@reddit
brand new series CAPTAIN CAPITALISM a superhero who will ensure maximum output at. any. cost.
DEBob@reddit
They might work across teams or on more than one project. Multiple JIRA boards if they're unlucky like one of my coworkers.
evacygre@reddit
Jesus Christ, you just started at this job and are already thinking of inserting yourself in drama? You don't even know the dynamics of the team yet. You might be wrong that he is not doing ANY work. But let's say you are right and he doesn't produce anything.. you have no idea what the dynamics are, there might be a reason they keep him there. He might be the boss' favorite or it might even be nepotism. You might end up causing trouble to yourself. You are at a new place, the first few months just try to gauge the situation and the dynamics of the company and the team and mind your own business.
srlguitarist@reddit
Exactly and it could be a case where he’s built the entire system with his two hands and has been there since the beginning and he has so much domain knowledge that when STHF, he’s the one you want
wantAdvice13@reddit
That’s not what quiet quitting means. Please google the term.
ghostwilliz@reddit
Just don't worry about it. Do you. Also, if he gets fired, you can have my resume, I'll gladly take his place
salty_cluck@reddit
> In a new company, new team.
You should focus on settling into this new company and doing what you were hired for. Why would you want to purposely place yourself in a situation to cause drama when you've just started the job?
-town-drunk-@reddit
Or how do they really know what this person is or isn’t doing?
Stay in your lane unless you are responsible for this person’s output.
Adept_Carpet@reddit
If the other employee is new, they may be awaiting assignment.
Also, consider what may happen if you succeed in exposing this person.
"Wow, we just discovered one of our devs went a year without doing any actual work. We can't let this happen again, please tell IT to install activity tracking software on all machines and require everyone to log any occasion they are away from their keyboard for more than 5 minutes."
secondhandschnitzel@reddit
This. I worked a place where they discovered this after a layoff. The CEO mandated every team had performance metrics. So we got a spreadsheet of PRs per person and code reviews per person. Not great.
signedupjusttodothis@reddit
Once took a job with an MSP-like shop (wasn't full blown managed services but they copied/cargo-culted a lot of the worst practices from some of the worst MSP's I worked at early in my career) and got assigned as one of my first tasks to pair program a reporting tool for one of our telecom customers.
Sparing a lot of details: we delivered to the customer on time, in scope and with very minimal quality of life revisions requested, and a week later I've got one of the owners asking why my contribs had such fewer lines of code compared to the other developer, the senior guy on the project.
Not much luck explaining that my feature simply had fewer requirements and less complexity, or that it passed code review by the senior and the customer's engineering team. Somewhere someone got the impression that my fewer lines of code meant I wasn't actually doing any work, and we began having to report on said LoC.
I didn't stay long there.
secondhandschnitzel@reddit
Exactly. Fewer lines is usually more work and more impressive.
hobbycollector@reddit
We have a regular all-hands meeting (100% remote). At one such meeting one of the devs was recognized for the amount of code he had deleted that week.
secondhandschnitzel@reddit
That is glorious.
signedupjusttodothis@reddit
Fewer lines certainly can be more impressive, but I'll take readable code over clever code every time, every day.
I get what you mean, though.
secondhandschnitzel@reddit
Yeah. Not that “look at how smart I am code.”
The stuff that doesn’t have more than it needs and got the abstractions right.
signedupjusttodothis@reddit
I like my code how I like my Jeeps.
Just Enough Essential Properties, lol.
lennarn@reddit
That's when you start making things overly complicated and exceeding everyone's LoC counts
Recent-Blackberry317@reddit
Nothing screams completely out of touch management more than LoC metrics
gajop@reddit
Doing nothing for 3 months is insane, their manager should be fired along with them. Not OPs job, I agree..
I do check up on people who haven't sent PRs in a few weeks. Especially with juniors, I don't want to deal with 1000 files changed mega PRs that might be going in the wrong direction anyway.
Kagura_Gintama@reddit
So the argument against it so in case you need to duck accountability u should ignore it instead of everyone holding everyone else accountable
GreenMario420HellYea@reddit
And chances are word would get out about who exposed them. I know I would never trust that person, even if I'm not slacking off.
ZealousidealLaw793@reddit
This! How do you know he’s not working on multiple projects?
biosc1@reddit
Some weeks, I look like I don't do a lot of work because I don't commit a lot of code. What I am doing is having a bunch of client/internal meetings and doing dev research for proposals.
OP may be too focused on specific metrics when they may not see the work these folks are doing because there is no quantitative metric they have access to.
Careful_Ad_9077@reddit
Once I spent a few months without coding.
I spent that time fire fixing a super botched release.
Fixing the content of the sdatabase, runing and creating querries for that end, logging everything that went wrong, finding contradictory requirements that flew thru the development team, etc..
Far-Consideration939@reddit
Fixing database contents without code, even one off scripts, seems like poor practice generally.
Careful_Ad_9077@reddit
Definitely, the place was a mess. It was not my problem, that was not even their biggest problem (or even in the top 10).
TimeToSellNVDA@reddit
If you are a senior engineer, you are indirectly reponsible for the output from other more junior programmers.
Subtle semantic difference - you are responsible for their output, you may/may not be responsible for ZERO output, unless it affects your project - in which case you ARE responsible.
endurbro420@reddit
Seriously. We see this same type of post often and all it does is highlight the inexperience of some people. Some of us push very little code but have our hands in a ton of different projects. Being the “magician” who is called into save the day comes at the expense of not just closing tickets like the rest of the team.
tittywagon@reddit
It shows inexperience but sometimes people get away with doing almost nothing. It’s common. If that’s true the manager knows. It’s likely obvious.
canadian_webdev@reddit
Bro wants to be a tattle tale
Forward_Thrust963@reddit
"Mrs. Smith, you almost forgot to collect our homework!"
- OP in 5th grade, probably,
dual__88@reddit
I mean if you made your homework, can't let that go to waste
BeerInMyButt@reddit
Big picture
a_library_socialist@reddit
Seriously, this person just shows that sometimes we need more bullying.
HRApprovedUsername@reddit
Bro should ask the manager if there’s any homework for today
Disastrous_One_7357@reddit
OP should focus on jerking off as much as his coworkers.
Kaizen321@reddit
This.
OP, in mean this in the best way, mind your business and do YOUR job.
You do you, that’s it.
Team stuff doesn’t sound like being under your responsibility as a teammate. It sounds like the manager job.
Source: was in similar stop. Guess what? Two underperforming jrs have a job and I don’t (various other reasons also). Looking back if I had minded my own damn business, I’d saved my time and mental energy to focus on my own performance
sir_clifford_clavin@reddit
I agree, but to clarify.. it's shitty, but you often have to mind to politics before doing what's actually good for the team/company.
Kaizen321@reddit
Aye, I feel you.
I’ve been around the block. I’ve been in awesome kick ass highly performance teams and the opposite of that.
My hindsight is the same: worry about yourself. Be a good team mate. Say you can help anyone needing help. If no one needs help, next ticket or task etc.
End of day it is a job. We fail and succeed as a team but performance is always individual.
PothosEchoNiner@reddit
Is it new for OP or just their coworker? The language is ambiguous
aa-b@reddit
Agreed, though one part of that is understanding the process of the team that you've joined. It seems strange to assign so many stories to one dev at a time regardless of their productivity, doesn't really fit either a Scrum or Kanban process. Assigning stories like that usually blocks them because devs don't like to take work away from others without good reason. Are they part of a sprint or in the backlog? Something unique about them?
OP, you should talk to your lead dev or tech lead and try to understand how and when stories are assigned to team member. Your question implies you don't really understand your team's process. If you and other dev have similar roles, suggest tagging stories by role/area instead of assigning, because over-assigning work can cause stress and burnout
TpOnReddit@reddit
Ya he might not even have access to all the repo's lol
FistThePooper6969@reddit
OP wants a target on their back
chaitanyathengdi@reddit
I've done this (in college, not the workplace) and regretted it big time.
No one likes a rat.
JohnDillermand2@reddit
Let them be your mine canary. In a small place, it's impossible for this to not be noticed. Let it roll, see how the company reacts and manages. Sometimes these things just take a while so the company isn't inviting a lawsuit... And sometimes it's just not a well run company.
Shark8MyToeOff@reddit
I call these type of people canaries also 😂
Crazy-Willingness951@reddit
Agree, it's the supervisor's job to monitor performance of individual contributors.
AdministrativeHost15@reddit
Promote them to manager so it will free up headcount for a real dev.
tinmanjk@reddit (OP)
unironically I believe he has some management experience :)
AdministrativeHost15@reddit
Program Manager or Scrum Master might also be match for their skills
EchidnaMore1839@reddit
Unless his lack of work is negatively affecting your day to day, don't get involved.
Our titled Tech Lead for the whole Web Team does fuck-all, but it makes no impact on what I do so I don't care. I don't want the job. Good for him for coasting into it.
_kashew_12@reddit
Out perform him then, the bar is on the floor. Once you do that, people who start noticing why he hasn’t gotten shit done
Different_Pain_1318@reddit
Dev who does 0 work is still better than a dev who thinks he is a manager and knows everything better
GongtingLover@reddit
Can you fire him or tell your manager? As a manager I would have fired this guy by now.
When people perform like this, it's awful for team morale.
tinmanjk@reddit (OP)
yeah, I feel automatically less motivated to do any work when I see this happening. Have to fight this urge and overcompensate to actually get something done.
fmae1@reddit
I think you're not being affected by that. Focus on your tasks, you're not losing money because of your colleague. Commits are a bad metric and you're also wasting time checking other people's branches.
heseov@reddit
I find it so strange that devs are so against reporting this person. If this person was my teammate then that means more work for me. Why would I want that? I don't want to get taken advantage of just because the manager is clueless. Even if the person wasn't directly on my team then he's taking away the opportunity for an actual good dev to be working with our company. I think everyone has a stick it to the company mind set but having someone draining resources hurts you, even indirectly.
im-a-guy-like-me@reddit
I don't think I've committed code in a couple of weeks. I'm running 5 applications for one company and maybe another 5 spread out over different clients, and i have 4 direct reports currently.
Am I working?
lab-gone-wrong@reddit
In my experience, he's doing work and you don't see it so you adopt dumb media narratives like quiet quitting instead of just doing your own work.
Scared-Ad-5173@reddit
10 years of experience and nothing to show for it. Sad.
Dark-magician-2203@reddit
Are you a team lead? If no, why don’t you just focus on your own work, you know the one you were hired for, instead of worrying about what others are doing? You just joined this company/team and you already trying to snitch on others? That’s a bit childish. If I were you I’d stay in my lane and do my work
SituationSoap@reddit
The short and unfortunate answer is that you won't get good feedback here about dealing with under-performing colleagues because this subreddit has a serious hangup about the idea of under-performing employees ever being held accountable.
Various_Mobile4767@reddit
Not just this subreddit. Its pretty common across all the job subreddits. Hmm wonder why lol.
SituationSoap@reddit
That's a fair point, actually. And your subtext is spot on.
tinmanjk@reddit (OP)
yeah, didn't think that was the case. Came a bit of as a shock. I guess management can sometimes be correct about devs... at least I understand them better now WHY they implement a bit too controlling practices. It's not for me and other responsible devs but for the not so negligible amount of devs who just plain abuse the system.
appoloman@reddit
I'll echo the advice that you shouldn't stir the pot early into a new start, although I do sympathize, I've been in this situation before. People saying to mind your own business must know it's not always that simple when it's someone on your own team.
Maybe I have high standards, but I need my team members to be performing and to be reliable. This isn't some assembly line job where someone else's work doesn't effect mine, it's a team.
Take a look at your manager, do they see the problem, are they sticking their head in the sand? Hopefully you have regular 1:1's, raise it there. Think especially if there are any tangible effects on your work. To give an example, I have had team-members unable to deliver documentation necessary to progress projects I was running, and have even had external teams reach out to me personally when they couldn't progress something with the other team member, which took up my time and also meant I had to play reputational damage control.
If you don't have any examples like this, then perhaps consider if you're merely annoyed that they're not working as hard as you. If that's the case, save it for annual 360 reviews.
lalalapomme@reddit
Ho they hired John? Say hi from me. Also, I would be careful because if John is doing it like usual: you will report to him and he wont have to see a terminal ever again in the next few month. He's just prepping.
Ballbag94@reddit
A lack of commits doesn't mean they aren't working, volume of commits is a dumb metric to judge
They could be in meetings, they could be mentoring junior devs, they could be designing layouts, they could be building POCs, all of those things are possibilities that are likely higher priority that fixing the bugs that have been assigned to them
progmakerlt@reddit
Do the actual work you're hired for. If you're a new guy in the company, the last thing you wanna be known for is conflicts. Regardless if you're right or wrong.
If there is a colleague who does zero work, that's not your problem (unless you're a manager, that is). Build your own reputation, do the actual work you're hired for.
Eventually, your colleague would reach end of the road.
Tango1777@reddit
Not his problem?! The guy is part of the team with somebody who doesn't give a shit and does nothing, while he earns around the same as the rest of the team that actually do the job. You're calling it NOT HIS PROBLEM? People attitude these days lol...
Few_Raisin_8981@reddit
Agreed with the caveat that you don't do their work too
ToThePastMe@reddit
Yes, or unless whatever they are not doing is making your workload bigger.
Has cases where someone was assigned making some simple tooling/reporting for the team. Something that would save us probably one good hour every day. Thing remained unfinished for weeks. Gave up and did it myself over a day.
Tango1777@reddit
3 months 0 commits? What are you even waiting for so long lol. I have encountered such dev, also senior. He introduced maybe 2 PRs in 2-3 months, I don't remember exactly. He barely asked us for help, which was already weird since our project is too complex to just understand everything yourself on day 1. He barely worked, so he had no legitimate questions. He was fired in like a week since we reported it to the management. The company even apologized the rest of the team for it since it's their responsibility to hire competent devs. The guy was probably making the similar money as we did, but we worked, he didn't, that is not fair. Report it ASAP. Not to mention your team velocity is affected by a guy who is doing nothing, but is theoretically hired full time.
Exciting_Agency4614@reddit
What exactly is your problem? Are you their manager? Did their manager ask you for help?
Why not focus on doing your best and leave others to do theirs? Weird post.
BoBoBearDev@reddit
My bet is, OP is stalking the ticket system and assume the person who is assigned to the ticket is always alive and working for the team. And those tickets are likely not part of the 2 week sprint but OP has no idea what a sprint is, because there is no mention of how this is not discussed during a sprint closeout and sprint planning.
tinmanjk@reddit (OP)
I am, just a new team and processes are lacking ...
RunnyPlease@reddit
You have a canary in your coal mine. Treats it as such. His job is to die before anyone else does.
Your job is to make yourself look amazing so you get promoted and get a raise. In every way you see your canary failing you should succeed and find a way to document it.
The canary doesn’t close any tickets? You track how many tickets and features you deliver.
The canary isn’t available to handle production bugs? You collect emails and messages from supervisors saying how you did.
The canary doesn’t write code or create unit tests? Do a git blame and find the percentage of the codebase you personally committed.
When it comes time for review for raises and promotions walk in with a dump truck of data. Don’t even mention the canary. He’s not your responsibility. Until you get promoted above him. Then he’s your responsibility. Then you might find out why everyone keeps such an unproductive person on the team.
Until that day it’s not your circus, not your monkeys.
tinmanjk@reddit (OP)
great comment and advice. Much appreciated!
raymond_reddington77@reddit
An inexperienced dev posting in experienceddevs. Oh the irony.
tinmanjk@reddit (OP)
haven't experienced this in 10-12 years. I guess I was lucky.
MediocreClient@reddit
option 1: he's actually a leech who's vampiring off the company, in which case management will love you and literally none of your team members will ever trust you becauee you're a rat and a suckup. whether or not the label is warranted or not is irrelevant, you will alienate yourself from everybody and will be one of the first to go.
option 2: you're not seeing other work being done elsewhere and you'll be outing yourself as a weirdo and a spy and an idiot. you will be the first to go.
option 3: that's the favourite nephew of the owner of the company(or some other relation to some other higher-up that exists so far up the food chain you can't see them). you're fucked.
tinmanjk@reddit (OP)
good analysis. I was thinking along the same lines, but wanted to gauge the pulse of the community on the matter.
budulai89@reddit
Employee could be overemployed.
And, I'm sure my comment will be heavily downvoted by the r/overemployed community.
tinmanjk@reddit (OP)
yeah I think that's what happening here. My post gets a lot of downvotes...was wondering where they came from.
Droma-1701@reddit
As a colleague it's not your problem. This isn't quiet quitting, it's just a complete refusal to operate in a professional capacity. Raise concerns and evidence to management. Culture is defined as the worst behaviours that leadership will tolerate, so if leadership are content with one person doing fuck all then do exactly the same for as long as the company stays in business, possibly getting a second job at the same time cause you may as well milk this level of epic idiocy, or leave because this won't get better. Under no circumstances pick up the slack for this person and be very clear and public in calling out why not. They need sacking, and if it's a new team this should be simple as falling off a log for management to deliver. It's just a question of "are they competent enough to do this?". Most are not, probably would be one reason why they hired this knuckle dragger in the first place.
tinmanjk@reddit (OP)
"Culture is defined as the worst behaviours that leadership will tolerate," stealing this for future use. Great comment altogether :)
ResponsibilityIll483@reddit
Let me guess, fully remote?
tinmanjk@reddit (OP)
yeah, bingo. This is hurting other remote workers as well.
Old_Cartoonist_5923@reddit
Repeat after me: "Not my monkey, not my circus."
_FIRECRACKER_JINX@reddit
God. It's like people are allergic to minding their own business...
It's like minding your business is lava. It's like minding your business is self harm almost.
Why.
Why would you, a completely happy self-fulfilled person who has no problems at all because you're busy working on all of them, focused on yourself....
Why would you as this person, choose to go out of your way to destroy this other person's hustle. What it obviously isn't hurting you???
What compels a completely fulfilled person who's minding their own business to go and do something like this? Legitimately I'm curious.
niuzeta@reddit
Assume best intentions until proven otherwise. It can be annoying but honestly it's not your problem.
The person may be helping others and unblocking them. The higher you go your contribution in actual code decreases. Maybe the person is in PIP and has given up.
Either way, I wouldn't engage with it unless you get asked about it.
UpgrayeddShepard@reddit
You sound like an asshole. A junior developer and an asshole.
t3klead@reddit
Don’t make this your problem
Salt_Pay_3821@reddit
I had someone join my team who did this and lasted a whole year with zero code submissions
Guy made like 200K for nothing
It’s crazy how stupid big corporations can be
Existential_Owl@reddit
On the other hand, some folks' hard work just isn't visible to others.
OP only thinks that this other dev isn't doing anything. For all we know, their boss strongly disagrees.
fr0st@reddit
Sometimes these people just work for another company while employed at their current one. r/overemployed loves to brag about this
TacomenX@reddit
You are new, stay in your lane, you are not the only one who notices, there are many reasons you may not be wary of for this to be accepted by management.
propostor@reddit
The overwhelming amount of responses saying "don't do anything" is fucking bizarre.
Just ask someone who's on your level (so not a manager or whatever), "Hey does that guy actually do anything?"
You'll get your answer in a casual, unofficial way. Then take it from there.
Round_Head_6248@reddit
I would only do something if his slacking impacted you, aka you’d have to do more work because he can’t be bothered.
Intrepid-Stand-8540@reddit
How do you know for sure?
tinmanjk@reddit (OP)
not a single commit pushed. just found he hasn't even cloned the project locally.
bonnydoe@reddit
You sound like a great co-worker! Do you keep tabs on all your new co-workers? Is that you r job?
tinmanjk@reddit (OP)
no. I don't there are other people that haven't cloned the repo still being there more than 1 week :) Interesting that I've received downvotes though :D
ToughAd4902@reddit
This is reddit, corporate bad up votes to the left.
You can't ask honest questions like this on this site, it's just not good at it. If you asked it in person, you would get completely different results, just have to know when this site will be useful and when it's not.
This sub is honestly 99% devs that work for shithole companies that have no idea how most of the world works and that's all they've ever known, the idea of this magical "RSU" or options is so far out of concept to them it's sad
13--12@reddit
Hey, if you actually decide to do something with it, I recommend asking this colleague to schedule a little call to know them more. In fact, you can do this with everyone in the team since you're new. Ask something along the lines of knowing what they're responsible for so you could ask questions about it, maybe ask for tips about the product and so on
chaitanyathengdi@reddit
If you think that's "interesting", you clearly don't understand or are incapable of understanding the message.
bonnydoe@reddit
How old are you again? You just don't seem to get it, do you?
chrisfathead1@reddit
Don't listen to these people, the best way to make your mark on a company is to immediately come in and cause drama and personal conflict. Become known for that. Make sure when your name comes up, people are like isn't that the guy who started all that personal conflict right after he started? That's how you advance
NoCardio_@reddit
If you’re working in an office, I’d also suggest writing their names on the whiteboard anytime they do something that you don’t agree with.
chrisfathead1@reddit
I find that timing lunch breaks and creating a spreadsheet is also really popular with colleagues
chaitanyathengdi@reddit
You might have forgotten a little something there
petiejoe83@reddit
They can have my
/snemec@reddit
Are they being assigned tasks which aren't getting finished?
Powerful-Film4714@reddit
Some people are dissing you here but if thats the case its crazy I still think that you should wait a couple of months before doing something
De_Wouter@reddit
You don't. Some people don't seem to do shit for months but then they put out a virtual fire saving the company half a million.
Don't judge people too fast.
sootybearz@reddit
Yeah I mean I’m in a senior position and also managing a team and whilst I don’t get the chance to push code as often as I’d like the discussions and solutioning I’m involved in I’ve no doubt are key to success in a lot of projects. Equally when something critical / more technical does need done that’s when I’ll tend to have to jump in. Lack of code commits does not equal zero work, some people are behind the scenes mentoring others, working on other things that keeps the whole ship going in the right direction.
And as others have said why make thjs your problem, it’s unlikely to turn out well for you, more than likely it’ll come out and others will be wary and you’ll be alienated.
the300bros@reddit
Good point. There’s definitely been times when I didn’t check stuff into a main branch but I was working on something major with full approval from higher ups. Also been times when I didn’t have approval but I’d already done assigned work and had freedom to do ad hoc stuff. Probably 2 month stretches way back in the day.
peripateticman2026@reddit
It's not your responsibility or business. Simple as that.
No-Evidence-08@reddit
It’s us vs them, remember that. If they’re not your direct report who cares. Stay in your lane.
Possible_Check_2812@reddit
Lol bro I barely code and have tonks or tickets on me. It doesn't mean anything.
tumblr_guy@reddit
Why would you go out of your way trying to knife someone? Just do the work you were hired to do, you’re not doing anybody any favours.
sobrietyincorporated@reddit
Stay in your own lane.
_fatcheetah@reddit
Stopped reading after "colleague".
Who are you to police others, unless specifically asked for. Do your job, end of story.
What if the colleague is a known to the manager? Then you'd be fucked instead.
thefightforgood@reddit
I don't mind working with people that do nothing. They're preferable to the people who roadblock everything instead of being productive.
I am not a manager and never want to be, but I am senior++. I will help with any project and mentor anyone who is willing to learn. It's not my job and not worth my time to care about Mr. DoNothing. It's not hard to guess who will get cut next time there's a headcount reduction.
luttiontious@reddit
I notice slackers and they annoy me. When I started at my current job, I brought up how I was working with slackers with some other people. It didn't do anything for me, and I think it made me look bad. These days, I try to focus on my work as well as working with those who I respect. Slackers still annoy me, but I keep my annoyance to myself.
darkveins2@reddit
High-level engineers don’t write much code once they’ve acquired enough responsibility, even ICs. It’s naive to measure output by commits or lines of code.
Additionally, a software development manager gets a finite headcount and budget. I’m sure they don’t need your help figuring out if it rolled under the table.
QuroInJapan@reddit
Unless whatever your colleague is doing is somehow hurting you personally, the best course of action is always to mind your own fucking business.
midwestcsstudent@reddit
You’re the kinda person to remind the teacher about the homework right before the bell rings. Get lost, narc.
Party-Lingonberry592@reddit
You can learn a lot from a new team by getting to know them and who the key players are. I wouldn't recommend rushing to judgment or verbally disparaging others on your team until you have the entire picture. The reality may be disturbing, or you may learn something new about these colleagues. The more you know...
Stubbby@reddit
Once in college we were doing group work. The lecturer (non professor) was an absolute idiot and nobody enjoyed the class. There was a kid in my group that said he’s going to end this bullshit, that he has a knife and he will visit the lecturer later at his office hours.
Right after the class I sent an email to the idiot lecturer telling him to be careful since that kid said these specific threatening words.
Guess what the idiot did? He told the kid that someone from his group snitched on him.
Next class the kid came furious but didn’t know who snitched. The only one he didn’t expect was me as I always referred to the lecturer as idiot/moron/meathead.
Long story short, don’t expect anything positive to happen when you report a peer. Even when you feel it’s justified.
kog@reddit
I'm skeptical of your experience if you think you can look at some ticket statuses and figure out if an engineer is productive
theunixman@reddit
Pushed commits are the tip of the ice berg of contributions. More importantly though why do you give a shit? Do you really think you’ll get anything out of pointing your little “discovery” out?
porkusdorkus@reddit
Just lay low and do your job. The guy could be doing side projects for the owner for all that you know, and it’s not your job to worry about other employees. Unless you’re some superstar employee that is irreplaceable then I would not stick my neck out.
ChanceYou488@reddit
…so fucking what? Most of my changes and work aren’t going to be in a commit, because our code base is archaic and we avoid deployments if at all possible (not my decision, mgmt obviously prefers it this way)
We do as much work in the db side as possible.
BoringHeron5961@reddit
Do you want everyone at the company including yourself to work harder for zero increased pay because this is a great way to do that
CutOtherwise4596@reddit
I'm a principal /staff engineer. I have a c few low priority item on my plate for the stuff my team is currently working on. 90% of my time is being spent coordination of work with teams/initiatives that my team will be working on in the next 6-12 months. I'm sure some of the newer hires think I do not do anything as they do not have visibility into my work and it could cause distraction and confusion if they know about it too soon, plus some of the stuff is limited due to project classification, only in a need to know basis. You may want to casually ask the person what they are working on first before you leap to conclusions based on your limited knowledge. I am assuming your manager hasn't told you what that person is working on etc.
Curiousman1911@reddit
If they already left in their mind, we should manage the vacancy, not the person. That is my approach.
aneasymistake@reddit
They might be working in repos you don’t see or just doing work that doesn’t result in code changes.
bronze-aged@reddit
Are you doing more work than you feel you should be? That’s something to bring up with your manager. Do it tactfully though “is this going to be the expected output?” or something like that.
If you’re comfortable with your load and you don’t feel like you’re doing more than your share then don’t worry about other people’s work ethic or impact.
I suppose the other alternative is to just look for another job if you’re really unhappy.
iraycd@reddit
May be they hired you to fire him? 😅
shozzlez@reddit
“Oh his wife died and we’re letting him settle back in slowly.” “Oh he’s going through chemotherapy but staying connected to work helps keep his mind off things.”
Just like asking if a woman is pregnant.. you better be 100% sure the guy is just fucking off for no legit reason, before you try reporting him.
nopuse@reddit
Maybe he's fucking off because he's pregnant. I ask everyone if they're pregnant, so nobody feels left out. Men often go their entire lives without anybody asking them. OP, this is worth investigating.
AchillesDev@reddit
Given OP's comments, they might actually do this.
chaitanyathengdi@reddit
Just don't get involved in the first place
drewSummer44@reddit
Focus on achieving your work first. Don't worry about someone else's. They're not your responsibility, and there's no reason to call them out, in my opinion.
There's probably nothing good that will come out of calling someone else out, unfortunately, especially being this team at a company. Also, you may not even realize what they contribute. Maybe they do work in other ways, and you're just not fully in the scope of it or in the know.
gomihako_@reddit
Some variation of this same issue gets posted here like once a week I swear. Y'all need to chill out and get a hobby.
originalchronoguy@reddit
If you are not his manager, it isn't your problem until you have to compensate for his lack of contribution.
As a manager, he'd be out the door in 2 weeks. As an IC, I just witness others complaining about picking up the slack. He will eventually get caught. Unless you work in a disorganized place.
FetaMight@reddit
You should NEVER have to "compensate" for a colleague's pace.
If the deadline slips, for any reason, that's a project manager problem, not a dev problem.
Don't let them make you resent your peers and force your to do unpaid work at the same time.
Your job is too develop, not too break your back so that a PM doesn't have to do their job.
originalchronoguy@reddit
Exactly, nothing in my post refutes that. In the first sentence, it is not a co-workers problem. It is a manager's problem.
No need to tattle tale to management until you have to pick up the slack. It is pretty clear to me.
SoggyGrayDuck@reddit
Lol is anyone organized in this area right now? They've solved these types of problems by assigning the entire project to one person so there's no messy & pesky responsibilities for the manager to deal with. Seriously, I've seen this take down an entire department because management refuses to dive in. It's like they know how much of a mess things are and are terrified to actually dive in. Hell even end user validation has gone out the window because management refuses to hold end users accountable so we just push it and wait for complaints. Shits fucked but yes eventually the person will be found out but will the entire team be offshored as a solution?
originalchronoguy@reddit
No, for me, it is a surgical extraction. One person can demoralize a team. If any other members have to do extra work or carry the slack of another employee, management has to take a look at that.
SoggyGrayDuck@reddit
I've yet to really see management get involved until basically quarter end and then they're trying to cover their own ass because they should have done so way sooner.
Cube00@reddit
More like 12 months once HR demand to run all their performance improvement and natural justice gubbins.
Chance_Pirate1356@reddit
This is a strategy at r/overemployed take as many positions as possible and milk them until they get fired.
flychance@reddit
This was my first expectation on reading the description
Artistic-Lifeguard36@reddit
Care to tell everyone where you work so we can steer clear?
No_Organization2032@reddit
He’s 100% working on something you’re not immediately aware of.
But do tattle. It’s best for the team if someone like you plays their hand early.
PM_Gonewild@reddit
Mind ya business lil bro.
akp55@reddit
You're new there. Worry about yourself before you start trying to throw shade at other people. Are you the team lead or manager? If not this is above your pay grade and not your concern
jayy962@reddit
I've had someone publicly call me out before.
I joined a new team to spectate and learn their processes because I was in line to be a tech lead for them as the existing tech lead/manager was going on paternity leave. So I'm mostly just fly on the wall for a few weeks.
New engineer on the team specifically asks me to pick up a ticket in a sprint planning meeting because "he never picks up tickets". Had to let him down gently and tell him I'm literally not even on the team. I could totally understand how he thought I was just someone who never did any work though.
Current-Fig8840@reddit
If their work doesn’t affect yours, then mind your business. Work is not your family house buddy.
robtmufc@reddit
Let it slide, you’re new and need to bed in. If it somehow crosses your path in the future and effects you directly, then I’d start having a word with the person otherwise collect the paycheck and keep moving
zogrodea@reddit
I highly recommend reading this article, "The Worst Programmer I Know".
https://dannorth.net/the-worst-programmer/
handle2001@reddit
This is juvenile, try-hard nonsense. Grow up and mind your own business.
Artistic-Lifeguard36@reddit
Lots of assumptions made in the original comment and many responses.
If your default position is accusation you might want to look closer to home for problems in a team.
Aware that was inflammatory, but have you tried talking to this person? As a human? No preconceptions just asking how they're doing and how they're settling in? Talking about their weekend and their life? Ultimately have you tried to understand their perspective on things? Their own self awareness? Their personal life? Their role?
Always seek first to understand, you know, like in software engineering, first understand the problem?
bonnydoe@reddit
HE is new to company, he doesn't say if the 'quiet quitter' is new. I would laugh my ass off if a newly arrived coworker would try to pry in my private life and thoughts ;)
Artistic-Lifeguard36@reddit
You'd laugh your ass off if a newly arrived coworker tried to understand more about you as a person and your role and perspectives?
bonnydoe@reddit
yes
80hz@reddit
Stockholders will love you but people are just going to hate you, try to understand before you pass judgment. Are they in meetings a ton are they talking to leadership much more senior does do less code and more Direction planning.
mothzilla@reddit
The collegue started at the same time as you? Or they've been there a while? I worked somewhere that had a Bez. He was just a vibes man. Made loud jokes as he walked through the canteen.
fungkadelic@reddit
mind your business
Mountain_Bat_8688@reddit
I’m going to go against the grain here and say that dev teams do not work in isolation and having a member or multiple members on the team that are low output does effect you and can become a situation where the high performers become overloaded. You are probably too new to start addressing those issues on your team though.
Also you asked this question on reddit where developers constantly brag about how they get away with this stuff so take the responses with that context
Ttbt80@reddit
You absolutely have the right to report this to your manager and request for complete anonymity. It impacts the team’s performance and makes all of the people who are trying look bad.
That said, I would come at it from a, “I just want to share what I’ve noticed since I got here, feel free to do what you wish with my observations,” and NOT “You need to fire this guy because I know for a fact he does no work.” Especially since you are new, you haven’t built enough trust to be taken at your word. But there’s a good chance your honest observation of the facts would help things get better for the team in the long run.
SteveRadich@reddit
They could be doing important project management work, helping set up projects / workflows, or meetings with management on features that could be delivered reasonable cheap vs how to reset what they want to be more achievable.
Code commits are one metric but not enough.
That said there are numerous masters of doing this and getting paid at companies where it’s hard to fire someone. They seek those companies.. It sucks but comes with the trade, as it does most trades.
soft_white_yosemite@reddit
Mind your businesd
fojam@reddit
Unless you have a stake in the company I don't know you'd care. It just less pressure on you and you'll look better when you do things. Work to live, don't live to work
CrappyInvoker@reddit
Not sure what everyone is trying to say here when they say ‘just do your work’. This is absolutely terribly advice and you should make your manager aware of your colleagues lousy performance because if mgmt is not aware, nothing will change and you’ll have to pick up his slack.
Say it once, then say it once more and if mgmt doesn’t act then it’s their problem. Refuse to do any work together with this colleague because you’ll have to do double the work in half the deadline.
PothosEchoNiner@reddit
Are you also new to the company? Most replies here assume that your new company new team sentence refers to yourself.
seinfeld4eva@reddit
What a dumb thing to snitch about.
Working-Revenue-9882@reddit
Easy. It’s not your business.
dual__88@reddit
If you don't depend on him for anything, then don't do anything. If you have to wait for him to finish his part so that you can finish your part then tell the manager i guess.
Reddit_is_fascist69@reddit
You're just a drone and don't care what others are doing UNLESS it directly affects you:
youngOE@reddit
I had someone join my team and they literally didnt do anything for 6 months. didnt run the code base. never configured their IDE. just sat there and had an excuse why they couldnt work.
unless your a manager, the most you can do is make note of that behavior and bring it up with whoever is responsible for the team. otherwise just ignore it and focus on your work because it can be very frustrating thinking about people who do that.
bonnydoe@reddit
I like your updates! You just can't let go lol
You somehow can't grasp what would be wrong with snitching on your coworkers, but still: here you are, asking if you should tell.
When you don't get the encouragement you are seeking you call this an 'interesting place'.
Are you just arrogant or are you just emotionally disconnected?
AllHailTheCATS@reddit
You sound like a bit of a dick, as long as its not effecting you who cares its his career
Helpjuice@reddit
Best to stay in your lane when you join a new company. You have no clue what the other person is working on. They could be working on things you have zero insight into. This was the situation for one place I worked at, I had things assigned to me, but I was also working on special projects that were the top priority of the C-Suite that the rest of the team knew nothing about and could not see any of my activity on.
Had the person complaining about fairness and activity join the group because I was reviewing their code and they were creating solutions that would be very helpful for contributing to the work I was doing. Thier jaw dropped when they saw the thousands of commits I had made to a very real new production service in a very short time.
My manager knew I would work on things assigned to me when I got time on the regular project, but the C-Suite special projects took priority over everything. Once the other guy was brought in they too barely made commits to the regular stuff and nobody could see what they were doing. Nothing the manager could do about it as C-Suite initiatives take priority over everything and due to the great work it turned out exceptional on my review.
RubyKong@reddit
my 2 cents:
Just focus on what you need to be doing. Don't worry about others. You might think that nobody notices - and maybe nobody really does notice - but mostly they do, and these people are ear-marked for termination the second there are budgetary issues to grapple with.
secondly, the more you work, the more you learn and the more valuable become. in all hard work ---> there is profit. don't forget that.
datOEsigmagrindlife@reddit
How about you don't be a snitch?
You're not that person's manager and you don't know what else they're assigned or working on.
Mind your own business.
allKindsOfDevStuff@reddit
“Nosy!? Eat a you manicott” 🤌
likwidoxigen@reddit
Lol these comments are so out of pocket. If you had framed the question as "I have a coworker that's not contributing and I don't want that to be seen as the standard for my team" you probably would have gotten real responses but since you said "quiet quitting" which literally translates into "doing what I'm paid for" everyone is jumping on you.
Few-Conversation7144@reddit
That’s a good way to start a new job. Pick fights with people before you even learn their name and force people to take sides
ListenLady58@reddit
Not saying this is the same situation, but people on my team bullied me because they thought I didn’t contribute anything. However, my role on the team involved doing work outside of their work, and apparently they didn’t understand or want to understand that. It wasn’t until I complained and told our manager what was going on and the developers were literally yelled at by my manager for it. He told them to mind their own effing business and let him do the managing… so yeah, maybe don’t bring it up.
West_Show_1006@reddit
How has that affected you? Or are you just monitoring them for no reason.
Tochuri@reddit
Are you the manager? No? Then mind your own business
PuzzleheadedPop567@reddit
Your edits make me believe that you aren’t actually asking a question. But trying to justify a decision you’ve already made.
Even if this co-worker isn’t doing any work, it’s not your job to monitor their performance. It’s their manager’s job.
And if you work at a company where slackers are common and things don’t get done, you can’t do anything about that either, apart from leaving the company.
It’s not your job to keep tabs on other coworker’s output. It sounds like you are just trying to start drama.
JaySocials671@reddit
Are you the manager? Then not ur prob
PeachSad7019@reddit
Sounds like OP is jelly.
arfreeman11@reddit
If you aren't management, you should just mind your business.
Also, you probably need to get the right definition for quiet quitter. Doing exactly what you were hired to do instead of going above and beyond for no extra pay is quiet quitting. You seem to be working with a bum. A bum just does nothing and gets paid.
zemele@reddit
Why do you care so much dude? The company isn't your best friend. Do your job, get your paycheck and go home. You're not the company.
InfoLurkerYzza@reddit
Had something like this before. Didnt really do much work. He also only worked 3 days.
Later i found he was a childhood friend of one of the chief officers. Yeah, it's best to mind your own business.
bjenning04@reddit
Are you their manager or otherwise responsible for their productivity? If not, better to mind your own business and leave that alone. At least until it becomes a problem for you or other colleagues.
Sky_Zaddy@reddit
Let him cook, you just need to simmer.
siqniz@reddit
let'em collect the their check
Alarmed_Inflation196@reddit
I worked with a guy like this. No, there was no good explanation. Just cronyism I think. He does barely 50% of the work of anyone else and the code he does produce causes 200% more work for all of us. It's utterly demotivating.
These_Translator_488@reddit
Report him to ICE and maybe even fight him
TeeeeeFarmer@reddit
It's okay man, some people just want to collect paycheck and leave the company anyways. Help that guy if needs anything, you never know what someone is going through in their personal life.
Work is just work (however interesting / competitive it might be) and they won't hesitate to layoff anyone if needed.
So, don't bother about it.
local-person-nc@reddit
Good God dude you just started and already are fucking for the company? There's so much more a software engineer can do that push code but you'd know that if you were a senior.
endurbro420@reddit
You have no clue what they actually do. It is that simple. You know they don’t commit to the repo you are looking at but you have no clue as to what they actually do.
Go ahead and bring it up and put a target on your back. I’m sure they will choose the new guy who is trying to make enemies over the guy who likely is very specialized and valuable to the company, so valuable that their work is not necessarily defined by jira tickets.
NoCardio_@reddit
EDIT 3 should be “sorry guys, I’ll mind my own business from now on.”
EvidenceDull8731@reddit
I say report him so you cause drama for yourself and find out what happens to people like you.
hachface@reddit
mind your own business
Fruitflap@reddit
Why do you desire to micromanage your colleagues?
ryo3000@reddit
Oh you should write up an email directly to them saying how they've done zero work and you're expecting improvements
If that doesn't work, write to your manager C.C.ing the employee that hasn't been doing anything
"This guy has done ZERO actual work."
If your manager doesn't act accordingly to what you think it was, go higher up
Message the CEO and owner if you have to (make sure to CC everyone that you've previously messaged too so they're aware that you've escalated the issue)
That will quickly solve the issue
Abangranga@reddit
OP is clearly ace MBA material.
friendlytotbot@reddit
Also the commit thing is dumb, because what if he doesn’t need to push any commits as part of his usual tasks? We have ops ppl who do tons of infrastructure work, but they work directly on the servers and don’t really need to push commits that often.
grizltech@reddit
Is he preventing you from getting your work done?
friendlytotbot@reddit
Unless you’re a manager evaluating the team or directly working on a project with this person, I’d mind my own beeswax. Also, probably won’t look good on to call that out as a new person, unless you’ve been hired as a manager lol.
mandalalalalalala@reddit
I spent 4 years in my last IC role as a Senior Software Engineer trying to get leadership to realize the person they put in charge of the entire engineering org was incompetent as a manager but essential as an engineer. It drove me crazy and ruined my reputation among every non-IC at the company who touched the eng org.
We never met our goals, the guy could not listen to or apply any of the feedback, and he managed to coast on whatever conversations he was having behind closed doors. This was his first job, he had zero startup experience, zero management experience, and every IC on my team hated working with him.
I ended up on a crusade driven by my own individual perspective and it wore me out more than it did any good. Other managers started seeing me as an enemy. It's wild how feedback can turn against you when people aren't willing to take a stand against incompetence. My reputation really suffered and looking back I can see why. If you are not a manager, technically that's not your responsibility, and that very much matters in business.
My advice is to stay in your lane. Document everything so you have a comprehensive record of what you're seeing. Provide concise, actionable feedback when asked. Deliver quality work. Avoid doing this person's job. Critically, save the crusader energy for the parts of your life that you have control of.
For what it's worth, a place that could really use that energy, from an ethical and human rights perspective, is local politics and community support programs. Which also have the pitfalls of people failing up but at least you'll see the gains in the community in which you live.
Learning to coexist with difficult people is an essential life skill.
m98789@reddit
They know.
Perezident14@reddit
Maybe I’m old school, but I tend to mind my own business.
chaitanyathengdi@reddit
It's one of those timeless things.
Rain-And-Coffee@reddit
Unless your his manager he's blocking you it's not your business.
Let's his actions speak for him, they have a way of catching up.
IDatedSuccubi@reddit
Quiet quitting does not mean "zero work", it means "doing only what's in the job description" (i.e. bare minimum). It's a stupid term, I bet a manager coined it to sound bad, but it'a usually used as "my workers won't do overtime when I ask them".
CricketMysterious64@reddit
It’s best to mind your own business in these cases. I found out the hard way, you never know who’s close with who when you’re new. You’re unlikely to look like the hero for calling someone’s baby ugly, especially when it’s true.
mkg11@reddit
Just stay in your lane
Status-Arrival-3757@reddit
If you are not his manager then it is not your responsibility. Focus on your own work. Only exception would be if he has something blocking you, in which case I'd raise only the specific item blocking.
chrisfathead1@reddit
MYOB. Kindergarten lesson that you can refer to for your entire life
MoreRespectForQA@reddit
You dont. It's not your problem.
binaryodyssey@reddit
I have worked with this type of situation before. Manager didn't really seem to notice, but they got laid off pretty quickly. It was a little annoying to be picking up all the slack for a while but it didn’t last too long.
wassdfffvgggh@reddit
Why complain?
If your manager is ever forced to fire an underperformer or lay off someone, this guy is the obvious choice.
It's in your best interest to have people like this around.
Now, if you ever get assigned to work on a project together with this person and they are blocking your work. Then you can escalate to your manager.
iwanttostaylowkey@reddit
I have a team mate or two like you in my team and let me tell you that it’s none of your business my friend. You are hired for a job, just focused on doing that especially when you are new. That should be all you should be thinking about, getting use to the work and start contributing instead of trying to evaluate what others may or may not be doing. I am defending anyone else but for your own sake, just focus on your own work and your contributions because at the end of the day, it’s what matters. What did you do? What did you contribute? Not others. We have managers for a reason.
MonochromeDinosaur@reddit
Not your problem. Also squashing makes commit history sparse so commit history is ‘t a good measurement.
Sammolaw1985@reddit
Mind your own business
fogcat5@reddit
post about it on reddit if you can't decide yourself.
__blueberry_@reddit
if you do decide to chat with management about it, you could frame it as that you're worried the person is not set up for success and getting the support they need. and provide solutions such as maybe more frequent 1:1s or an onboarding buddy for the person. i've done this before but at the same time i was a technical lead so i kinda had some responsibility in the matter.
if you don't really have a stake in it, i would recommend trying to build a relationship with this dev. reach out to them, get to know them, ask if they need any help with anything, offer them help, etc.
it could be that this person is quietly struggling with getting used to a new codebase, or just feels overwhelmed and doesn't know how to work effectively at the company. or they could just be a straight up coaster. we had a coaster like that who lasted about a year and a half and just got fired recently since we are tightening up our budget due to how the current economic situation is impacting our business.
K9ZAZ@reddit
i have no idea why you would insert yourself into this situation. if he is blocking your work, let him and then if no followup your manager know. if not, wgaf?
Main-Eagle-26@reddit
You should keep to yourself, mind your own gd business and let your bosses figure it out.
If it starts to impede your work, you can bring it up, but if not, it isn't your business.
Main-Eagle-26@reddit
I've been where you're at and spent so much time being stressed about what my coworkers are doing or not doing, and all it does is make you unhappy, makes your work slow down...and if you snitch on them, it just makes you look bad in your boss' eyes.
Your boss, if they aren't also checked out, is aware.
MediocreDot3@reddit
Do not fucking bother with this my man - I'm telling you that you are treading unclear water - behind the scenes you have no clue what this person is doing it very well could be out of sight and if he's in his managers favor you're gonna be the one that gets a target on their back
I manage people and I do not want anyone on my team acting like this even if it is true - I'll get rid of shit stirrers very quickly - if it's a problem I tend to find out because that falls on me if it is, not the people who I manage
kenflingnor@reddit
Not your problem
DataIron@reddit
Don't say anything, not your place. Bet they know and there might be something happening there life personal, HR kinda thing, that you're unaware of.
Besides as others said. New person, new company. Your job is to be a fly on the wall, observe and absorb.
froughty@reddit
Mind your own business.
floopsyDoodle@reddit
If you're a dev, I'd give it 5-6 months till I knew for sure what's going on a bit better, if they're still doing nothing, and you want to throw them under the bus, talk to the lead, they almost certainly know it's happening and having other devs on the team also noticing will encourage them to do something about it.
If you're the team lead, talk to them privately (and without accusations, just a friendly chat for info), see what's going on, if they have no reasons and are just not doing anything, start checking in daily on what they're doing and how their estimates are looking, if they are continually not hitting estimates and have no reason as to why, start reaching out to PMs or HR, or whoever you need to to get some written evidence of their lack of work for future PIP/Firings.
kingDeborah8n3@reddit
Does them not doing work make you work more?
AggressiveResist8615@reddit
How about you mind your own fucking business
Sensitive-Ear-3896@reddit
Lay low, at least until you know what the reason is, then wait 6 months more
prodsec@reddit
Not your problem
Gxorgxo@reddit
Are you their manager or is their slacking off making your job harder? If not I'd mind my own business, especially since it's a new job. Until you have full context be careful
the300bros@reddit
Unless you are team lead, manager or it’s blocking your work it’s not your concern. Partly because they may be doing work outside of your area/ability to monitor.
g_bleezy@reddit
Eyes on the wrong target. What do you want to personally accomplish in this new role to use as a stepping stone for your ultimate career goal? I doubt it has anything to do with this bozo.
tlagoth@reddit
If his behaviour does not affect you, or the team, I’d not bother. Sometimes they are going through a momentary hard phase, and crying wolf prematurely may make you look bad, especially if they have a legit reason for hitting the brakes.
However, if their lack of work causes you or the team to work more to compensate, it’s a different story. Depending on your position and seniority, you could have a talk with him, asking if things are ok and telling them you noticed they are not participating / contributing. If you are a regular team member, at his level, I’d mention it as a feedback to your common line manager, and let him deal with it.
I’ve seen many people like this colleague, in different companies I worked for. The usual case is that someone or the whole team will end up having to carry this person. In all cases I’ve seen, they remained doing nothing until someone had the guts to fire them.
IMovedYourCheese@reddit
If their work (or lack of work) is affecting you, talk to your manager about it.
If it isn't affecting you, it is not your concern.
Xsiah@reddit
Are you responsible for this team? If no, it's not a problem you need to solve.