Why I'm starting Blogging as an Engineering Student
When I started my engineering journey this year, I spent hours learning — tutorials, documentation, late-night debugging — but at the end of each week, everything blurred together.
I was learning a lot, but retaining very little.
That’s when it hit me:
“If I can’t explain what I learned, I probably don’t fully understand it yet.”
So, I decided to start writing.
I’m not starting this blog to go viral or look smart.
I’m starting it to think more clearly.
Writing forces me to slow down, break things apart, and understand what’s actually happening behind the code.
It’s not about showing off — it’s about learning in public and leaving a trail of what I’ve figured out along the way.
I’ve realized that in tech, your ability to build and explain are equally valuable.
Blogging builds both.
Every post:
Reinforces what I learn
Helps someone else avoid the same mistakes
Builds a small corner of my online identity — proof that I’m genuinely curious about technology
In a world full of résumés, I’d rather have something that shows what I know instead of just listing it.
This blog will be my open notebook — a mix of:
Project write-ups
Simplified explanations of topics I’ve struggled with
Lessons learned from experiments that didn’t go as planned
If you’re an engineering student or beginner in tech, maybe you’ll find something useful (or at least relatable).
Blogging isn’t about perfection. It’s about progress.
If one post helps me understand a topic better — or helps one person learn something faster — that’s enough.
Here’s to documenting the journey, one post at a time!
