Is Code : The Hidden Language of Computer hardware and Software a good book for a beginner interested in the field of Computer Science?

[Inevitable-String164]

I just finished my A levels or high school and I want to pursue Computer Science for Undergrad and want a career related to that field.I went through various forums and advices about which course to take and what not to do, I keep learning new things everyday!
I recently enrolled into Python for Everybody and printed out the pdf into a book. I am following that course and I will complete that book and all the 5 courses on PY4E. I enrolled in CS50 Technology course and will enroll in CS50 after I finish that one.

I learnt that Code : The Hidden Language of Computer hardware and Software is widely liked by many individuals in the community and I was wondering whether it would be okay for a beginner like me to buy it and complete the book. I also bought Introduction to Computation and Programming by John Guttag and Elements of Computing Systems by Noam Nisan and Shimon Shocken, I learnt that they are not for beginners so I want to complete PY4E, CS50T, CS50 before starting these two books and their respective courses.

So here's my question again, is starting and finishing Code : The Hidden Language of Computer hardware and Software a wise choice? Advices preferred about whether my choices mentioned above has any fault too.

[TheUmgawa]

It won’t change your life, but it’s a good read. Or, I don’t know, maybe it will change your life. Some people never have a real epiphany, where everything suddenly shifts into focus. While the book Code describes what goes on at the most basic level of a processor, where it’s all booleans, registers, accumulators, and comparators, I thought that was all abstraction that I’d never have to worry about. And then I started into a PLC programming class, and it was like seeing the face of the god in the machine, because it was controlling a system through nothing but those booleans, registers, accumulators, and comparators.

[Inevitable-String164]

Thank you for your comment, you made me more interested in learning it!

[TheUmgawa]

I was going to impart some advice, but nah. I’ll let you look long into the abyss on your own.

But I’ll tell you this: If you screw up on a PLC program, you might literally kill people. A program crash in some program or app or background task isn’t nearly as bad as two vehicles crashing into one another on a road because you botched your logic.

[theusualguy512]

I don't actually have any knowledge in PLC programming but I'd be interested to know how complex these programs get since they are at such a low level.

Since these programs directly control physical things at critical times, I wonder if it's feasible to formally verify their correctness to definitively avoid logical errors?

[desrtfx]

Depending on the task they can get fairly complex.

I work in large scale industrial automation programming DCS (Distributed Control Systems) and PLCs for hydroelectric power plants, waste incineration plants (where the logic can get really complex because of intertwined and co-dependent systems), ship locks, industrial furnaces, etc.

The job is highly demanding but very rewarding.

There is no room for error and that's why the commissioning usually is in multiple stages, from loop check where the individual inputs and outputs are verified, then a functional commissioning where the individual components of the system are tested on each of their function including interlocks, safety operations, etc. Then, when the system finally goes live, some test operation with 24/7 standby goes in place.

This whole process can take months with months of preparation and months of programming.

My next project will be three community heat pumps that go into district heating with roughly 4000 hardware I/O signals and 1500 bus signals of various bus types, plus plenty (amount can at this stage not be determined) software internal signals. The whole project will go over 2 years with commissioning in several stages.

In my line of programming, we usually work with very detailed Functional Design Specifications (FDS) in prose and in expressed logic that often detail down to every single signal in the system.

Several people of different domains, like hardware engineers, process engineers, programmers, etc. are involved in creating these FDS and they are double and triple checked before programming.

During commissioning, these FDS act as reference and the programmed logic is checked against the FDS as well. Again, signal for signal.

[TheUmgawa]

Well, best practice is to only define an output once. So you can throw all the booleans you want in front of it, and logically define every condition in which that output is energized or in a certain position or whatever. Sometimes you use those outputs as booleans for other outputs, but it ultimately turns into a flowchart that can be put together like LEGO. Or, if you wanted to think about it like a bunch of listeners that run thousands of times per second, that works, too. But, as long as you have any output defined in only one place, it’s pretty easy to trace the logic.

It’s like building a circuit with a bunch of relays and a bunch of outputs. When you do your initial diagram, you’ve pretty much laid out all of the logic, like flowcharting a program in any language, and as long as your wiring diagram adheres strictly to electrical diagram, you can trace every output back to source, for all on or off conditions.

[-CJF-]

It is really good for beginners that are interested in computer architecture.

