Stack choices, small projects, and shipping checklists for solo learners
Build Next Stack lives at https://buildnextstack.com. The name is the desk: pick a stack without a popularity chart, finish a small project that teaches the tools, keep a shipping checklist, and run a Friday learning review. The domain is just the address. Each page is one choice or one file you finish — not a bootcamp syllabus and not a job guarantee.
These pages assume a solo learner with a laptop, a week that already has work, and a project small enough to demo. They are not career coaching, not hiring advice, and not a promise that a language or host will match a job board. If a page uses minutes, file sizes, or day counts, treat those figures as illustrative examples unless we point to a source you can open yourself.
Start in Stack Choices Without Hype when the tool list is the problem: a first-language fit card, a static-vs-database call, hosting that matches month-one traffic, or a local-first vs always-online grid.
Use Projects That Teach the Stack when you need a build with an edge: a habit CLI, a todo API with tests you actually run, a CSV dashboard, or a two-week notes app with a written done definition.
Open Workflows for Shipping Small when the repo is the mess: a recoverable Git habit, a README future-you can run, an env-file leak check, or a Friday ship card with a rollback tag.
Use Learning Loops and Reviews when study time leaks: a Friday stall sheet, an error journal row, a one-tutorial lock, or a two-hour lab block that ends with a commit.
If a step is confusing or a page is broken, write to the address on Contact. Legal notes live on Disclaimer, Privacy, Advertising Disclosure, and Terms.
spaced-practice-init rust-pattern-matching runs the three-session recall setup for your target syntax skill. This tool eliminates the passive, low-retention work of rereading syntax notes repeatedly by forcing active recall across spaced intervals, which is proven to build long-term, usable memory of programming syntax far faster than passive review. Run the initial recall workflow command When you … Read more
docs/debug/error-journal.md is a plain text markdown file you update every time you hit a blocking error during development. It cuts down hours of wasted time re-solving familiar errors, helps you spot gaps in your technical knowledge, and creates a shareable resource for your team if you choose to commit it to your repo. You only … Read more
docs/weekly/friday-4-12-blocker-note.md is pre-filled with three empty section placeholders for your end-of-week progress review. This 10-minute exercise cuts through the vague “I got a lot done this week” self-reporting that usually leaves you scrambling on Monday morning to remember what you were working on, why you were stuck, and where to start next. This framework is … Read more
docs/side-project-outage-runbook.md lives in your project’s root docs folder, formatted to fit fully on a single printed or screen page for fast access during outages. It is designed exclusively for your solo side project, a task tracker used by 120 registered users, to eliminate the need to dig through scattered notes or server documentation when you … Read more
scripts/copy-sqlite-backup.sh stores all the logic to copy your production SQLite file before running schema migrations. Unlike relational databases that run as separate server processes with built-in point-in-time recovery tools, SQLite stores every row of user data, app configuration, and session information in a single, portable file. That portability comes with a key risk: a failed … Read more
.github/workflows/tag-to-changelog.yml sits in your repo’s automation folder with placeholder configuration lines. This GitHub Action workflow automates syncing every Git tag you push to your default branch with a human-readable one-line entry in your root CHANGELOG.md file, eliminating the common mismatch between tagged production releases and what’s listed in your public changelog. These mismatches often cause … Read more
scripts/portfolio-demo-beats.md holds the structured 90-second demo runbook and live failure fallback for your full-stack inventory tracker portfolio project. Run the pre-demo validation command The command you’ll run to populate this file is `npx demo-prep inventory-tracker –timeout 90s –fallback-assets ./demo-screenshots`, which executes three key checks before generating your structured beat sheet. First, it sends 5 consecutive … Read more
app/utils/debug_log_formatter.ts is pre-populated with 12 lines of generic timestamp formatting code. For months, you’ve relied on this formatter to standardize logs across all your backend services, but you’ve noticed it’s getting harder to resolve old bug reports because the logs lack consistent, actionable context. The current template only includes a timestamp and plaintext message, so … Read more