A guide to improving code reviews by focusing on constructive, non-personal feedback and providing clear, actionable comments.
Explores practical team mechanisms like end-of-week debriefs and monthly learning sessions to boost productivity and collaboration in technical teams.
Explores practical mechanisms like pilot/copilot roles and literature reviews to improve the success rate of machine learning projects.
A developer's weekly reflection on George Hotz's Twitter exit, codebase criticism, and the challenges of tech management.
Analyzes George Hotz's resignation from Twitter, highlighting the pitfalls of technical arrogance and poor teamwork in large tech companies.
A guide to writing constructive and polite code review comments on pull requests, emphasizing clarity and empathy.
Argues against prematurely squashing/rebasing PRs before review, explaining how it hinders reviewers and suggests using 'Squash and merge' on merge instead.
A developer explains the advantages of using email workflows for code review and patch management, comparing it to platforms like GitHub.
A senior engineer at Lyft outlines the risks of using third-party libraries in production apps and proposes a framework for consistent risk assessment.
A guide on introducing Test-Driven Development (TDD) to a software team through leading by example and building consensus.
Introduces the 'Code Review Pyramid' concept to prioritize important aspects like functionality and performance over style in code reviews.
Introduces the 'Code Review Pyramid' concept to prioritize important aspects like functionality and performance over style in code reviews.
A guide to effective code review practices, focusing on goals, culture, and team collaboration for maintaining code quality.
A developer shares their structured process for conducting effective code reviews, focusing on PR size, UI checks, and common pitfalls.
Learn how to fetch a remote feature branch from a GitHub pull request to review changes locally using specific git commands.
Guidelines for effective pair programming in software development, covering when to pair, session length, and team dynamics.
Best practices for developers to prepare and submit code for review, ensuring productive feedback and positive team dynamics.
Tips for creating high-quality pull requests in open source projects, focusing on communication, style guides, and documentation.
A developer argues for the value of inline code comments as a durable form of documentation, contrasting them with ephemeral pull request discussions.
A software engineer shares four techniques to improve skills beyond learning new frameworks, focusing on problem-solving and impact.
