4

I work daily on a project, in which, rather than buy in a decent message bus a bunch of half interested, unqualified developers were tasked with hammering together an in-house solution. This monstrosity has around six layers of abstraction, separate objects per project and dynamically loading converters between the components. It's largely not unit testable, certainly not integration testable and has already wasted more money in developer time and Bugfixes than a half decent external solution would have cost.

Every time I have to change an object in one part, start the associated web/win service and do a "update service references" I die a little inside.

There are so many better ways but we'll never be able to change because "there's no time for that"

And all for some up front savings

Comments
Add Comment