Shashwot Ghimire · Kathmandu, Nepal

Blog

Why I keep shipping side projects

Eight projects, six in production, every one open source. A note on why side projects matter for a software engineer's learning.

Every project on this site started as an itch. Not a roadmap item and not a resume bullet — something I wanted to exist, or something I wanted to understand by building it.

The fastest way to learn is to ship

Textbook knowledge fades fast. Deploy a production app and the real lessons show up immediately: connection pools, cold starts, rate limits, the gap between how a library is documented and how it actually behaves.

My AI projects taught me more about LLM pipelines than any tutorial. Wiring a multi-agent script generator, a fact-checking step, and a TTS voiceover into a single pipeline meant learning where each piece genuinely fails — not where the demo says it works.

Open source keeps it honest

Publishing every project publicly changes the standard. Code you know others can read tends to be code you bother to structure well. It also means anyone can fork, learn from, or improve what I've built — which is the whole point of shipping in the first place.

If you're early in your career: build something small, deploy it, and put it out in the open. The compounding effect is bigger than any single project.

← All notes