this post was submitted on 10 Jul 2023
20 points (100.0% liked)

Experienced Devs

3950 readers
1 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

founded 1 year ago
MODERATORS
snowe@programming.dev
jmk1ng@programming.dev
drewsiferr@programming.dev
20
Advice for shifting into a software developer management role (kbin.social)
submitted 1 year ago by SirNuke@kbin.social to c/experienced_devs@programming.dev
5 comments fedilink hide all child comments
 

I've thought it over, and I've decided the best next step for me is to shift from a software developer to a management role.

I've worked a lot of high stress, fast paced positions, mostly in R&D groups/companies, which I always excelled at. I now understand why I did well in that type of environment (undiagnosed ADHD), and how to be properly organized enough to perform in an SDM role (ADHD meds lol).

Honestly sitting in meetings for 30+ hours a week doesn't sound so bad anymore. Racing to get a lot of technical work done in a tight timeline now sounds miserable. I've had some amazing SDMs, and I'm confident I can be better at it than most I've worked under.

So: any and all thoughts, what books or resources would you have recommended to yourself, what companies or roles might be a particularly good fit.

you are viewing a single comment's thread
view the rest of the comments
[–] ICastFist@programming.dev 6 points 1 year ago

Read the old Dilbert strips to learn everything you should -not- do about being a manager 🤡

Regarding skills, the most important is having keen ears and being good at **understanding **what people want. People might say or write something, but mean another thing, for any reason: malice, lack of knowledge, insecurity, etc. Document as much as possible when it comes to decision making. An email of "Go ahead with X" is the best defense you can have if the project blows.

The manager needs to juggle the team under him and the avalanche of demands coming from elsewhere, so the pressure comes from all sides. The manager becomes "the face" of the team, so whatever the team does becomes his responsibility. The more you see them as a team to be guided/led, instead of servants to be ordered, the better your relation will tend to be with them.