My work gives us a learning budget so I have a crap-ton of books all at once and I’m wondering what would be the most effective order to read them in. I estimate each book will take me at least a month to read, maybe more, since I like to take copious notes and really digest the info.
I have about 13 years of professional experience, entirely in web applications on the front-side of things, with some minor backend experience (although most of the books are more generalized). I’ve been told my code is fairly well organized, but I’d like to get better at planning/completing story work efficiently as well as understanding whole systems.
The books are:
- The Pragmatic Programmer (Thomas/Hunt)
- Designing Data-intensive Applications (Kleppmann)
- The Mythical Man-Month (Brooks)
- Code (Petzold)
- Clean Code (Martin)
- Refactoring (Fowler)
- Understanding Distributed Systems (Vitillo)
I’ll get through them all eventually, but I’m leaning towards backloading the system design ones (and maybe MMM) since I don’t do much related to SD on a daily basis (I have an ok understanding of why things are chosen at a high-level, but my knowledge is not very detailed at all). Thoughts?
submitted by /u/PabloEscribir
[link] [comments]
r/cscareerquestions My work gives us a learning budget so I have a crap-ton of books all at once and I’m wondering what would be the most effective order to read them in. I estimate each book will take me at least a month to read, maybe more, since I like to take copious notes and really digest the info. I have about 13 years of professional experience, entirely in web applications on the front-side of things, with some minor backend experience (although most of the books are more generalized). I’ve been told my code is fairly well organized, but I’d like to get better at planning/completing story work efficiently as well as understanding whole systems. The books are: The Pragmatic Programmer (Thomas/Hunt) Designing Data-intensive Applications (Kleppmann) The Mythical Man-Month (Brooks) Code (Petzold) Clean Code (Martin) Refactoring (Fowler) Understanding Distributed Systems (Vitillo) I’ll get through them all eventually, but I’m leaning towards backloading the system design ones (and maybe MMM) since I don’t do much related to SD on a daily basis (I have an ok understanding of why things are chosen at a high-level, but my knowledge is not very detailed at all). Thoughts? submitted by /u/PabloEscribir [link] [comments]
My work gives us a learning budget so I have a crap-ton of books all at once and I’m wondering what would be the most effective order to read them in. I estimate each book will take me at least a month to read, maybe more, since I like to take copious notes and really digest the info.
I have about 13 years of professional experience, entirely in web applications on the front-side of things, with some minor backend experience (although most of the books are more generalized). I’ve been told my code is fairly well organized, but I’d like to get better at planning/completing story work efficiently as well as understanding whole systems.
The books are:
- The Pragmatic Programmer (Thomas/Hunt)
- Designing Data-intensive Applications (Kleppmann)
- The Mythical Man-Month (Brooks)
- Code (Petzold)
- Clean Code (Martin)
- Refactoring (Fowler)
- Understanding Distributed Systems (Vitillo)
I’ll get through them all eventually, but I’m leaning towards backloading the system design ones (and maybe MMM) since I don’t do much related to SD on a daily basis (I have an ok understanding of why things are chosen at a high-level, but my knowledge is not very detailed at all). Thoughts?
submitted by /u/PabloEscribir
[link] [comments]