Chaosvex

Assuming you're talking about Scott Meyers, that's a fabrication.

I think you may be slightly biased about your wife's ability to replace an entire IT team with no technical knowledge, no offence.

> test if the key exists

Double lookup.

Name a more iconic trio when it comes to exploits.

iPhones actually can. I'm guessing some Androids have an equivalent.

Yeah, that's right and I believe that was the episode that introduced McKay. I've been binging Stargate over the last month or so, so it's pretty fresh.

Isn't the whole CG effect of flying through a magical tube seeing the wormhole?

Although the explanation of how it all works is rather inconsistent in Stargate. Initially, gate travel was something that people experienced and it was only later changed to being dematerialised.

Windows doesn't support overcommit, so you can't unless you have a ridiculously huge swap set. It is an issue.

When most of the elements are no-ops/unused, I don't think we should be making any assumptions about the performance at max capacity. Contiguous iteration is cheap. The author may call it the constant work principle but I can't agree.

In the context of HFT, since the author drew inspiration from the domain, there's also the issue of now having introduced new branches into the hot path. A lot of work goes into reducing branches and priming the predictor in advance of orders actually being placed. Granted, you could potentially be avoiding branches elsewhere as a byproduct but that's probably getting into the weeds and nitpicking the examples.

It's generally a little more complicated than that. Not up to writing paragraphs about it so I'll just leave this as a note so anybody that's interested can do their own research.

> Do you think it's impossible for someone to have a 25K line PR / diff but not know what's going on in the system?

If you didn't write any of it? Yes, you only think you know what's going on.

Given the decades of consumer and enterprise GPUs often being identical or near identical hardware, it'd be interesting to see if there's any evidence of this actually being true.

Too slow to edit this post but *morale. I'm blaming lazy phone typing.

On complex codebases, I've seen this strategy absolutely decimate team moral.

A large tech company decided to stop having subteams responsible for particular features or areas of the code for one of their products. The result was developers having to spend inordinate amounts of time researching highly complex spec documents and reference manuals on a daily basis for even the smallest of fixes. It drove moral into the ground and developers started a mass exodus to other teams or tech companies.

After some changes of management for the team, the policy had to be reversed to stem the bleeding. Turns out that developers don't like permanently being in unfamiliar territory.