@lain Thank you. Now I'm starting to wonder just how much of modern IT architecture is a holdover from the times of 32 KB memory. This seems like the one instance where saying "to hell with it" and just inflating the requirements 20x would be the correct call. But what do I know.

I feel like making headers and splitting workloads should be a computer job anyways.
The book seems to agree:
>Having a large number of header files is a big pain. Unfortunately, this situation occurs whenever you try to write a C program that does anything useful. Header files typically define data structures and many header files depend on data structures defined in other header files. You, as the programmer, get the wonderful job of sorting out these dependencies and including the header files in the right order.

>If you get the order wrong, the compiler will testily inform you that you have a syntax error. The compiler is a busy and important program and doesn’t have time to figure out the difference between a missing data structure definition and a plain old mistyped word.

The section below that complains that the compiler aborts when it sees a single syntax error, but I thought to myself "And? Just run it again, doesn't take that long..." and that's where I realized just how old this commentary is.