A developer argues against using AI for every problem, highlighting cases where classic programming is simpler and more reliable.
A blog post discussing the importance of speed in technology and work, referencing Daniel Lemire's insights on avoiding obsolescence.
A critique of AI's role in software development, arguing that output is not productivity and that expertise remains essential for solving real problems.
An article arguing that engineers should not use complexity as an excuse for poor design, emphasizing the importance of creating simple user experiences.
A senior developer shares key lessons on software quality, automated testing, and bridging the gap between technical and non-technical stakeholders.
A developer draws parallels between physical clutter and technical debt, advocating for regular 'code cleaning' sessions to improve team happiness and productivity.
Engineers should focus on understanding the underlying problem behind a task, not just executing it, to avoid creating useless or poorly designed features.
A consultant outlines six common signs that a software system's architecture lacks visibility and discoverability, hindering developer understanding and maintenance.
A guide to manually tackling tedious software development tasks like linting and dependency upgrades, and when brute force is the right approach.
Strategies for development teams to identify, plan for, and break the vicious cycle of accumulating technical debt.
Explains how to leverage urgency to justify large-scale refactoring projects and gain organizational buy-in for technical improvements.
A monthly update on TinyPilot, a tech hardware project, covering revenue, product development challenges, and business bottlenecks.
A developer shares 9 key lessons learned from maintaining a large Vue.js codebase for 3 years, focusing on consistency, legacy code, and dependencies.
Explores the causes of legacy software and offers developer strategies to prevent codebases from becoming hard-to-maintain systems.
A developer's chart on career priorities goes viral, sparking discussion on the evolution from making code work to valuing readability and avoiding over-abstraction.
A developer explains why they left a job due to stagnation, outdated tech, and lack of growth, critiquing high turnover as a company failure.
Article argues that code quality directly impacts user experience by enabling faster feature delivery and fewer bugs.
A satirical article about a town building a new, high-tech road that prioritizes cars and revenue over pedestrians and cyclists.
The article argues for co-locating code comments with the relevant code, explaining the maintainability and clarity benefits over separate documentation files.
A speaker's reflections on PyTexas 2019, summarizing key talks on feature flag management and using mypy with ORMs.
