A software developer argues that writing less code is a key skill for creating maintainable, efficient systems and solving problems effectively.
A developer argues that writing 'dirty code' is acceptable and beneficial in certain situations to overcome blocks and foster creativity.
Explores why skilled developers write poor unit tests by misapplying production code principles, arguing test code should prioritize clarity over abstraction.
A guide to essential flake8 extensions for improving Python code quality, covering import order, exception handling, and logging best practices.
Explains the importance of the 'refactor' step in the Test-Driven Development (TDD) 'red, green, refactor' cycle for writing better code.
A guide on applying the 'focusing question' technique to identify the most valuable code refactoring tasks that will simplify current project work.
Explores the benefits of Test-Driven Development (TDD), including preventing false positives, improving design, and providing fast feedback.
A software engineering article arguing that simplicity is the most critical quality for achieving correctness and performance in software development.
A defense of seemingly messy CSS code, arguing that complex class structures often evolve from practical needs and team collaboration.
Explains why reassigning variables in JavaScript can lead to bugs and complex code, advocating for using 'const' instead.
Introducing Revive, a fast and extensible linter for Go that improves upon golint with configuration, custom rules, and better performance.
A developer's perspective on separating self-worth from code quality, emphasizing creation over perfection and the importance of refactoring.
Explores debugging techniques like rubber duck debugging and divide-and-conquer, and discusses Stack Overflow's approach to handling novice questions.
A JavaScript tutorial on refactoring a calculator app using best practices like early returns and pure functions.
Explains the three main types of linter errors (unused variables, parsing, formatting) and how to handle them to improve code quality.
Discusses the reasons for 'quick fix' code and provides strategies for avoiding them in front-end development (HTML, CSS, JavaScript).
A web developer's call to action: share only accessible, semantic code examples and be responsible when publishing technical articles.
An analysis of nine code quality tools for Clojure, evaluating their functionality and issues in a real-world project with cljc files and spec.
Argues that code reviews should be a team effort, not a single person's responsibility, to improve quality, share knowledge, and build ownership.
A guide to disciplined C programming, emphasizing maintainability, simplicity, and avoiding dangerous patterns for writing robust code.
