**Parent Topic**: [[Software/README]] ## The Framework Becoming a master web operations engineer is, Schlossnagle argues, no different from mastering carpentry or teaching. It requires four pursuits: - **Knowledge** — the Internet is a high-yield retention system, but don't limit yourself to it; books, user groups, and freely available specs (the RFCs) build a deep foundation. Peers need you as much as you need them. - **Tools** — know them as extensions of your limbs; the craftsman, not the tool, makes the work. See [[The Craftsman Not the Tool]]. - **Experience** — good judgment, gained by making bad ones. Knowledge is studying others' experiences; experience is grasping causality directly. - **Discipline** — controlled behavior from training and practice; the single most commonly missing ingredient in ops teams. ## The Apprentice Model Because no formal education exists, the trade runs on an informal master–apprentice model, virtualized by the Internet but wildly variable in quality. Mastery is the slow conversion of all four pursuits into reliable judgment — the basis of [[Seniority Is Consistent Judgment]]. --- *Source: [[Web Operations]] (Allspaw & Robbins, O'Reilly 2010) — Ch 1 — Web Operations: The Career*