markdown guide
 

Listen to their needs. Put standards into place, work smart not hard. Take care of impediments asap. Don't betray them just to look good with your superiors. Protect them from stupidities. No one wants to maintain legacy code whole day, every day. It's easy to know, wear their shoes and see what would you want. Don't be a seagull manager, they will hate you for it. Technical debt is real, don't encourage it. Deal with things don't let them fester. Make them review each others code if time permits. I can go on forever...

 
 
 

Treat them like a human, not just a resource. Shelter them from bureaucracy. Criticize them privately, praise them publicly.

 

I am not a lead but I can suggest you to treat your team members the way you wanted to be treated when you were a part of someone else's team.

Classic DEV Post from May 10

What do you wish you knew about Developer Relations?

A conversation... what do DevRel professionals wish devs knew about their job? And what do devs wish they knew about DevRel?

Arswaw profile image
Lead Programmer @Whirlpool , Gamer, JavaScript and Star Trek fanboy. Perpetual WoW Noob for 12 years.

A blogging community of over 100,000 software developers Join dev.to