News for hackers. Stuff that matters.
Re:5.5 mm in 1.25 nanoseconds by Ciantic on Thursday January 13, 2022 @09:31AM (#29921087)
> I got a copy of the detailed descriptions of the Xbox 360 CPU and I read it through multiple times

This way of learning is not taught often enough, we learn it in school when learning another language (e.g. repeating words over and over). But in sciences and engineering the repeated reading of the material is not usually encouraged or talked about.

It would be interesting to see what the material was, it's not linked, but it must have been really detailed.

Re:5.5 mm in 1.25 nanoseconds by brucedawson on Thursday January 13, 2022 @01:56PM (#29925014)
The material was all proprietary/NDA and I don't think it's ever been shared publicly, sorry.

The main point I wanted to make with how I became the CPU expert was not actually the "reading multiple times" in order to deeply understand it (although that was important) but rather the fact that I chose to become the CPU expert rather than having it assigned to me.

It was one of many times that I became the acknowledged expert of some area, and perhaps therefore in charge of that area, just by working hard in that area until I was "obviously" the expert.

Re:5.5 mm in 1.25 nanoseconds by zeusk on Thursday January 13, 2022 @06:28PM (#29928483)
Yeah, I definitely echo this.

I work on Display team in Windows and in past worked mostly on IddCx and SoftGpu but recently went through some VESA docs and chimed in my opinion during some meetings. Now I'm leading DisplayPort reliability efforts with graphics IHVs

Re:5.5 mm in 1.25 nanoseconds by scoutt on Thursday January 13, 2022 @11:03AM (#29922202)
> repeated reading of the material

I taught myself almost everything I know, and repeated reading is the method I usually use. I don't memorize, but instead I attack any material to learn by "reading sweeps" (this only applies to topics I know nothing about).

I first read all the material and, even if I don't understand a word about anything, I keep going until the end. Then I read everything again from start to end and here I can definitely say that I'm starting to understand. Then again, and this time I allow myself to go back and clarify something I didn't understand. When I feel confident, I try to implement something with the reading material at hand.

I can't recall any material that I recently learnt that way but "The definitive guide to the ARM Cortex M3" by Joseph Yiu is a book I remember (back in 2007 when I started with Cortex microcontrollers).

Re:5.5 mm in 1.25 nanoseconds by billti on Thursday January 13, 2022 @11:58AM (#29923160)
That the approach I've settled on that works best for me. I used to get frustrated that there wasn't "one source" of information that could take me on the journey from novice to expert, and that there was "so much to choose from" on most topics.

Now I happily browse through as many sources as I can find, noting which I think are high quality even if above my head, and absorbing what I can for my current knowledge level. Then I'll revisit the good stuff and scan it to pick up the next layer deep, and repeat over select material until I feel I have what I need.

The other thing I do is make flashcards as I go (I use an app called Quizlet, but I know there are lots out there). Especially with a new subject, just basic terms can be overwhelming at first. I capture want I feel is important in a question & answer format, and just fire it up when I have to a few mins to run through some flashcards (e.g. waiting for a meeting, sitting on the lav, etc.). It seems to work really well for me.

Re:5.5 mm in 1.25 nanoseconds by tomcam on Thursday January 13, 2022 @11:16AM (#29922407)
Impressive. I’m just now learning how to learn that way, and I’m at retirement age. My way is much less efficient, because I stop and research each thing I don’t understand until I feel comfortable moving on. Highly inefficient, I now believe. My kid does what you do and learns way faster than I ever did.
Re:5.5 mm in 1.25 nanoseconds by Cthulhu_ on Thursday January 13, 2022 @10:23AM (#29921689)
It depends, as always. A CPU is a whole unit, where (I think) it's worth knowing all the details. A programming language's standard library would be more about having a high level overview of what is available, and not a rote reading of all APIs.

...Unless you're into that kind of thing, and I do believe it will help "pick the right tool for the job", instead of writing your own or picking a random library off the internet. Maybe I should make a habit of it, I'm quite invested in Go at the moment.

On the other hand, probably a bigger factor is 'arsedness'. I don't have the attention span or interest to read something back-to-front, or maybe not anymore? I don't know for sure. But there's not many things that grip me enough to really draw me in.

...except writing shitpost comments on HN.

Re:5.5 mm in 1.25 nanoseconds by erosenbe0 on Thursday January 13, 2022 @11:56AM (#29923132)
Yes, I teach my students to always at least look at the overview and see what is available and the taxonomy or ontology!

Don't treat all sources as a mere dictionary of self-evident structure. Quitting just because the blurb of immediate interest has been rendered leaves out key opportunities to learn what is available.

Re:5.5 mm in 1.25 nanoseconds by Tepix on Thursday January 13, 2022 @09:41AM (#29921202)
I used to read a lot of books when learning about computer science topics. I'm sure i've read the Camel book at least 4 times over several years. A well written book like that can really do much more than just provide a reference.

A lot of documentation these days is mostly references that you look up when you need the nitty gritty details and the bigger picture is not documented as well.

Re:5.5 mm in 1.25 nanoseconds by 123pie123 on Thursday January 13, 2022 @09:48AM (#29921290)
this is my standard way of learning stuff,

I don't repeatedly read books just to memorise or remember stuff, but I repeatedly read books because you learn and fully digest certain concepts which are then needed before moving on to other concepts

Re:5.5 mm in 1.25 nanoseconds by JasonFruit on Thursday January 13, 2022 @10:23AM (#29921692)
This is exactly it for me: on your first reading, there are underlying concepts you kind of get, but don't fully understand until you grasp what's built on top of them. Then, with that fuller grasp, you can go back and increase your understanding of the underlying material, which lets you understand the superstructure better — and the effect persists for several iterations if the topic is involved enough.

Short version: don't be too concerned if you're not completely confident on the details the first time through, because it will make a lot more sense next time around.

Re:5.5 mm in 1.25 nanoseconds by 123pie123 on Thursday January 13, 2022 @11:09AM (#29922289)
I also have the same approach for new projects

I appologise in advance for the fact I will repeat questions to people and get it wrong initially, it's part of the learning process

Re:5.5 mm in 1.25 nanoseconds by ehnto on Thursday January 13, 2022 @10:05AM (#29921474)
I think rote memorization is less useful in engineering than critical thinking/problem solving, that is probably why. It's not really important you know X value of Y part by heart, you need to know how to get X value of any possible part you encounter.

To learn a language, you can't problem solve your way to the solution, you either know it or you don't, and when you use it in practice (in a conversation) you can't look up what you need to know on the spot.

Re:5.5 mm in 1.25 nanoseconds by wpietri on Thursday January 13, 2022 @10:55AM (#29922088)
We're not talking about rote memorization here. We're talking about deeply studying something.

In the mid-90s I set up my then-employer's first WAN. Cisco 2501 with T1s for in-city links and frame relay for inter-city/international. As part of our Cisco contract, we got a full manual set, which was maybe 24" of shelf space. In my spare time over a couple of weeks, I sat down and read the whole thing. Then I went back and actually studied the parts that were relevant, mostly by reading and re-reading until it all made sense to me.

On top of that, I added a lot of practical experimentation with the gear. But foundational for me was really understanding the perspective of the people who made it.

Re:5.5 mm in 1.25 nanoseconds by ehnto on Thursday January 13, 2022 @09:27PM (#29929917)
Ah, that is different then yes. I think another comment alluded to it but much documentation these days is just simple reference material which without context is only so useful for deep understanding.

I fully agree with understanding the perspective of the people making the thing, knowing the what isn't always as useful as knowing the why. I speak a lot about being idiomatic, which is to say developing in a way that is sympathetic to the system and its existing approaches. That takes understanding the why more than the what.

I am reminded of the Honda motorcycle maintenance manuals. They are like being face to face with the engineers who designed the bike, reading that back to back would give you that deeper understanding of the system I think.

That's my pet peeve with auto-generated docs, they don't actually help much. I can see the function for myself, I don't need to be told it exists, I need to know why!

Re:5.5 mm in 1.25 nanoseconds by tomcam on Thursday January 13, 2022 @11:19AM (#29922451)
Aargh the thing that amazes me about people like you is the ability to push through when the docs don’t explain something before it’s referenced. How do you get past that point so quickly?
Re:5.5 mm in 1.25 nanoseconds by wpietri on Thursday January 13, 2022 @11:39AM (#29922839)
On the first pass? I usually just let it be. Maybe I'll mark it or make a note, but probably not. I've spent my whole life not understanding almost everything right away. If it's important, it'll come up again. It's sort of like starting a new job: you don't know who everybody is right away but you get it over time.

On later passes, I'm more inclined to jump around.

Re:5.5 mm in 1.25 nanoseconds by tomcam on Thursday January 13, 2022 @11:46AM (#29922966)
Thank you! I never tire of learning how people learn.
Re:5.5 mm in 1.25 nanoseconds by tanseydavid on Thursday January 13, 2022 @01:31PM (#29924624)
It is important to develop the confidence that you are not actually wasting time reading something which feels as if you understand almost none of it.

It is counter-intuitive because it tends to feel a little bit like a small child who has not yet learned to read, picking up a book and pretending to read by mimicking what the behavior looks and sounds like.

Re:5.5 mm in 1.25 nanoseconds by wpietri on Thursday January 13, 2022 @11:07AM (#29922240)
For what it's worth, I think this "deep study" mode of learning is perhaps less useful today in tech. We have a lot more things we need to work with with now, and a searchable internet means we can draft off other people's learning a lot more. Deep understanding is both less possible and less useful for the bulk of us, who are mainly integrating lots of libraries, services, tools, and frameworks.

But for every given topic, we still need deep experts, like Bruce Dawson was for this processor at Microsoft. So I think this mode is still very valuable, so I agree with Ciantic: this way of learning is something everybody should have at least some practice in.

Re:5.5 mm in 1.25 nanoseconds by thereddaikon on Thursday January 13, 2022 @11:27AM (#29922581)
What he is describing is just RTFM. It shouldn't be groundbreaking or really up for debate yet here we are. Manuals are written expressly for this purpose. A properly written manual has everything you need to know to get it working in a practical sense. Theory is a different matter altogether. But we are talking about engineering not science. Engineering is very much in realm of practical application.

If reading a manual front to back for a bit of tech doesn't tell you everything you need to know to use it properly then its not a good manual.

Re:5.5 mm in 1.25 nanoseconds by onemoresoop on Thursday January 13, 2022 @01:10PM (#29924311)
This applies well for some manuals and poorly for others. When technology changes fast you're likely to read a lot of deprecated stuff. It's an unfortunate state of affairs we find ourselves in.
Re:5.5 mm in 1.25 nanoseconds by thereddaikon on Friday January 14, 2022 @04:09PM (#29940478)
It doesn't even have to move fast. There are plenty of vendors who are just awful at their documentation even when given all the time in the world.
Re:5.5 mm in 1.25 nanoseconds by ehnto on Thursday January 13, 2022 @10:51PM (#29930410)
I think it is my fault, I misunderstood that the GP meant RTFM where available essentially. Though I think it's still relevant, as what is clear to me now is that a lot of us are working with tech that has no true manual, just reference docs, which is a poor substitute for a real user manual.

My argument was essentially that you gain very little from memorizing reference docs. Reading a good manual is definitely invaluable on the other hand.

Re:5.5 mm in 1.25 nanoseconds by thereddaikon on Friday January 14, 2022 @04:08PM (#29940452)
That is sadly the case. So much documentation is incomplete or out of date to the point of uselessness.
Re:5.5 mm in 1.25 nanoseconds by ehnto on Thursday January 13, 2022 @09:37PM (#29929982)
I am not sure why you were downvoted, this is a fairly common response to real world work. There is so much to know, and as systems get more abstracted working in the industry typically requires breadth not depth.

Is that good? Honestly I don't think so, it would be nice to be able to spend more time mastering a stack and using that, and I feel like the outcomes would be infinitely better than jumping ship every 12 months. But that is the reality of parts of the industry, it moves fast.

Re:5.5 mm in 1.25 nanoseconds by im3w1l on Thursday January 13, 2022 @10:47AM (#29921975)
Memorizing facts is necessary to make them accessible to your critical thinking and problem solving though.

Like it's much easier to find a connection between two things you know about compared to two things you could look up.

Re:5.5 mm in 1.25 nanoseconds by kryogen1c on Thursday January 13, 2022 @11:00AM (#29922161)
> I think rote memorization is less useful in engineering than critical thinking/problem solving

i think this is exactly the right take in entirely the wrong direction.

proficiency and mastery are about committing more and more complex things into sub- or un- concious action; muscle memory as it were. grandmaster chess players dont think about solving puzzles that stump novices, they absorb whole board states and many/all permutations instantly. BJJ black belts dont have to think about arm bars, they anticipate complex possibilities of moves and countermoves that a novice simply cannot fathom. this is as true in engineering as any other field. a simple litmus test: is there a difference between a college grad and a 40-years experienced engineer? of course there is

I think GPs point is exactly right. there is a certain lost magic to simply smashing your brain into something and absorbing as much as possible. big eyes, big ears, ego to attempt but humble to fail. one might call such a person a hacker.

edit: see The Art of Learning, Waitzkin

https://www.amazon.com/gp/aw/d/0743277465/

Re:5.5 mm in 1.25 nanoseconds by ehnto on Thursday January 13, 2022 @11:07PM (#29930486)
I have pretty much the same outlook as you have described, so it's notable that we disagree at least a bit on this point of memorization. I think this is my fault as I misunderstood the GP a bit in my reply. But I would suggest in some ways that practice is different to memorization in some interesting ways. Memorizing a manual on motorcycle riding wouldn't make you a good rider if you have never ridden a bike, and you can become a better rider without it, but it would prepare you for the topics involved and you would likely be far more effective at absorbing the learning from the practice having read the manual.

In other instances memorization is a foundational requirement, like language learning. Can't leanr a word if you don't know the alphabet, for example. In that sense practice only serves to reinforce the memorization it is the memory that is most important to being effective in that case.

Re:5.5 mm in 1.25 nanoseconds by bostonsre on Thursday January 13, 2022 @09:38AM (#29921165)
I think it depends alot on your rate of digestion (or understanding? can't find the right word...) of a piece of material. Being dropped in an alien book can make it tough to grasp everything on first pass. If you already have a lot of knowledge that links to the topics being discussed it is a lot easier to grok it in one pass.
Re:5.5 mm in 1.25 nanoseconds by foobarian on Thursday January 13, 2022 @10:59AM (#29922144)
Specifically for CPU manuals, detailed reading used to pay off especially back when every cycle counted. You would spend days rereading tucked away sections describing some weird extension or edge case hoping to harness it for your game/program and get more speed out of it.