> However I hope you will also agree with me in that the term "lead" for many things gets thrown around quite easily in the tech world.
Hm, actually I haven't seen it. For me, "lead" has a very exact meaning: a developer who is personally responsible for code that developers people write, and has authority appropriate to that responsibility.
In my experience a lead developer is the primary contact and owner for a specific feature or program. This person should know everything about what they are lead of inside out, they make decisions on design and implementation. They are able to support members of the team that are below them. They can delegate work to those in their team. Review the work done and offer constructive feedback. Communicate their ideas and vision to those below and above them. Present their ideas and concerns to management and stakeholders with ease.
So there are a few buzzwords in that but that is pretty much my personal experience of what a lead developer should be.
I think part of the problem is that there is no industry standard definition of what a lead developer is. It has been my experience it is abused in the ways I mentioned in my previous post.
Again this is all just my personal experience. We are all shaped by our history and though we try and not judge people automatically it will happen from time to time.
Hm, actually I haven't seen it. For me, "lead" has a very exact meaning: a developer who is personally responsible for code that developers people write, and has authority appropriate to that responsibility.
What else can it mean?