↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

We are destroying software

The author argues that software is being damaged by practices that ignore or increase complexity, from bloated build systems and dependency chains to frequent rewrites and trend-chasing in languages and frameworks. These habits undermine learning, tailored design, backward compatibility, simplicity for basic tasks, and the pleasure traditionally associated with programming.

Reading notes
#

  • Claims software is being harmed because developers add features or optimize specific aspects without considering the resulting complexity.
  • Criticizes complex build systems as a factor contributing to the degradation of software.
  • Argues that long chains of dependencies make software bloated and fragile.
  • Challenges the advice to avoid reinventing the wheel, saying reimplementing things teaches how they work and can lead to new variants.
  • States that disregarding backward API compatibility contributes to destroying software.
  • Sees the push to rewrite working systems as a harmful trend.
  • Describes jumping onto every new language, paradigm, or framework as damaging behavior.
  • Notes that developers often underestimate the difficulty of using complex existing libraries compared to building their own solutions.
  • Points out a tendency to assume that de facto standards are always better than custom solutions tailored to specific needs.
  • Disagrees with the claim that code comments are useless, presenting it as another way software is harmed.
  • Objects to treating software solely as an engineering discipline, implying this view is incomplete.
  • Criticizes systems that cannot scale down, insisting that simple tasks should remain simple in any system.
  • Warns that prioritizing speed of code production over thoughtful design quality damages software.
  • Concludes that these practices are eroding software to the point where it may stop providing the joy of hacking.