Explores how code complexity creeps into projects and offers automated strategies to detect and prevent it, promoting continuous refactoring.
A guide to refactoring PowerShell switch statements, demonstrating how to replace them with hash tables for cleaner, more maintainable code.
The article argues for the importance of developing code reading as a critical skill for software engineers, alongside writing code.
Developer updates on email-based tools for software development, including web patch review for sourcehut and new email composition in aerc2 terminal client.
A developer reflects on two unexpected lessons from their first in-house software job: the value of code reviews and the importance of communication over just coding.
The article argues for optimizing code for auditability to make security vulnerabilities easier to spot, using cryptography as a key example.
A guide to the GitHub pull request review process, covering merging, commenting, and updating code from both reviewer and submitter perspectives.
A beginner-friendly guide explaining what a pull request is, using an analogy, and detailing the steps to submit one on GitHub.
A developer shares 10 frequently violated clean code principles, covering naming, comments, duplication, and formatting.
A summary of key talks from Day 1 of the Lead Developer Conference, covering containers, tech leadership, and code reviews.
A guide to implementing effective code reviews, covering tone, automation, and best practices for teams.
A summary of a Python Frederick meetup featuring Christine Lee's presentation on data science tools and features available in Python.
A guide on improving code review communication and avoiding conflict, based on a real-world example of a failed review process.
A guide to improving code reviews by focusing on constructive communication and empathy, treating it as a social process rather than just a technical one.
Argues that code reviews should be a team effort, not a single person's responsibility, to improve quality, share knowledge, and build ownership.
A tech lead's role is to guide the team's future direction, not just write code. Focus on strategy, planning, and empowering engineers.
A guide on how to approach and learn valuable lessons from legacy codebases, distinguishing between good and bad examples.
A guide for open source maintainers on how to gracefully close or reject unwanted pull requests and patch submissions.
A guide on managing difficult pull request discussions, focusing on setting ground rules, assigning roles, and maintaining productive collaboration.
A developer recounts a massive, poorly-scoped code review and the strategies used to salvage it, emphasizing best practices.
