What do you visualize while programming?

It depends a lot on the problem, but I tend to visualize the /processes/ of the programs that I am working on, rather than the code itself: for example, if I'm writing a function that parses a string, I try to imagine it going over the string, finding the positions of individual characters and capturing substrings between them. If I'm working with asynchronous or network code, I try to visualize how the processes (or hosts) should be working at different times, and how they might send messages to each other.

I find it very necessary and useful a lot of the time to draw diagrams, or even just written notes on the problem I am dealing with. A lot of my mental visualizations are very clear, but it is difficult to retain several at a time.

And like someone else in this thread shared, I often have to get away from the problem and do something else for my mind to garbage-collect itself and have enough room to clearly think up new angles. For me only a matter of even a few minutes away from the computer helps a lot.

I have kind of a crummy mind's eye, so my mind spontaneously produces vague "fantasy mechanisms" that seem to float in a void and interact with one another in some way that is analogous to the program, but there's no coherent metaphor and I don't think these visualizations actually hold any useful information or help in any way.

So at least for me: no, definitely no schema in mind. If you're missing out on that, so am I! Affect is weird.

What would happen if I do the opposite of what I am doing.

For example, if I am using a switch case, how would this application work in the if statement universe?

Both can achieve the same result but one enables the other to function in a different way.

The last time a programming task called for the use of my spacial visualization capability (not that long ago, a couple of weeks perhaps), it went like this. I was working on a system with two priority queues, and three stacks, which were all working together to affect a stream. The goal was to try and come up with counterexamples where the code I needed to work out would fail.

Ended up pulling out an iPad, and using Procreate to draw a bunch of overlapping boxes, and determined that strict stacks weren't going to work here and I was going to have to look for the actual value in the stack and remove it. But that most of the time it would be the top element, so this would be fine.

I don't mostly visualize when coding, and when I need to, most of my capacity is already taken up by something complex. So I have a growing collection of these sort of squiggly impressionistic diagrams, which I sketch out so I can fix the visual component of what I'm working on, to free up some capacity for the real work, which is just, thinking.

Pen and paper are not nearly so good for this as Procreate, I've found, because I can undo marks, and rather frequently do so, in a way which is much more fluid than erasing pencil marks. I can even try several approaches, by making new layers, and cacheing them by setting them invisible, trying again, juxtaposing, and so on.

I agree with the sibling comment that the intellectual work of programming is primarily verbal in character, although it can certainly draw on spacial reasoning at times. This, along with arguments from density, leaves me broadly pessimistic that "visual coding" will ever prove itself as a useful tool, and very skeptical indeed that it could ever be a durable replacement for syntax-based programming.

It also calls for a fair amount of arithmetic, for which I keep a Julia REPL open at all times, and a smaller but significant amount of higher maths, for which said REPL is also a treasured resource. But surprise surprise, it's mostly logic, and while the validity of logic is amenable to mathematics, its soundness cannot be resolved that way, but only through reasoning in an irreducibly verbal fashion. Or experiment, which is of value in programming, but the logic of programs is not nearly so empirical as that of real life.

Clockwise with the Vernal Equinox at 9 o'clock. I suspect that's the most common case.