Leading developers without becoming a meeting
Technical leadership is mostly subtraction. Subtract unclear tickets. Subtract hero culture. Subtract the meeting that could have been a written decision.
At Digital Six in Australia I work as a team lead and senior WordPress developer. I also lead a team of 10. The job is not to be the smartest typist. It is to keep architecture coherent and estimates honest while people still have a life outside Slack.
Remote from Nepal only works if writing is infrastructure. I write decisions down so nobody needs me awake at 3am to unlock a merge. Reviews should teach. Staging should embarrass you before production does. That is the whole operating system.
Building something that needs this mindset?
Start a conversation, or request the CV.