Our CI is down and we can't deploy because...
AWS on the East Coast is over capacity and just kills our instances
Last time I said it would just be easier and cheaper to buy a threadripper and put it somewhere, I met significant disagreement. Ah welp...
AWS on the East Coast is over capacity and just kills our instances
Last time I said it would just be easier and cheaper to buy a threadripper and put it somewhere, I met significant disagreement. Ah welp...
I mean, the amount of downtime for our team today alone is enough to pay for half of that threadripper.
@newt Peter principle perhaps
though I no longer freak out about the amount of parasites out there, and the resources wasted due to them, I'm just trying to take my fair share and let others divide the rest however they can
though I no longer freak out about the amount of parasites out there, and the resources wasted due to them, I'm just trying to take my fair share and let others divide the rest however they can
@amiloradovsky doubt it. Our company is like 20 people. We have nowhere to promote anyone.
Follow
@newt @amiloradovsky
Everyone expects some very competent people overseeing all this cloud infrastructure, and that it would be build on some rock-solid technology — but in reality it's the same engineers as everywhere else and the same throwaway nodes running same Linux systems.
When Google introduced its App Engine and they were already accepting payments for it, despite it still being in beta: both formally and de-facto, judging by its reliability — it went unresponsive for days.
@newt @amiloradovsky
And this alone made me never consider this cloud shit.
In part it was due to working for organizations for which relying on offsite infrastructure wasn't acceptable — but I would never suggest it myself either, maybe as a backup or for occasional spikes in workload, not more than that