Earlier quoted context omitted.
I'm 43 and I agree with this.
The fact that you're 43 makes me even more impressed.
The fact that you're impressed makes me impressed.
I'm 17 and wrote this guide on how CPUs run programs
281–290 of 327 posts
Re: I'm 17 and wrote this guide on how CPUs run programs
#282Very nice guide! I love your writing style, and your research skills are clearly top-notch. Great stuff!
You might enjoy reading some articles by Julia Evans (https://jvns.ca/), who has a similar informal, conversational, exploratory style.
Stay curious!
Re: I'm 17 and wrote this guide on how CPUs run programs
#283Earlier 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…
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!
> I will henceforth be referring to CPUs as "shazam alakablams" and there isn't anything you can do to stop me!
It will join "cursed thinking-rocks" in my vocabulary.
Re: I'm 17 and wrote this guide on how CPUs run programs
#284OP, don't excuse your work by prefixing it with your age. Your write-up is better than most people will ever do. Nice work!
Very unlikely anyone would care about this ChatGPT-level summary of how a CPU works if the author didn't mention they were 17.
Did you actually read the guide? It’s definitely not ChatGPT level summary material. While you could induce ChatGPT to issue the details, much as you can get it to issue details on string theory or almost any technical subject discussed on the web, it can’t provide the narrative or the stringing of details or guidance through the material.
The book is more about how Linux interfaces with the CPU and the CPU level discussion itself is more an introduction to CPUs to prepare for a discussion of Linux and the CPU - ELF, system call interfaces, etc. I think it’s a fairly useful overview and includes an awful lot of well thought out minutia and digging into “why is this that way” that clearly didn’t come from ChatGPT, but also didn’t come from the mind of a 17 year old - it came from googling and reading and then summarizing.
The accomplishment is that :
1) it’s remarkably well organized and structured, with clear language (n.b., the voice is clearly that of a 17 year old girl, not a pandering AI)
2) it’s detailed in a depth that’s remarkable for any engineer, but also is complete enough taking a bottoms up approach in explaining the Linux kernel interface
3) its clearly a learning exercise for the author, not a teaching of prior knowledge - which is wonderful they learned a subject as esoteric in depth in public and had the grace to invest energy in making it well presented and free
4) the combination of these things is a rare thing - depth, clarity of word and thought, and investment in quality presentation
I would have read it regardless of their age and been impressed, I think “I’m 17” is beside the point and could have just as easily been elided. But I didn’t read it as a “forgive my quality” or “read my stuff out of charity,” but rather “I am proud of what I did” and agree she should be.
Re: I'm 17 and wrote this guide on how CPUs run programs
#285Hi! 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…
Well done! It reminds me of my OS textbooks. The ending graphic with the bird yelling about E gave me a good belly laugh
Re: I'm 17 and wrote this guide on how CPUs run programs
#286Damn. If you're producing this type of content at 17, I can't even imagine the amazing things you'll be able to do it you choose to pursue the field professionally. Absolutely amazing!!
When I read this and looked through her repos my thought was the opposite in a way - I hope she doesn’t go into the tech field professionally and finds a way to do what she’s doing without her soul being crushed by petty management, pettier corporate goals, and pointless career growth. She’s doing great work as is, I wish there were a fellowship that could let her just keep going without crushing her soul in the hamster wheels of tech.
Re: I'm 17 and wrote this guide on how CPUs run programs
#287Hi! 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…
Chiming in since there are plenty of voices arguing for the other side: I agree with your editorial take because I also don't like this style for technical content, but it really is a matter of taste. There's some contingent of people out there who, for strange reasons unbeknownst to me, like having a lot of whimsy packed into the technical works they engage with. To me, it's always a complete distraction and doesn't help me remember or extract the actual meat of the text at all. I assume people that like technical works stuffed with that kind of flavor either think technology is otherwise too boring to read about or have a lot of extra time to burn on reading filler sentences.
But, that aside, I think this is a grand slam. Kudos to the author.
Re: I'm 17 and wrote this guide on how CPUs run programs
#288This is so cool! And I'm dismayed that you have been subjected to the typical Hacker News cynicism.
By looking through some of your other project and interests, I can see that you likely have a healthy sense of your own capabilities and certainly don't need my validation or approbation. But I'm going to give it anyway.
Piffle on anyone who knocks you on tone! It is not trivial to make this level of technical information available in such an approachable fashion. When we first start our careers, detailed technical knowledge and the ability to solve low-level problems are super important. But the way you "crawl up the value chain" in software engineering is to become a "force multiplier" - someone who can make other people more productive. And the ability to communicate well (both what to communicate and how to communicate it) becomes a more and more important skill. This work clearly demonstrates your communication skills.
I hope you make software engineering your career choice. The field could use more people like you.
Re: I'm 17 and wrote this guide on how CPUs run programs
#289Awesome! All I could do at 17 was chase skirt and get drunk.
Re: I'm 17 and wrote this guide on how CPUs run programs
#290Very nice guide! I love your writing style, and your research skills are clearly top-notch. Great stuff! You might enjoy reading some articles by Julia Evans ( https://jvns.ca/ ), who has a similar informal, conversational, exploratory style. Stay curious!
I am very glad you liked it! Julia Evans is one of my biggest inspirations ever. I have a lot of her zines. SHE ACTUALLY READ MY ARTICLE EARLIER AND I JUST ABOUT EXPLODED https://twitter.com/b0rk/status/1689331862487932928