[PragmaticPulp]

> I am with you on most of your points, but definitely not on the "normal and mostly acceptable".

The "normal" part is easy to disprove: If everyone was doing near zero work and lying their way through standup about it, nothing would ever get done. That may be normal in certain zombie organizations, but those organizations can't last forever without people doing actual work. Somebody is doing the work, even if the OP isn't.

> Coasting from a standup to the next with zero work in between is definitely not normal (_if done on a regular basis_) and the sign that something is not right in your current situation.

The part about doing nothing all day and then lying their way through standup stood out to me.

Like you said, we all know that programmers aren't hands-to-keyboard programming for 8 straight hours every day, nor do we expect that. However, we do expect that everyone is putting in similar amounts of effort to their peers.

I'm surprised how many comments here are justifying the zero-work behavior because the manager hasn't caught on yet. This doesn't mean the work disappears. It means the person's teammates have to pick up the slack and carry the project forward without the OP.

Working with a deadbeat teammate is an awful experience. If you need to get anything done, the only way forward is to plead with them to get some work done, or just do it yourself. More often than not, the team ends up doing it themselves.

We've all been stuck with deadbeat team mates, from group projects in school to the workplace. It's not okay to be the deadbeat teammate.

[marktangotango]

> However, we do expect that everyone is putting in similar amounts of effort to their peers.

I think there's a distinction here between two types of "work" (at least). Work that moves the product/business forward in tangible ways, in addition to just adding features (decrease down time, reliable repeatable deployments, reproducible, easy to understand configuration, fast bug remediation) and work that doesn't.

I think we've all experienced teams who switch frameworks and libraries at a whim, or worse yet, adopted entirely new languages "just because". They usually don't ask permission, or if they do the sell the decision makers on some hula balu about "increase productivety" or whatever when they really just want to use new cool X. Or howabout the frontend teams that switch naming conventions, and never rename the old stuff before starting another naming convention?

The point being there are a lot of developers who waste a lot of time "working" on things that just don't matter. The business never asked for it, it serves no purpose or real need other than to scratch someones itch (or build their resume). I maintain if wasting time doing nothing is "stealing" from the company, then so is this.

[spaced-out]

>Working with a deadbeat teammate is an awful experience. If you need to get anything done, the only way forward is to plead with them to get some work done, or just do it yourself. More often than not, the team ends up doing it themselves.

I've never had this issue with the projects I've managed.

Create a doc/Jira for the project, including timelines and tasks. Allocate tasks to all teammates. Daily/weekly go through those tasks, updating progress. If timelines are being held back by someone, I'm going to make management aware because I'm not taking the fall. If they're not then I don't care.

[TigeriusKirk]

> those organizations can't last forever without people doing actual work.

Maybe not no work, but very little work, they can last a very long time.

>This doesn't mean the work disappears.

It may have never existed in the first place.

[Retric]

This isn’t about dead beat team members, this is about not having enough work to do which can happen for various reasons. Sometimes companies just want redundancy and don’t care if that costs real money. Other times a team is built and just gets less work than expected and or people are simply more productive. And of course, if you actually want to make important deadlines you want be conservative in how much work the team takes on.

Finally if you get a 10x person but don’t have 10x the stuff to do they often spend a lot of time twiddling their thumbs. You could keep giving them a larger share of work, but that’s hardly fair and you don’t want to reduce staff in case that person quits.

[tharkun__]

I would beg to differ. While I agree that some of your reasoning is valid enough I read the OP as what I would call a dead beat developer.

Its not easy to distinguish sometimes because we all know from our own experience that it just happens that you get a task that happens to have 10 pitfalls hidden in a row and what looks like an easy peasy fix is a day of debugging. Sure.

What usually is the case though is that if this happens 10 times in a row it isn't particularly bad luck. It is very very likely something else. Such as what the OP described. And especially if the manager is also overworked then distinguishing the two cases becomes even harder. Then even a manager that wants to do something can't because you don't want to fire someone that doesn't deserve it based on incomplete information.

Some managers are also just afraid of the organizational hassle, the emotional toll on themselves, might fear the overall consequences for morale too high vs. the morale impact of co workers noticing the slacking or simply couldn't care less since they are doing the same thing just one level up. What's another dead weight at a company the size of GE or a large bank or insurance etc.

I definitely say something. Many others say something as well. But we aren't the majority especially in large orgs. Usually it's known which people you try to keep away from your projects and that's as far as everyone goes.

If you really have a 10x person, there's no need to lie on stand-up 3 days in a row.

[Retric]

I agree that 10 hours per week is rather extreme, but I have been in similar situations. The difference is I tent to say something because boredom gets old. I see less confrontational people say stuff that everyone knows is BS, and then just add the aside about being available if something is more important/useful/pressing.

In the most extreme version of that I once had absolutely nothing to do for months at a time and my manager was completely aware of that fact. Their response, “Look you’re fully billable so if the client is happy I am happy.”