Every developer has an origin story. Some start young, some start late. Some follow a straight path, others zigzag through trial and error. Here's mine — from writing my very first <h1>Hello World</h1> to building full-stack AI-powered applications.
The best time to start learning to code was yesterday. The second best time is now.
The Timeline
The Spark — First Line of Code
It started with curiosity. I opened Notepad, typed some HTML, and saw a heading appear in my browser. That tiny moment — seeing something I wrote come alive on screen — was magical. I was hooked.
Learning the Fundamentals
I dove into HTML, CSS, and JavaScript through free resources — freeCodeCamp, YouTube tutorials, and MDN docs. I built terrible websites. And they were beautiful to me because they were mine.
First Real Project — College Event Website
I volunteered to build the website for our college tech fest. It was messy, the CSS was spaghetti, and the JS probably had more bugs than features. But people used it. That feedback loop changed everything.
Discovering Backend & Databases
Frontend felt limiting. I wanted to build things that stored data and had logic. I learned Node.js, Express, and MongoDB. Suddenly I could build complete applications — login systems, dashboards, APIs.
Internships — Real World Code
Interning at Amypo (Web Dev) and Nexoris (AI/ML) taught me what textbooks can't — code reviews, Git workflows, team collaboration, and writing code someone else has to maintain.
The AI Chapter
I fell in love with AI. Python, TensorFlow, LangChain, OpenAI — building intelligent applications felt like a superpower. My final year project combined full-stack and AI, and it was the most rewarding thing I've ever built.
Lessons I Wish I Knew Earlier
1. Don't Chase Frameworks — Understand Fundamentals
I spent months jumping between React, Vue, and Angular before realizing I barely understood JavaScript. Once I invested time in vanilla JS, closures, prototypes, and async patterns — everything clicked. Frameworks became tools, not mysteries.
2. Build Stuff. Break Stuff. Repeat.
Every tutorial I followed made me feel smart. Every project I built from scratch made me feel dumb — at first. But that struggle is where real learning happens. The projects you struggle with teach you 10x more than the ones that go smoothly.
3. Read Other People's Code
Open-source repos on GitHub taught me more about clean code architecture than any course. I'd pick a library I used, clone it, and try to understand how it worked. It was humbling and enlightening.
4. Your Portfolio Is Your Resume
The best way to stand out isn't a fancy degree or certificate collection — it's a portfolio of real projects that show what you can build. This very portfolio website has opened more doors for me than any resume ever did.
5. Community Matters
Joining dev communities on Twitter, Discord, and local meetups connected me with people who inspired me, challenged me, and helped me when I was stuck. Nobody succeeds alone.
What's Next?
I'm focused on deepening my AI/ML expertise while building production-grade full-stack applications. My goal is to create technology that solves real problems — whether that's healthcare, education, or accessibility.
If you're just starting out — keep going. The path isn't linear, and imposter syndrome never fully goes away. But every line of code you write makes you better. And one day, you'll look back at your journey and realize just how far you've come.
The code you wrote yesterday that you're embarrassed about today? That's called growth.