Personal Mode
Bikesh ChaudharyThe person behind the code.
DeveloperLearnerBuilderExplorer
Technology is my craft. Photography and exploration are my way of seeing the world.
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.
My Nepal Journey
The map of my life.
Every place leaves a story. Here is where Nepal has found me.
The map is waiting for its first adventure.
Add your first journey from the travel admin.
Click a marker to open a place’s story.
Where I’ve Been
Nepal0 places
Pick one to open it on the map.
No places visited yet.
Where I’m Going
Next Destinations
The list that keeps getting longer.
No next destinations yet.
My Trips
The journeys behind the pins.
Every trip gathers a handful of places into one story — what happened, what stayed with me, and what I’d tell anyone going next.
No trips published yet.
Add one from the travel admin and it will appear here with its story.
Journal
Thoughts & reflections.
Lessons from building, failing, traveling, and growing. Everything that didn't fit into a commit message.
Learning to Learn in Public
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.
What a Production Outage Taught Me
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.
Finding Flow Between Code and Life
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.
My First Open Source Contribution
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
Visual stories.
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
Mountain Sunset
The golden hour light hitting the peaks — a moment that reminded me why I love the outdoors.
Collections
Writing
Words & ideas.
Thoughts on technology, life, and the space where they meet. Sometimes technical, sometimes personal, always honest.
Personal Universe
THINGS I LOVE
Beyond the code.
Beyond the work.
This is what makes me, me.
The End
THERE'S MORE TO ME THAN CODE.
These are the things I watch, listen to, explore, and enjoy.
Web Stats
WEB STATS
The network behind the developer.
Every number here is a thread — code, kilometres, films, caffeine. Pull one and the rest move with it.
Bikesh
8 strands connected
ME · Bikesh
8 strands, one web.
Hover a node — or tap one — to pull its thread. Every number is something I actually did.
“With great power comes great responsibility.”
Full readout
THE REST OF THE WEB
Everything the centre keeps count of.
34
Repositories
Public and private repos I actively maintain.
1,200+
GitHub Contributions
Commits, reviews and issues across the last few years.
6,000+
Development Hours
Deep-work hours spent building and debugging.
85
Artists on Repeat
Songs and artists that keep the late-night builds moving.
25
Trips & Rides
Weekend rides and road trips out of the valley.
Proficiency
SKILL WEB
Each ring is spun the moment it enters view.
JavaScript
The language everything else is built on.
TypeScript
Types first — the compiler is a teammate.
React / Next.js
App Router, server components, streaming.
Java
Backend services and the fundamentals underneath.
Node.js
APIs, workers and everything in between.
PostgreSQL
Schema design, indexes and query plans.
Connections
MY WEB
Everything I'm connected to.
“With great power comes great responsibility.”
Now
What I'm up to right now.
Inspired by Derek Sivers' /now page movement. A snapshot of my current focus areas.
Building
Portfolio Platform v2
Dual-mode portfolio with PostgreSQL, Drizzle, and cinematic UI
Multi-Tenant SaaS Platform
Enterprise SaaS with event-driven microservices
Learning
Rust
Systems programming for performance-critical services
Kubernetes
Container orchestration at scale
System Design
Distributed systems, consensus algorithms, and scalability patterns
Reading
Designing Data-Intensive Applications
By Martin Kleppmann
Building Microservices
By Sam Newman
Exploring
Event-Driven Architecture
Patterns for resilient microservice communication
Street Photography
Capturing everyday moments in Kathmandu
Interested In
Timeline
The complete journey.
Professional milestones and personal memories — it's all one story.