Live data from Hacker News

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

news.ycombinator.com

111–120 of 186 posts

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

#111

Most important thing to me, learn the difference between leadership and management. A long time ago I was mentored by some great leaders who taught me the difference, and also taught me when to manage situations or specific people. Management isn't a bad word, but applied the way it is most places it should be. My goal with teams is to inspire them to make good choices, show them the right paths and help them succeed…

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 think you're right, and so do a lot of other people.

https://en.wikipedia.org/wiki/The_Tyranny_of_Structurelessne...

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

#112

In the past 13 years have gone from dev -> tech lead -> manager -> director -> VP/CTO at startups (50-250 people). Here are my tips: - Your job is to provide effective technical solutions to business problems via managing a team(s) of engineers, everything else is an extension to that. - Managing is nothing like coding and requires a completely different mindset and skill set. - Authority comes through respect and un…

"- Say no / only agree to what you know your team can deliver on... and always double your estimate. In the long-term reliability is valued over agreeableness."

Early in my career I read that X (almost) __always__ takes twice as long and cost twice as much as you typically estimate.

I can't count the number of times that's been true. It's also universally true. e.g. Wanna hang a picture. Piece of cake, right? Until you have to find the stud. Likely get a tape measure to get the height right, etc.

Perhaps an over-implied example, but once you start to keep track in your head of your estimate vs actual, the 2x Rule pans out quite a bit.

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

#113

Earlier quoted context omitted.

I do all the writing first thing when I sit down in the morning. Before I talk to anyone. I use a dot journal, kind of like a graph paper moleskin, but a dot grid. Date the left page and time. Do feelings. I’ll also note the weather, if it’s a special day or holiday and if people are around, who. Then I review the last few pages and I start musing. On the right page I title “ todo:” and start making the list. As I ro…

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 on accuracy monospacing and staying in the grid. A big thing I learned was that it was ok to slow down, it gives me more time to think about the thing, the clarity of the lettering seems to reflect the clarity of the idea. I think previous attempts to improve my handwriting had failed because I wanted to write as fast as I type. It's a different thing obviously, but I didn't really realize the benefits the slower pace has for processing things and concept recall.

I also bought some drafting tools. Angle rulers, protractor, etc. I decided to overdo a couple network layout projects and work on it in that context. The end product was so nice that I laminated a bunch and gave them to people and they’ve been a great reference!

Oh, there is also a tool called an architectural lettering guide[1] that can be helpful.

It took about three weeks to really kick in. Now I’ve got my own style and it changes a bit still and I experiment, but the core just adds to the rote process of the daily exercise. I can see by looking through the journal if I'm not fully on my game by how much drift there is.

I would probably drill for 10-20 minutes a day for the first week. After that, it was just here and there if I noticed something just wasn't working. Like when I decided Ps and Ys got flourishes, but only in some context. Also changing anything usually meant other letters would start regressing to my scrawl. It's weird how related the patterns are in your head.

Another thing that helped me was finding a pencil I liked. I ended up with a super fat 5.6mm HB firm lead on a woodworkers pencil[2]. It sharpens to a fine point and holds it forever and never breaks. Always using the same tool is really important to me now. I had to go through a bunch of stuff until I found a pencil I didn’t hate. It might not be the right one for you. I love them though and buy extras and hand them out to anyone that likes to write. My polling seems to agree that they are dope.

Here is a pretty good blog[3].

[0] https://www.amazon.com/Set-Dotted-Notebook-Travel-Journal/dp...

[1] https://www.dickblick.com/products/alvin-ames-lettering-guid...

[1] https://www.woodcraft.com/products/woodcraft-woodworkers-pen...

[2] https://www.google.com/amp/s/artdepartmental.com/2009/10/12/...

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

#114
I wish you luck. There's a lot of good advice in this thread, but if I were talking to my younger self I would say DON"T DO IT!!!!! I became a manager the first time when I was 28 and I was very excited about the opportunity. I found very quickly that I hated it. If you really love coding and solving problems, you will never find being a manager satisfying even if your team is successful. So I transitioned back to developer. Fast forward 12 years at a different company, and I was talked into being a manager (bad sign) again. I told myself that I'd approach it differently and focus on being a mentor, etc. Same exact result. I hated it, and transitioned back. You have to know yourself and what you find rewarding. Unfortunately, there are a lot of terrible managers in technical fields, and I've always thought it's because most of those people in their heart of hearts don't want to be managers.

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

#115
Workplace toxicity's impact on your career increases the higher your title gets.

Never assume your manager peers will do you a favor for free. No good deed will go unpunished.

If your role will include hiring and firing people on your team, start having regular 1:1's with your direct reports. Make it clear 1:1 time is for your direct reports to talk to you about whatever they want, and for you to listen. Not your time talk about their tasks.

If you have to give critical feedback, give it sooner, rather than wait for a 1:1. The absolute worst time to provide feedback is during a performance review.

For folks who struggle, make sure the performance bar is clearly defined for them and let them know you are there to help them, but it's their responsibility to meet that bar.

Develop your team. You'll have your all-stars, your role-players, and your under performers. A majority of your time naturally goes towards your best and worst people. Your goal is to move everyone on your team to the all-star category. That means not short-changing time with the people who are performing.

