A software developer's monthly retrospective on writing a book about effective writing for developers, covering progress, metrics, and reader feedback.
A software engineer explains the pitfalls of organizing code into generic 'utils' modules, using a real-world example of circular dependencies.
A developer details refactoring Astro content collections configuration for the Piccalilli platform to enable open working and project pages.
Explores using onion architecture, separation of concerns, and cohesion to build adaptable, maintainable software under tight deadlines.
A guide for developers on addressing gaps in code coverage, covering strategies like writing unit tests, refactoring code, and handling edge cases in TypeScript.
The article explains the true meaning of 'refactoring' in software development and argues for its proper use to avoid client misunderstandings.
A senior developer shares eight key lessons on writing clean code, conducting effective reviews, and professional best practices from decades of experience.
A developer refactors an outdated JavaScript performance snippet to improve security and adhere to modern web best practices.
A developer reflects on a year of launching the Swift Academy podcast, discussing iOS topics like TDD and modularization, and building a new framework.
A developer recounts the decision to revert a major refactoring of the EqualsVerifier library after encountering persistent edge cases and bugs.
Explains structure-cementing tests that hinder code refactoring and introduces a TestDsl approach to write flexible, maintainable tests.
A developer shares a specialized git workflow for separating refactoring from feature work to improve code review efficiency and clarity.
A guide to refactoring Vue.js 3 applications by replacing manual fetch logic with TanStack Query for efficient data fetching, caching, and state management.
Explains why OpenAPI definitions break in ASP.NET Core Minimal APIs after refactoring and how to fix them by preserving metadata.
Explores how comprehensive testing enables the 'Four Rules of Simple Design,' focusing on how tests support change, intention, and duplication removal.
Explores the 'Fewest Elements' rule in software design, advocating for removing unnecessary code like unreachable lines, comments, and unused abstractions.
Explains evolutionary design in software development as a middle path between over- and under-design, emphasizing simplicity and refactoring.
A technical article explaining how to use TypeScript's type inference to reduce explicit type annotations and improve code maintainability.
A developer explains how using flow diagrams in Miro helps plan and refactor complex state management in a Vue.js application for a wind turbine data visualization tool.
A developer compares coding in volunteer, agency, and product roles, using gardening as a metaphor for managing legacy code and continuous improvement.
