21–30 of 137 posts
I often here comments about finishing a mathematical/technical book over the course of a "few" weekends. But I don't see how thats possible if it includes completing all (or even most of) the given exercises. Especially when you have a full-time job.
I think such books are pointless if you aren't going to use them in your day-to-day work.
I often here comments about finishing a mathematical/technical book over the course of a "few" weekends. But I don't see how thats possible if it includes completing all (or even most of) the given exercises. Especially when you have a full-time job.
Mmm. Besides, I find my programming/work/etc. improves when I read novels in my spare time :)
"I find algorithms to be useful in the same way I find math to be useful"
I'd hope so :)
I often here comments about finishing a mathematical/technical book over the course of a "few" weekends. But I don't see how thats possible if it includes completing all (or even most of) the given exercises. Especially when you have a full-time job.
The idea is good: a list of general topics, a "why should you care" section for each (the part I really liked) and a few specific titles. I would love an expanded list of topics (the current one is short) e.g., compilers, comms, security, Arduinos/ raspberry Pi / IoT. I personally did not like long lists of specific books -- I'd rather know about the topic and browse bookshelves at a Barnes and Noble to pick a couple…
These type of lists have nothing to do with efficient learning. In the information age we have more available information than time. Knowing how to learn is the multiplication factor. If you do your due diligence these lists quickly becomes anecdotal.
We had "Structure and Interpretation of Computer Programs" by Abelson/Sussman when I was at university, which I found a good introductory book. For a more thorough understanding I would recommend Donald Knuth's "The Art of Computer Programming".