3 ms·
> Today it’s common for first-time managers to get the advice that they should immediately stop writing code at work. Really? It seems like a very complicated
by lbriner 5y ago
> Today it’s common for first-time managers to get the advice that they should immediately stop writing code at work.
Really?
It seems like a very complicated blog and I think the trust more easily comes from openness. If I am speaking to a dev about why their task count is much lower than the team average, I can be open and say, "If your task count is lower, it might be my process, it might be that you are being distracted by the company or by others or it might be that you are struggling in some way and I can help...", that openness (which is true, I am not out to get people), means that the developer knows that it isn't personal or because I am an arse. We can then talk about what is going on.
Same with the "I have a problem", if it is small, sure, trust them to fix it. If it is something bigger (we want to change from Git to SVN), then I don't think anyone would be offended by a Zoom call to discuss the challenges that exist and whether they could be resolved in another way.
- gfxgirl 5y agohow about "the feature turned out to be a rabbit hole of subfeatures and bug fixes"?