Embed Notice

@lwriemen
This is an overly pedantic quibble, though I agree with the underlying sentiment that people rush into coding too fast without thinking.

Doing the work of filling the things left between the lines for the reader to infer above: coding something •while thinking• — assessing the results, letting the ideas talk back and surprise, treating design and implementation problems as prompts to think about goals and context — is a deep way of understanding a problem.