The mistake everyone makes with programming books

I don't know about you, but I don't casually read a study book for, let's say, biology. But yet when it comes to programming books, we tend to expect to just read them like we do with fiction books. Maybe, we shouldn't?.. ==== Chapters 0:00 Why other books are easier to read? 1:31 Are technical books study books? 3:02 Case study: Understanding Distributed Systems 5:01 The general approach 6:03 The questions method 8:45 How to lower the frustration? ==== Stuff I'm using: Monitor: LG 40WP95C-W 40” UltraWide Curved https://amzn.to/4rZOy7H Keyboard: Nuphy Air75 https://nuphy.com/products/air75-v2?s... Camera body: Sony a7iv https://amzn.to/4v6aEZ0 My favorite lens: Sony 20mm f1.8 G https://amzn.to/481TRfw Second camera: DIJ osmo nano https://amzn.to/4sMK6KA (all links are affiliate. supposedly. They don't change anything for you, but I get a tiny payback from the store for helping you find things) ==== You can find me here: Instagram   / simpikkle   Patreon   / lifemeetscode   Newsletter https://substack.com/@lifemeetscode