To find a coding partner, post a specific ask — the project, the stack, your timezone and the hours you can commit — where developers with that stack already gather, then run a single short trial session before you commit to anything. Vague asks ("anyone want to build something?") get vague replies; specific asks get partners.
1. Write the ask before you post it
The best asks fit in four lines:
- What: "A CLI that lints .env files against .env.example."
- Stack: "TypeScript, Node, no framework."
- When: "Two evenings a week, 7–9pm Karachi (UTC+5)."
- Level: "I'm mid-level; happy to pair with anyone who has shipped a CLI before or wants to learn."
That takes five minutes and filters out ninety percent of mismatches before they happen.
2. Post it where the right people are
Post in a stack-specific community rather than a general feed. On DEVAE that is the community hub for your stack (for example /community/typescript) and the find-teammates page, which lists open requests. Elsewhere, a relevant subreddit, a Discord server for the language, or a local meetup group all work. Tag the post with the stack so it reaches people searching for it.
3. Screen for overlap, not enthusiasm
The two things that predict whether a pairing survives are timezone overlap and similar availability. Skill mismatch is fine if both people know it; a six-hour timezone gap is not. Ask each reply two questions: "Which hours are you free?" and "What have you built recently?" Skip anyone who cannot answer the first one.
4. Do one trial session
Open a live room, share your screen and terminal, and work on a real task for 45 minutes: set up the repo, write the first test, sketch the CLI flags. You will learn more from one session than from a week of messages. If it felt slow or awkward, say so kindly and move on; nobody owes anyone a partnership.
5. Agree the first milestone
If the trial went well, agree three things: how often you meet, who owns what this week, and what "done" means for milestone one ("the CLI runs and reports missing keys"). Write it in the repo README. Partnerships die from ambiguity more than from disagreement.
Where to look
- DEVAE: post on your stack hub, then check the find-teammates page for open requests.
- Hackathon threads: people looking for a team are looking for a partner.
- Open-source issues: comment on a "help wanted" issue and offer to pair with whoever else replies.
- Study groups and bootcamp cohorts: you already share a schedule.
Keeping it going
Pairings usually fade at week three when novelty wears off. Put the sessions in a calendar, keep a shared TODO in the repo, and post progress publicly — a small audience is a surprisingly good reason to show up.
A worked example
A self-taught developer in Toronto wants to build a Chrome extension but keeps stalling. He posts: "Building a tab-grouping extension in TypeScript. Two evenings a week, 8–10pm Eastern. I've shipped one small extension before; looking for someone at a similar level." Three people reply. One is in Sydney (no overlap), one wants to use Svelte for everything (mismatch), one is in Montreal and has the same evenings free. They run a 45-minute room, set up the manifest and the first content script together, and agree to meet Tuesdays and Thursdays with a milestone of "groups persist across restarts" by the end of week two. The extension ships in six weeks.
Questions people ask
**What if I am a complete beginner?** Say so in the ask and look for another beginner or a patient mentor-type. Two beginners pairing learn faster than one alone because each explains their reasoning out loud.
**How do I handle a partner who stops showing up?** Ask once, kindly, if the schedule still works. If it does not, thank them and post the ask again. It is normal; most pairings are temporary.
**Should we use a shared repo from day one?** Yes. A repo with a README and a TODO list is the cheapest coordination tool that exists.
