He doesn’t want to go to sites that are ad supported. He wants to support sites that don’t get their funding that way.

Well it’s obvious the users of other browsers doing the murdering.

Normally the use case is

• Constructed a long command, but it didn’t work for some reason.
• I go fix the reason it didn’t work
• I do the first thing again

It’s in my recent memory, but maybe there’s been 10 or so commands of me fixing stuff in-between.

That’s why you can add “:p” to the end just to print it.

The one people see me doing that gets a “huh?” Is:

~$ !find
find -type f -name '*blah*' -print0 | xargs -0 gzip
~$

“Wait! What did you do?” “Oh. Do you not know about bang?”

.net

Anything I run in C# or similar seems to allocate 512GB of virtual address space and then just populates what it actually uses.

It’s more my back than my knees

While the drones are armed, they use non-lethal or less-lethal weaponry,

Less lethal? So still lethal.

Why is everyone so keen on making Terminator real?

…or PCMCIA for short.

Indeed. A huge proportion of Gen X professionals were self taught children who learnt on home computers and then grew up.

CS degrees don’t teach you how to code. They teach you computer science.

I think it’s cheese-stringification.

It’s a few hundred lines of C across 7-8 files. It checks the password hash against a set of predefined ones and then calls a script if it matches.

It doesn’t need a lot of maintaining.

So I can never commit a test without also implementing the functionality?

That’s madness.

You’re both right. You’re both wrong.

• You write tests for functionality before you write the functionality.
• You code the functionality so the tests pass.
• Then, and only then, the test becomes a regression test and is enabled in your CI automation.
• If the test ever breaks again the merge is blocked.

If you only write tests after you’ve written the code then the test will test that the code does what the code does. Your brain is already polluted and you’re not capable of writing a good test.

Having tests that fail is fine, as long as they’re not part of your regression tests.

Just to add to that, a lot of the confusion comes from Microsoft and Apple wanting to lock applications to their platforms.

• Direct X was Microsoft’s competitor to OpenGL. Versions 3 to 11 were largely feature for feature comparable with the OpenGL version of the time.
• Direct X V12 and Vulkan compete in the same way.
• Metal is Apple’s Vulkan

Now you’re being silly.

What’s a good alternative to Jira?

A better way to say that (more accurate) is that abusers often learnt “how” through personal experience.

The key point is not to look at someone who has been abused and think that they are likely going to become an abuser.

deleted by creator

I’ve tried this a few times. I don’t think it works.

Basically the way you want to explain a piece of reasoning , and the order in which things need to be defined for a program, are different. You end up either making the document match the code structures, or the code structure match the document. Both are bad.