|
|
|
|
|
|
by thekhatribharat
2566 days ago
|
|
|
A couple of points: 1. Provide developers with convincing reasons for important product decisions. 2. Developers do not like to be led by someone they think isn't technically capable. Being a smart rubber duck for the team works in most discussions, and when niche technologies are presented, you can always buy time to read up on it before greenlighting solutions. 3. Be proactive in resolving internal team conflicts, in an amicable and respectful fashion. |
|
|