Explores why developers overcomplicate software and proposes deliberate side-projects as a solution to balance innovation with practical technology choices.
Article argues that code quality directly impacts user experience by enabling faster feature delivery and fewer bugs.
A developer discusses challenging management's demand for 100% test coverage, arguing it leads to meaningless tests and suggesting direct communication as a solution.
A satirical article about a town building a new, high-tech road that prioritizes cars and revenue over pedestrians and cyclists.
A critique of blindly following software development 'best practices', arguing for more thoughtful discussion and application.
The article argues for co-locating code comments with the relevant code, explaining the maintainability and clarity benefits over separate documentation files.
Argues against Friday deploy freezes, explaining how they create technical debt, hurt team productivity, and indicate a fear of deployment that should be fixed.
A speaker's reflections on PyTexas 2019, summarizing key talks on feature flag management and using mypy with ORMs.
A software developer's guide to maintaining codebases and tools, emphasizing addressing warnings and keeping dependencies updated.
A guide to creating effective performance budgets for web development, focusing on concrete metrics and team integration.
An article discussing the importance of fixing hidden technical debt and friction in software development, even when it's not immediately visible.
A guide on applying the 'focusing question' technique to identify the most valuable code refactoring tasks that will simplify current project work.
A retrospective on the OpenStack Telemetry project's evolution, covering technical debt, project splitting, and challenges with community adoption.
Analyzes three strategies companies use to innovate with cloud technology: born-in-cloud, startup acquisition, and creating centers of excellence.
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 developer recounts a massive, poorly-scoped code review and the strategies used to salvage it, emphasizing best practices.
Explains why smaller code reviews are more effective and offers practical strategies for splitting large patches into manageable pieces.
Analyzes the three major challenges hindering government IT: change aversion, lack of technocratic leadership, and non-scalable processes.
The article argues that web performance is a cultural, not just technical, problem and requires a holistic approach throughout development.
A programmer discusses common bad habits like leaving unused code, over-generalization, and OOP fixation, offering advice for cleaner development.
