Why Visual Thinking Matters in Programming

I recently discovered a video from a few years ago: A Picture Worth a Thousand Programs, a talk by Maggie Appleton, and it still feels wildly relevant; maybe as much now than when it was first given.

Her core argument: programming is hard not just because of its logic, but because it asks humans; who live in a visual, embodied, metaphor-rich world; to manipulate abstract systems through pure linear text. That friction is where so many people get lost.

This lines up with the way I think about design, learning, and clarity. Whether it’s building UX flows, helping others start blogs, or breaking down concepts for myself of my team; I’m always hunting for ways to make the invisible visible.

Maggie frames visuals not as decoration, but as bridges. Diagrams, metaphors, spatial maps; they’re cognitive tools that can reduce complexity and build shared understanding. As someone trying to lead, teach, and design more clearly, resonates.

It’s also a reminder: thoughtful craft includes how we represent ideas, not just the ideas themselves. With the current trend of tech dominated by text-heavy documentation and abstract workflows, even a small shift toward visual clarity can be a powerful to help these tools help more people.

“We need more visuals that reveal metaphors, spatial meaning, and change over time.”

Yes. And maybe it starts with the next diagram, the next sketchnote, the next thoughtful blog post.