My Dreams — The Mountains I Will Climb

A dream written down becomes a goal. A goal broken into steps becomes a plan. A plan backed by daily action becomes reality. This page is my promise to myself — written in ink, lived in code.

I. To Master the Art of DevOps

Right now I can deploy. But I want to deploy with the confidence of an engineer who has seen systems fail at 3 AM and built them back stronger. My dream is to reach a place where infrastructure is not something I fear — it is something I design.

I am building toward deep fluency in Docker and Kubernetes — the ability to orchestrate containers at scale, manage rolling deployments, and write infrastructure that heals itself. I want to architect CI/CD pipelines so clean that pushing to main feels like signing a painting. GitLab, GitHub Actions, ArgoCD — I intend to know them the way a musician knows their instrument.

The dream is not just to use the cloud — it is to understand it. AWS certifications are on the horizon. Cloud architecture, serverless functions, managed Kubernetes on EKS — I want to build systems that scale from ten users to ten million without a single sleepless night.

Beyond the tools, DevOps is a philosophy: the elimination of the wall between building and running. I want to live that philosophy completely — owning every stage from a developer's first commit to a user's first click.

II. To Build Intelligence Into Everything

Artificial Intelligence is not the future I am waiting for — it is the present I am stepping into. My dream is to become an engineer who does not just consume AI tools but builds them, fine-tunes them, and deploys them into products that genuinely improve lives.

My Paddy Leaf Disease Detection System was a first step — a proof to myself that machine learning is not magic, it is craft. Now I want to go deeper. I want to train models on real-world messy data, understand the mathematics behind transformers, and build pipelines that take a raw idea all the way to a production-grade intelligent feature.

The specific territories I am determined to conquer: Computer Vision for real-world image problems. Natural Language Processing — building systems that understand context, not just keywords. MLOps — deploying and monitoring machine learning models with the same rigour I bring to backend engineering.

One day I want to build an AI product that is genuinely useful to people in Nepal — something that solves a local problem with local data, in the local language. That dream keeps me studying long after midnight.

III. To Ship a Flutter App That Millions Use

I chose Flutter because I believe in the premise: write once, run beautifully everywhere. But I want to push that belief to its limit. My dream is to ship a Flutter application that sits on millions of devices — something that people open every day without thinking about the engineering underneath, because the engineering is invisible and the experience is everything.

To get there I am going deep into the Flutter internals I currently only know at the surface. Custom render objects, shader-based animations, platform channels that reach all the way into native iOS and Android code. I want to understand the widget tree so deeply that performance is never an accident — it is always a deliberate choice.

The app I want to build most is an education platform for Nepali students — offline-first, fast on low-end devices, available in Nepali and English. A Flutter app that does not apologise for its origins but is genuinely competitive with anything built anywhere in the world.

IV. To Become a Full-Stack Architect

I do not want to be a specialist who cannot see the full picture. My dream is to be the kind of engineer who can walk into a room, understand a problem completely, and make confident decisions at every layer of the stack — from the database schema to the API contract to the mobile UI to the deployment pipeline.

That means going deeper on system design: understanding when to use a relational database and when a document store is the right tool. Knowing when a monolith is an asset and when microservices are the answer. Learning to write APIs that are not just functional but are a genuine pleasure to integrate with.

It means reading source code — not just documentation. It means contributing meaningfully to open source, not just filing issues but shipping patches to projects I respect and depend on.

V. To Build in Public and Give Back

The developers I admire most are not the ones who work in secret and emerge with finished products. They are the ones who share the journey — the failures, the pivots, the breakthroughs, the lessons learned the hard way.

My dream is to build in public. To write about what I am learning — not just the polished tutorial version but the real version, with the confusion and the dead ends included. This portfolio book is the beginning of that commitment. Every page I add here is a brick in a body of work I want to be proud of ten years from now.

I also dream of mentoring. Nepal has an extraordinary generation of young developers coming up — hungry, talented, and sometimes lacking access to the kind of guidance that changes trajectories. I want to be part of changing that. One conversation, one code review, one answered question at a time.

VI. The Summit

Behind all of these specific dreams is one larger one: to build something that outlasts me. A product, a company, a community — something that started because one developer in Kathmandu refused to think small and kept showing up, every single day, until the dream became undeniable.

The mountains are high. The air is thin at the top. I am still at base camp in many ways. But I have my gear, I know the route, and I am not turning back.

The best time to plant a tree was twenty years ago. The second best time is now. Every commit I push today is a seed. I intend to plant forests.