gemstones

C++ is proposing pre- and post- conditions to verify functions in C++26; notably, Bjarne Stroustrup (C++ creator) is opposed

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.

If you're already an American, move to St. Louis.

- 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

But a mountain would work, yes? And if you already need the mountain lab for physics, what is the extra cost to staff military personnel there?

(This is not China-bashing, as I assume lots of other nations do this for the same reasons.)

It's a lot harder to have unwanted intruders, and satellite surveillance is less likely. This lab will 100% have a military research purpose.

Do you think that most businesses have the consistent cash flows needed to pay out wages every hour?

I’m not sure this is a technical problem, I guess. Maybe a financial engineering problem but is the demand there?

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.

One suggestion - it would be really cool to allow FFI. Something like

    <script type="text/javascript">
      const foo = (bar) => {
        document.getElementById('my-element');
        // More here!
      };
    </script>

That way you could really leverage the full power of HTML, the programming language!

Are you serious?

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.