I agree on the first point, allocating time to design the expected outcome is also key. But on the second point, I find myself having to use the g! Operator of

I agree on the first point, allocating time to design the expected outcome is also key. But on the second point, I find myself having to use the g! Operator of ddg to get the result I need. Recently it was looking for a workaround I knew existed for a documented defect. ( weirdly not documented on the bug tracker of the library ... go figure ) Google gave me the result, Duck Duck go was serving me the doc or the bug tracker. Hmm. Actually maybe Google just remembered that from my previous search.