Books you may want to consider reading
Generally speaking, I love to read books. Particularly I love to read books about Tech, Health, and Economics. These are some of the books I’ve read with some notes for those interested.
The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations
If you read one book about how to deploy and run a software company at scale this should be it.
- Flow of code is important (ABM) always be merging to master
- Test at the system level as well as the unit level
- Work in progress is to be avoided (small frequent releases)
- When the build breaks all developers have one responsiblity (get the build working)
- Quality is not a department, it is a requirement
- Monitor performance and errors so they can be addressed as part of normal dev cycle
- You can’t have agile project management without agile code release
- Developers should have full control of early stage projects in production until they are stable
Great book on object oriented design. Especially useful for ruby developers as most of the examples use ruby.
- Developers can’t know the future, therefore developers preserve flexibility in their code (good design allows isolation of changes)
- Inversion of control and dependency injection help you swap components
- Focus on the messages your objects send and receive
- Strive for single responsiblity