FIELD NOTE / 2026.09.212 MIN READ / 5 SOURCES

The Minds Behind Visual Programming Languages – 7 People Redefining Software

Seven pioneers helped turn diagrams, icons, graphical objects, and blocks into executable programming languages rather than mere illustrations of code.

TL;DR

Seven pioneers helped turn diagrams, icons, graphical objects, and blocks into executable programming languages rather than mere illustrations of code. [1][2]

Why you should read it anyway

Visual programming challenges the assumption that source code must be a linear stream of text. In domains where relationships, dataflow, geometry, or state are inherently spatial, a visual representation can make structure directly manipulable.

Imagine where Visual Programming Languages would be without them

Without these systems, graphical user interfaces would still exist, but executable diagrams, block programming, dataflow tools, and direct-manipulation programming environments would have developed more slowly.

Time Estimate of how many years we would be hindered without them for human progress

Editorial counterfactual estimate: 6–12 years. This is not a measured historical fact. It is an editorial estimate of how much slower the field might have matured without this cluster of people, institutions, products, and ideas.

The 7 people behind Visual Programming Languages

1. Ivan Sutherland

Why they matter: created Sketchpad, demonstrating that graphical objects, constraints, and direct manipulation could become a language for computational design.[1]

2. David Canfield Smith

Why they matter: created Pygmalion, one of the earliest icon-based programming systems, showing that program behavior could be represented visually through concrete objects.[2]

3. Alan Kay

Why they matter: developed the Dynabook vision and led Smalltalk work that treated graphical objects and direct manipulation as programmable media.[3]

4. Adele Goldberg

Why they matter: helped develop and document Smalltalk and the graphical environments that made computation explorable through windows, objects, and live interaction.[4]

5. Jeff Kodosky

Why they matter: co-created LabVIEW and its G graphical dataflow language, turning diagrams into executable programs for engineers and scientists.[5]

6. Brad Myers

Why they matter: conducted foundational research on visual programming and programming-by-example and helped classify what visual languages could and could not make easier.[1]

7. Mitchel Resnick

Why they matter: led the creation of Scratch, bringing block-based visual programming to millions of learners through a low-floor, high-ceiling creative environment.[2]

How they each differ from one another

Sutherland and Smith established direct graphical computation; Kay and Goldberg created live object environments; Kodosky built industrial graphical dataflow; Myers developed the research theory; Resnick brought block programming to mass education.

Final Take

Visual programming is most powerful when the picture is not documentation of the program—the picture is the program.

RESEARCH / PROVENANCE

Works Cited

5 SOURCES
  1. 01
  2. 02
  3. 03
  4. 04
  5. 05

CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.

Contribute / Corrections

Improve the record.

Use this moderated submission form to suggest a correction, provide a source, challenge a priority claim or identify a missing contributor. Submissions are treated as research leads, not automatically published comments.

Submit a research lead

Please do not submit confidential material or claims you cannot support.