Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Quirinus85939dThis is satisfying to read. 😊
ed-dev-edu4539dThanks for interesting stories. :)
If I may ask, how many years of experience do you have? :)
AvyChanna59338dHow the fuck did that n! program even work. You cant even run it for 100 values
RANTSMCPANTS36037d@AvyChanna There's a sad story to that. After making it super fast compared to before I was eventually given a real version of the upstream API to submit data to.
Before I only has a WSDL file and a ticket open that it was too slow with a spec telling me it should work with a lot of items added.
It was a case of having to run it on the front end as front end validation to show the user before confirming and submitting.
It turns out the upstream API in practice had a bunch of limits, such as a 500 permutation limit.
Eventually we ended up working with another API system doing the same but another vendor and that would do some stupid things like expand every list into every possible permutation in the database then sending a webhook on every update.
I gave them some algorithms and specs so they should have been able to reduce their servers by an order of magnitude or two while saving around three or four on callback bandwidth.