3 ms·
this looks like it's describing the typical java horror where you have to make a generic interface to every single dependency to pretend you might be able to sw
by lexicality 2y ago
this looks like it's describing the typical java horror where you have to make a generic interface to every single dependency to pretend you might be able to swap them out at some point and then you drown in a sea of interfaces and indirection trying to abstract everything into purity
please just write plain code that's easy to follow, easy to debug and easy to delete!
you don't need the survivability onion
- seanhunter 2y agoYes exactly. Anyone who has worked on big java codebases has at least one horror story where there are 10s or 100s of classes each with "use once" interfaces wrapping them and there are bizarre consequences like for example, there is only one possible way to wire the application up but for "flexibility" you have to go through (and occasionally debug) a spring boot nightmare for some reason anyway because somebody read a blog post on dependency injection and thought that was a good idea.