A developer shares a specialized git workflow for separating refactoring from feature work to improve code review efficiency and clarity.
A humorous guide to common code review antipatterns that hinder development, written from a 'dark side' perspective.
A monthly tech digest covering Meta's DotSlash tool, AI-powered code reviews, AWS Lambda scaling, observability trends, and Cloudflare's logging pipeline.
A summary of John Ousterhout's book on managing software complexity through decomposition, encapsulation, and incremental design.
A developer analyzes a 'magic number' in code, exploring the hidden conversations and UX decisions behind a seemingly simple limit.
A developer shares personal insights and best practices for conducting effective and collaborative code reviews within a software team.
A developer discusses overcoming the personal impact of constructive criticism to grow professionally and personally, using the concept of anti-fragility.
Argues that pull requests are a valuable form of documentation, capturing the 'why' and context behind code changes for future developers.
A tech manager argues that team problems are often human issues, not process flaws, using a PR example to advocate for direct communication.
A code review of the Obsidian Clipper plugin, focusing on its TypeScript and Svelte implementation for clipping web content into notes.
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.
