Diagrams, for people who ship.
Practical writing for software and DevOps teams: turning code and infrastructure into diagrams, working together, and why a hand-drawn look does more than you think.
From docker-compose.yml to a clean architecture diagram in seconds
Stop redrawing your stack by hand. Paste a Compose or Kubernetes file and LetDraw lays out the architecture, clusters your services and stamps the right product icons, ready to edit and export.
Your query is slow. Here's how to see why.
Turn a Postgres or MySQL EXPLAIN plan into a heat-mapped tree and spot the expensive node at a glance.
Diagrams as code, without losing the whiteboard
Bring Mermaid and D2 in as editable shapes, tweak by hand, then export back to code when you need it.
Let your AI agent draw the diagram: the API and MCP server
Generate and export diagrams from a CI script or an AI assistant with scoped API tokens and an MCP server.
Why the best engineering docs are a little bit hand-drawn
The case for sketchy diagrams: friendlier, faster to make, and far more likely to actually get read.
Model a database schema your whole team can actually read
ER tables, crow's-foot cardinality and smart foreign-key routing that keeps lines readable.
Real-time whiteboarding for engineers, no install required
Live cursors, workspace roles and point-anchored comments, right in the browser.
Local-first, encrypted, self-hostable: diagrams that stay yours
How LetDraw keeps your work private: end-to-end encryption, strict headers, and self-hosting.
Try the thing these posts are about.
Open a canvas in your browser, paste some code, and see your architecture draw itself.
Open LetDraw, free