Item: Self-Study Computer Architecture + Operating Systems
Rating: 4
Author: 이때의 나

Background for Reading#

I chose this book to read while participating in the 12th cohort of Hongong Study Group. I wanted to gain a better understanding of computer architecture through this book. I always felt that my knowledge of computers was lacking. I hoped this book would be a great help.
I had read a book on a similar topic called So How Does a Computer Work? before starting this one, which made it feel much easier.

You can see more detailed book summaries through these links:

While Reading#

The book Self-Study Computer Architecture + Operating Systems was great because it provides many illustrations and supplementary explanations for non-CS majors, allowing for a detailed understanding.

In the operating systems section, it was interesting to see content I had learned at 42 Seoul. It was nice to revisit in a book the material I had learned through coding assignments at 42 Seoul. Although the order of instruction was different from the book, I was able to review topics like processes and threads once more.

Some parts were easy to read because I had already learned them from other books or other sources. Still, I think it could be somewhat helpful for non-CS majors or people just starting out in development. It might be more difficult if you read it without any sense of how computers work, but I recommend giving it a read. Personally, I think watching videos to see how things actually work is even better.

After Finishing#

The book has a very high page count, so it sat on my shelf for a very long time after purchasing. But this time, by reading little by little through the Hongong Study Group, I was finally able to finish it. More than the content itself, I'm really happy about the fact that I read through all 500 pages.

Now I'm finally going to read the books I've been wanting to read. Lately, my concern has been that I want to manage feature development systematically, like how companies handle planning-design-development, but since I've been building apps alone, some things have been glossed over. So I want to create an environment where when other people collaborate on the apps I've built, they can look at the documentation and start working right away without issues. That's why I'm planning to read books related to this!

If anyone knows of tools or smart ways to communicate requirements and designs so that developers can comfortably focus solely on development, please let me know.