A code review is an engineering practice and a knowledge management process; it should not be confused with a merge or pull request, which is a change management and version control process. When you say, “code review wasn’t even ubiquitous until around 2012–2014…,” I think you’re referring to the approval tooling built into merge requests, not to code review itself. Engineers were having their code reviewed long before then.
By the time you genuinely expect a PR to be merged, it should be essentially rubber-stampable, in my opinion. It shouldn’t be the first time someone else is looking at your code—let alone the first time anyone is reviewing your design.
You are correct on both accounts, as of tahoe 26.3 you can't nest a macOS guest under a macOS guest. However you can nest 2 layers deep with any combo of layer 1 guest so long as the machine is running Sequoia and is M3/M4/M5.
files are stored as BLOBs inside the SQLite database, so cp micasa.db backup.db backs up everything – no sidecar files
SQLite is just so cool. Anyway, this whole project looks amazing. I can't wait to kick tires (and then track when I last changed my tires... wait, can it do that?!)
[1]: https://thermalprintcameras.wordpress.com/blue4est-paper/
reply