I try to keep the same name/idenity-ish across systems. It was originally a collision of names (three people on the team all had the same first name). One got the short form, one the long form, and the Scoobie Do movie had just come out and for some reason, I got "Shaggy". A bit later, had a coworker who was Japanese and my first name is awkward to say to the Japanese sounds, but "shaggy" is fine - except that it was pronounced as "SHA-gie" which turned out to be much less taken as a user name than the traditional form, so I use it where I can.

That order also had Slack and Peopleware by Tom DeMarco (which I'll also recommend).

These are things that are timeless (though Peopleware is on a 3rd edition).

Death marches are often software projects, but I've seen some lawyers on a "death march" case where its dragging on and on.

The ideas of Slack are applicable to every job - though especially those of knowledge workers (the book is likely as good for building architects as it is for software developers). Similar things about productivity and desk space are also true for architects and software developers.

They're good books and interesting things to read... but they're not books about software development as software.