I've had a resume sitting in a Google Doc for a while now, and every time I looked at it, it felt... flat. It listed my skills and projects, but it never really showed how I think or what I'm like as a person. As a student, I wanted something that goes beyond a document — something that actually represents me.
Why Not Just Use LinkedIn?
Honestly? Because I wanted something that felt like mine. Social platforms are great for networking, but they're rented land — the algorithm decides who sees what, the layout is the same for everyone, and you can't really express yourself beyond a headline and a few bullet points.
I wanted a space where I could design things my way, write freely, and actually demonstrate what I know instead of just listing it.
Building It Was the Point
When I say I know HTML, CSS, and JavaScript on my resume, it's just text. But when you're on this site — reading this post, switching between dark and light mode, browsing my projects — that's the proof. I didn't use a template. I built the layout, the theming, the Markdown pipeline, all of it.
Was it perfect from day one? Absolutely not. I broke the styling more times than I'd like to admit. But every bug taught me something, and that's kind of the whole point.
Writing Helps Me Think
I've always found that explaining something forces you to actually understand it. This blog is where I plan to document what I'm learning — whether it's a framework I just picked up, a weird bug I spent hours on, or an idea from a course that clicked.
It's not about having all the answers. It's about showing up, being curious, and sharing the journey.
What's Next?
I have a bunch of ideas I want to explore — project deep-dives, data science experiments, maybe some notes from my engineering coursework. We'll see where it goes. The cool part is, this site grows with me.