Boost Delivery Stream with Code Discipline Engineering
summary
Claim that disciplined code habits speed delivery and cut cloud waste by using concrete Java features and small fixes: adopt Java 21 switch pattern matching and records for simpler factories/builders, add targeted caching and use Java Flight Recorder for visual bottlenecks, apply a one-line autoboxing fix that dramatically reduces GC churn, and track impact against studies showing 57% effective engineering time and ~$300B annual cost (2018) from bad code.
AI-written summary · about
chapters (7)
- 0:00Introduction and motivation
- 3:58Code discipline engineering explained
- 9:45Understanding anti-patterns and their cost
- 15:24Java 21 features and functional paradigms
- 21:50Solid principles and maintainable code
- 26:12Concurrency and structural patterns
- 34:49Conclusion and benefits of discipline
related talks
41mUsing Boundary-Driven Development to beat code complexity
40mDesigning Function Families and Bundles with Java's Behaviours Parameterization and Lambdas
01h 26mChaos Development: Removing Software as the Inhibitor of Agile
40mDeveloping at Cruise Speed
36mDesign Develop Deploy!
10mBeyond “try harder”: Effective strategies to tackle bugs
54mBreaking Down Your Build: Architectural Patterns For A More Efficient Pipeline
53m5 ways to improve your Java EE applications in reactive way