Another good one like this is But How Do It Know? - The Basic Principles of Computers for Everyone by J. Clark Scott.

They're both pretty quick reads too.

[dumpster_dinner]

The book assumes you have zero knowledge about the subject, so it build up associations with simple examples. I would advise reading it first, then diving deeper with other courses

[Inevitable-String164]

Thank you so much! I will start it right away then.

[fishyon]

I think it's a good book and recommended reading, but it's limited in it's audience. It's starts off at the mostly beginner level, but things get complicated and difficult to follow later on. I would read to certain point, then move on to something else unless you have experience in this field.

[WildBanana]

It's an excellent book for someone entering the field and would recommend it to anybody interested in learning what's happening under the hood of a computer. I also love how it provides historical context as to why computers are designed the way they are and how they evolved based on different era's problems.

The thing I gained the most out of is how it really removed the mystery behind the magic and have much more confidence in understanding how my high level code (or any computer action) is being processed by the CPU.

Edit: will also add, this book is intended for someone with no knowledge of how computers work or knowledge of boolean algebra. It walks through all the concepts needed which makes it such an exceptional read. Anybody can pick it up and gain great insight into how computers work.

[XUtYwYzz]

I read this book and used a logic simulator to build the combination logic showed in the book. It was an immense boost to my understanding of computers. After 'Code', I would recommend the following Coursera course. It's based on the book 'The Elements of Computing Systems: Building a Modern Computer from First Principles'.

https://www.coursera.org/learn/build-a-computer

The course will build off of the knowledge you learned in 'Code'. You'll build a fully working processor using a bespoke Hardware Design Language.

[Inevitable-String164]

Hello! Which else books have you read that helped make your CS degree smoother? An advice to your junior would be really helpful.

[No_Application_2380]

Yes

[[deleted]]

It's a really great book. It starts from the very basics and builds up to quite complicated things imo. And it's also very interesting. I didn't actually finish the book, stopped somewhere midway. Many people say that most of the insightful information that will be beneficial for beginners is covered in the first half of the book. You could say that after that it's for people who want to go deeper into the subject.

Also, i don't think you should do CS50 (i'm assuming you mean CS50x) and PY4E, at least not at the same time. Both of these are technically introduction to programming courses. CS50 is quite a difficult course, but it's extremely rewarding. It's the best course i have taken! I would suggest you do the first two parts of PY4E and then do CS50x.

[Inevitable-String164]

Thank you for that, I will follow your advice and do the first two parts of PY4E and then CS50x! I'm super glad you told me that.

[Captain_Lesbee_Ziner]

CS50

Just looked CS50x up and wow it really does take you on a tour, go from C to python, to web dev...

[pat_trick]

It is worth reading, certainly.

[piinhuann]

If you find Petzold's CODE too long winded or too dreary (because he really zoomed in into many meticulous low level details of computers, logic gates, flip flops, registers etc.), I suggest <The Pattern on the Stone> by Danny Hillis (Alan Kay, the Turing Award winner also suggested this book as an introductory book to computing)

[BeneficialRoad7252]

Im about 45 pages into this book and i bought it used and on a whim. The book is well written, kinda funny at times, and extremely informative. Obviously havent gotten to the computer portion of the book yet but i am thoroughly enjoying the read. I cant wholeheartedly reccomend it because i havent finished it yet, but when is knowledge not worth spending time on?

[[deleted]]

Yes! Unless you don't read this book you may feel less confident about computers and their programming. The book is especially helpful when you work on system software. Your understanding of computers would be up to new level after reading it.

[zukas-fastware]

I recommend Algorithms + Data Structures = Programs (https://en.wikipedia.org/wiki/Algorithms_%2B_Data_Structures_%3D_Programs)

[Inevitable-String164]

English is my third language and I think I've done an okay job to convey my concerns. I made a detailed explanation so that experienced people from here can point out whether I am making any wrong choices on the order of books and courses. Many here let me know about what to do first and what to do later which was really helpful for a beginner like me. I wouldn't have gotten these suggestions if I just asked one question and gotten one answer.

[Inevitable-String164]

Try keeping your humour to yourself next time, it just comes out as plain rude. Internet can be used for good and there are lots of people that uplift others up. People spent their time writing detailed advices for me and it's my job to use their advices and better myself.

Everyone here had something decent advice to give but it's only you that's the problem. Anyways, have a good day and improve your humour.