18/03/2026


Have been practicing file operations such as reading, writing and appending. Remembering when and how to use the the file pointer and using the fprintf and fgets functions too. I'm also learning how to use more functions from the time.h header so that I can use variables that interact with actual time in my applications, which is pretty cool. Daniel Hirsch, a Youtuber I like to watch gave me an idea for a project. The project might by some people sound a bit meta and "woo" sounding, but I think it's actually cool. It's basically like an interactive diary, that asks you questions once you run it. After you have answered these prompted questions, the answers get stored into a log file, with a given time stamp. Because it only uses the appending file operation, it does not overwrite your data when you execute the program again, and like the write function, can also create the log file if it doesn't already exist.

Daniel's approach to this was sort of weird, he created his program in a needlessly sophisticated way. But in saying that, he did it out of pure prior knowledge which is to me quite impressive. As I've already mentioned, I've just freshly learned about file operations which couples perfectly with what he made. So I had a crack and was successful! The program asks 3 simple questions:

  1. What are you going to focus on today with your programming?
  2. What is your reason for focusing on this?
  3. What will you be looking forward to learning next?

It is so simple and concise, but is very good for keeping you on the ball and being productive, and doing/learning things with purpose. I chose these 3 questions because I think it gives a really good insight to my thinking process over a period of time. Then I can shape an optimal approach to my learning by extrapolating from prior entries. In other words, I can fuckin learn from the past - LOL. I've been doing a lot of experimenting and just playing around with C too. I personally think experimentation and playing with what you already know is a big part of learning programming. Sometimes I'll be playing around and hit a road block with something I want to do (regardless how pointless it may be), which forces me to look stuff up and increase my understanding. There are many little intricate details that are easy to look over when learning a language.

On the side, I've been learning about computer architecture. I'm currently learning about how adders, multiplexers, buses, registers. I'm doing this by looking at how people build a simple 8 bit computer. I've spent about 5 hours today learning about the 555 chip which is used as the clock for a lot of 8 bit computers. 32 and 64 bit computers like ours would laugh at a 555 chip. But I got to start somewhere, so I'm sticking to 8 bit computers for now. Don't be mistaken, It's a struggle for me trying to understand the electronics, but it's fascinating at the same time, I love it. My brain cells will get me there eventually, all three of them.

Back to homepage <<<©2026 Cforcat2k26>>>