Software Mistakes and Tradeoffs (1 ed)

Software Mistakes and Tradeoffs: How to make good programming decisions 1st Edition

Optimize the decisions that define your code by exploring the common mistakes and intentional tradeoffs made by expert developers.

In Software Mistakes and Tradeoffs, you will learn how to:

• Reason about your systems to make intuitive and better design decisions
• Understand consequences and how to balance tradeoffs
• Pick the right library for your problem
• Thoroughly analyze all of your service’s dependencies
• Understand delivery semantics and how they influence distributed architecture
• Design and execute performance tests to detect code hot paths and validate a system’s SLA
• Detect and optimize hot paths in your code to focus optimization efforts on root causes
• Decide on a suitable data model for date/time handling to avoid common (but subtle) mistakes
• Reason about compatibility and versioning to prevent unexpected problems for API clients
• Understand tight/loose coupling and how it influences the coordination of work between teams
• Clarify requirements until they are precise, easily implemented, and easily tested
• Optimize your APIs for a friendly user experience

Code performance versus simplicity. Delivery speed versus duplication. Flexibility versus maintainability—every decision you make in software engineering involves balancing tradeoffs. In Software Mistakes and Tradeoffs, you’ll learn from costly mistakes that Tomasz Lelek and Jon Skeet have encountered over their impressive careers. You’ll explore real-world scenarios where poor understanding of tradeoffs leads to major problems down the road, so you can pre-empt your own mistakes with a more thoughtful approach to decision making.

Learn how code duplication impacts the coupling and evolution speed of your systems, and how simple-sounding requirements can have hidden nuances with respect to date and time information. Discover how to efficiently narrow your optimization scope according to the 80/20 Pareto principle, and ensure consistency in your distributed systems. You’ll soon have built up the kind of knowledge base that only comes from years of experience.