Solutions for source control platform, branching strategy, IDEs/tools, lib-stack, linters, PR procedures, deployment, infrastructure, unit/e2e testing. Then plan and break the work up into bite sized chunks and feed to developers - provide guidance during development. Shouldn't need much more than that for strictly a tech lead. If you include architecture, you're going to be looking for audit-ability, exit-strategies, backup systems, viability of vendors, support contracts, long term support, future-proof, synergies with existing solutions.
Use work assignments as an opportunity to leverage strengths of weaker devs and career progression for stronger devs. Spot blockers early and tackle those first.
Work with management to understand team key performance indicators and orient processes toward improving those numbers.
Work with product/requirements sources to ensure their KPIs are measurable in the final product.
I'd expect a lead to be very hands-on.
Focus on developer UX. Can they choose their favorite IDE, clone a repo, build, test, PR, merge and deploy with minimal hiccups without delay? Then you've done a good job.
EDIT: I forgot to stress to not be a tech dictator, but work with tech resources on the project to make the decisions and understand them as a group. When they understand and agree you have buy-in you won't have disgruntled devs.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Solutions for source control platform, branching strategy, IDEs/tools, lib-stack, linters, PR procedures, deployment, infrastructure, unit/e2e testing. Then plan and break the work up into bite sized chunks and feed to developers - provide guidance during development. Shouldn't need much more than that for strictly a tech lead. If you include architecture, you're going to be looking for audit-ability, exit-strategies, backup systems, viability of vendors, support contracts, long term support, future-proof, synergies with existing solutions.
Use work assignments as an opportunity to leverage strengths of weaker devs and career progression for stronger devs. Spot blockers early and tackle those first.
Work with management to understand team key performance indicators and orient processes toward improving those numbers.
Work with product/requirements sources to ensure their KPIs are measurable in the final product.
I'd expect a lead to be very hands-on.
Focus on developer UX. Can they choose their favorite IDE, clone a repo, build, test, PR, merge and deploy with minimal hiccups without delay? Then you've done a good job.
EDIT: I forgot to stress to not be a tech dictator, but work with tech resources on the project to make the decisions and understand them as a group. When they understand and agree you have buy-in you won't have disgruntled devs.