I started my programming career in the late 1980s. We were taught "design top down, build bottom up". Been doing it that way ever since. If you've ever used the Forth programming language, you _have_ to build your software that way. That's no other way.
i swear that's how I think of things ...the base components that can add to the complete thing...I started with BASIC in the late 90s, then moved to C and so on
this is what we study in electrical engineering and embedded systems it's digital electronics and yes it's a way of programming things too this is way lower than the assembly code this is the binary code in person
Yep, being an electronics major and programming is so fun, because you know combinatorial circuits…which are clocked in fully parallel logic at low level, like Half Adder, Full Adders, Ripple Carry Adder, barrel Shifter, Mux, DMux, etc…the sequential circuits are when the memory and feedback starts to get introduced…the whole knowledge including clock timing and some HDL, makes high level programming optimization extremely simpler to understand Not to mention karnaugh map (K-map) logic simplification
I'm neither a CS major nor do I program as part of my job (other than some Python that I did a few years ago), but I do look at code frequently, and I deal with PCBs. About 3 years ago, I had to learn 8051 assembly, and at the same time I really dug into all of the low-level stuff that you talked about (I knew a fair bit - no pun intended - about some of it, but I didn't feel really comfortable with it). Let me tell you, learning about how hardware and assembly work together helped me to understand how computers/hardware really works MUCH better. I would HIGHLY recommend learning from the bottom up. There are probably some people who couldn't care less about the low-level details, but I, for one, absolutely love knowing how things work at their most basic level. Just as an aside, besides doing lots of googling to learn, I also read (more than once) the book But How Do It Know?, which helped explain much of what you talked about in a very simple easy to understand way.
That's great! The low-level learning approach certainly gives appreciation for the shoulders of giants we stand on and confidence from having a foundational understanding. Unfortunately I completed my Machine Organization course which is really the only hardware/low level class in my CS program so I'm not sure how much more of this type of content I will do. Doing content on modern languages like Go seems to be what people like the most.
this would be great for the majority of web devs which take everything hardware gives, and immediately throws it away in about a billion layers of abstractions
Fantastic recommendation, just picked this book up... wow, it's great. Reminds me a lot of Computer Systems: A programmers Perspective 3rd edition. Looking forward to working my way through it.
I started my programming career in the late 1980s. We were taught "design top down, build bottom up". Been doing it that way ever since. If you've ever used the Forth programming language, you _have_ to build your software that way. That's no other way.
i swear that's how I think of things ...the base components that can add to the complete thing...I started with BASIC in the late 90s, then moved to C and so on
Forth... how real OS's bootstrap.
Thanks for the recommendation. I've been looking for something like Introduction to Computing Systems for a while now
It's a very dense book but worth it. I'd love to get good at animations somehow to show binary/hex conversions.
this is what we study in electrical engineering and embedded systems it's digital electronics and yes it's a way of programming things too this is way lower than the assembly code this is the binary code in person
Yep, being an electronics major and programming is so fun, because you know combinatorial circuits…which are clocked in fully parallel logic at low level, like Half Adder, Full Adders, Ripple Carry Adder, barrel Shifter, Mux, DMux, etc…the sequential circuits are when the memory and feedback starts to get introduced…the whole knowledge including clock timing and some HDL, makes high level programming optimization extremely simpler to understand
Not to mention karnaugh map (K-map) logic simplification
I'm neither a CS major nor do I program as part of my job (other than some Python that I did a few years ago), but I do look at code frequently, and I deal with PCBs. About 3 years ago, I had to learn 8051 assembly, and at the same time I really dug into all of the low-level stuff that you talked about (I knew a fair bit - no pun intended - about some of it, but I didn't feel really comfortable with it). Let me tell you, learning about how hardware and assembly work together helped me to understand how computers/hardware really works MUCH better. I would HIGHLY recommend learning from the bottom up. There are probably some people who couldn't care less about the low-level details, but I, for one, absolutely love knowing how things work at their most basic level. Just as an aside, besides doing lots of googling to learn, I also read (more than once) the book But How Do It Know?, which helped explain much of what you talked about in a very simple easy to understand way.
That's great! The low-level learning approach certainly gives appreciation for the shoulders of giants we stand on and confidence from having a foundational understanding.
Unfortunately I completed my Machine Organization course which is really the only hardware/low level class in my CS program so I'm not sure how much more of this type of content I will do. Doing content on modern languages like Go seems to be what people like the most.
this would be great for the majority of web devs which take everything hardware gives, and immediately throws it away in about a billion layers of abstractions
I a had class that went over logic gates all the way to learning MIPS assembly interesting class all things considered.
Fantastic recommendation, just picked this book up... wow, it's great. Reminds me a lot of Computer Systems: A programmers Perspective 3rd edition. Looking forward to working my way through it.
Nand to Tetris is a lot of fun!
niiice! circuitverse is cool
I'm i d only one seeing the gui in slow horses
thanks
And this is why CS degrees are useless and you should be studying EE or CE instead.