A guide to managing complex Git workflows using stacked branches, focusing on techniques for handling common scenarios beyond basic commit changes.
An engineering manager reflects on the role's challenges, feeling accountable but not directly credited, and compares it to surfing.
A developer explains why generative AI coding tools don't increase their productivity, citing the time needed to review code and the responsibility for the final product.
![AI: did you check your work? [blog]](https://alldevblogs.blob.core.windows.net/thumbs/article-98b23f154f19-full-84e80bd4.webp)
A developer's cautionary tale about LLM inaccuracies in simple tasks, highlighting the need to verify AI-generated results.
A software engineer shares stories of taking initiative to meet colleagues and Alan Kay, leading to career opportunities and collaboration.
Explains why developers should split unrelated changes into separate pull requests for faster reviews, cleaner Git history, and better automation.
A senior developer shares eight key lessons on writing clean code, conducting effective reviews, and professional best practices from decades of experience.
A developer shares a custom Git script to improve the process of reviewing large Pull Requests by creating a dedicated review branch for local IDE navigation.
Explores how AI-powered tools automate and improve code reviews by identifying bugs, vulnerabilities, and inconsistencies to enhance software quality.
A developer explains why they limit AI use in programming, citing the difficulty of verifying AI-generated code without a proper mental model.
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.
