It's about a specific type of debilitating fear. The DSM has a rule for criteria that, to be considered as having a condition, it must seriously affect your ability to live a normal life.
Most social anxiety is not debilitating, and would not meet the diagnosis. This is why therapists receive so much training - you must encounter enough people with a truly debilitating fear that you know when to diagnose it.
- North enough that climate change will not affect it as much
- Inland so not at risk of sea level change
- Next to a large fresh water source
- Food security - weather suitable for all kinds of crops, even as temps rise
- A large enough group of people in a rich country that it will still be able to get resources as things get worse
- Because of the city/county split, the city crime rate is arbitrarily high despite being a safer metro than most. Means that housing prices are low. Places like Chicago are more at risk of becoming unaffordable as refugees crises get worse
- The region is one of the few that has been continuously settled from pre-colonial days, indicating some Lindy effect in play
Aren’t most security vulnerabilities in C or C++ code? Seems a bit rich to point to C’s write-your-own approach as being a security benefit. I’d want to see some data on that before I arrive at that conclusion.
The interesting stuff tends to be webapps, that people pay for and are often internal to a company.
If you just care about sites that are document based, of course you’d prefer the static content stuff! But he wouldn’t be working on a project you’d be visiting anyway, so who cares if you stop visiting?
Oh it's not good advice for everyone! If they're a lead on a team you must interface with, they fall into my "you must work with them" bucket, and then the article is pretty good advice.
Eh, I disagree that it's childish advice! It works out pretty well for everyone except the person being frozen out - no matter if you're a child or an adult.
As in software, the best tool for avoiding errors is to not have the software in the first place.
If you must work with someone, or consider yourself to have an ethical obligation to follow this, this is good advice.
If you don't...
Just slowwwly remove your touchpoints with them. Freeze them out. Go through other channels. If you do this right, the person will feel like you have just gradually drifted apart, but won't be able to pinpoint a clear cause.
You don't have to try and get them fired, or anything (and that may backfire on you, so I don't recommend doing it.) But if enough people do this, then they will gradually be the most replaceable person on the team, and they may be let go regardless.
Oh haha I forgot how much information was not exposed in the API at all. I remember having to bring in a senior engineer because I thought I was going crazy. I could only ever find like half of the useful data on a server I just provisioned.
This was almost a decade ago, I assume (hope?) things have changed in a decade of trying. But it was official VMWare advice! It was literally in their documentation too.
Oh my lord, I remember dealing with a VSphere API early in my career. They didn't have a concept of service accounts so the official advice for our nightly automation was:
Pay a sysadmin to be up at night, then before your job is meant to run, have them log into the VSphere GUI, open devtools, click refresh to trigger a GET request, copy the cookie, paste the cookie into our custom software, and send it in the cookies of our API requests.
When we asked if there was an easier way, they said that we could probably use Selenium to automate that.
Needless to say, we did not sign the contract, and moved wholesale into AWS.
China is closed to us! Not super surprising from that lens. They make nice EVs, though.
It's political suicide to entertain making things easy for China, particularly in auto manufacturing, where there are several big union voting blocs that will look very dimly on allowing their products entry.
I would vote in anyone who recognizes what a giant problem it is that the first suggestion for someone who only wants to write SQL for one specific database is our federal government.
I do not want the government to be the landing place for people who just want to coast. We could make a rubber-room department if we really need it, just pay this woman to make SQL reports on nothing to nobody if just getting her a salary is the goal.
But if we need real work done this woman is not our collective best option.
Well, with the hollowing out of OpenAI, it seems that someone else will easily take the lead! They're not my personal hopes - this move destroyed OpenAI's best chance at retaining control over cutting edge AI as well. They destroyed their own hopes.
The board vote did it! They had a tender offer in the works that would have made employees millionaires. The board clearly signaled that they viewed the money-making aspects of the company as something to dial back, which in turn either severely lessens the value of that tender offer or prevents it from happening.
I mean, he didn't have a button on his desk that said, "torch the shares", but he ousted the CEO as a way to cut back on the things that might have meant profit. Did he think that everyone was going to continue to want to give them money after they signal a move away from profit motives? Doesn't take a rocket scientist to think that one through.
I think he was just preoccupied with AI safety, and didn't give a thought to the knock on effects for investors of any stripe. He's clearly smart enough to, he just didn't care enough to factor it into his plans.