3 ms·
Honestly, I think that his book Principles (which is the one I'm reading) is just really dense and reads like an encyclopedia. Possible that it's just really ha
by catsarebetter 4y ago
Honestly, I think that his book Principles (which is the one I'm reading) is just really dense and reads like an encyclopedia. Possible that it's just really hard to get through?
The decision-making frameworks that he describes go down to a micro-level. I do think that a lot of this stuff maps to engs like us, esp. the tradeoffs we make in deciding to pursue projects, skills, and jobs.
- themodelplumber 4y agoI came to his book after working closely with someone who created a unifying system, documented it, and trained large groups in its use, so that may be why it stood out as a problem. The difference was obvious. 200 principles may be "just" really hard to get through from one perspective, but from a systems standpoint it's really only at square one. Not a judgment on the principles themselves of course. But unfortunately principle-compilers (more like broad describers of phenomena) and model-architects (more like deep designers of interventions) are often two different people entirely.