What Programming Book Should I Read Next?

[Peter Alexander via Digitalmars-d]

On Saturday, 26 July 2014 at 23:42:33 UTC, Adam D. Ruppe wrote:
> Maybe this is arrogant or whatever, but my view is that I'm 
> kinda maxed out as a programmer. Sure, there's a handful of 
> specific things (like framework method names) I don't know and 
> some concepts I don't know the names of, but as for like 
> revolutionary new lessons, I don't think I've actually learned 
> anything like that directly related to programming for a pretty 
> long time.

I suppose it depends on what "related to programming" means. I 
presume you, like everyone else, could not write a general 
purpose AI, so we all still have that to learn. I'm guessing 
you'd classify that as more of an application rather than being 
directly related to programming?

The applications are where most of the fun is. There's so many 
algorithms, concepts, and theories to learn. I don't think I'll 
ever stop. Even with things directly-related-to-programming, 
there's lots for me to learn. I know very little about all the 
Haskell-level category theory stuff, and I really should spend 
some time to play with things like Forth to see what all the fuss 
is about there. I'm sure there are still many gems to discover.