I can't read books because I lose interest after the first couple of chapters. How do programmers do it? There’s noway you read a 1000 page book on CMake or Modern Operating Systems and remember it all…
Did you study Computer Science in college?
Anyway, I didn't studied Computer Science. I majored Electronics and Automation Engineering, but I did take one CS-core course, which was about Digital Systems and Computer Architecture, where I had to learn how to design a micropressor starting all the way from logic gates.I know Tanenbaum wrote another book on Operating Systems which is about programming an operating system from scratch (the same one that Linus Torvalds used when he came up with the earliest version of Linux, as far as I remember), so I guess you could just go through some online course materials on that subject and build a tiny OS as a personal project so you learn how OSes work.
>>24911372>micropressor*microprocessor
I study by relentlessly breaking things until I figure it out and I do that dozens of times. It's the only way. I won't read shit, I won't watch shit.
>>24911249amphetamines
>>24911249i use text to speech with PDF's and read/follow along as well as pause to look things upeven with having severe ADHD this really helps mehere's your bookhttps://files.catbox.moe/2zqbux.pdfalso, studying networking and sys admin worked out career wise for me
>>24911249>read a 1000 page book on CMake and remember it all…kek, as ifthe book should serve as a reference; you learn far more by actually doingyou absolutely do not need to learn all of the byzantine intricacies of CMake to make good use of itfrankly, you'd have to be deranged to *want* to do thatand when you do encounter a situation where you want CMake to do something you DON'T know how to make it do already, your first approach should be taking the question to a search engine; then discussing with a friend, or colleague, or even an AI; and only THEN I would check the booktake something like Vulkan - I have many books on it, but it's an ever-evolving standard, and the way that the spec might say to do XYZ is typically excessively verbose, and generally not how I would actually do it in practice given the existence of extensions which mean I don't *have* to do it that way in practice, so I don't, because I'm lazy - and all good programmers are lazy, that's the whole point of programmingI doubt I know even 1% of the C++ Standard Library - I know what I use, and occasionally I might read around and learn something new, and have a play with it, but I don't have to learn ALL of it before I can make use of ANY of ityou're holding yourself to an impossible standardjust make something work for you, and when you have a working knowledge of the topic or area you're dealing with, then you can start researching and reasoning better ways - even optimal waysbut just start with 'whatever works'a mentor once said to me:>if it works, it's not bad code
>>24911249Computer science is interesting to me so I read books about it. It didn't feel like work for the most part.Also after a certain point you can just start reading the reference manual and then you don't have to read the whole thing, you just look back to it when you need it.
>>24911542>text to speech with PDF'sInteresting, i’ll try this in Chromium or Firefox as I have the PDF open.
