-
2025-01-18 11:33:52
also yes, when i get to ackchually being paid for the task, i'll make a lot more effort
like, even at my current paid job, there's such a small amount of tasks in it that have moderately long times to pass each one i'm hardly even noting what i'm doing
it's a matching engine, and i think there is a slim chance they will be persuaded that i will also build a queue/proxy/cache for their front end so they can stop having 5 second long confirmation waits and push that onto their proxy cluster... and for that i need to also have some kind of distributed database to store the query cache in so it can save on calls to the - eventually expensive, if big userbase - gateway API calls
that's the thing, i know the layout of the architecture better than most of them do, so i just focus on where i am digging for now but i only have to pause a few minutes and i'll vomit out a whole architectural work order plan