The Pragmatic Programmer

重要なポイント

• Take responsibility for your work and your career; nobody else will manage them for you
• Every piece of knowledge should live in one place, so a change is made once
• Fix small problems early because neglect spreads, like one broken window inviting more
• Build in small steps, get feedback fast, and let the design adapt to what you learn
• Automate anything you do more than twice, from tests to deployment to setup

このbitの内容

1. 小手先の技より確かな職人技

   Picture 2 developers at a Bengaluru startup. One writes brilliant, dense code that only she understands and grumbles when requirements change.

2. 同じことを繰り返さない（DRY原則）

   The book's most quoted principle is DRY, short for don't repeat yourself. The idea is not simply avoid copy and paste.

3. 割れ窓理論とソフトウェアの腐敗

   Hunt and Thomas borrow an idea from urban policing. A building with one broken window that stays unrepaired soon has many, because neglect signals that nobody cares.

4. 曳光弾とプロトタイプ

   How do you build something when you do not fully understand the problem? The authors offer 2 tools that are often confused.

5. 自動化、テスト、ツールの熟知

   Pragmatic programmers are lazy in a useful way. Anything you do more than a couple of times, they say, should be scripted: building, testing, deploying, setting up a new machine.

6. 実践に移す

   This week, find one piece of duplicated knowledge in your project, a rule or a value that lives in more than 1 place, and give it a single home. Fix one broken window: a flaky test, a misleading name, a comment that lies.