Learn-by-building tracks: build an MCP server, build a RAG pipeline
Skip tutorial hell. The 4 build-tracks (MCP server, RAG pipeline, payments integration, realtime app) that teach more than any course and double as portfolio.
Learn-by-building tracks: build an MCP server, build a RAG pipeline
Status: Outline — full guide coming soon. Get notified when it ships →
What this covers
- 4 build-tracks (MCP server, RAG pipeline with evals, Razorpay+webhook integration, realtime collab toy) that double as resume artifacts
- Why building 1 hard thing teaches more than finishing 5 tutorials
- The "ship-then-blog" pattern that gets the same project linked from your DMs and PR descriptions
- How to scope a build so you actually finish it in 2 weekends
Why this matters for Indian devs going remote
Indian devs lose interviews not on knowledge but on "have you actually built X?" A shipped, deployed, blogged-about project is the single highest-leverage artifact when your previous employer brand doesn't open doors. Build tracks fuse learning with portfolio in one effort.
Outline
Track 1: MCP server
TODO — what to build, what it teaches (Anthropic spec, stdio/SSE transport, tool schemas), 2-weekend scope.
Track 2: RAG pipeline with evals
TODO — embeddings, chunking, retrieval eval harness, latency budget; what to blog.
Track 3: Razorpay + webhook integration
TODO — idempotency, signature verification, retry handling — the production-discipline signal.
Track 4: realtime collab toy
TODO — CRDTs or OT-lite, websockets, presence; the network/state-sync interview transfer.
The ship-then-blog cadence
TODO — code commit → README → deploy → blog post → tweet → PR description link, all from the same artifact.
Common mistakes to avoid
- Picking a track that requires 6 weekends — you'll abandon it
- Skipping the blog post — half the leverage is the writeup
- Building 4 trackes in parallel instead of finishing one
Templates / examples
TODO — per-track scope sheet (in / out), a 2-weekend timeline, a README template that converts, and a sample blog-post outline.
Related guides
- Building an MCP server as a portfolio weapon
- Portfolio projects: building one strong proof-point repo
Have a question about this? DM me on LinkedIn or drop your email to get the full guide as soon as it's published.
Get the full playbook
I'm writing one in-depth guide a week. Drop your email to get them as they ship — plus templates and curated job leads.