First time I'm seeing this concept myself and it's intriguing at first sight! (will obviously have to do some scrutiny before drawing conclusions though).
It's evoking memories of Omashu & factorio-like games :)
I didn't know anything about sailing, but your one comment made me search up point of sail and now you've opened my eyes to something that was a mystery to me for all my life -- how sailboats can "course made good" against the wind. Thank you.. this stuff is amazing, and sailing is an incredible science!
I'll admit I haven't had the chance to look through it at all yet.. in fact, I'm typing this comment just I took a glance at the table of contents. It's a small thing, but it kind of irks me that "Final Notes" following "0x509 ImplementingPlayer" is indexed as 0x510 rather than 0x50a
Anyway, I'm going to save this for later viewing.. very interesting post.
In context of this, I've always been thinking that software engineers should be held way more liable -- like those of the physical engineering disciplines. In order to enforce good software engineering practice, there must be either incentives or disincentives (carrot or stick) that have clear consequences on the engineer himself/herself. Otherwise there is nothing stopping them from producing bad work. It may be unintentional and the code perhaps is simply sloppy (but still works).
This is just a thought (and may be unpopular): practices differ wildly from one company to another, and between enterprise software vs hacky side-projecty node apps, nonetheless, maybe it's time to standardize software good practices across the entire industry and enforce them, making them not just "good" practice, but mandatory practice.
No, it has not improved. I last used it around a year ago at a company where a lot of young engineers had to pick up a 20 year old code base. Suffice to say, the expertise for ClearCase really wasn't there and it was an absolute mess.