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

이 비트의 내용

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.