As a tech lead your job is to support the developers in your team so they are as effective as possible. This means:<p>1. You must know the code. Say &#x27;no&#x27; to meetings - spend most your time coding
2. Be honest - When you know the answer say so even if that means someone will have to redo a lot of work. If you don&#x27;t know the answer, say so (there&#x27;s no point pretending to be cleverer than you are - you got the job so you deserve it, never try to prove your abilities to others)
3. Remember your job is to support others so fight for your team&#x27;s interests even (especially) when unpopular higher up.
4. Lead by example - take the shit jobs and write awesome code.
5. Let your team members review your code AND TAKE THEIR ADVICE!
6. When team members ask you questions attack their problems with the same determination as you would attack your own
7. To inspire your team members you need to be loyal to them.
8. To inspire your team members you need to be loyal to the business (often forgotten)
9. &#x27;7&#x27; is more important than &#x27;8&#x27;
10. Be the best developer you can be (note the word &#x27;be&#x27; not &#x27;appear to be&#x27;)<p>Ultimately, if your team regularly invite you for beers after work and your boss respects you then you are doing ok. Never, ever assume that &#x27;team lead&#x27; is anything more than a specialist role within the team. Your job is to support others. That does not make you more special or important. Respect is earned not given. Being a good team lead is much the same as being a good developer. If you find the job hard then you weren&#x27;t really a good developer. This is why a lot of companies don&#x27;t externally recruit tech leads, preferring to recruit from within.