News for hackers. Stuff that matters.

A comment on We don't need a Tech Lead. Parent comment

Re:We don't need a Tech Lead by titzer on Friday December 02, 2016 @09:54AM (#13088962)
Of the systems I have worked on, I cannot imagine any of them working well having been designed by consensus, no matter how skilled the team members. A techlead role is that of an architect; come up with the overall design to make it logical, consistent, coherent. You definitely wouldn't want a programming language that was designed by a committee, or would you?
[ Parent | on HN ]
Re:We don't need a Tech Lead by bryanlarsen on Friday December 02, 2016 @10:06AM (#13089078)
My favourite programming language, Rust, is designed by committee.
[ Parent | on HN ]
Re:We don't need a Tech Lead by zaphar on Friday December 02, 2016 @10:11AM (#13089135)
According to the Rust team page Rust has not just one "Tech Lead" but 6 who have the responsibility of

    overall direction of the project, subteam leadership, 
    cross-cutting concerns
Which to means if a deadlock happens on a subteam these six will be breaking it.
[ Parent | on HN ]
Re:We don't need a Tech Lead by steveklabnik on Friday December 02, 2016 @12:08PM (#13090318)
Yet in general, consensus is the guiding mode of operation for all teams. The core team has never overridden a team's decision against their will, and while such a thing is technically possible, it would be considered a catastrophic event, I'd imagine.

(Source: I am one of those 8 (not six))

[ Parent | on HN ]