4 ms·
It really depends on who they are and how good at their job they are. I’ve seen more bad ones than good ones. I prefer a lead or senior developer to have the r
by i_like_apis 4y ago
It really depends on who they are and how good at their job they are. I’ve seen more bad ones than good ones.
I prefer a lead or senior developer to have the role rather than a dedicated non- or even former- developer.
When a good lead dev with good communication skills and experience has the role it can be awesome.
- morelisp 4y agoIt is rarely awesome for the lead or senior dev.
- i_like_apis 4y agoAnyone who doesn’t want to do it is the wrong person, and doesn’t sound like a good lead dev to me.
- morelisp 4y agoA lead dev isn't necessarily a team lead. They could be a technical lead, or an architect, or simply a senior dev with deep knowledge of one specific project. They may not have the interest, skill, or authority to deal with the situation. Even if they can do it you may be pushing them towards quitting or burnout; or creating a feedback loop where their technical contributions drop because they need to coordinate more people because quality is dropping because your top dev's technical contributions dropped.
- i_like_apis 4y agoSounds weak. I wouldn’t call that person a team lead or a lead dev. Agile doesn’t take much effort if you know what you’re doing. It’s just a card wall, standups and a planning meeting. This is not hard for a good lead dev. If you think it’s hard, you probably aren’t a good lead dev, or you don’t know how to do it right, which is the same thing.