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
-
Only vape reason (although one can usually avoid it) is even an object implements two interfaces. The API requires a param for each interface. Ah the same object is presented twice.
Most of the time I've seen doc like that it's premature optimization (interfaces should not have been split) or huge class syndrome.
Pretty sure someone already posted it here, but I don't have the patience to check. Just want to share it.
So...
messy backend API. root level payload object has a property that is being repeated in a property that takes an array of objects where this same property exists in each object in this array.
why do people work in a messy manner like this? why pass the same data twice in the exact same request?
(lead architect is smart, but holy fuck is his work a goddamn mess of technical debt and hurts my brain and productivity)
rant
messy code