3 ms·

I googled the name of this book and for me your post on Reddit about it four years ago (I assume it's you due to the similar username). Guess it hasn't gotten a

I googled the name of this book and for me your post on Reddit about it four years ago (I assume it's you due to the similar username). Guess it hasn't gotten anymore out of date. I'll have to look into a getting a copy.

shagie 4y ago
Assuming its the same post as I found when searching, that's me... https://www.reddit.com/r/cscareerquestions/comments/9ymkmg/how_do_i_get_out_of_a_death_march_project/ https://www.reddit.com/r/cscareerquestions/comments/9ymkmg/h... you'll also see the same date too. The order itself - https://imgur.com/TkDmLPv https://imgur.com/TkDmLPv 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).
- MivLives 4y ago
  Yup that's the post. Thanks for the recs! Been trying to learn more as I come from a nonCS background.
  - shagie 4y ago
    These books are about time management, project management, culture, workspaces... and reasonably applicable to all domains - not just software development. 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.

shagie 4y ago

Assuming its the same post as I found when searching, that's me... https://www.reddit.com/r/cscareerquestions/comments/9ymkmg/how_do_i_get_out_of_a_death_march_project/ https://www.reddit.com/r/cscareerquestions/comments/9ymkmg/h... you'll also see the same date too. The order itself - https://imgur.com/TkDmLPv https://imgur.com/TkDmLPv 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).

MivLives 4y ago
Yup that's the post. Thanks for the recs! Been trying to learn more as I come from a nonCS background.
- shagie 4y ago
  These books are about time management, project management, culture, workspaces... and reasonably applicable to all domains - not just software development. 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.