2 ms·
A lot of the most annoying and time-consuming abstractions at my company are, ironically, geared towards maintainability/extendability concerns. We have wrappe
by plaguuuuuu 10y ago
A lot of the most annoying and time-consuming abstractions at my company are, ironically, geared towards maintainability/extendability concerns.
We have wrappers around generic web service callers that rely on factories that create classes that convert between web service objects and domain objects, all wired together using interfaces for each service class and an IoC container, with its own XML configuration file.
The irony is that if the web service were to change its interface, you'd have to change like 10 files instead of like.. a single conversion function somewhere. And to begin with you had to create those 10 files in the first place. It's absolute fucking madness.
- Chris_Newton 10y agoThat looks like a great (that is, horrifying) example of the problem where the extra complexity introduced by the abstractions is actually greater than any complexity they successfully hide. It’s frightening how often this happens at all scales, from little utility functions with names that are several times as long as their implementations right up to the kind of enterprise architecture that nightmares are made of.