Hacker News new | past | comments | ask | show | jobs | submit login

It is easier to track people being at their desks than diving into the git repository and looking at what got done.

Also, for a programmer who did not code for 5 years because they got into management, it is a huge source of anxiety and forces them to contemplate the obsolescence of their skills. Having to ask a junior dev how to compile the project you are supposed to overwatch can be felt as humiliating.

When I had a team to manage, I tried to keep involved enough so that I could do the whole build process. Most of my work was complaining about broken master branch and regressions, praising the correct person when a feature gets implemented, shout with the higher management to stop adding irrelevant features every time they meet a client and have a weekly discussion on how things are going on.

We had one lay off during that period, on my recommendation. I was worried about the team morale, but got told we should have fired that person earlier.

Why would you feel humiliated for not knowing which button to press to build, on the current bullpoop, if you hadn't yet needed to use that particular bullpoop?

It's possible that a junior dev who showed you the button might then joke to other junior devs about you not knowing. But a smarter junior dev, wise beyond their years, will realize it's just bullpoop trivia, one of thousands of bullpoops one has to pick up and later discard in favor of a fresher bullpoop, and be happy to help.

In any case, you, as an experienced person, should know it's just a different flavor of bullpoop, and not the most valuable thing anyone knows.

Your decision to stay in the loop, with the bullpoop that your team is currently enjoying, sounds like it might come in handy. But I wouldn't want anyone to ever feel humiliated over bullpoop.

I totally agree, but many people feel that way, especially if they got into a higher position because they are supposedly more knowledgeable.

A build process is one thing, knowing C++17 or rust is another. Knowing if refactoring all these templates structures was really worth 2 weeks is something that is hard to ask to a junior dev.

Good point. On something like the refactoring question, sometimes that kind of question can be bounced off a senior developer, maybe as a bit of a mentoring role for them (official or unofficial)?

Being humiliated (humbled) is probably a good thing because status and responsibility often cause people to become callous, self-serving, and out of touch.

> It is easier to track people being at their desks than diving into the git repository and looking at what got done.

Why not both? Time tracking with tomsething like toggl doesn't take much effort, and you can combine that with reviewing git activity.

Applications are open for YC Winter 2020

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact