Summary of "Hackers & Painters"

Core Idea

Programming is making, not science: treat code like painting—learn by doing, iterate obsessively, focus on invisible details that matter to users.
Hacker disobedience drives innovation: protect individual freedom to think differently; totalitarianism kills breakthroughs.
Measure yourself by output, not effort: you're paid for measurable productivity, not hours worked. Startups let you capture that difference (10-100x variance).

School popularity ≠ life success: competing for status in artificial environments is wasted energy. Real world rewards different priorities.
Taboo ideas are diagnostic: track which thoughts get you in trouble—those are candidates for genuine insights competitors miss.
Ignore "Daddy Model" thinking: stop conflating effort with deserving payment. Reality pays for results.

Good design is simple, timeless, and looks easy: requires obsessive refinement invisible to others. Simplicity is harder than complexity.
Copy masters before innovating: study nature and skilled predecessors. Originality emerges naturally once competent.
Cluster physically near talent: excellence is nearly impossible in isolation. Proximity matters for breakthroughs.
Watch real users, not specs: their behavior reveals design flaws no specification catches. Iterate based on observation.

Use powerful languages as competitive moat: if tool X delivers 20:1 code efficiency over competitors' tools, they can't catch up even with larger teams.
Choose tech by measurable productivity, not ideology: let capability drive decisions; non-technical managers shouldn't pick your stack.
Interactive development beats batch cycles: real-time feedback (REPL, toplevel) improves morale and speed. Daily visible progress matters.
Enable unexpected uses: design systems to let users do things you didn't anticipate. Don't over-specify.

Remove bureaucracy, not people: small teams with high autonomy outpace large orgs exponentially.
Release constantly (daily, not annually): faster feedback, better quality, higher morale.
Server-based software wins: easier for users, no installation friction, rapid iteration.

Create measurable value, not excuses: wealth = things people want. Income inequality reflects productivity inequality—natural and healthy.
Choose hard problems: they create barriers to entry and prevent competitors from copying you.

Identify your unfair advantage: What tool, language, or approach do competitors dismiss? Use it to ship faster.
Measure by output: Define one metric that matters (code shipped, users served, features deployed). Optimize for it.
Move near talent or build async culture that works: proximity beats remote for breakthroughs.
Watch users constantly: deploy daily if possible. Let behavior (not your assumptions) guide refinement.
Protect time for deep thought: hacker disobedience requires mental freedom. Defend it from process/bureaucracy.