Reading List

Books

Development

• The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business
• Microservices Patterns
• Release It!
• REST in Practice
• Secure by Design
• Working Effectively with Legacy Code

Personal Development

• Deep Work: Rules for Focused Success in a Distracted World
• Essentialism: The Disciplined Pursuit of Less
• Finish: Give Yourself the Gift of Done
• Getting Things Done: The Art of Stress-Free Productivity
• Starting Strength
• Quiet: The Power of Introverts in a World That Can’t Stop Talking

Leadership

• Boundaries
• The Five Dysfunctions of a Team: A Leadership Fable
• EntreLeadership
• Getting to Yes
• Good to Great
• How to Win Friends & Influence People
• Integrity
• Radical Candor
• Turn the Ship Around!: A True Story of Turning Followers into Leaders
• Who Moved My Cheese

Blog Posts

• Awesome Falsehood: A curated list of falsehoods programmers believe in
• Be Kind
• Beware SAFe (the Scaled Agile Framework for Enterprise), an Unholy Incarnation of Darkness
  • SAFe is the worst process I’ve had the displeasure of working under
• Best practices for REST API design
• Cargo Cult Software Engineering
• Design a DDD-oriented microservice
• Design by Committee
• The advantage of no funding
• The Fallacy Of ReUse
• FrequencyReducesDifficulty
• The Guerrilla Guide to Interviewing (version 3.0)
• How to Make Your Code Reviewer Fall in Love with You
  • Review your own code first
  • Separate functional and non-functional changes
  • Break up large changelists
• How to Write a Git Commit Message
• How to write great interview feedback
• Microservices: a definition of this new architectural term
  • Built around business capabilities and independently deployable
  • Conway’s Law: Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure.
  • Services organized around business capability
  • A team should own a product over its full lifetime “you build, you run it”.
  • Applications built from microservices aim to be as decoupled and as cohesive as possible
  • Applications need to be designed so that they can tolerate the failure of services
• On Being A Senior Engineer
• Programmer Competency Matrix
• SOLID
  • Think you understand the Single Responsibility Principle?
• Testing Strategies in a Microservice Architecture
• Why you should follow the robustness principle in your APIs
• Understanding write-through, write-around and write-back caching (with Python)

Principles

• Principle of least astonishment
• do what I mean (DWIM)

Java

• Field Dependency Injection Considered Harmful
• Lombok: A Love/Hate Relationship

Videos

• The Art of Speaking: Scott Hanselman

Martin Fowler has a great take on the abbreviation S.A.F.E. in this video. It’s a terrible project management system to work under.

This is one of my favorite talks on refactoring. It changed the way I approach and talk about the refactoring process.

Workflows of Refactoring:

• Litter-Pickup Refactoring
• Comprehension Refactoring
• Preparatory Refactoring
• Planned Refactoring
• Long-Term Refactoring

> Why refactor in the first place, isn’t it wasteful work?