[masukomi]

It's been commented by others, but I just wanted to chime in that when I was a tech lead I was _very_ happy if I could close one ticket a week. It took me a while to accept just how much I had to delegate because while I _knew_ how to solve the problems faster and better than most of the people on my team (i had more experience with the product and more experience writing software) I simply couldn't productively contribute to the codebase _and_ do my job as a tech lead, which was _mostly_ answering questions and making decisions about how to proceed all day.

I'm not saying your lead isn't an idiot. I just wanted to give another viewpoint on why "tickets closed" is a terrible metric to apply to a tech lead. If you're fixing tons of bugs and closing lots of tickets you're probably not tech leading as much as you think you are.

Being tech lead isn't about being a productive coder or being the _best_ coder. It's not even about knowing more about coding than the others on your team. It's about eliminating the technical roadblocks for your team by answering questions helpfully and making good decisions about the direction to move the codebase, and having meetings and discussions about the future of the codebase. All of that takes a ton of time.