“If i write something and it doesnt get used, i get angry”
The ultimate test for a tech lead:
Does the codebase look like it was written by a single person?
We need consistency in what we are doing
Tech lead focus:
Effective tech lead needs to code?
Definetely… 30% of time writing code
You need to experience the same problems that the people have
consistency over cleverness
-what is best? context
-> most of the times there are more important topics to spend time on
- how long does the build stay broken
- do people avoid conflict?
- do people offer new ideas?
- do people fail and learn?
- do people flag when they need help?
- do people admit to being wrong?
XP practice: the metaphor
- Why does your software exist?
- Why is it important?
Culture: Ask for help: ”no i am almost done. “
- Diversity is important
#book: strengthsfinder tom
help people find their strength
- #book the difference scott e page
- Diversity —> ability to integrate them
- trust is built incrementally. not in 1 day
- create opportunitites for social time -> lunch
- small activities are important
- grow the people
challenge / skilly(ablity)
- have 1on1s with people
- challenge them outside their skillset
#book flow book
maximize potential to people
- team code reviews
- brown bad sessions
- spike showcases (show off features, what have learned)
- techincal retrospectives (pick parts of the code and talk about it)
- video/book club
bad is stronger than good (1negative — 10positive) #paper
is it okay to tell people what to do?
“yes but only sometimes”
the “situational leadership model”
Difference between: directing, coaching, supporting, delegating
- forming, storming (conflicts), norming, performing, adjourning
- every change in the team, and you start again.
add or remove 1 person