Back to Basics: Crafting Quality Software in the Age of Complexity
summary
Shows concrete practices to keep a codebase maintainable: a Quarkus sticker-catalog demo uses Panache, Kafka and OpenTelemetry and reproduces a 102ms end‑to‑end request and 50µs DB call to prove observability value. Recommends static tools (SpotBugs, ErrorProne, Semgrep, CodeQL, Snyk, SonarQube), ArchUnit architecture tests to enforce layering, auto‑instrumentation or OpenTelemetry SDK for traces, and continuous profiling with JFR to catch regressions in production and correlate traces, logs and profiles.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:29Software quality matters
- 6:08Limits of upfront design
- 7:10Static analysis for quality
- 12:09Security as quality
- 15:59Static application security testing
- 20:09Architecture with tests
- 27:51Dynamic analysis & observability
- 35:49Performance as quality
- 41:03Key takeaways
related talks
49mBack to Basics: Crafting Quality Software in the Age of Complexity
40mAssuring top-notch code quality in the Java Universe
14mThinking of Quality as developer productivity tool
30mTest-Driven Development: It's easier than you think!
46mThe Road to Improving Testability
46mFull Court Quality: Lacing Up for Speed, Stability & Style
58mTesting Software Architecture
33mBuilding Code Quality