Should I Build Projects or Read a Book First for Learning C?

While reading can be beneficial, I think it’s crucial to at least skim a book or relevant documentation before starting a project. It helps you get a foundational understanding and best practices, so you’re not going in completely blind. Then you can start building and do more in-depth research as you go.

Honestly, I’d say both! It’s like weightlifting; just lifting weights without any guidance can lead to injuries and inefficiencies. Reading a good book can teach you the principles and give you a foundation, but if you only read without practicing, you're missing out. It’s best to combine the two—learn from a book and apply those concepts in projects. Some books even have exercises to do alongside the reading, which can really help you get hands-on experience.

I recommend you read just a single book to avoid getting stuck in analysis paralysis. Start with something manageable—maybe an Edabit challenge or simple coding tasks like those on LeetCode. Once you feel more comfortable, tackle a tiny project. This way, you're learning as you build without falling into the endless trap of reading more."

Just dive right into building! You learn so much more through practice than by just reading. Start with something simple, like a small application, and you'll hit walls that will really challenge your understanding. That's when you pick up the book or do some Googling for specific help.

I say just jump in! Since you’re already familiar with frontend stuff, pick a simple C# project, like a REST API or a CRUD application. You might feel unprepared at first, but that’s where the real learning happens. You’ll face challenges along the way that will require you to research and figure things out, which can be way more effective than just reading.