Writing code (Programming) is a thinking tool too.
When you are writing code manually, actually you are thinking about what you are doing, what you will build actually, what are your or users' real requirements, etc.
When you are writing code manually, actually you are thinking about what you are doing, what you will build actually, what are your or users' real requirements, etc.
I don't use it too often because of the time it takes, but for critical work it is really good.
I have tried to come up with other equivalent ideas, like asking questions about a specific aspect of a feature, or showing the diff with some gaps to be filled, and even though they help I am still on the look out of methods to "imprint" the understanding of features into our brain.
Does anyone know any good papers or studies that could be useful in this research?