Clean Architecture? Clean Code? Refactoring? Tests? What does this change in my code?
summary
Practical rundown of what changes in code: concrete Java and Spring Boot examples show a simplified clean‑architecture microservice with clients/domain/service layers, translators (interface adapters), and repository gateways; clear refactoring triggers: refactor during code review or when adding a feature or fixing a bug and keep behavior identical while extracting methods, replacing magic numbers with constants, moving responsibilities and reducing long parameter lists; testing details cover JUnit/Jupiter unit and integration tests, JSON assertions and WebFlux endpoint checks, plus why tests act as living documentation and when technical debt blocks progress.
AI-written summary · about
chapters (7)
- 0:00Introduction to talk
- 0:32What is clean code?
- 2:19Code smells explained
- 4:56Refactoring fundamentals
- 9:50Unit testing basics
- 13:25Clean architecture overview
- 21:10Conclusion and key takeaways








