Wash it down with a cold glass of sarcophagus juice

One of my old phones would consistently correct "and" to "AMD" (all caps)

It felt like a brand deal gone wrong lol

imo unit tests are great for utility classes and functions that are general, that work well in isolation (i.e. you don't have to mock up any bullshit to test them). Anything past that, I'm less a fan.

...still hate writing the tests though 🙃

I'm with you on one point, though: when it comes to game systems, those typically aren't something that I would unit test, as they tend to truly rely on their interactions with other systems. Instead I'd do what you're suggesting: lots of carefully-chosen asserts and checks throughout the game code

...and of course, that particular one was only a problem much later when the pointer was used (because it was freed but the smart pointer thought it was still alive), so it was a bit of a pain to track down.

A targeted unit test for that case would have caught it early and saved me much pain.

For instance, in one project years ago I had a standard intrusive smart pointer class (based on AddRef/Release so it works with COM object because DirectX), it turned out there was a bug in the move assignment operator with an unexpected free that was there for *years* before I happened to hit it

The problem there is that if you have a codepath in there that hasn't been exercised (especially if you *think* it has already), and then you add game code that suddenly uses it... well, I've spent a lot of time trying to debug the *new game code* instead of the *older library code* before realizing

Also possibly I have too broad an idea of what constitutes a "unit test" vs whatever other kinds of tests there are

basically, I think, anywhere the API surface is likely to remain stable, the internal implementation doesn't matter, and you don't have to do all sorts of weird bullshit poking into the internals to write the tests.

Anytime a unit test pokes into implementation details that's a red flag

There are places where unit tests are useful, and places where they're not.

For instance, if you're building a core library (think: an STL) it can be really useful to have a suite of tests for that type of utility code...and those classes/functions should be stable, ideally

I don't want the real answer I just want the funny version 😅

at least they acknowledge he is 100% gonna be on the hell road

It should just be a font ligature and not a whole-ass separate thing

C'MON

what if instead we just spend 70 million on trying to make people feel bad

I love that not only can you see how much he and his writing/directing team have really gotten better through Breaking Bad/Better Caul Saul, but also how he's letting his X-Files flag fly again