If they had suggested a viable cold blooded herbivore, we might get somewhere.
1,230 karma · joined April 30, 2009
If they had suggested a viable cold blooded herbivore, we might get somewhere.
For comparison, Russia had a 2.29 fatal accidents/million departures safety rating in 2021, which is terrible, worst of all operating regions. 737-maxes had a 3.08 in 2019 when they got grounded. Every other plane in North America is averaging about 0.20 right now.
Granted, the 737-max's stat is based on a fairly low number of crashes. Regardless, the odds of a fatal crash are still vanishingly low on any given trip.
If you want a Klugey non-production IoT solution that bodges up something really important THESE days, all the cool kids are using ESP32s.
And as much as I think that would be a totally inappropriate solution for src.ht, I kinda wanna go make a "black-hole" switch for my office.
Hell, I don't even trust that they'll still own/maintain _Android_ in 7 years.
My partner _is_ a professional graphic designer, and we _have_ seen some pretty terrible client graphics that came out of Midjourney. They're amazing for what they are, but it's very difficult to get something out of it that competes with a professional illustrator, even ignoring the whole copyrighted content in the model issue.
Now, that said, it's pretty amazing that this works at all, but it'll take some pretty specific training on a model to get something that can compete with a human made font that's curated for good usability _and_ aesthetics.
Sadly, we'll also probably see adoption of these kinds of fonts (along with graphic design, illustration, songwriting, screenwriting, etc)... because "meh, good enough" combined with some Dunning-Kruger.
TL;DR: Thanks, I hate it.
The world's energy consumption was about 5.67x1020 Joules in 2013.[18] This number has increased by more than 2% per year on average in the last 50 years. The average world economic growth rate in the last 50 years is about 3%, which requires a corresponding increase in the energy supply. So, the 2% growth rate for world energy consumption should be a conservative assumption.
... is a bit naive. If we're consuming (does some math) `1.02^1000 = 398264651` ...Four billion times as much energy as we do today. I don't think there's much risk of us growing our population to that degree, nor of us being that power hungry if our population stabilizes. We'll be either extinct or back to a sustainable agrarian population far before we reach that upper limit. Honestly, if we produced that much power, I suspect we'd have long since boiled the oceans, making the whole argument moot.
TL;DR: Don't extrapolate FAR into the future based on a small (relatively) set of data points.
For the more serious attacks mentioned, the automakers are essentially saying that they build extremely vulnerable systems and are afraid to disclose that fact.
I suspect we're in violent agreement though, that the correct outcome is to fix the vulnerabilities AND to document the repair methods.
How do they test that across the infinite number of permutations of configurations and deployments of K8S in the field though? It'll work for some people on the happy path, but it's really hard to maintain over time. Worse, it'll break randomly at some point in the future that is hard to predict, instead of at some publicly announced point in time where the breaking change is deployed (how it happened this time).
I worked at a large company that deployed it's own Kubernetes stack, on a VERY large number of physical hosts. The theory was that the K8S would simplify our devops story enough that we could iterate quickly and scale linearly.
In reality, the K8S team ended up being literally 10x larger than the team building the application we were deploying on it. In addition, K8S introduced entirely new categories of failure mode (ahem; CNI updates/restarts/bedsh*tting, operator/custom resource failures, and tons of other ego driven footguns).
The worst part? The application itself ran fine on a single dev workstation, but also on any random assortment of VMs. Just pass the consul details as environment variables. I am not saying everybody on K8S is in the same boat, but I think that far more people are planning on becoming a unicorn cloud service than have any hope of becoming a unicorn cloud service.
TL;DR: If your hosting solution requires more maintenance than the application itself, you made a boo-boo.
He's thought about this stuff for a very long time, in great depth, and is very much worth listening to.
As for security, while the automotive manufacturers are aware of dangers, and standards like ISO21434 https://www.iso.org/standard/70918.html are driving them towards better security engineering practices, there is a huge gulf between process/compliance/governance, and truly secure engineering practices as a core part of engineering culture.
Many/most of the people working on the on-board systems come from an embedded development background that doesn't include pervasive connectivity. That's a problem. They might check the boxes to appear secure, but they aren't necessarily invested in the process.
My prediction; there _is_ going to be a severe and widespread automotive security event which cannot be ignored, before that culture shifts.
But yes, you are absolutely correct, and the value added by a productive developer is probably vastly larger than the value added by the rest of the rank and file. That's why developer centric startups can grow so large, so quickly.
Still need the rank and file to take care of pesky things like sales, payroll, governance/compliance, etc...
Also conservatives: "Let's trick this chatbot into repeating racist/misogynist hard-right talking points"
ref: https://www.cbsnews.com/news/microsoft-shuts-down-ai-chatbot...
Complaining that the chatbot won't fabricate a false narrative decrying drag-queen book readings strikes me as disingenuous, because that feature was probably added to combat people who were already tricking the chatbot into fabricating false narratives around the LGBT+ community. They literally had to try and do that to find out it wouldn't do it, and then they're acting incensed because it won't.
I guess they're pissed because they have to construct their own crappy editorials for their Parler accounts.
That 1000 random people will build it, get it on the launchpad, and press the button. That's not the problem. It's getting to orbit (and back) that would be highly unlikely.
https://www.ucl.ac.uk/news/2018/jun/high-levels-oral-disease...
Bitcoin/Blockchain was designed specifically to circumvent the legal frameworks used
to regulate financial transactions. It follows then that any non-fraudulent use of
these technologies is the exception, not the norm.
Blockchain currencies are designed to avoid being regulated. I am not saying that all
of the current regulations are _good_, but irreversible "anonymous" transactions are
always going to be attractive to fraudsters.There exists in such a case a certain institution or law; let us say, for the sake of simplicity, a fence or gate erected across a road. The more modern type of reformer goes gaily up to it and says, “I don’t see the use of this; let us clear it away.” To which the more intelligent type of reformer will do well to answer: “If you don’t see the use of it, I certainly won’t let you clear it away. Go away and think. Then, when you can come back and tell me that you do see the use of it, I may allow you to destroy it.”
Not a perfect XKCD match, but pretty close: https://xkcd.com/743
And the people in control of the training corpus get to decide who to arbitrarily add into which disorder category, either on purpose or through incompetence.
What could go wrong?!
I know we're all hot and bothered about getting our apps to scale up to be the next unicorn, but most apps never need to scale past the limit of a single very high-performance database. For most people, this single huge DB is sufficient.
Also, for many (maybe even most) applications, designated outages for maintenance are not only acceptable, but industry standard. Banks have had, and continue to have designated outages all the time, usually on weekends when the impact is reduced.
Sure, what I just wrote is bad advice for mega-scale SaaS offerings with millions of concurrent users, but most of us aren't building those, as much as we would like to pretend that we are.
I will say that TWO of those servers, with some form of synchronous replication, and point in time snapshots, are probably a better choice, but that's hair-splitting.
(and I am a dyed in the wool microservices, scale-out Amazon WS fanboi).
https://www.aircraftspruce.ca/
I've built a bike frame with their 4130 tubes.
I am asking seriously; what did you criticize?
Also, it's likely that his camera is mostly at fault; OBS with my Logitech camera doesn't have any significant lag. OBS itself has very little lag.
- Those developers in India are 180 degrees out of phase time-zone wise. There is effectively zero overlap in working hours from the west coast of the US to India. Makes it hard to collaborate.
- You get what you pay for. Skilled developers in India move to the US (or some other country where they have better opportunities). I've worked with some _fantastic_ developers from India, but they've mostly relocated.
- Quantity != Quality, although quantity does have a quality all it's own.