My career had great benefitted from visualization.
At one point, I was working on a terrible piece of code as a programmer. (Literally, I failed the code review, they put it in production anyway, it didn't work so, so they fired the contractor who had done the work and handed it to me.) My boss said I should "just fix the code", not change the design.
I realized eventually that he thought of "the design" as the database schema and triggers, and that he had a hand in the design. So if we blamed the programmers, that was okay, but if we crictized the design, he felt he would lose something.
After three months of "just fixing the code" (I wrote 70% of the non-SQL code), I presented him the data flow diagram of the triggers by drawing it on a white board.
He said "this doesn't work, you've got backflow here ..."
And I said "yes, that's true."
He said "You don't understand. This can't possible work! You'll have to rewrite it"
And I said "Well, boss, if you say so. Okay. I guess I can rewrite it."
True story.
That said, my visualization skills stink. I have a writing disability; my small motor skills developed excruciatingly slowly. That's why my parents bought me a keyboard and encouraged me to use the computer.
I'm on here to learn.
--heusser
--
Matthew Heusser,
Principal Consultant, Excelon Development