Hacker News new | past | comments | ask | show | jobs | submit login

See "conceptual integrity" in The Mythical Man-Month. There needes to be someone who resolves technical conflicts and keeps the design conherent.



You can have a business / product person effectively prioritize the work - this is not necessarily a requirement of tech lead.

But I for one, suggest that 'coherence' is an important thing and someone needs to 'lead' that.

Feasibly, it could be an 'architect' or someone in that role, meaning that 'theoretically' you don't need a 'tech lead'.

But I'd suggest in reality, someone should be the 'lead' in one way shape or form.

Maybe they can soften the role and get the devs to understand that it's more of a 'principal' than a 'boss' type thing.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: