Stack choices, small projects, and shipping checklists for solo learners
Workflows for Shipping Small
Open this section when the repo is the mess: a README nobody can run, a secret in the wrong file, a Friday tag with no rollback. Pick the page that matches the file you have open.
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
.github/workflows/tag-small-release.yml is empty. You’re drafting the check logic directly in this comment block before you write the actual workflow code, so you don’t miss any edge cases that tripped you up in past releases. Small releases make up 80% of the tags you push each quarter, so streamlining this process will save you hours of … Read more
docs/current-sprint-issues.md is pre-populated with only four section headers on its first save. You don’t need a paid project management tool, shared dashboard, or elaborate tagging system to stop dropping tasks mid-sprint. This flat, plain-text file lives in your repo, works offline, and requires no login or sync setup beyond standard Git commits. It offloads the … Read more
repo/.env.example sits alongside your uncommitted .env file and .gitignore at the root of your Next.js project. This file acts as a single source of truth for every environment variable your application needs to run, without ever storing plaintext secrets that can leak to public or private version control repos. Unlike your actual .env file, which … Read more