We skim websites/articles because there is so much information out there, and not all of it is useful. I skim articles and then go back to fully read them once I make sure they’re actually worth the time. Same with some books, but books generally are worth it since they went through the publishing process, etc.
A book that definitely wasn't in the category I described above (for me) was John Ousterhout's Philosophy of Software Design - https://www.amazon.com/Philosophy-Software-Design-John-Ouste... . I haven't run into software design/tech books like that very often.
Many books belabor the point and take a chapter to explain what a paragraph could.
It might sometimes be useful - for example, to explain a scenario to a newbie who can't relate from their own experience - but for someone who's been in the industry for a while, most of that information is just not useful.
Trying to pick up a book about a new programming language that is trying to explain the concept of an 'array' or whatever is annoying--I wish there was something to just lay out (still in a thoughtful and guided way) the concepts I needed to understand for that language based on already knowing several others.
This style is popular nowdays and finding books that succintcly describes a subject is hard. This is mostly because you need to have common ground, and writing for the smallest common denominator is better.
I set a single New Years Resolution goal to build this muscle: 12 books in this year. I’ve read 22 now.
What compels me to keep reading is the Reading Insights Streak feature in Kindle. It’s like a little reminder I can always check on to see if I’ve read today or not.
Schopenhauer’s essay “On Reading” is instructive here. He recommends reading fewer books but going deeper into them.
The a builds on b builds on c style of learning is only one way of learning things, and in many cases, the foundations (a, b) serve you no real value.
Just jump to the sections that interest you (c) and go back to previous sections if you feel like you’ve lost track of what they’re talking about.
For example, the first 20 pages of ‘Remote’ cover why remote working is good. It is intended for people who are considering if remote working is suitable. If that’s not relevant to you, do not waste your time reading it.
Of course, you still have to actually sit and read the chapters that interest you… but, if you struggle with that for the chapters you’re actually interested in perhaps a more project based (do a thing, use references from book) approach, or notes based (treat book as study text, rewrite it as your own notes) might work for you.
…but, don’t feel bad. These are super boring ass books with a few interesting parts to them.
Often, it’s some variant of starting with studying the table of contents then doing a fast first pass of the text. That’s usually a pretty good way of figuring out where to start.
Does that mean reading it end to end?
No issues doing the actual programming, could sit for hours on end without any issues.
One nifty thing about my ADHD is that something that was super interesting can become dull as hell. For no apparent reason.
Issues with focus, staying on task and motivation are generic issues that everyone has. Just like everyone gets sad or down sometimes. When it becomes a constant problem that affects your life, that's when it becomes a depression and needs treatment. ADHD is similar, except that it doesn't really come and go but is more of an undulating constant.
w.r.t. books on programming - I've found that ones that offer a hands on project really aid in staying engaged with it. That's usually enough to give you a solid primer on a topic, where other literature starts to become a bit more accessible/less of a drag/less overwhelmed with unknown terminology
On my phone I've read 250k word books cover to cover, same books I could never read on a PC. Attention is weird like that.
Another trick is getting your dopamine* externally. There's an association between ADHD and substance abuse, and I can see why. Pharmacology is a cheat code: a few hours of infinite motivation, will power, and attention.
Unfortunately, when people start needing a substance just to feel normal, that is the definition of an addiction.
(* More complicated than just Dopamine or Serotonin, both seem to play a role. Medecine has not solved this one yet.)
Disagree. What is 'normal'?
A better definition for addiction is the brain no longer produces the neurotransmitter without the presence of the drug (or is doing so at a highly diminished rate). There's no evidence that such occurs with the amounts prescribed for adhd.
For that matter, people needing an external source of a substance to feel normal is unavoidably part of being an organism. We need water, or we wont feel normal. We need vitamins -- and plenty of people have vitamin deficiencies, are they addicted to said vitamins?
If they would otherwise not feel normal and there are no negative side effects, is that a problem?
Negative side effects of note with usual ADHD medication (amphetamine salts) include increased cardiovascular load, development of a tolerance (you need higher doses to achieve the same effect). Sometimes amphetamines induce small changes in personality, rarely full blown psychosis (this has happened at therapeutic doses!).
In general you should apply the same sort of risk-benefit analysis we use for every other drug. If you don't experience any side effects so strong you want to stop, and you believe you're aware of the risks, great.
If you're taking them without a script, I'd advise you to find a steady-state dose that works for you and stick to it. Don't let yourself increase the frequency or the dose without a conscious decision. That's how many people have spiraled.
Finally, I think it's important to have a lot of respect for psychoactive chemicals. Nature doesn't care very much for human overconfidence. If you start being careless, chemistry will do what chemistry does.
I'm a prescription-attention-drugs person and specified drugs do not exist.
I use one of them, and it has been a great help for me for studying and for work. I don't take them during "off-time", i.e., weekends and holidays, and I don't feel like I need them for my hobbies, where part of what makes it fun for me is that I can take my time, shift my focus constantly, and define "progress" by my own internal metrics.
I don't know how to evaluate the risk, basically. Medical stuff tends to have a lot of noise.
But also, every body and mind are different. Consult a specialist. There's many different types of ADHD medication out there now.
If you can't read books, then you are missing out on a lot. It's important to be able to read books (and work through large portions of them). Start reading books by reading fiction, then transition into nonfiction books (that are closer to fiction at first, e.g., history), finally transitioning into long-form technical books. If your budget permits, buy a long-form book on a technical topic and commit to reading it instead of just jumping on a website. For example, if you want to learn Kubernetes, just buy the Kubernetes book written by Beda et. al. I doubt any website will be better than that, and you will spend perhaps a week or two on a shallow read of the book, but you'll have found that you have a much better appreciation of the subject matter than you would have had you just glanced at a few website articles.
When I was a kid, I read books by the meter, regular at the local library. At age 35, after life happened and after I was immersed in quick internet articles, I realised I haven't finished a book in ages. Which made me slowly read more, having that extra page after "mental exhaustion", slowly working my way up to a while chapter ... trying to get back into the habit.
Now at age 41, I read long stuff again - best decision I've made. But I am under no illusion that I won't fall back into bit-sized consumption if I would stop keeping it up.
I love reading literature though. Hours, engrossed.
This might just be me. Tech is just a means to pay the bills for me - there’s no passion, hatred, love involved here.
Pragmatic Programmer for example could be thought of as a very curated list of blog articles. Great book, but also not intimidating or deeply technical in that sense.
The content may not be super relevant immediately, but the book and (really simple) methodology of taking notes on these readings and graphing relationships between concepts means you're slowly building a network of knowledge that grows and becomes more powerful over time.
I used to but now it feels like a fun game to me.
My example is from the Windows Internals books, it’s a great book, but I don’t think the authors could write it in a “gripping” way, that’s just technical books.
What I do however be it books or video is chunks, takes MUCH longer to do but I find for me it sticks, so if in my learning season (I do bursts of learning, burn out leave it for a couple of months, rinse repeat),
- Read a section or chapter - Make quick, rapid notes in my notes app (or notebook, I use bear but whatever suits yourself) - Once I’ve done, go to sleep (I normally study at night, my brains more in a learning mode then for me) - Maybe at dinner time (at work) I go through my notes, if it’s something I feel may benefit my colleagues I make a brief PowerPoint, I try to translate it into a less technical write up, not everyone is super technical, it’s just a job to them!.
I have a terrible memory for learning, I remember things long term great, short term not so much, so I reference my notes a lot, it’s essentially my mind map/bank.
Video learning is very subjective, I’m currently learning Cisco Umbrella and it’s very boring to me, the creators voice is very mono tone and boring to the point I’ve nearly fallen asleep, but other creators (mostly in the Microsoft MVP zone) are very lively, a good mix of demos and theory that keep me engaged and actively want to learn, Pluralsight is the same, keeps me awake and motivated, I found CBT a little on the boring side in comparison.
Minimum means that I need to finish it that day no matter what.
I put a maximum because I found through trial and error that if I push myself too hard, even if a topic is interesting, I burn out quickly and procrastinate, sometimes for months, before continuing reading said book. And that is worst case scenario for me.
What helped me to go back on track was reading novels and constantly asking myself: did I understand the last sentences that I've just read?
No, your brain just tricked you. It trained you into thinking that you're doing rapid research of useful info, while it just looks for path of least resistence.
On the other hand, I taught myself electronics and programming from a combination of books and just trying things. Maybe trying things is a different kind of classroom in a sense. Certainly a different teacher: Mother Nature, who takes no crap from cocky teenagers.
As for having trouble reading difficuly texts try this - read two pages. Try to recall what you read. Then try to connect it with what you already know. You only need to do it for the fundamentals not every sentence and it will help build up flow.
I cannot just sit and listen without doing anything, I need to be doing something with my body to be able to stay focus on an audio feed. I mean, I can do it but I won't be able to keep my attention on the audio content. When I bike, walk, or do laundry, no problem at all!
The only exception was a Linux kernel podcast but the format was really unsuitable for the topic.
Do you have any good technical podcast to recommend?
"Algorithms + Data structures = programs": https://adspthepodcast.com/
Crypto Critics' Corner may be my favorite podcast: https://cryptocriticscorner.com/
Anything from microbe.tv: https://www.microbe.tv/science-shows/. They have podcasts covering evolution, microbiology, neuroscience, parasitism, virology, urban agriculture, and more. Lot of stuff to dig into, you can try and see which one you like.
Not technical, but I like to listen to Startup Therapy, I like how they openly talk about failures and mistakes: https://adspthepodcast.com/
Someone once recommended me to start at the back of each chapter and do the the problems and only read the chapter or even parts of the chapter for problems I couldn’t solve.
It comes with its own set of drawbacks but it does help with getting through text books where the author was paid by per letter.
For the really good books you’ll actually reach the end.
It's not that I don't comprehend, it's that my brain finds it boring and hard to focus. I think I have trained my brain so much on rapid skimming of websites for useful info, while throwing away most of the content, that I tend to do the same with books, which really doesn't work well.
Has anyone found alternative ways to consume this information for brains that work like mine?