A developer explains 'Parametric Progress', a method for improving codebases by changing only one aspect at a time to better understand system effects.
Announcing a live stream with a typescript-eslint maintainer to build custom ESLint rules and answer questions about ESLint for JavaScript/TypeScript.
A guide to improving code reviews by focusing on constructive, non-personal feedback and providing clear, actionable comments.
Explains why deep code nesting is problematic and demonstrates refactoring techniques like extraction and inversion to reduce complexity in C#.
A detailed review of Mat Ryer's 'Go Programming Blueprints' book, covering its strengths, weaknesses, and key takeaways for Go developers.
Five practical tips for software engineers to improve their skills in 2023, covering learning, code quality, complex systems, cloud, and self-care.
A programmer's reflection on the philosophical and practical differences between truly fixing a bug versus just patching it, emphasizing testing and documentation.
A review and guide to NDepend, a static code analysis tool for .NET, covering its features, setup, and use for improving code quality.
Argues that well-written unit tests serve as the most reliable and up-to-date form of documentation for software code.
A developer reflects on their technical contributions at Forem, including implementing pre-commit hooks, upgrading Preact, and advocating for accessibility.
A guide for developers joining an Angular project, advocating for proactive codebase improvements like enabling strict TypeScript to enhance quality and team morale.
A step-by-step tutorial on installing and configuring the ESLint extension in VS Code to enforce consistent code style.
A developer shares practical principles for successfully refactoring complex, large-scale codebases without introducing regressions.
A developer investigates a bug in a Space War game where duplicate bases cause crashes, detailing the debugging process and unit testing.
A critique of publishing code as images in academic papers, highlighting errors and reproducibility issues in statistical computing examples.
A developer's personal rule for avoiding technical debt by not writing 'bad' code, based on experiences with legacy systems.
Explains what 'magic values' are in programming and provides examples of how to replace them with named constants for better code clarity.
A senior software engineer shares practical tips for succeeding in a new job, focusing on kindness, work attitude, and code quality.
Analyzes the problems with if/else/switch statements in code and proposes a polymorphic factory object solution for better architecture.
A developer's reflection on how writing a test for a simple one-line bug fix can become a complex, time-consuming task.
