From my observation, we programmers are supposed to have two non-discrete modes of programming: 1.) the trial&error (or jiggle) mode and 2.) the literate mode.

From my observation, we programmers are supposed to have two non-discrete modes of programming: 1.) the trial&error (or jiggle) mode and 2.) the literate mode. Trial&error mode works well when working with randoms, e.g. exploration, research, acquiring information, identifying unknowns. Literate mode works well when working with exacts. Identifications for example produce exacts from unknowns. Enough facts enables you to build stuffs out of it like Lego. This is where literate mode works well. Jiggle programmers that does not quite grow out of their jiggling mode is because they stay in trial&error mode and does not slide slowly into the literate end of the spectrum. After acquiring some facts, they don't deduct or intuit from them. They don't attempt to philosophize a bit. A problem as simple as "how to do X after the window loads" for example, some programmer can find `window.addEventListener("load", X);` in stack overflow, but the main differentiator lies whether after fixing the issue, they care enough to at least wonder about what's the meaning of `window`, `addEventListener`, `load`, "why is the call shaped that way", "what is Event and what is Listener". Those who do slide slowly into their literate mode. It is also not less dangerous to be stuck in the literate mode. Although this happens rarer, often to more experienced people.