For some people (like me) thinking through problems with pen and paper is a tool.
For others I guess it is annoying: look at him, now he's doing this wannabe software architect stuff again.
Same might go the other way: here he goes again, trying to prove his programming super skills by jumping into it without even the smalles amount of planning.
FWIW I like to jump in and start coding, but what’s happening behind the scenes is that I “see” the algorithm or architecture in my mind. It’s not exactly a foowchart or a state machine, but it does have a sort of plastic manipulatable shape.
As someone who does both (flowcharts etc and exploratory coding) I think I experience something similar.
For me it is not very visual when I code. It is more a gut feeling: this goes here, that goes there. This is good, bad, weird but works etc.
This is nice for me but I know I have to work on how to explain it to others.
Bad example but I guess this is somewhat closer to what I want to be able to explain: "it currently works but it is a bad idea because it means you'll have to remember to patch seemingly unrelated functions x, y and z whenever you update this.
Also, in this case it is even worse as in the worst case you won't see the errors until the quarterly reporting run and that code is well known for having bad test coverage."
Edit: as usual I'm curious as to why parent was downvoted?
For some people (like me) thinking through problems with pen and paper is a tool.
For others I guess it is annoying: look at him, now he's doing this wannabe software architect stuff again.
Same might go the other way: here he goes again, trying to prove his programming super skills by jumping into it without even the smalles amount of planning.