Embracing Imperfect Code
The best code isn't perfect — it's code that ships, adapts, and solves real problems for real people.
Bikesh Chaudhary
I build systems for a living. I travel, photograph, and write to remember what systems are for — serving people, connecting lives, and making space for wonder.
Wanderings
Every journey leaves something behind — a lesson, a photograph, a memory that changes how you see the world.
Journal
Lessons from building, failing, traveling, and growing. Everything that didn't fit into a commit message.
For years I believed that mastery meant knowing everything before you start. That you should read the documentation cover-to-cover before writing a single line of code. That 'I don't know' was a confession of weakness. I was wrong. The most significant leap in my career came when I started learning in public — sharing what I was building before it was polished, asking questions before I had fully formed answers, and treating ignorance not as a flaw but as a starting point. Every project I've shipped started with a moment of uncertainty. The GoSpot recommendation system began with a whiteboard full of wrong ideas. The AI fake news detector started as a notebook where I was just trying to understand tokenization. The key insight: learning isn't the prerequisite to building. Building is the vehicle for learning.
At 2:47 AM on a Tuesday, the pager went off. Our primary database was replicating with a 45-minute lag. Transactions were queuing. Users were seeing stale data. My heart rate hit 130 before my brain caught up. We'd shipped a migration earlier that day — adding an index to a table that had grown to 200 million rows. The migration itself ran fine, but it triggered a cascade: the index build caused a write lock storm, which triggered replication backpressure, which cascaded into the lag. Three hours later, the system was stable. But I learned more in those three hours than in months of smooth operations. 1. Monitoring isn't a feature — it's the entire foundation 2. Every migration is a risk; test it against production traffic patterns, not just staging data 3. The people you're on-call with matter more than the tools you have 4. Post-mortems should be blameless learning exercises, not witch hunts That outage shaped every architectural decision I've made since.
I used to believe that being a good developer meant coding 12 hours a day. That side projects should fill every weekend. That rest was laziness in disguise. It took a burned-out November (2023) to realize I had it backwards. The best code I've written came after long walks, after photography sessions in the golden hour, after conversations with people who never write a line of code. Creativity doesn't come from grinding — it comes from living. Now I protect my non-coding time like it's production-critical. I take Sundays off completely. I read fiction. I travel without a laptop. I've found that the best architectural insights often arrive when I'm hiking, not when I'm debugging. Flow isn't about how many hours you sit at the keyboard. It's about how fully you engage when you're there.
I remember staring at the 'New Issue' button for ten minutes before clicking it. The repository was a popular UI library. The bug seemed trivial — a missing aria-label on a button component. But my hands were shaking as I typed the description. I'd read all the contributing guides, forked the repo, set up the dev environment, wrote the fix, added tests — and then sat on the PR for two weeks before posting it. What if my code wasn't good enough? What if the maintainers rejected it? They merged it within 24 hours. One sentence of feedback: 'Thanks for the thorough test coverage.' That single merged PR changed everything. It taught me that open source isn't a stage for perfect code — it's a conversation. A community. A shared effort to make things better. Now I contribute regularly, not because my code is exceptional, but because I understand that every contribution, no matter how small, moves the ecosystem forward.
Photography
A collection of moments, places, and stories captured through my lens.
@mbks.jpg
Bikesh Chaudhary
Photography Creator | Travel Enthusiast | Visual Storyteller Capturing moments through a lens. Nepal based.
Featured

Himalayas, Nepal
The golden hour light hitting the peaks — a moment that reminded me why I love the outdoors.
Collections
Writing
Thoughts on technology, life, and the space where they meet. Sometimes technical, sometimes personal, always honest.
The best code isn't perfect — it's code that ships, adapts, and solves real problems for real people.
From system design to philosophy — the books that changed how I approach both code and life.
At its core, software development isn't about technology — it's about the profoundly human act of creating something from nothing.
Now
Inspired by Derek Sivers' /now page movement. A snapshot of my current focus areas.
Portfolio Platform v2
Dual-mode portfolio with PostgreSQL, Drizzle, and cinematic UI
Multi-Tenant SaaS Platform
Enterprise SaaS with event-driven microservices
Rust
Systems programming for performance-critical services
Kubernetes
Container orchestration at scale
System Design
Distributed systems, consensus algorithms, and scalability patterns
Designing Data-Intensive Applications
By Martin Kleppmann
Building Microservices
By Sam Newman
Event-Driven Architecture
Patterns for resilient microservice communication
Street Photography
Capturing everyday moments in Kathmandu
Timeline
Professional milestones and personal memories — it's all one story.
Started Higher Education
Studied science and mathematics. Built the analytical foundation for engineering.
educationFirst Line of Code
Wrote a Python calculator. That 'Hello, World!' moment sparked everything.
personalFirst Freelance Project
Built a landing page for a local business. First dollar earned from code.
professionalFull-Stack Developer — Freelance
Started full-stack projects with MERN stack. Transitioned from Python to JavaScript.
professionalMERN Stack Certification
Completed MongoDB University certification and deepened full-stack expertise.
educationFirst Open Source Contribution
Fixed accessibility issues in a React component library. Learned the etiquette of OSS.
professionalLaunched First SaaS Product
Inventory management for small businesses. First product from concept to production.
professionalTypeScript & Next.js Deep Dive
Migrated from JavaScript to TypeScript. Discovered Next.js App Router.
professionalBuilt Real-Time Collaboration Tool
WebSockets, CRDTs, and operational transforms. Understood distributed state.
professionalDevOps Deep Dive
Docker, CI/CD with GitHub Actions, deployment strategies on AWS and Vercel.
professionalSystem Design Study
Distributed systems, microservices, event-driven architecture, and consensus algorithms.
professionalPublished Technical Blog
Started writing about full-stack development, sharing lessons from production builds.
professionalBuilt Payment Processing System
Stripe integration, webhook idempotency, and transaction reconciliation handling 10k+ transactions.
professionalStarted Mentoring
Code reviews, pair programming sessions, and guiding junior developers.
professionalPerformance Optimization Specialist
Achieved 95+ Lighthouse scores and mastered Core Web Vitals optimization.
professionalEnterprise Architecture Project
Designed a multi-tenant SaaS handling 100k+ concurrent users with event-driven microservices.
professionalPortfolio v2 Launch
Built this dual-mode portfolio with PostgreSQL, Drizzle, and cinematic UI.
professional