Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
heyheni2062767dIs it more work to fix this than redo the api with GraphQL?
heyheni2062767d@vorticalbox could you calculate a cost benefit analysis with a clear path with deadlines, so to convince the higher ups?
"With this measeure we will be meeting our goal x times faster at a x amount of saved hours and cost. It is in line with our company philosophy to encourage innovation. With this technology we are able to innovate and bring products to market faster. Which gives us an edge over our competitors. The potential longterm cost earnings/savings amount to x."
you may want to read up the term "opportunity cost" It will help you sell this thing.
Opportunity cost - Wikipedia
M3m35terJ05h63567dYou can't just convince higher ups you need to rewrite something. Especially if that something is fairly new. You'd be trying to convince them they made a bad decision. Plus, it's very hard for them to get that you can't easily bolt some new features on or patch up something that, as far as they can tell, works fine.
I'm also constantly annoyed that non technical people are instinctively drawn in the opposite direction of the Unix philosophy. They're always trying to sell that one app that does everything you need