↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Philosophy of a Good Developer

The post says a good developer is not defined only by technical strength. It presents six rules that stress readable code, documentation, user awareness, responsibility, and seeing the product as part of a larger team effort.

Reading notes
#

  • In commercial projects, code should be readable for other people, not just for the person writing it.
  • Variable names should clearly show their purpose.
  • Comments and tools like JSDoc can help other developers understand code faster.
  • A project wiki should capture setup steps, recurring problems, and other useful project knowledge.
  • Proper formatting makes code easier to read and maintain.
  • Developers should write down things they might forget, including TODO items.
  • Developers should think from the user’s point of view and check whether the feature is actually usable.
  • Copy-pasting and other shortcuts can create more work later, so the work should be done properly.
  • Team members should avoid blaming each other when something breaks and instead take ownership.
  • A developer should look at the bigger picture and understand that their work is tied to the product and the company’s reputation.