When I was 11 I coded in assembly and machine language, what do I win?
It's just someone impersonating a kid to get GitHub stars. I am baffled HackerNews bought it.
I'm 17 and wrote this guide on how CPUs run programs
251–260 of 327 posts
Re: I'm 17 and wrote this guide on how CPUs run programs
#252Hi! 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…
Having read the first couple of pages, my only feedback is a strong suggestion to drop the cutesy language. >The central processing unit (CPU) of a computer is in charge of all computation. It’s the big cheese. The shazam alakablam. It starts chugging as soon as you start your computer, executing instruction after instruction after instruction. Given the context, that would read much better as: >The central processin…
[deleted]
Re: I'm 17 and wrote this guide on how CPUs run programs
#253Re: I'm 17 and wrote this guide on how CPUs run programs
#254Re: I'm 17 and wrote this guide on how CPUs run programs
#255Hi! 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…
I can't resist pointing out that LWN ( https://lwn.net/ ) has been dedicated, for many years, to the production of operating-system information that is not terrible. Have a look, and perhaps consider joining us :)
OP should reach out to LWN. This content would be a great addition.
Re: I'm 17 and wrote this guide on how CPUs run programs
#256Earlier quoted context omitted.
Having read the first couple of pages, my only feedback is a strong suggestion to drop the cutesy language. >The central processing unit (CPU) of a computer is in charge of all computation. It’s the big cheese. The shazam alakablam. It starts chugging as soon as you start your computer, executing instruction after instruction after instruction. Given the context, that would read much better as: >The central processin…
She's a 17 year old girl. I'd be more worried if the language wasn't "cutesy". Lexi, don't change a thing. This document you've created encompasses who you are right now and more importantly, where you are in your technical journey and understanding. The tone is just fine the way it is. If you're compelled to "fix" something, just correct errors and call it a day.
[deleted]
Re: I'm 17 and wrote this guide on how CPUs run programs
#257Re: I'm 17 and wrote this guide on how CPUs run programs
#258Earlier quoted context omitted.
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 n…
> While these are great projects, they're for very different audiences.
That was my point in posting The Elements of Computing Systems since it seems that the author of this post might be more interested in hands-on side of building a CPU and the software stack on top of that.
I think the authors are actually right in that the syntax of their HDL can be learned in an hour. It's more that learning how to use that syntax to build a CPU takes a good amount of time.
Thanks for the mention of Shenzhen IO. I'll check it out.
Re: I'm 17 and wrote this guide on how CPUs run programs
#259Re: I'm 17 and wrote this guide on how CPUs run programs
#260Hi! 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…
Hey great work you did there. I'd also like to recommend nand2tetris and its companion book Elements of Computing Systems. If you'd like to dig deep into how a cpu is actually elemented via HDL.
I agree this would be a great addition. If I had a minor complaint about the work presented here, it's that it starts "in the middle"; pushing down to CPU OpCodes without describing how the ML codes are actually defined. It's typically easier to understand if you start at either the very top (like how does "Hello, World!" actually get executed?) or very bottom (though I'd argue you could stay above the physics of semi-conductors, at the chip level).