I'll start: + He provides great code reviews while educating people - He fails at contributing actual code and his tickets usually drag across sprints
+ Explains difficult technical stuff without withholding any information - Changes decisions frequently and misses the big picture
+ Has good intuition and asks for double checks where complex behavior may go wrong (and tests don't catch it) - Has no direction and is doing whatever they want, a week on this module, another in an entirely different part of the stack. - Impossible to convince on anything slightly subjective
Don't code.
+ offers great code reviews + SME in system designs - lacks strategic view (could also imply that management is restraining on this?)
Tech leads rarely have time to contribute code because they have to deal with other things.