Live data from Hacker News

Ask HN: Going from Developer to Manager. What should I know or learn?

news.ycombinator.com

161–170 of 186 posts

Re: Ask HN: Going from Developer to Manager. What should I know or learn?

#161

Earlier quoted context omitted.

How do you define 'toxic'? How often do you fire workers for being 'toxic'?

Toxic examples: - "This is stupid" or other negative comments in code reviews (aka non-constructive criticism) - Yelling or cursing at people because they question you and your decisions. - talking bad about the company or other teammates to people behind their back. - throwing a "temper tantrum" when you don't get your way when it comes to some architectural decision. - refusing to work with certain people or only w…

Thanks for the answer. I hope all firms have a formal HR process where they state expectations and confront the individual before he is labelled as toxic. I think everyone should have a chance!

Re: Ask HN: Going from Developer to Manager. What should I know or learn?

#162

Earlier quoted context omitted.

How do you define 'toxic'? How often do you fire workers for being 'toxic'?

There is a quote I once heard “Good teams are usually great for the same reasons, bad teams are almost always bad for different reasons”. This is the much the same for people. Generally speaking, the best people you have worked with are very similar in terms of what they provided that made you really happy to be with them. Example “good” traits: - honestly - dependability - integrity - intelligence - humility - excel…

I think that quote comes from Tolstoy when he was writing about families in Anna Karenina. " All happy families are alike; each unhappy family is unhappy in its own way"

I am not sure he was right here, different people may have different ideas of happiness.

Re: Ask HN: Going from Developer to Manager. What should I know or learn?

#164

Earlier quoted context omitted.

To be honest a lot of your suggestions are probably very solid but come off like the "Find a mechanic you can trust" solution. By that I mean the advice of "find a mechanic you can trust" only is applicable to someone already familiar enough to know how to determine if a mechanic is trustworthy. A lot of your advice is probably 100% valuable, but as someone working through a lot of these same concerns I'm stuck wonde…

That is a fair criticism, my tips were just a list of the top notes I could think of to help. I could dive extensively into each and every bullet. I will say if you constantly questioning whether you are doing a good job and if you can do better... you are probably above average at least.

A struggle I've had is I'm used to casing performance in terms of errors or negative feedback. So far the feedback I've had is almost all positive (team is far above previous performance, flight risk is far lower than other departments, etc) but I don't feel like that's helping me improve cuz I don't know how to actually deal with positive feedback.

Some personal introspective criticism I've been wrestling with.

Re: Ask HN: Going from Developer to Manager. What should I know or learn?

#165
The cynicism and negative attitude towards managers in the "Developer Hegemony" book is at dramatic odds with the many positive comments here - so much so that Insuspext the books main thrust (managers are complicit in holding "delivering" developers to impossible timescales and enforcing hierarchy needs on devs top down) is even more correct

Re: Ask HN: Going from Developer to Manager. What should I know or learn?

#166

Earlier quoted context omitted.

RE the architect handwriting tutorials: do you have any recommendations? I can barely read my own scribbles, and I've struggled with poor penmanship forever. I'd looked for courses/tutorials, but hadn't found anything that resonated.

I have a few friends that are draftsmen. I asked them and they said they just gave them a font and graded them on it with homework blueprints. What I did was just googled architect fonts and downloaded a bunch of examples then used a field notes pocket dot journal[0] to practice. I would just try to copy a font exactly, then do drills on problem letters. I probably drilled on four fonts I found that I liked. Focusing…

Even though I was not able to understand 100% of it (non native speaker) it was a fantastic read. Thanks for sharing that!

Re: Ask HN: Going from Developer to Manager. What should I know or learn?

#168

Earlier quoted context omitted.

Toxic examples: - "This is stupid" or other negative comments in code reviews (aka non-constructive criticism) - Yelling or cursing at people because they question you and your decisions. - talking bad about the company or other teammates to people behind their back. - throwing a "temper tantrum" when you don't get your way when it comes to some architectural decision. - refusing to work with certain people or only w…

Thanks for the answer. I hope all firms have a formal HR process where they state expectations and confront the individual before he is labelled as toxic. I think everyone should have a chance!

Well, for truly toxic individuals, warnings or confrontations are useless (I’ve learned this the hard way, and not for lack of trying). It is impossible to get them to understand that they have a problem; anything you say, no matter how clearly articulated, fact-based, and objective, will be rationalized away. These individuals cannot accept that they may be wrong.

Re: Ask HN: Going from Developer to Manager. What should I know or learn?

#169

A basic podcast that I’ve found useful is Manager Tooks. It contains a lot of good habits and tools. Listen to it on your commute for a month or two and you’ll get the gist of it. The Effective Executive by Drucker is a great intro to leadership. He puts the role in the context of getting results. A couple other thoughts: 1 - Communicate the same message over and over. Do it verbally and in writing. 2 - Have weekly 1…

Weekly 1 on 1s with all reports is not useful or feasible. If you have 8 reports that's 10% of your work week swallowed.

More than that when you consider the To Dos and followups. That’s why it’s hard to stay active as an individual contributor when you have a large team.

If you don’t invest the time in advance, you pay it more with fighting fires later.

Re: Ask HN: Going from Developer to Manager. What should I know or learn?

#170

Earlier quoted context omitted.

I honestly don't believe flat organizations exist. They claim to be but there is always an informal heirachy. Which is trickier to navigate then just having a bit of structure. No need to go overboard but at least formalize what exists but unsaid.

I would agree, people call it flat but in reality there are always some structures, processes etc either known or not. But I do see that there are quality organizations that call themselves flat, when in reality they are more like an open door, open culture workplace. But they still have a structure and organization on how you do things. e.g. you can talk to the CEO, but you are not to use that access to manipulate t…

This is dead on. You could approach directly but it's probably better to bring up issues with someone else first then escalate to the CEO if necessary. Flat organization means you can go directly, but you probably shouldn't. So the structure exists.
Post reply on HN