I think I generally agree with this take, with the caveat that I still hugely value AI generated art, even the kitsch stuff. Why? Because it's me. I wouldn't have been able to have a portrait of my wife and I together without finding an artist and commissioning a painting. Now, I can have something that is personalized, pleasant to look at, and meaningful. Even if it isn't an original style or anything noteworthy artistically, I hugely value the AI art because it can give me something that I want, that is meaningful to me.
i think that the story is loaded with about 80% superfluous context and 20% story.
op worked at us airforce base managing access control to global intel systems. he delegated authorisation check to jr. jr told op they checked out, however, jr had not adhered to latest security protocol that required cross checking request against request database, relying instead only on physical credentials. op granted access however asked that an officer watch the civilians’ access directly.
a week later it turns out the civilians were conducting pen testing for the systems and op had to debrief how they gained access.
I definitely agree with a lot of the comments here especially the ones in the vein of “don’t do dangerous things with json. “ if you have control of the sender and the receiver, it makes sense to have fields that add a bit of extra type information e.g. this is an integer or this is a float with this much precision
Yeah, since there are multiple studies that show that alcohol in any quantity is bad for you. People are (slowly) poisoning themselves as replacement for therapy or lack of a support network.
Australia also probably has some of the worst deployments of asbestos in the developed world. Drive around even nice neighborhoods in Sydney and you’ll see plenty of cracking and breaking “fibro”, a cement asbestos sheet. Canberra is full of asbestos. They had to completely remove an asbestos mining town (Wittenoom) from the map because it was so contaminated.
There is a ton of asbestos currently in Australian households. Plenty of aussies drink water collected in tanks off of asbestos cement roofs.
Yes - unfortunately we have a lot of leftover usages of asbestos.
Historically, it was used a lot. My father even remembers playing around in the bush as a kid, and using asbestos for chalk a bunch of time to mark stuff on trees. My friends dad also remembers coming home covered in asbestos after work a bunch of times too.
I'm not sure I agree with your assessment about seeing asbestos in nice neighbourhoods. It depends how you define nice.
Asbestos was banned in 2003,but hasn't been used in housing since the 80s, so it's only going to be in older developments that you'll really encounter it.
Your wording regarding "plenty of Aussies" is also unclear to me. The numbers as a percentage are going to be very low, but it undoubtedly is a thing.
I was visiting a relative in their $3M+ house in Bronte and saw plenty of it. Not in the front facades of the homes, but drive through the back alleys, and you can spot some in < 1 min. I remember an uncle there who's neighbor had a fibro cement mail box which was built into some stone work.
I agree my usage of "plenty" was more in absolute terms. It is probably thousands to tens of thousands, which is small in percentage terms. I also spent a lot of time on Australian farms, and they have lots of asbestos sheets buried in places. Most farmers would rather pile it up or bury it then pay the costs of having it removed properly.
I work for a company called CloudFix, and we are solely focused on AWS costs. We do automated AWS cost optimization. We find one of two reactions when we deliver savings to customers:
(A) "Hey wow, this is great! We are so excited to be saving from here on out." OR,
(B) "This should have been caught earlier. $TEAM was supposed to be experts..." and then blame game starts.
It is really unfortunate when institutions react in the latter way. Often the engineers are assigned to cost optimization, along with a million other things. And, the incentives aren't really aligned well to reward savings. For example, S3 Intelligent Tiering is the right thing in 99.9% of cases - so it should be your default bucket type. BUT, engineers often face only downside risk for the change, and very little upside reward. And, it isn't their money so they just leave it. The cost of overprovisioned S3 can be staggering!
What is really needed is to establish a proper FinOps discipline, put someone in charge of cost savings, and make sure incentives are aligned properly. And of course check out CloudFix if you can!
We work with a competitor called Vega, the product seems OK although the UI is very slow and confusing.
The biggest problem they have is they have no business insight into what these costs are, and if we can reduce the cost without any kind of engineering, effort, or loss of performance.
I think it's like saying if you learn how to maintain a submarine, have you become a good swimmer? Or, if you know how to maintain a submarine do you understand fluid mechanics?
Ok let's take one step back and look at the parent:
> I don’t see how this can be true under any definition of computer science.
Let me arbitrarily copy one definition of computer science, from Wikipedia:
> Computer science is the study of computation, automation, and information. Computer science spans theoretical disciplines (such as algorithms, theory of computation, information theory, and automation) to practical disciplines (including the design and implementation of hardware and software).
I think that designing an OS counts as computer science, at least under "some definition of computer science". And learning how to maintain an OS is a step towards understanding how it is designed.
Of course, maintaining your OS does not teach you Javascript. But Computer Science is not limited to Javascript. And I have seen many developers distribute libraries without having a clue about how package management works, which results in a big mess. And then they complain about the tools ("CMake sucks, it's not my fault"), where actually they just don't have a clue how it works below.
I see computer science as the discipline that makes the whole computer work. Because one can't be bothered to understand anything below their favourite framework doesn't mean it doesn't count as "computer science".
I just watched this video on a plane, going nearly 600mph at 33K ft above northern Canada. The pace of technological evolution I have experienced in my lifetime is absolutely miraculous.
I often think about this. My grandmother was born at the end of the 1800s (yes, I'm old) and remembered electricity and the first car coming to her rural village in Wales. By the end of her life she'd lived through two world wars, seen men on the moon, could talk to her relatives in Australia on the phone, and been on holiday to America on a 747.
And what always amazed me was that she grew up with people (mainly farm workers) who had never been more than 5 miles from where they were born. I go further than that to visit the supermarket!
Many years ago, my father bought a house and one day when he was talking a neighbour about time and age, and the neighbour told him that he'd had an uncle that had been born in the 1700s...
This isn't as remarkable as it sounds when I say this was in 1960, and the neighbour was 80 something, and his uncle had been born in 1798, and had lived well into his 90s. But is still seems such a large span to be able to reach back.
Heck, I grew up in a village and I remember my family didn't have electricity when I was 6. Fast forward 25 years later, everyone there has fiber optic internet.
I've had many pourovers and I appreciate them if I have the time. If I like pour overs at value P, then I would rate an instant coffee at 0.9P. The 0.1P of value I miss out on isn't worth the hassle of filters, dealing with coffee grounds, all that stuff.
