I think this assumes a fine distinction between "domain" and "non-domain" knowledge that often doesn't exist. If you're writing a trading strategy, the technic

I think this assumes a fine distinction between "domain" and "non-domain" knowledge that often doesn't exist. If you're writing a trading strategy, the technical details of how the code's executed often dictate what kind of trading you're planning on doing. e.g. How do I balance speed vs how sophisticated the algorithm is? Also, if your "domain" is technical in nature (e.g. building a new database), it's not clear at all what parts are "essential" and what parts are "accidental". Is the file system accidental? Is the underlying data store (SSDs, spinning disks) accidental? Often the purpose of the project is intrinsically tied to the technical capabilities of the platform it's built on top of.