About
What Would A Dev Do?
WWADD is the answer an experienced developer gives when you ask them how they'd actually do it.
The name
WWADD — What Would A Dev Do? Three parts: tools (what each one is for), moves (the snippet you need right now), and stacks (the decision you need to make before you write any of it).
Free reference
No account, no paywall, no newsletter gate. Pages are rendered on the server, so they work without JavaScript and deep links keep working. Search runs entirely in your browser.
Content philosophy
- Short bodies, real snippets. A move should fit on one screen and be copy-pasteable without edits.
- Every stack gets a “skip if”. A recommendation without a tradeoff is marketing, not advice.
- Examples link to their sources. Every real-world example points to a public repo, case study, or engineering post, and says only what that source shows — never invented internal detail.
- Licenses stated precisely. Source-available is not open source, and freemium limits are spelled out. Tool facts carry the date they were last verified.
- Opinion, clearly labelled. Circumstance and synergy sections are judgment calls, and they say so.
Not here (yet)
No accounts, bookmarks, AI chat, or CMS. Those add surface area before the content is worth returning to.