Hey folks,
Sorry for the late start to the discussion thread this week — I know it doesn’t look great to be late in Week 1, but I imagine most people can empathise with how intense this week has been across the subcontinent.
That said, I really enjoyed reading the book. It made me slow down, feel more like myself, and sparked a kind of curiosity I hadn’t felt in a while.
This week we read Chapter 1 – Crunching Knowledge.
I found the chapter extremely engaging. What stood out most is the way Evans brings first-principles thinking into the foreground.
The PCB example at the start was a great entry point — even as someone who didn’t really know what printed circuit boards do, I could follow the idea of knowledge crunching. The cargo example later on was more accessible, but both worked well.
This excerpt in particular stayed with me:
“The model was distilled. Important concepts were added to the model as it became more complete, but equally important, concepts were dropped when they didn’t prove useful or central. When an unneeded concept was tied to one that was needed, a new model was found that distinguished the essential concept so that the other could be dropped.”
I’ve faced this kind of situation at work — building something elaborate, only for the scope to be reduced. Because everything was interconnected, trimming things down became painful. The idea of creating a new design that only preserves what’s essential, rather than just cutting back the old one, feels unintuitive but makes a lot of sense.
Another line that clicked instantly:
“Domains that seem less technically daunting can be deceiving — we don’t realize how much we don’t know. This leads us to make false assumptions.”
I’ve definitely experienced this. It’s one of those things that seems obvious in hindsight, but hard to spot in the moment.
We’re just getting started, but I already feel drawn in. The book has definitely piqued my curiosity. I’ll be keeping this last quote in mind when approaching future designs:
“Knowledge crunching is an exploration, and you can’t know where you will end up.”
Challenge for the Reader
- Have you experienced a moment where trimming a model revealed a simpler, better design?
- Think of a domain you assumed was simple — what hidden complexity surprised you?
Very true. I recently started my internship project and am completely able to relate with the steps given since these are the very steps we are following here.