[maest]

> calmly contemplating a system until you get to a point where the next right decision reveals itself.

I think I am not getting it because that just sounds like thinking about things and designing stuff.

I mean, sometimes, I focus on getting the right primitives so that the rest of the decisions just naturally fall out from that, but I'm not sure that's what you meant.

[gdubs]

In the book he uses the example of trying to get a stripped screw out of something. It’s a classic example of where a lot of people will kind of mindlessly make the problem worse. But when you approach it calmly, maybe it leads you to realize it just needs some oil applied to it, etc.

So, I think we’ve all been there with coding where in either a rush, or driven by ego to solve the problem in some impressive way, we kind of get ourselves tied up. But when we calm our mind, it’s easier to see, “oh, I can just leverage this little change”.