The Pragmatic Investment Plan

Definition

Hunt (extending an idea from his earlier book, The Pragmatic Programmer) argues you should treat your accumulated skills and knowledge as a "knowledge portfolio" that must be actively managed exactly like a financial investment portfolio: have a concrete plan, diversify deliberately across risk/return profiles, invest actively rather than passively (review and revise), and invest on a regular schedule rather than only in leftover "free time."

In the Book

Hunt lays out the plan's four components directly. Have a concrete plan means setting SMART objectives at multiple horizons — the next action, goals for next year, goals five years out — because "the planning is far more important than the plan" (a line he attributes to Eisenhower); the plan will change, but the discipline of setting it won't. Diversify means consciously spreading learning across languages, techniques, industries, and nontechnical areas, and explicitly weighing risk versus return — betting early on a low-adoption, high-upside technology (his example: Java when it was still called Oak) is a genuine high-risk, high-reward move, unlike learning the technology everyone already knows. Active, not passive investment means periodically stepping back to ask whether the plan is still working, in the same way an investor rebalances a portfolio rather than "sitting around on your assets." Invest regularly enables what Hunt calls the knowledge-portfolio version of dollar-cost averaging — steady investment smooths out the inevitable stretches where a given skill bet looks bad.

A load-bearing point Hunt makes explicit: unlike money, "all knowledge investments have some value" — even a technology you never use commercially changes how you think and solve problems — so the portfolio logic isn't really about hedging against total loss, it's about deliberate allocation of a genuinely scarce resource (attention and time) that otherwise defaults to whatever falls into idle moments.

Why It Matters

This gives anyone managing their own development — not just programmers — a structural alternative to "learn whatever comes up" or "learn whatever is safest right now." Framing skills explicitly as a portfolio surfaces two failure modes that are easy to miss individually: over-concentration (all your skill-eggs in one basket, vulnerable when that domain declines) and under-investment (treating learning as something that only happens in leftover time, which in practice means it never happens, since — as Hunt puts it — time can't be created, only allocated).