Which part? Mechanical turk is an Amazon service for crowdsourcing work, and Africa has cheap IT literate labor so would be a good source for this type of work.
Ohhh absolutely. And it's not just users, it's also management. "How does this affect us? Are we compromised? What are our options? Why didn't we prevent this? How do you prevent this going forward? How soon can you have it back up? What was affected? Why isn't it everyone? Why are things still down? Why didn't X or Y unrelated vendor schlock prevent this?..."
And on and on and on. Just the amount of time spent unproductively discussing this nightmare is going to cost billions.
Nothing is more annoying than having a user ask a litany of questions obvious to the person working on the problem and looking for the answers while working on the problem and looking for the answers.
They’re valid for a postmortem analysis. They’re not helpful while you’re actively triaging the incident, because they don’t get you any steps closer to fixing it.
Exactly my thinking. Asking these questions doesn't help us now. But after all the action is done, they should be asked. And really should be questions that always get asked from time to time, incident or no incident.
The problem is that you are only focusing on making the computers work and not the system.
"we don't know yet" is a valid response and gives the rest something to work, and it shouldn't annoy you that it's being asked, first of all because if they are asking is because you are already late.
you have to to tell the rest of the team what you know and you don't know, and update them accordingly.
until your team says something the rest don't know if it's a 30 minute thing or the end of the world or if we need to start dusting off the faxes.
Plus, CrowdStrike runs on Linux as well. _This time_ they only crashed Windows devices, but there's no guarantee that switching to Linux would prevent any of it.
You can switch away from CrowdStrike but I doubt you'll be able to convince whoever mandated CS to be installed to not install an alternative that carries exactly the same risks.
>CrowdStrike runs on Linux as well. _This time_ they only crashed Windows devices, but there's no guarantee that switching to Linux would prevent any of it.
In fact there was a recent CrowdStrike-related crash in RHEL:
At least on Linux it runs on eBPF sniffing so the chances of fudging something are lower. There are some supported Linux distributions where they also have a kernel module and there might a higher chance of that exploding.
There's nothing special about Windows beyond the fact that you can run arbitrary executable files. The problem could just as easily have happened for Linux or iOS/Mac and in fact it has. ChromeOS kind of works if you want to run a web application that's hosted on some web server... but it's not appropriate for running programs where a dumb browser doesn't suffice.
I'm not in IT anymore and we run 100% macs, so serious question here: isn't nearly everything a webapp nowadays? Every "non dev" thing that I have to do for work happens in my browser or an electron app. I guess maybe MS Office apps may be the biggest hitch? We use Google Workspace and that's all in browser.
It's horrible to use though. Google's suite is somewhat better than MSFT's web one, but it still is weak compared to any established desktop office suite, even libreoffice.
I've found it alright to be honest. I'd like to use libre office but the incompatibilities with .docx make it too annoying. Finally I can easily work with .docx on Linux, thanks to the web version :)
Do they still do the thing where if you search for a domain name and decided not to buy it they mysterious buy it themselves a couple days later and increase the price threefold?
Personally its because there was a lot of question mark hanging over second hand EVs for ages. If i buy this car for £10k will it need a new 8k battery in 18 months?
I don't know if this is still accurate but it was top of my mind 5 years ago when i last changed one of our cars. Ill consider EVs again next year when one is due for replacement at which point ill need to total up the additional home infrastructure in the price.
There's over a decade of real-world data available from Tesla and Leaf, and the batteries are very long-lived: they degrade about 1%-2% per year with a good battery management system, and around 3% per year with Leaf's weaksauce one.
Additionally, batteries are getting cheaper and more energy dense, so when it's time to replace them, you'll probably get an upgrade for cheaper. Leaf started with 24kWh batteries, and now you get 40kWh for the same price, and a 64kWh upgrade option.
People often extrapolate from their experience with cell phone batteries, but these "lithium" and those "lithium" batteries are very different. There are different chemistries, different conditioning with active cooling/heating, different rates of discharge, and a big difference in redundancy when you have 1 cell vs 7000 of them.
All i can think of is billing for a fraction of plans from the early 2000s who still pay per min/per text. Or maybe for capacity metrics but even then you only need the overall data point not the actual records once collaborated.
What's the US law for keeping data as long as its relevant and needed?
If you write something at work does anything realistically stop you retaining enough person documentation / snippets to fully or partially recreate it?
My buddy Slim seems capable of it and has built up quite a portfolio of "ready to go" solutions for common problems over the years.
It's a matter of degree, obviously, but every time you do this it's likely to count as IP infringement. Generic libraries? Probably nobody will ever notice or care. But if they do, it could be expensive for you.
It may be expensive, but that's unlikely to be due to infringement.
Most code written by most companies has been written a thousand times already, and there is nothing illegal about recreating a library which behaves the same as something you wrote at a company.
