Context shifts are actually great for changing your perspective and reinvigorating your ability to work around road blocks. Switching from screen to paper is one way of context shifting. You could also switch a whiteboard. You could switch to talking through the problem verbally with a colleague or, lacking that, a rubber duck. You could just get up and go for a walk to think about that problem. Context shifting from…
I think you are right to generalise it to "context switch". Countless times I deleted my yet-to-be-posted, detailed Stackoverflow question, when after typing (ha!) it, i would realize my mistake. I never tried duck - debugging, maybe should give it a go too
I feel dumb(er) when typing, and smart(er) when writing
21–30 of 57 posts
Re: I feel dumb(er) when typing, and smart(er) when writing
#22I can't keep the variables, constraints, and edge cases in my mind. I use diagrams and crude flowcharts so paper/S-pen on Note/Tab is a must for me. Staring at the screen or typing it out doesn't do much for me.
Do you use the s-pen for general note-taking or only when you need to draw something?
Re: I feel dumb(er) when typing, and smart(er) when writing
#23Re: I feel dumb(er) when typing, and smart(er) when writing
#24I am the exact opposite. I type 150+ WPM and can’t write to save my life. Writing things down with pen/paper does nothing for me.
Re: I feel dumb(er) when typing, and smart(er) when writing
#25Code is what keeps me down to earth. It may seem like an unnecessary detail to think about how to pass a variable when you are barely familiar with the subject, but if you can't get something that simple right, chances are that your are going it the wrong direction and when time will come to do the implementation, you will be in a world of pain. Of course, a lot of that early code ends up being thrown away and reworked, but in the early phases, it is rarely a problem.
It probably has to do with a top-down vs bottom-up approach. I am much more comfortable working bottom-up, thinking first about the details and how they fit the big picture, rather than to top-down approach, where you think of the big picture and work up the details later. I think that both approach will eventually lead you to the same destination, so choose the one you are most confortable with.
Also, context matter. I do mostly low-ish level programming (mostly C++), I don't know about coq, but it seems to be more maths than technical engineering, so maybe a different mindset is required.
Re: I feel dumb(er) when typing, and smart(er) when writing
#26Re: I feel dumb(er) when typing, and smart(er) when writing
#27Re: I feel dumb(er) when typing, and smart(er) when writing
#28What I experience is that I can remember things I write a lot better. I’m not sure why. I can type a lot faster than I write. Also for problem solving I agree. I also don’t know why but I feel a lot “freer” when I have a sheet of paper in front of me.
Re: I feel dumb(er) when typing, and smart(er) when writing
#29Re: I feel dumb(er) when typing, and smart(er) when writing
#30Without all the context, I think it is due to structure of the problem. Some problem can't be understood clearly with just text, but needs diagrams etc. Coq problem seems like one that could fall in this category. And if you are like me, rough diagramming in computer seems slower/harder than with pen and paper. For these kind of things, I found apple pencil+ipad to superior to both as you don't need to worry about sp…