Playbook

GitHub, step by step

Right now your profile has no bio and no profile README, and most public repos are from 2021–2022 or forks. A recruiter spends about 30 seconds there. Goal: in 30 seconds they see who you are, 6 strong projects, and steady recent work.

1. Profile basics

   Settings → Public profile:

   • Name, and the same photo as LinkedIn
   • Bio: one line (copy below)
   • Location, your LinkedIn link, and website = your live Pace link

   Software engineer at Technance · TypeScript, React, Next.js, React Native · Growing into [your path]

   Copy

2. Profile README

   Create a public repo named exactly like your username: mowhcen/mowhcen. Its README shows at the top of your profile. Keep it short and real — no badge walls, no stats cards.

   ### Hi, I'm Mohammad Mohsen
   
   I build trading products for web and mobile at Technance — TypeScript, React, Next.js and React Native, in a large Turborepo monorepo. 1,500+ merged pull requests since 2024.
   
   **Now:** a 6-month plan to grow into [your path], tracked in public with [Pace](https://pace.mowhcen.dev) — a roadmap that re-plans itself when I fall behind.
   
   **Projects**
   - [Pace](https://github.com/mowhcen/pace-planner) — roadmap planner with pace-based forecasts (React, TypeScript)
   - [next project] — [one line]
   
   **Writing:** I post what I learn on [LinkedIn](https://www.linkedin.com/in/mowhcen).

   Copy
   • GitHub docs: profile README ↗

3. Clean up old repos

   Keep public only what you're proud of. Archive or make private — don't delete your history.

   • Early practice (hangman, note-app, task-app, Recipe-App, Indecision, snake-and-ladder, database-hw, web-engineering): make private, or archive.
   • Forks with no work of yours (rsuite, react-dates, react-pageflip, country-flags, react-datepicker2, react-multi-date-picker): delete the fork. A fork you never changed adds nothing.
   • cookies-next: keep it only if you sent a merged PR, and link that PR in the README.
   • Fix names and descriptions: "web3expamle" → "web3-example". Keep one of the three Next.js starters.
   • Private projects that could shine (for example mizban-chi): make public only if it is your own code, has no secrets, and is not client work.

4. A real README for every pinned repo

   A screenshot or GIF matters most. Also set: description, website link, 3–5 topics, and an MIT license.

   # [Project name]
   
   [One sentence: what it does and who it is for.]
   
   ![Screenshot](docs/screenshot.png)
   
   **Live:** [link] · **Stack:** [tech]
   
   ## Why
   [The problem in 2–3 sentences.]
   
   ## Features
   - [feature]
   - [feature]
   
   ## How it works
   [The one interesting technical idea. A small diagram helps.]
   
   ## Run it
   pnpm install
   pnpm dev
   
   ## What I learned
   - [lesson]

   Copy

5. Pin 6 repos

   Profile → "Customize your pins". Newest and strongest first.

   • Now: pace-planner, your 2 best older projects, cookies-next if you contributed.
   • Later: swap in your learning-log, your path project (tiny-limiter, Ship Radar or Pace v2) and your capstone.

6. Honest green squares

   Your work at Technance happens in a private repo, so it doesn't show by default.

   • Settings → Public profile → turn on "Include private contributions on my profile". They show as anonymous squares.
   • Commit to your learning-log on learning days. Real notes only — fake commit scripts are easy to spot and hurt trust.

7. CI badge, releases, social preview

   • A GitHub Actions workflow that runs tests (Pace already has one).
   • Tag v1.0.0 with release notes when a project is usable.
   • Repo Settings → Social preview: upload a 1280 × 640 image so links look good on LinkedIn.

8. Open source, once a month

   Start small: fix docs, add a test, or take a "good first issue" in a tool you already use. One merged PR a month for 6 months is a strong signal.

   • Good first issues ↗