What Programming Book Should I Read Next?

[Rikki Cattermole via Digitalmars-d]

On 29/07/2014 1:18 p.m., Jonathan M Davis wrote:
> On Monday, 28 July 2014 at 14:22:01 UTC, David Gileadi wrote:
>> On 7/26/14, 4:26 PM, H. S. Teoh via Digitalmars-d wrote:
>>> On Sat, Jul 26, 2014 at 04:23:23PM -0700, Walter Bright via
>>> Digitalmars-d wrote:
>>>> http://www.reddit.com/r/programming/comments/2bt8a5/what_programming_book_should_i_read_next/
>>>>
>>>>
>>>> Ali's book is the latest, so I posted that one!
>>>
>>> What about TDPL? Even though it's somewhat dated, it *was* what finally
>>> drove me to non-trivial programming in D.
>>
>> I am, alas, still a D dabbler, but I'm a huge fan of Andrei's book.
>> It's not just the fantastic content, it's also the engaging style. I
>> like it so well that I read it once in a while just for enjoyment.
>
> Honestly, what I like the most about TDPL is that it assumes that you
> already know how to program. It's not out to teach you how to program.
> It's out to teach you how to program in D. That was _incredibly_
> refreshing to me. I can understand why so many language primers assume
> that you don't know much about how to program in any language, but I
> find it incredibly frustrating that they do that, and it makes it that
> much harder for me to get myself to read them - and I'm the kind of guy
> who likes to read the whole instruction manual before doing anything.
>
> - Jonathan M Davis

I'm similar with how I learn programming languages, except I drown 
myself in the language almost quite literally. Lets do the most complex 
task first! Like setting up build management and get packages installed. 
Then go read the documentation and specifications.

Hence I love a 'getting started' guide for all the common things. From 
here's a commonly used industry standard IDE, this is our build manager 
to here's a PDF which is our specifications!

We're really missing that getting started guide. Everything else is 
slowly getting there.