↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Nobody cares about your code

The article argues that programming work should be judged by the product, not by the code itself. Code is presented as a tool for delivering features, so refactoring, craftsmanship, and tool choice matter because they help make the product better and easier to review.

Reading notes
#

  • Programmers are not paid to write code for its own sake; they are paid to supply software that provides needed features.
  • Refactoring should be framed as a way to improve the product, fix defects, or implement features, not as code improvement alone.
  • Security and fault tolerance depend on good craftsmanship and the right libraries, while the rest of the code should stay uninteresting and easy to review.
  • Communication with product managers or customers should focus on feature status, not on classes, lines of code, deployment scripts, exception strategy, or database schema.
  • A client asking for source code usually wants continuity, security review, or legal auditability, not the code as an end in itself.
  • A library may be valuable to its author because it speeds up work, but that does not make it inherently valuable to others.
  • Writing poor code is not justified; quality workmanship is still necessary because bad tools can prevent the product from meeting requirements.
  • The programmer’s goal is to polish the product, not the code.