Glean 拾遗
Recent picks

2picks · chronological

11-09

Karpathy: ask LLMs for diagrams, HTML pages, and explainer videos

Karpathy argues that as models improve, more of our work shifts upward into oversight and understanding rather than production, so we should optimize the format of model output. He suggests a ladder of increasing readability: have the model rewrite explanations in ASD-STE100, the controlled-language spec built for aerospace maintenance docs (or ask for "80% of the way" there when the constraints bite); ask for diagrams; ask for HTML and get an interactive page with animation; and, his most bullish bet, custom 3b1b-style explainer videos with ElevenLabs narration or a free local substitute. Because intelligence and code are increasingly abundant, you can request large, discardable software artifacts that never made economic sense before.

x.com · 2 min · Ai Tooling · LLM · Prompt Engineering
09-14

Healthy Documentation: A CTO's Case for Docs-First Engineering

A CTO's field notes on running a docs-first engineering culture: replace half-hour check-ins with a one-page memo, budget documentation time explicitly in estimates, and require a short "why X over Y" paragraph on every merged feature. He is candid about the failure modes — stale pages are worse than none, and some workarounds should be fixed in code rather than explained in three paragraphs of handbook. Concrete mechanisms include a lightweight CI check that fails the build when a new analytics event ships without a matching wiki entry, ADR and post-mortem templates, the Diátaxis split between tutorials and reference, and a part-time "docs gardener" who prunes dead links.

vadimkravcenko.com · 11 min · Developer Tools · Documentation · Engineering Culture