Writing and Code: Same Leverage, Different Story
The article compares writing and coding as two domains that both offer high leverage—enabling a single person to reach many—but differ in how that leverage is realized and perceived. Writing scales through time (a piece read years later), while code scales through automation (a program runs without the author present). The piece explores why writing's leverage is undervalued compared to coding's.
Background
- The blog post draws an analogy between writing and software engineering, arguing that while both offer leverage (i.e., the ability to produce disproportionate output from a single effort), writing's leverage is direct and independent, whereas code's leverage is indirect and requires extensive supporting infrastructure.
- The author, Vincent Ping, is a software engineer and writer who explores productivity, tooling, and the intersection of technical and creative work. This piece fits a common debate among programmers about which skills offer the most impact per unit of effort.
- "Leverage" in this context means how much one unit of work can scale: a single article or book can reach millions, but a piece of software may only be useful if it's part of a larger system or platform.
- The piece assumes familiarity with concepts like developer tooling (VS Code, GitHub), open-source work, and the idea of "shipping" code, which may be opaque to non-technical readers interested in writing or productivity.