// free resource
the build experience checklist
four proven paths to manufacture your own credentials — distilled from "how to build programming experience when no one will hire you" into a printable checklist you can work through week by week.
// get the pdf
enter your email to unlock the downloadable checklist.
// 1. open source contributions that matter
- pick projects you already use — check your package.json, cargo.toml, or go.mod. user context is your advantage.
- start with bug reproduction — find an issue with a vague description, clone the repo, write a minimal reproduction, and post it.
- trace requests through the system before writing code: cli parsing → config → core logic → output.
- submit small, well-scoped prs — missing test cases, better error messages, updated docs, clarity refactors.
- avoid rewriting core logic, adding unrequested features, or ignoring contribution guides.
// 2. build real saas clones (not tutorials)
- go beyond localstorage — real projects use postgresql, auth, and deployment.
- multi-environment deployment — staging and production, not just localhost.
- write unit + integration tests with ci/cd pipeline.
- add rate limiting and validation — real apis handle abuse prevention.
- set up monitoring — error tracking and analytics from day one.
- make architectural decisions — collision-resistant ids, graceful degradation, retry logic with backoff.
// 3. strategic freelance work
- filter by skill gap, not budget — need api design experience? build a rest api for a small business.
- never work for free — paid work (even small amounts) creates accountability.
- turn every project into a case study — document the problem, constraints, your approach, and the outcome.
- avoid red flags — clients who can't explain what they want, and exposure-only offers.
// 4. the "fake but real" project
- real users — even if it's just 10 people. feedback from real users is irreplaceable.
- real data — postgresql (not hardcoded json), with proper schema design and indexing.
- real failures — simulate database downtime, network errors, bad inputs. add retry logic.
- real maintenance — come back after 3 months and refactor.
- stress-test code — stop the database container. watch how your app behaves.
// 5. package & present your work
- pin 3-4 repos on github that show depth. each needs a comprehensive readme with architecture decisions.
- include architecture.md for complex projects. ensure ci passes and code is linted.
- write specific resume bullets — describe metrics, tech, and exact constraints solved.
- prepare 3-5 star stories — situation, task, action, result. be metric-specific.
- build in public — share projects, failures, and learnings. teach what you learn.
- ship regularly — done is always better than perfect.