Read writers who operate

Shreyas Prakash headshot

Shreyas Prakash

We have more books on birds written by ornithologists than books on birds written by birds, and books on ornithologists written by birds. Taleb eloquently describes this as the key problem of knowledge, or in other words as epistemic arrogance. Strong corollary can be drawn with various disciplines, including entrepreneurship.

Entrepreneurs simply spend more time doing entrepreneurship rather than writing about entrepreneurship. It’s very difficult for successful entrepreneurs who are in the thick of action, to be talking about action.

Take the example of the Elon Musk biography by Walter Isaacson written on 2023. It’s been just a year, and it seems to be already outdated. In this short span, Musk has gone ahead to influence Trump’s 2024 election, grow xAI as an alternative to ChatGPT, and even make great progress on Neuralink/Boring Company and shitpost (and buy Twitter) at the same time. (Walter Isaacson should rather do something similar to Robert Caro’s four-volume series on Lyndon Johnson). Raw material is necessary for all professions of any importance; all the more merrier when they write about in a first-hand account.

I’m interesting in this rare breed of folks who thrive in this intersection: of being operator-writers. Will Larson describes this phenomenon in his essay (also originally coining this term of writer-operators). For whom, ‘writing about their experiences’ is a part-time hobby. And when their own experience is a resource:

‘A writer—and, I believe, generally all persons—must think that whatever happens to him or her is a resource. All things have been given to us for a purpose, and an artist must feel this more intensely. All that happens to us, including our humiliations, our misfortunes, our embarrassments, all is given to us as raw material, as clay, so that we may shape our art.’ — Luis Borges

I’m imagining there’s more to this relationship between writing and doing. My hypothesis here is that (doing) makes your thinking clearer, so you write better. Without the fluff. Speaking about fluff, the Arabs have an expression for trenchant prose: no skill to understand it, mastery to write it. The more I listen to Naval Ravikant or Steve Jobs, seeks to confirm this hypothesis; that “you have to work hard to get your thinking clean and simple”. Simplicity is the ultimate sophistication, and writers who operate have a unique knack to shine at this, when they talk about their domain.

The content of the book-writers without adequate episteme also seem to be a dull dud in contrast. You will also notice the writers shift from genuine passion in a given niche, to a more ephemeral engagement in topical events and the latest new controversy in limelight. Larson contrasts “writers who operate” with full-time writers, noting that the former are less influenced by the expectations of writing audiences or other writers’ communities.

So here are some lists:

Venture operators (as mentioned originally in Patrick Collinson’s list)

Writer-operators are generally a broad church, and many more writers out there who fit this archetype. Someone who hasn’t written anything for the past few years would also NOT make it into this list.

Apart from venture operators and entrepreneurs, we also do have some genius individual contributors who are having fun writing about all that they’ve shipped (originally from Guzev’s list):

  1. Adam Green (twitter)
  2. Adam Strandberg (twitter)
  3. Ali Cy (twitter)
  4. Alvaro De Menard (twitter)
  5. Andy Kong (twitter)
  6. Anson Yu (twitter)
  7. Applied Divinity Studies
  8. Avital Balwit (twitter)
  9. Basil Halperin (twitter)
  10. Benjamin Spector (twitter)
  11. Bruno H.S. Aguiar (twitter)
  12. Ching Lam Choi (twitter)
  13. Chris Beiser (twitter)
  14. Clare Birch (twitter)
  15. Croissanthology (twitter)
  16. Daniel Kirmani (twitter)
  17. Diana Leung (twitter)
  18. Gavin Leech (twitter)
  19. Gytis Daujotas (twitter)
  20. Isaak Freeman (twitter)
  21. Justin Wang (twitter)
  22. Ker Lee Yap (twitter)
  23. Kevin Liu (twitter)
  24. Kyle Schiller (twitter)
  25. Lada Nuzhna (twitter)
  26. Leopold Aschenbrenner (twitter)
  27. Lev Chizhov (twitter)
  28. Lucas Chu (twitter)
  29. Luke Farritor (twitter)
  30. Lydia Nottingham
  31. Madhu Sriram (twitter)
  32. Marley Xiong (twitter)
  33. Matt Lakeman
  34. Max Langenkamp (twitter)
  35. Max Shirokawa (twitter)
  36. Mehran Jalali (twitter)
  37. Michael Truell (twitter)
  38. Misha Yagudin (twitter)
  39. Olivia Li (twitter)
  40. Paul Han (twitter)
  41. Richard Fuisz (twitter)
  42. Sebastian Cocioba (twitter)
  43. Suspended Reason (twitter)
  44. Sundari Sheldon (twitter)
  45. Tejal Patwardhan (twitter)
  46. Theia Vogel (twitter)
  47. Will DePue (twitter)
  48. Yoyo (twitter)
  49. Yudhister (twitter)
  50. Zhengdong Wang (twitter)

I’m consciously intending to read more of writers who operate. We are what our feed is.

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

