We all know the guidelines - hexagons, TDD, DDD, event storming, event sourcing, SOLID, YAGNI, KISS, etc. We know frameworks that say to save our time to let us focus on "domain business" alternatively of configuration or method aspects. We survey architectures, patterns and anti-patterns. We know well-known books, courses and their celebrated authors. However, haven't we gone besides far? Don't we take a sledgehammer to crack a nut? How many times do we choose between a clean or fast code? Is there any definition of "good code" at all? Let's effort to discuss the case with a case survey of a simple application created multiple times utilizing different approaches for the same business requirements.
Website: https://jdd.org.pl
Facebook: https://www.facebook.com/JDDconf
Twitter: https://twitter.com/JDD_Krakow
