Skip to main content

Human Docs Mirror

2 min read

Generated index of the human docs mirror. Each page is a mechanical transform of the canonical human doc.

Playbook mirror​

  • Request For Microproducts — A call to build useful microproducts instead of portfolio projects optimized only for hiring signals.

    Playbook​

A living collection of contributor-built modules for building microproducts that turn data into value, moving from shared foundations into the analytics development lifecycle: frame, build, and operate.

Plan​

The planning layer of the analytics development lifecycle, organizing content around defining opportunities, understanding users, scoping microproducts, and analyzing whether an idea is worth building.

  • Frame — Validate whether a microproduct is worth building and feasible to deliver before execution.
  • Data Licensing — Access is not permission. Before treating a dataset as a product input, document the rights you have to store, transform, combine, serve, and commercialize it.
  • Modern Data Stack — Modern data infrastructure is not a list of products. Reason from product constraints before choosing a warehouse, orchestrator, or lakehouse.
  • Quality-First — How a modern approach to QA and spec-driven development helps ship quickly and confidently.

Build​

The development layer of the analytics development lifecycle, organizing content around designing, developing, testing, and deploying microproducts through iterative implementation.

  • Build — Execute, validate quality, and deliver a reliable MVP through focused delivery workflows.
  • From Chat to Tickets — Chat is an interface; a ticket is a unit of work. Move agentic development from conversation history into bounded tickets that preserve intent.
  • Release Guide — A decision framework for releasing microproducts that informs prior phases of development.

Operate​

The operational layer of the analytics development lifecycle, organizing content around operating, observing, learning from, and improving shipped microproducts over time.

  • Operate — Own distribution, learning, and iteration after launch so the product keeps improving.
  • Microproduct Deployment — GitHub stores the code. Vercel runs the application. For many web-based microproducts, that is enough deployment architecture to get a product into users' hands.
  • Authors — The people and organizations listed in the shared author registry for the docs.