Originally published on Homingo Learn. An isometric architecture diagram that lives in the repo, diffs in review and redraws itself when the system changes. The spec, the layout rules and a small generator in plain JavaScript. The spec names zones,…
We've all been there. You join a new team, open the repository, and find a beautifully written README.md, an architecture document, and a collection of Markdown files explaining how everything works. A few minutes later, you notice that the…
Most AI-assisted development still follows the old split. A human writes the spec, a human writes the code, and the AI helps with autocomplete or generates tests at the end. AI-DLC (the AI-Driven Development Life Cycle) reverses that. The AI…
In this quickstart, you describe a Python function to a model, let the model ask for it when a question needs it, run the function, and send the result back so the model can answer. It takes about 10 minutes. This…
SO-101 arm pick-and-place with LeRobot — sim training, real demo recording, ACT and SmolVLA, safe real-arm runners Start with setup, then dataset → training → simulation; use hardware and bring-up when moving to the arm.
Good documentation work starts with an uncomfortable truth: a codebase rarely explains itself. A package.json tells only part of the story. A directory name can be misleading. A framework convention may not actually be used. The most valuable details…
The exporter traces tensor operations and records input and output metadata. Run the exported policy in simulation with LeappDeploymentEnv, on a robot with Isaac ROS Deploy, or in a custom runtime that reads the exported YAML. A LEAPP-exported Isaac-Reach-UR10 policy…
A design doc is a decision record, not an essay. A one-page structure that gets to a decision quickly: context, goals and non-goals, options with trade-offs, the decision, risks and rollout — plus how to run the review. At staff level,…
Raw HTML is a poor thing to feed a model. A typical docs page is mostly navigation, scripts, styles and wrapper divs, and the actual text is a fraction of the bytes. Markdown keeps what matters (headings, lists, links, tables,…
A lot of company knowledge still lives in Word files: refund policies, onboarding guides, SOPs, proposal templates. If you want that content in a prompt, a RAG index or a chatbot's knowledge base, Markdown is a better format than the.
Decision records, onboarding docs, runbooks, and internal wikis.
An article joins this feed when it matches these terms. Each one is also a search of its own.