"I managed to save three bytes here."
"My God, you're a sick person. I love it."
Then I went back to my "day job" data mining a couple dozen terabytes of stuff in a database.
I love working with computers.
And I really hope you misplaced that hyphen in "cow-orkers".
EDIT: As far as I know, the definition of "ork" as a verb is left to the imagination.
When I was developing educational software for Apple II computers in the mid-80's, one program we did had, at a given moment, 43-and-half bytes of free memory in the whole machine. The half byte is there because we were using that byte, but the counter wouldn't exceed 12, so we had 4 bits we could use for something else.
But my most impressive feat there was a graphics window-overlay library that used RLE to store obscured regions and was implemented in less than 1K of 6502 code. If you didn't want to preserve color information, it would shave one bit off every byte of screen data (increasing RLE efficiency)
In (most) modern environments, the optimizations are toward maintenance and support and speed of programming. Not toward memory optimizations.
All sorts of bizarre constructs can be commonplace when you are looking to stuff an application into a tiny ROM or tiny RAM; into 32 KB main RAM memory that was commonplace on a number of systems years ago, for instance. This using instructions as data storage for constants, modifying the return pointer in the call stack, using instruction side-effects, and otherwise.
When you're at the edge of needing a bigger (and then far more expensive) ROM or falling out of available memory or needing to switch over to overlaid segments or other run-time hackery, getting a dozen bytes back somewhere could be a big deal.
Some of these coding techniques can be appropriate in and still show up in very tight loops and embedded applications, but they're far less common now.
And thankfully, cheap "large" physical memory and virtual memory means we seldom have to deal with anything like TKB and its overlays:
http://wjh.conflux.net:16080/RSTS-V9/documents/DEC/AA-5072C-...