A Google engineer shares 14 lessons on teamwork, decision-making, and focusing on the right problems, based on 14 years of experience.
A tech manager shares lessons on handling team salary disputes and collective issues after competitive hiring leads to pay disparities.
A senior engineer shares advice on driving technical change and influencing teams without formal authority, based on a conference talk Q&A.
A software engineer reflects on how passionate, friction-filled debates within a tech startup signal team investment and care, contrasting with apathy.
Discusses why blindly copying technical solutions or processes from one team to another often fails due to unique team and company contexts.
Analyzes George Hotz's resignation from Twitter, highlighting the pitfalls of technical arrogance and poor teamwork in large tech companies.
Discusses the importance of human factors like team onboarding, reversibility, and support when choosing software architectures and technologies.
Discusses the importance of context and team factors over hype when choosing software architectures and tools.
Explores the mental framework of 'builders' vs 'architects' in programming to understand team conflicts and improve collaboration.
An engineering manager shares their personal Manager README, outlining their philosophies on team leadership, feedback, and software development processes.
Explores the concepts of 'bikeshedding' and 'honeypots' in software, introducing the idea of a 'bikeshed honeypot' to manage feedback.
Explores the subjective nature of defining a 'good programmer,' arguing it depends entirely on the perspective of the person asking.