2026

  1. How I started building softwares with AI agents being non technical

2025

  1. Legible and illegible tasks in organisations
  2. L2 Fat marker sketches
  3. Writing as moats for humans
  4. Beauty of second degree probes
  5. Read raw transcripts
  6. Boundary objects as the new prototypes
  7. One way door decisions
  8. Finished softwares should exist
  9. Essay Quality Ranker
  10. Export LLM conversations as snippets
  11. Flipping questions on its head
  12. Vibe writing maxims
  13. How I blog with Obsidian, Cloudflare, AstroJS, Github
  14. How I build greenfield apps with AI-assisted coding
  15. We have been scammed by the Gaussian distribution club
  16. Classify incentive problems into stag hunts, and prisoners dilemmas
  17. I was wrong about optimal stopping
  18. Thinking like a ship
  19. Hyperpersonalised N=1 learning
  20. New mediums for humans to complement superintelligence
  21. Maxims for AI assisted coding
  22. Personal Website Starter Kit
  23. Virtual bookshelves
  24. It's computational everything
  25. Public gardens, secret routes
  26. Git way of learning to code
  27. Kaomoji generator
  28. Style Transfer in AI writing
  29. Copy, Paste and Cite
  30. Understanding codebases without using code
  31. Vibe coding with Cursor
  32. Virtuoso Guide for Personal Memory Systems
  33. Writing in Future Past
  34. Publish Originally, Syndicate Elsewhere
  35. Poetic License of Design
  36. Idea in the shower, testing before breakfast
  37. Technology and regulation have a dance of ice and fire
  38. How I ship "stuff"
  39. Weekly TODO List on CLI
  40. Writing is thinking
  41. Song of Shapes, Words and Paths
  42. How do we absorb ideas better?

2024

  1. Read writers who operate
  2. Brew your ideas lazily
  3. Vibes
  4. Trees, Branches, Twigs and Leaves — Mental Models for Writing
  5. Compound Interest of Private Notes
  6. Conceptual Compression for LLMs
  7. Meta-analysis for contradictory research findings
  8. Beauty of Zettels
  9. Proof of work
  10. Gauging previous work of new joinees to the team
  11. Task management for product managers
  12. Stitching React and Rails together
  13. Exploring "smart connections" for note taking
  14. Deploying Home Cooked Apps with Rails
  15. Self Marketing
  16. Repetitive Copyprompting
  17. Questions to ask every decade
  18. Balancing work, time and focus
  19. Hyperlinks are like cashew nuts
  20. Brand treatments, Design Systems, Vibes
  21. How to spot human writing on the internet?
  22. Can a thought be an algorithm?
  23. Opportunity Harvesting
  24. How does AI affect UI?
  25. Everything is a prioritisation problem
  26. Now
  27. How I do product roasts
  28. The Modern Startup Stack
  29. In-person vision transmission
  30. How might we help children invent for social good?
  31. The meeting before the meeting
  32. Design that's so bad it's actually good
  33. Breaking the fourth wall of an interview
  34. Obsessing over personal websites
  35. Convert v0.dev React to Rails ViewComponents
  36. English is the hot new programming language
  37. Better way to think about conflicts
  38. The role of taste in building products
  39. World's most ancient public health problem
  40. Dear enterprises, we're tired of your subscriptions
  41. Products need not be user centered
  42. Pluginisation of Modern Software
  43. Let's make every work 'strategic'
  44. Making Nielsen's heuristics more digestible
  45. Startups are a fertile ground for risk taking
  46. Insights are not just a salad of facts
  47. Minimum Lovable Product

2023

  1. Methods are lifejackets not straight jackets
  2. How to arrive at on-brand colours?
  3. Minto principle for writing memos
  4. Importance of Why
  5. Quality Ideas Trump Execution
  6. How to hire a personal doctor
  7. Why I prefer indie softwares
  8. Use code only if no code fails
  9. Personal Observation Techniques
  10. Design is a confusing word
  11. A Primer to Service Design Blueprints
  12. Rapid Journey Prototyping
  13. Directory Structure Visualizer
  14. AI git commits
  15. Do's and Don'ts of User Research
  16. Design Manifesto
  17. Complex project management for product

2022

  1. How might we enable patients and caregivers to overcome preventable health conditions?
  2. Pedagogy of the Uncharted — What for, and Where to?

2020

  1. Future of Ageing with Mehdi Yacoubi
  2. Future of Equity with Ludovick Peters
  3. Future of Tacit knowledge with Celeste Volpi
  4. Future of Mental Health with Kavya Rao
  5. Future of Rural Innovation with Thabiso Blak Mashaba
  6. Future of unschooling with Che Vanni
  7. Future of work with Laetitia Vitaud
  8. How might we prevent acquired infections in hospitals?

2019

  1. The soul searching years
  2. Design education amidst social tribulations
  3. How might we assist deafblind runners to navigate?