About / shouldenough
One guide per technology. Then it stops.
Most technical writing is padded to look thorough. shouldenough is the opposite bet: the shortest correct path from zero to shipping something real, run against a named version before it is published, and re-run when that version moves.
- Courses
- 2
- Lessons
- 16
- Reading
- 157 min
- Graded tasks
- 26
How everything here is written
- 01
Only what ships
A guide ends when you can do the thing, not when the API surface is covered. Anything that does not move you toward a running system is cut.
- 02
Named versions
Every command is run against a stated version before it is published. A guide that will not say which version it was written for is a guess.
- 03
Re-run on change
When the tool moves, the guide is re-run and re-dated. Articles that quietly rot are worse than no articles.
What it deliberately does not do
- No cookies
- Nothing is written to your browser except the theme you pick.
- No analytics
- No page-view script, no session recording, no third-party pixel.
- No accounts
- Nothing to sign up for, so there is nothing to leak.
- No answer key
- Quiz answers are graded on the server and never sent to the browser.
Details in the privacy policy.