When you get promoted to the next level (managing managers) you'll be glad you can tap that bench of all-stars to take on additional responsibilities allowing you to take on bigger challenges.

Under performance is typically a motivation issue or a communication issue. Make sure you are doing your part to address your deficiencies in each (trust me).

Learn to delegate, but not just the crappy work.

People leave companies because of bad managers. Remember that. No matter how great of a manager you think you are, someone will ultimately lump you in as a bad manager.

It's easy to deal with under performers if they also have personality clashes. Dealing with under performers who you personally enjoy working with is a lot harder. I have no advice on how to deal with this. Firing people you have a personal connection with is tough, and it comes with the job.

Communicate often. My rule was no company news hit my team through the rumor mill before I got a chance to speak to them. The moment I had news I could share, I would share it.

Here is the top tip I can tell you to engender loyalty: talk to your team about promotions and career growth. Rarely ever do managers talk to their teams about career growth. Take an interest in the individuals on your team, and it will pay off immensely.

Source: My experience having built the 5 top performing software engineering teams at my last company.

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

#116
post #48

I made the jump from developer to team lead, and all the advice here is great. One thing that I wasn't prepared for and that I don't see other people mentioning (on a cursory glance at the replies) is that your reward function for job satisfaction changes, and the feedback loop length changes. By that, I mean that for me personally I derived most of my job satisfaction from solving tricky problems, fixing bugs and im…

One thing you can do that's useful is making sure you can still compile and run the code. The occasional minor off-critical-path edit could also be enough to give you that hit you need as a developer.

I used to make a point of submitting a minor contribution to every project's code. I used to (part jokingly) liken it to Alfred Hitchock making a cameo in most of his own films. The stated reason was to make sure I had the dev tools and env set up so if there was ever an emergency I'd be all ready to help out, and the unspoken reason was to help gain the confidence of the team. I think it was a good idea, but unfortunately the approach doesn't scale to work across large numbers of projects.

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

#117

Most important thing to me, learn the difference between leadership and management. A long time ago I was mentored by some great leaders who taught me the difference, and also taught me when to manage situations or specific people. Management isn't a bad word, but applied the way it is most places it should be. My goal with teams is to inspire them to make good choices, show them the right paths and help them succeed…

Leadership: doing the right thing Management: doing things right Peter Drucker

Another way of putting this is that leaders determine the best destination and managers determine the best route there.

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

#118
Managers have to communicate both up and down while developers only need to communicate up. When I made the jump from a developer to a manager I had to learn how to properly communicate issues and risks to upper management. If there's an issue related to your team, you should be the first to escalate it. If management hears about your team's issues from a different source, you'll look bad. As manager, my number one job was staying on top of risks and issues, which meant getting up to date information from my reports and communicating the exact magnitude and priority of the risk/issue. If you develop a reputation as someone who can communicate and handle risks and issues well, that'll set you on good footing.

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

#119

In the past 13 years have gone from dev -> tech lead -> manager -> director -> VP/CTO at startups (50-250 people). Here are my tips: - Your job is to provide effective technical solutions to business problems via managing a team(s) of engineers, everything else is an extension to that. - Managing is nothing like coding and requires a completely different mindset and skill set. - Authority comes through respect and un…

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…

Our mechanic was ripping us off. There's this scam where they overtighten the screws on the oil pan and crack the gasket. Oil leaks out very slowly and in some cars ends up on the leads to the battery. This corrodes the leads. They then charge you for a new battery and tell you that there is a electrical problem in your car that will cost thousands of dollars, etc, etc. Luckily I knew about this scam and when our car started losing oil directly after an oil change and the mechanics refused to do anything about it, I was able to tell my wife what was about to happen. This convinced her that the mechanics were scamming us.

So the question became, who do we send the car to. There was a young guy down the street. He was taking apart cars and putting them back together again. His friends were all into racing and while he had previously worked at a dealership, he quit to live the dream of repairing racing cars. Of course he was broke. I told my wife to wander over and see if he wouldn't mind looking after our car. Great mechanic and saved us thousands compared to what the swindlers were doing. Previously the car was breaking down all the time. After we switched it never had a problem. When we replaced our car recently, we gave him our old car as a thank you. Good mechanics are worth keeping happy :-)

It's not really a science for finding people who are good at what they do. There is not a thing that you can pinpoint and say, "That person is definitely good and that person is not". But I think if you start with the proxy of, "That person loves what they do and sacrifices a lot in order to do it", I think you are more likely to find someone good. Not 100%, but you've got a much better shot at it.

Edit: I misinterpreted your post and assumed you meant that you were looking for a good lieutenant to help you. I need more sleep! But either way, work at being that good mechanic in the same way -- love what you do and work hard at it. You'll definitely make progress, so don't worry about it.

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

#120
Your team should see you as a leader who is available, dependable and is providing them space.

You shouldn't see yourself as a "manager" right from day one but gradually in your mind shift into a managerial mode.

Shameless plug - I got obsessed on how great teams get built and run. I started a podcast and the very first episode I got recorded was "How to transition from Individual Contributor to a Manager".

Would appreciate feedback and also any names to the ones I can approach for a guest

https://podcast.nurture.team/episode-01-how-to-transition-fr...

Post reply on HN