Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I'm 17 and wrote this guide on how CPUs run programs

github.com

Post reply on HN
Print view View original

221–230 of 327 posts

Re: I'm 17 and wrote this guide on how CPUs run programs

#221

Post by mananaysiempre »

zahllos wrote: post #198
archmaster wrote: post #14

Hi! 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've only skim-read your articles so far, but it looks excellent. Congratulations and please keep doing work like this. I previously worked as a research engineer (a fancy name for a software engineer working in a university lab, in my case doing computer security research) so believe me when I say there are graduate students who don't have your grasp of operating systems (see the comments elsewhere on OS courses bei…

> https://git.lain.faith/sys64738/airs-notes.git

Oh, that’s awesome, it even has some things transcribed from Fengrui Song’s blog (https://maskray.me/) as well—I sometimes feel like it’s the only place where some particulars of binutils(-compatible) behaviour are documented (I don’t come there for the generalities, though, like GP is seeking). I only wish there were more of these transcriptions :)

Re: I'm 17 and wrote this guide on how CPUs run programs

#222

Post by AndrewKemendo »

archmaster wrote: post #14

Hi! 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…

We Will Watch Your Career With Great Interest

Re: I'm 17 and wrote this guide on how CPUs run programs

#223

Post by astroalex »

trogdor wrote: post #204
archmaster wrote: post #14

Hi! 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…

I couldn't disagree more. I found the tone charming, funny, and accessible. I think it would particularly resonate with kids and beginners. It reminded me, in the best way, of why the lucky stiff's writing.

I will henceforth be referring to CPUs as "shazam alakablams" and there isn't anything you can do to stop me!

Re: I'm 17 and wrote this guide on how CPUs run programs

#224

Post by depressedpanda »

cbozeman wrote: post #213
trogdor wrote: post #204

Earlier 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.

You both have a point.

"Cutesy" language may act as a distraction to the reader, and -- like anything when overdone -- can be detrimental to the text. Kill your darlings and all that.

_However_, if something isn't supposed to be a terse reference manual, it will convey a lighter tone and seem more approachable to most people, if used judiciously.

I don't think anyone has enough experience at 17 to know where to strike the right balance, so overdoing it (and being called out for it) is just part of the journey of becoming a better writer while finding your own personal style and tone.

Re: I'm 17 and wrote this guide on how CPUs run programs

#225

Post by paulmilligrams »

trogdor wrote: post #204
archmaster wrote: post #14

Hi! 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…

If I was your editor, I'd add the following with a red ballpoint pen:

Out of touch, tone deaf take. Revise.

Re: I'm 17 and wrote this guide on how CPUs run programs

#226

Post by astroalex »

archmaster wrote: post #14

Hi! 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…

You have a gift for writing and teaching technical concepts. I think you could make a serious impact on computer science education if you pursued that as a career. Congratulations on finishing this mini-book!

Re: I'm 17 and wrote this guide on how CPUs run programs

#227

Post by [deleted] »

mgaunard wrote: post #59
archmaster wrote: post #14

Hi! 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 haven't done the research, but I can't believe most of the information could be that hard to find or wrong, at least if you know where to look. These sorts of topics are usually well-covered in the matching undergraduate-level computer science courses (computer architecture and operating systems, which, these days, are mostly optional since out of fashion). Several universities have free courses available, and some…

[deleted]

Re: I'm 17 and wrote this guide on how CPUs run programs

#229

Post by Southworth »

trogdor wrote: post #204
archmaster wrote: post #14

Hi! 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…

I loved the poignant guide to ruby and that’s not dissimilar at all. I think you’ve been a little unkind/too honest.

Re: I'm 17 and wrote this guide on how CPUs run programs

#230

Post by Southworth »

trogdor wrote: post #204
archmaster wrote: post #14

Hi! 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…

I loved it, and it reminded me a lot of The Poignant Guide to Ruby.
Post reply on HN