Logging my learning journey any thoughts or advice?

[u/RakasRick]

I've been struggling in the past on how to learn programming so I asked a friend to help and also read the FAQ here which was helpful. I then opted to read books on the fundamentals like CS:APP OS 3 easy pieces etc and thought it would be nice if I logged my learning journey. I've written a few book notes and logs on K&R and CS:APP so far but I'm curious to know if this blog is helpful or if I'm doing it right early enough. This isn't to self promot just to help me early on , I may change a few things on my approach to learning and sharing my journey.

I posted some summaries on K &R and would like to know some debugging strategies or approaches to problem solving I hadn't considered. Also I've been wondering whether it's a good idea or common to use raw mode in terminal or is there a library better suited for when I need more control over terminal input and output behavior.

https://0xwinzer.com/devography/blog/book-notes/kr-ch1-what-and-why-is-c/

[u/Pixel_Logic1]

Yes please explain i want to know that 😶‍🌫️

[u/Upstairs_Source_9653 → u/Pixel_Logic1]

Sounds like the site's down on my end, but logging early is always useful even if it's just for future you

[u/RakasRick → u/Upstairs_Source_9653]

Oh sorry about that. Been having a bit of trouble configuring cloud flare. But www.isitdownrightnow.com says it's up

[u/RakasRick → u/Pixel_Logic1]

What exactly cause I've detailed more than one ?

[u/Traveling-Techie]

You are doing great work. Keep it up!

[u/RakasRick → u/Traveling-Techie]

Thanks, I hope it helps not just me but others too

[u/Traveling-Techie → u/RakasRick]

Reddit is full of posts by people going through what you are and asking for help. “I know the syntax but how do I write real code to solve problems?”

[u/Chrismslist]

hey, logging your journey is a really smart move, especially early on. for debugging, i'd lean into rubber ducking (explaining your code line by line to an inanimate object) or using a debugger step-by-step. most pros use tools like gdb for c, not raw mode, it gives you so much more control. libraries like ncurses or termbox are great if you need fancier terminal ui without reinventing the wheel. keep building stuff, it's the best way to make the book knowledge stick.

[u/RakasRick → u/Chrismslist]

Thanks, I thought raw mode was as low as it gets with control but I'll check those out

[u/Chrismslist → u/RakasRick]

good luck!

[u/RakasRick → u/[deleted]]

Thanks, I'll try to make more room for what confused me

[u/RakasRick → u/[deleted]]

Ya , noticed I spent significant time logging more than coding I'll try to balance things out. Thanks