The Stack Overflow podcast is back! Listen to an interview with our new CEO.
2 additional response
source | link

Your have two primary roles as lead developer: to be an advocate for your team with the business side of your operation, and to provide technical guidance to your team.

As advocate, you should be helping to communicate requirements to your team, pushing back when the business side (be it management, project managers or sales people) makes unrealistic requests or demands, and generally dealing with anything that stops your team from writing code.

As technical mentor, you need to help your team make good decisions, assist them with any technical problems they have, and direct them to proper solutions. You should be encouraging them to improve their skills, and be an absolute stickler for following proper development standards.

Most importantly, you need to be an impeccable role model. Your code should be of the highest standard, your projects should be delivered on time and be of the highest quality. What you do is going to be far more important than what you say.

EDIT: One further thing. You need to be proactive with technical issues. Do not wait for your team to come to you with problems. Be aware of what they're working on, and go to them if they're taking too long, if you know they're on something tricky or outside their core skill set, or if they look frustrated. Listen when people on your team start discussing technical problems without you, and step in if (and only if) you feel like they're starting to drift away from a decent solution, or if they're going in circles and not accomplishing anything.

Your have two primary roles as lead developer: to be an advocate for your team with the business side of your operation, and to provide technical guidance to your team.

As advocate, you should be helping to communicate requirements to your team, pushing back when the business side (be it management, project managers or sales people) makes unrealistic requests or demands, and generally dealing with anything that stops your team from writing code.

As technical mentor, you need to help your team make good decisions, assist them with any technical problems they have, and direct them to proper solutions. You should be encouraging them to improve their skills, and be an absolute stickler for following proper development standards.

Most importantly, you need to be an impeccable role model. Your code should be of the highest standard, your projects should be delivered on time and be of the highest quality. What you do is going to be far more important than what you say.

Your have two primary roles as lead developer: to be an advocate for your team with the business side of your operation, and to provide technical guidance to your team.

As advocate, you should be helping to communicate requirements to your team, pushing back when the business side (be it management, project managers or sales people) makes unrealistic requests or demands, and generally dealing with anything that stops your team from writing code.

As technical mentor, you need to help your team make good decisions, assist them with any technical problems they have, and direct them to proper solutions. You should be encouraging them to improve their skills, and be an absolute stickler for following proper development standards.

Most importantly, you need to be an impeccable role model. Your code should be of the highest standard, your projects should be delivered on time and be of the highest quality. What you do is going to be far more important than what you say.

EDIT: One further thing. You need to be proactive with technical issues. Do not wait for your team to come to you with problems. Be aware of what they're working on, and go to them if they're taking too long, if you know they're on something tricky or outside their core skill set, or if they look frustrated. Listen when people on your team start discussing technical problems without you, and step in if (and only if) you feel like they're starting to drift away from a decent solution, or if they're going in circles and not accomplishing anything.

1
source | link

Your have two primary roles as lead developer: to be an advocate for your team with the business side of your operation, and to provide technical guidance to your team.

As advocate, you should be helping to communicate requirements to your team, pushing back when the business side (be it management, project managers or sales people) makes unrealistic requests or demands, and generally dealing with anything that stops your team from writing code.

As technical mentor, you need to help your team make good decisions, assist them with any technical problems they have, and direct them to proper solutions. You should be encouraging them to improve their skills, and be an absolute stickler for following proper development standards.

Most importantly, you need to be an impeccable role model. Your code should be of the highest standard, your projects should be delivered on time and be of the highest quality. What you do is going to be far more important than what you say.