Yes. Because it can be semi-insulating (straw bales) or it can be externally insulated. Mass isn't just mass ... it needs controls and energy input. A hole in the ground is attached to the ground and that's the end of the story. No control. No thermal inputs.
Did I mention this was 15 years ago? Software development back then looked very different than it does now, especially in Wincore. There was none of this "Cloud-native development" stuff that we all know and love today. GitHub was just about 1 year old. Jenkins wouldn't be a thing for another 2 years.
In this case the "automated test" flipped all kinds of configuration options with repeated reboots of a physical workstation. It took hours to run the tests, and your workstation would be constantly rebooting, so you wouldn't be accomplishing anything else for the rest of the day. It was faster and cheaper to require 8 devs to rollback to yesterday's build maybe once every couple of quarters than to snarl the whole development process with that.
The tests still ran, but they were owned and run by a dedicated test engineer prior to merging the branch up.
Pretty much standard for HN, there are endless mod comments explaining it. Although they make more sense if you distinguish between 'changing' and 'editorializing'.
This chip:
8 MHz, 8 bit processing
1K x 14 bits EPROM.
48 bytes SRAM.
6 general purpose I/O pins (GPIO), PB[5:0], with independent direction control.
In comparison to the usual suspects like Apollo guidance computer or TI-83, it has a higher clock speed but shorter word length and extremely limited ram and memory. Precisely due to the cost engineering - this is meant to run simple, limited size programs.