Lately I've had a bit of a renaissance in my intake of software development literature. I've been taking the time to read the canonical source of concepts which I'd previously consumed through distillation.
The "distillation" process is extremely important. It's vital for the industry that ideas spread naturally, get mixed around and presented in different ways for different use cases. This is the purpose of a lot of posts on dev.to. I could never take the time to read the papers or books which inspire the great posts I read on a daily basis. But it is very worth getting to it eventually.
It can be discouraging to read materials that are above your understanding in a topic. I think it's perfectly reasonable to skip over the source material and gain the wisdom in bits and pieces as you go. But once you're reasonably comfortable with the concepts, going back and reading the deeper take or the original reference material is an incredibly illuminating activity.
Some people can just pick up a paper or book and read it for its value whenever they feel like it. Many others really need to proper headspace to find the material valuable. The pattern of consuming the byte-sized chunks and following up eventually with the deeper source material has been wonderful for me. Lengthier (or dryer) reads are a tough way to get introduced to a topic for me, but a great way to extend knowledge once I'm comfortable.
I'm writing this post because for a while it didn't occur to me to read books on subjects I was already comfortable with. If you don't read a lot of software books or papers, I suggest seeking out materials that do not introduce you to new subjects but instead help enrich concepts that you've been exposed to here and there for a while.