brooke2k

with a legacy codebase, or a fork of a dependency that had to be patched which uses an incompatible buildsystem, or any C/C++/obj-c/etc that heavily uses the preprocessor or nonstandard build practices, or codebases that mix lots of different languages over awkward FFI boundaries and so on and so forth -- there are so many situations where sometimes an IDE just can't get you 100% of the way there and you have to revert to grepping to do any real work

that being said, I don't fully support the idea of handcuffing your code in the name of greppability, but I think dismissing it as a metric under the premise that IDEs make grepping "obsolete" is a little bit hasty

Since a game runs as a loop, all synchronous code needs to be able to execute within one frame.

So you end up making overcomplicated state machines to represent processes that last for multiple frames.

Coroutines make writing this code sooooo much easier. You can actually start to see the logic again at a glance rather than having to dive into a big stateful mess.

When I herniated a disc in my lower back, the ER doctor was very very hesitant to give me an opioid even though I was in constant, excruciating pain. But if you're allergic there's basically no other options out there.

This textbook (work in progress but mostly complete) is an attempt to do exactly that: start at foundational math like group theory and topology and build up to higher and higher levels of math.

I worked through the first few chapters a while ago, and it's very good. My only issue is that sometimes he assumes knowledge of things that I didn't know about, but cursory googling was good enough for those situations.