↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Becoming a pale, pasty programmer

The post says that getting better at programming requires real practice, not just interest. It recommends building side projects, even by cloning an existing idea, because coding time and repetition matter more than waiting for the perfect concept.

It also argues for persistence, rewriting sloppy shortcuts, and learning from other people’s code and technical papers. The main point is that strong programmers keep working through problems, fix mistakes properly, and spend enough time reading good and bad examples to improve.

Reading notes
#

  • Practice matters, whether it comes from class, a side project, or a job.
  • Starting with a cloned project can help by removing pressure from ideas and design.
  • Programming problems require persistence and the ability to keep going after repeated setbacks.
  • Solving problems is presented as more valuable than raw intelligence alone.
  • Shortcuts in code should be replaced by proper structure, even if that means rewriting.
  • Reading other people’s code, including bad code, helps show what better code should look like.
  • Books and papers are also useful, but the post says doing the work matters more than reading alone.