Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@PaperTrail ... Oh. No...
-
There wasn’t much justification, though I think the underlying one was deduplication.
Missing the point though as the micro services should be independent.
Now we have spent two weeks updating them all because someone wanted 2 new properties on a couple of types. It’s ridiculous.
I keep raising that the amount of work caused by this small change is unreasonable, but the architect doubles down on how necessary it is.
Got a nice solution, part of a micro-services system. Interfaces where they should be. Single responsibilities. Easily unit testable (and plenty of tests in there).
Then the Senior rewrites things because he didn’t see the point in having interfaces and couples every layer to a shared set of objects, and those objects are now shared by all the other micro-services too. One change in one and we have to repeat it in every service. 🤦♂️
rant
wk216