An engineering manager reflects on the role's challenges, feeling accountable but not directly credited, and compares it to surfing.
A software engineer discusses strategies for prioritizing and integrating technical cleanup work into the development process, arguing against isolated "technical sprints".
A critique of over-engineering in software development, arguing that excessive abstraction can create complex, unmaintainable code.
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.
The article explains the true meaning of 'refactoring' in software development and argues for its proper use to avoid client misunderstandings.
A summary of talks from DevFestMN 2024, covering tech debt, AI in interviews, on-device AI, and the UX of AI.
Puzzmo removes its chat feature due to low usage and technical challenges, shifting focus to core UI improvements.
Engineers should focus on understanding the underlying problem behind a task, not just executing it, to avoid creating useless or poorly designed features.
A podcast discussing why all code becomes legacy and how to write modular, maintainable code to reduce future technical debt.
A podcast episode discussing how to write code that becomes manageable legacy code, using a personal game development example.
A senior engineer reflects on the complex reasons behind messy codebases, arguing against blaming developers and for focusing on systemic solutions.
A TypeScript tip on using a custom `TODO` type as a purposeful escape hatch for difficult type problems, with a caution against overuse.
The article uses the visible routers at Centre Pompidou as a metaphor for how software systems evolve and adapt to new requirements over time.
A summary of a study showing how technical debt and low code quality significantly slow development and increase defects.
A developer's reflection on the challenges of modernizing the aging Dask project blog, exploring technical and community communication hurdles.
A senior engineer explains why writing less code is often better, focusing on long-term maintenance costs and technical debt.
A consultant outlines six common signs that a software system's architecture lacks visibility and discoverability, hindering developer understanding and maintenance.
A developer argues for proactively cleaning up unused code and dependencies to prevent future technical debt and hidden bugs.
