News for hackers. Stuff that matters.
Re:The Programmer Identity Crisis by AnimalMuppet on Tuesday October 21, 2025 @04:20PM (#45661159)
They should get a clear explanation of the problem and of the team expectations the first time it happens.

If it happens a second time? A stern talk from their manager.

A third time? PIP or fired.

Let your manager be the bad guy. That's part of what they're for.

Your manager won't do that? Then your team is broken in a way you can't fix. Appeal to their manager, first, and if that fails put your resume on the street.

Re:The Programmer Identity Crisis by sudahtigabulan on Tuesday October 21, 2025 @07:10PM (#45662937)
> If it happens a second time? A stern talk from their manager.

In my experience, the stern talk would probably go to you, for making the problem visible. The manager wouldn't want their manager to hear of any problems in the team. Makes them look bad, and probably lose on bonuses.

Happened to me often enough. What you described I would call a lucky exception.

Re:The Programmer Identity Crisis by sevenseacat on Wednesday October 22, 2025 @07:55AM (#45667714)
For interrupting the velocity and efficiency of the other dev.
Re:The Programmer Identity Crisis by aleph_minus_one on Tuesday October 21, 2025 @05:44PM (#45662110)
> Let your manager be the bad guy. That's part of what they're for.

> Your manager won't do that? Then your team is broken in a way you can't fix.

If you apply this standard, then most teams are broken.

Re:The Programmer Identity Crisis by 01HNNWZ0MV43FF on Tuesday October 21, 2025 @06:24PM (#45662493)
"A big enough system is always failing somewhere" - can't remember who said it