Part of that equation, FWIW, is that certain countries would flood the market with supply to make any new projects suddenly unprofitable.
Which sucks extra bad because if you shut the project down but start it back up you can't just flip a switch. Gotta put together a whole new team and possibly retrain them.
E.x. if the data breached was not critical to legal retention requirements, the penalty is more severe. (Ofc this assumes good definition of what is critical for legal retention).
At the very least it would encourage companies to keep such data less or for shorter times to minimize damage.
Global Foundries sent their EUV machine back (and paid a fat restocking fee to do it), they've stopped trying to compete at the leading edge of logic processes.
SMIC has a DUV multi-patterning 7 nm node which is already economically uncompetitive with EUV 7 nm nodes (except for PRC subsidies) and the economics of DUV only get worse further down, but at least they're trying and will certainly be the first client to use the Chinese EUV machines, whenever those come online.
I think you meant KB here but now im also wondering how many MB you -could- actually scale tp and what the overhead would be due to the numbers of banks to switch between...
Northern Virginia's Fairfax County public schools have the day off for Diwali, so that's not an unreasonable question.
In my experience, the teams at AWS are pretty diverse, reflecting the diversity in the area. Even if a lot of the Indian employees are taking the day off, there should be plenty of other employees to back them up. A culturally diverse employee base should mitigate against this sort of problem.
If it does turn out that the outage was prolonged due to one or two key engineers being unreachable for the holiday, that's an indictment of AWS for allowing these single points of failure to occur, not for hiring Indians.
Seems like a lot of people missing that this post was made around midnight PST time and thus it would be more reasonable to ping people at lunch in IST before waking up people in EST or PST.
Then I missed it too because I let my Indian coworkers handle production issues after 9,10pm unless the problem sounds an awful lot like the feature toggle I flipped on in production is setting servers on fire.
My main beef with that team was that we worked on too many stories in parallel so information on brand new work was siloed. Everyone caught up after a bit but stuff we just or hadn’t demoed yet was spotty for coverage.
If I was up at 1 am it was because I had insomnia and figured out exactly what the problem was and it was faster to fix it than to explain. Or if I wake up really early and the problem is still not fixed.
reply