My First Technical Blog: Why I'm Learning in Public

Introduction

Hey there! Welcome to my very first technical blog post.

I'm Nash — a second-year Electronics and Communication Engineering (ECE) student who loves building things, both in hardware and software, that can make a real difference in the world. This blog is the beginning of something I've been thinking about for a while, and today I finally decided to just start.

If you're curious about why an ECE student is suddenly writing blogs, or if you're someone just starting out in engineering and feeling a little lost — this post is for you. Let me tell you my story.

What Is This Blog About?

This blog is called "Learning in Public" — and that title means exactly what it says.

Instead of learning quietly in a corner and only showing the world my finished results, I want to share the whole journey — the confusions, the breakthroughs, the late-night debugging sessions, and everything in between.

The idea is simple: learn out loud, grow together.

Through this blog, I plan to write about:

• What it's really like to be an ECE student

• The technical skills I'm picking up (Embedded Systems, VLSI, AI, and more)

• Internships, projects, and real-world experiences

• Honest roadmaps and advice — especially for juniors who are just starting out

The Meaning Behind "Learning in Public"

A lot of people wait until they're "ready" to share what they know. They want to look perfect, polished, expert-level before they speak up. I used to think the same way.

But here's what I realized — nobody starts knowing everything. And if people like me don't share what we're going through while we're going through it, then the students who come after us are left without a map.

Learning in public means:

• Sharing what I know, even when I'm still figuring it out

• Being honest about what's hard, not just what looks good

• Building in front of people instead of hiding until everything is perfect

• Connecting with others who are on the same path

It's not about being the smartest person in the room. It's about being real and being useful.

My Story So Far — My First Year: Grades Without Goals

Let me be honest with you about my first year of engineering.

When I joined ECE, I had zero clarity on where I was headed. I didn't know what skills to learn, what to focus on, or what kind of engineer I even wanted to become. So I did what most students do — I focused hard on my studies, attended classes, and pushed for good grades.

And it worked. I finished first year with a solid CGPA and a good understanding of subjects like Mathematics, Physics, and Chemistry.

But then came the reality check.

When I sat down and looked at my resume, I realized something uncomfortable — I had studied a lot, but I hadn't built anything. I had knowledge, but no real skills to show for it. No projects. No internships. No direction.

That moment was a turning point for me.

I started asking myself real questions:

• What kind of engineer do I want to be?

• What problems do I want to solve?

• What skills actually matter in the real world?

Slowly, I started to figure things out. I discovered my interest in hardware-software integration — the intersection where circuits meet code. My long-term goal is to become an ASIC (Application-Specific Integrated Circuit) design engineer, which means I'll need to prepare seriously for competitive exams like GATE while also building hands-on technical skills.

So now, in my second year, I've built a clear plan. I'm actively learning:

• Embedded Systems — programming microcontrollers and working with hardware

• VLSI Design — chip design and digital circuits

• Artificial Intelligence — because AI is shaping every field, and ECE is no exception

I'm also doing internships, working on real projects like Project Aerotrax (solar-hybrid robotics) and Project BreatheSafe (air quality detection), and slowly building a portfolio I'm actually proud of. Not only that I have also started to do some AI based web that really gave a clear path in Artificial Intelligence

It took me a full year to find this clarity. I don't want the same for you.

Conclusion — Why This Blog Exists

Here's the summary of everything I've said:

1. I was lost in first year — no roadmap, no direction, just studying to survive.

2. I found clarity — through reflection, planning, and honest self-assessment.

3. I built a plan — focused on Embedded Systems, VLSI, AI, and career-building through internships and projects.

4. Now I'm sharing it all — because I believe no junior should have to figure everything out alone.

This blog is my way of giving back before I've even "made it." I want to document everything — the roadmaps, the mistakes, the technical concepts, the career insights — so that whether you're a fellow ECE student, a job seeker, or just someone curious about engineering, you'll find something useful here.

In my upcoming posts, I'll be sharing detailed roadmaps for ECE, honest reviews of internship experiences, explanations of technical topics in simple words, and a lot more.

This Is Just the Beginning

I'm also completely open to collaborations and internship opportunities. If you're working on something exciting or want to connect, feel free to reach out!

Thanks for reading my very first post. This is just the beginning — and I'm glad you're here for it. 🙌

— Nash | ECE Student | Builder of Things