The Hexagonal Hangover
The Hexagonal Hangover by Ties van de Ven
Room 8 · Conference · 13:50-14:40
Summary
Section titled “Summary”The talk critiques dogmatic use of Clean and Hexagonal Architecture, arguing that unnecessary abstraction can hurt code clarity and maintainability. Using Java examples, it explores trade-offs and decision metrics—coupling, cohesion, and distance—to help choose architecture based on context rather than universal “best practices.”
Timeline
Section titled “Timeline”- Bogen van Corp[?]
- Mental Model
- it Depend
- everithing is a thrade oPP
- Fruil-tella
- Barillere[?] have a purpose
- But hard to arrive ot[?] to the candy
- go will Alays Depend ou Something
- every win has a downside
- story time[?]
- Distance
- Copling
- Which component is more Allowed to change other component
