Stop Learning Frameworks
The author says he bought these books:<p><pre><code>    The Pragmatic Programmer
    Clean Code
    The Clean Coder
    Domain-Driven Design
    Growing Object-Oriented Software, Guided by Tests
    Continuous Delivery
</code></pre>
Not to curb anybody&#x27;s enthusiasm, however these are soft-skill books.<p>I&#x27;ve read The Pragmatic Programmer on a 10 hour flight and I fell asleep 2 or 3 times, because it was freaking boring. Beginners might get some value out of it, but it&#x27;s all common sense stuff that you learn in the first couple of months on the job.<p>Everybody has some of these books in their bookshelf, including other classics such as the Art of Computer Programming. What I find interesting is that few people read these books, either because they are boring (the soft-skill ones) or because they are really hard to follow (AOCP), but keeping such books in your bookshelf is like a rite of passage. You can&#x27;t call yourself a programmer if you don&#x27;t have a couple of programming books in your bookshelf that you&#x27;ve never read :-)<p>To switch from framework learning to soft-skill books doesn&#x27;t feel like much of an upgrade. If you want to learn something with long lasting value, learn actual <i>computer science</i>.<p>This means algorithms and math.<p>It also means exposure to paradigms like functional programming, or logic programming. I recommend Haskell, not because you need to learn yet another language, but because the knowledge ceiling in its ecosystem is really high and it&#x27;s the current lingua franca for papers on functional programming.<p>Also some technologies are longer lasting than others. POSIX for example is still with us. The architecture of CPUs has evolved, but the basics of how a CPU processes instructions and accesses memory are the same. Frameworks and libraries come and go, but the fundamentals of concurrency, parallelism, asynchrony remain the same. Etc.