What happened to the Show HN: on this?
I took it off because reading material isn't supposed to be Show HN.
That's not any judgment about the content, which as far as I can tell is great.
I'm 17 and wrote this guide on how CPUs run programs
161–170 of 327 posts
Re: I'm 17 and wrote this guide on how CPUs run programs
#162Very nicely written, and congrats on doing such a deep dive on this kind of topic. These days 17 year olds can get away with "programming" by gluing things they don't understand, but I think they'll eventually hit a ceiling. So what you're doing is super valuable, not for yourself, but for everyone else who will learn from your materials. Well done :) EDIT: now go write an emulator if you haven't already, it's a ton…
These days 17 year olds can get away with "programming" by gluing things they don't understand... I've been doing that for 26 years. ...but I think they'll eventually hit a ceiling. I wonder if it'll happen soon.
I think there are different ceilings.
And probably everyone has some spaces where they didn't reach their ceiling yet.
Re: I'm 17 and wrote this guide on how CPUs run programs
#163Wow, so because you're 17 we should click on this article? I was 17 also some time ago
"Please don't pick the most provocative thing in an article or post to complain about in the thread. Find something interesting to respond to instead."
"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."
Re: I'm 17 and wrote this guide on how CPUs run programs
#164Halfway through part one and I'm hooked! Thanks for writing this. It's something I didn't know I needed.
Re: I'm 17 and wrote this guide on how CPUs run programs
#165Nicely done!
Re: I'm 17 and wrote this guide on how CPUs run programs
#166Very cool.
What a novel way to show your skills to employers.
Re: I'm 17 and wrote this guide on how CPUs run programs
#167As someone who has worked a bunch with debugging Linux itself, debugging qemu, and vulnerabilities in kernel and userspace, I really struggle to appreciate stuff like this because my initial reaction is “well, duh, of course that’s how it works” but looking back at myself getting into those fields I really applaud you and thank you for creating this great content
Re: I'm 17 and wrote this guide on how CPUs run programs
#168Congrats on completing this guide. > There aren't many comprehensive systems resources if you aren't going to college, so I had to sift through tons of different sources of varying quality and sometimes conflicting information. The absolutely best resource you will find is Charles Petzold's Code: The Hidden Language of Computer Hardware and Software . The 2nd edition was just released. https://codehiddenlanguage.com/
I think The Elements of Computing Systems by Noam Nisan and Shimon Schocken and the associated nand2tetris project is just as good if not better and is much more hands-on. https://mitpress.mit.edu/9780262539807/the-elements-of-compu... https://www.nand2tetris.org/
While these are great projects, they're for very different audiences. Code is a really well written pop-science book that goes into logic circuits. The Nand2Tetris book comments for example that:
> The HDL that we will use is documented in appendix 2 and can be learned in about one hour
which about as meaningful as saying you can learn X's syntax in an hour. Nand2tetris is a serious investment of time and if you've never done something like FPGA design (VHDL etc) or assembly, it takes a bit of getting your head around.
It's also worth mentioning Shenzhen IO as an interesting take on this (edutainment for programmers) https://www.zachtronics.com/shenzhen-io/
Re: I'm 17 and wrote this guide on how CPUs run programs
#169This is really great. There are many developers with decades of experience that don't understand these things.
Count me in.
Re: I'm 17 and wrote this guide on how CPUs run programs
#170Hi! I'm Lexi, I wrote this article/mini-book. There's a classic question of "what happens when you load a website?", but I've always been more interested in "what happens when you run a program?". About 3 months ago, I was really annoyed at myself for not knowing how to answer that question so I decided to teach myself. I taught myself everything else I know in programming, so this should be easy, right? NOPE! Appare…
Hi Lexi, pretty cool project you finished there! Congrats!
I was a little confused about how you only talked about the sources on the internet are kinda poor. But I didn't see any comments about books for research...
Did you use any? Can you recommend some on this topic?