I have a bad habit of reading 5 things at once, here's my list of books I'm currently reading:
The Healthy Programmer
I'm loving this book! It's health advice geared specifically toward helping those who sit in chairs most of the day. Rather than trying to give you 6-pack abs, it focuses on making small changes to routines, standing up, taking walks, reducing back and wrist pain, all things that are critical to long-term health for programmers.
The Phoenix Project
An interesting read about the turn-around of a failing IT organization. We're reading it as part of my work book club, and it has a lot of interesting insights on team organization and time management.
User Story Mapping
The key takeaway from this book is that Documentation != Shared Understanding. It focuses on getting team members and leaders into a room together to make sure everyone has a shared vision of what actually matters to make sure you build the right things for the right reasons at the right time.
Clean Architecture
Written by Uncle Bob Martin, this book makes it clear that there are some fundamental architecture principles that lead to maintainable, scalable software that is much less likely to break down over time.
The Pragmatic Programmer 2nd Ed.
Great all-around advice for developers. The new edition makes much more sense to me, as it uses examples with modern technologies and software practices.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have a bad habit of reading 5 things at once, here's my list of books I'm currently reading:
The Healthy Programmer
I'm loving this book! It's health advice geared specifically toward helping those who sit in chairs most of the day. Rather than trying to give you 6-pack abs, it focuses on making small changes to routines, standing up, taking walks, reducing back and wrist pain, all things that are critical to long-term health for programmers.
The Phoenix Project
An interesting read about the turn-around of a failing IT organization. We're reading it as part of my work book club, and it has a lot of interesting insights on team organization and time management.
User Story Mapping
The key takeaway from this book is that Documentation != Shared Understanding. It focuses on getting team members and leaders into a room together to make sure everyone has a shared vision of what actually matters to make sure you build the right things for the right reasons at the right time.
Clean Architecture
Written by Uncle Bob Martin, this book makes it clear that there are some fundamental architecture principles that lead to maintainable, scalable software that is much less likely to break down over time.
The Pragmatic Programmer 2nd Ed.
Great all-around advice for developers. The new edition makes much more sense to me, as it uses examples with modern technologies and software practices.