Tonsky Blog offers insights, essays, and discussions on programming languages, software design, and user interface development. Covering topics such as functional programming, ergonomic code editors, and interactive user experiences, Tonsky Blog provides resources for developers and design enthusiasts. Readers can explore unconventional ideas in software development, delve into the principles of good design, and challenge conventional wisdom through Tonsky's blog posts and reflections.

tonsky.me

Visual programming should complement, not replace, textual coding. By integrating diagrams into the development process, especially in areas like state transitions and memory layouts, developers can improve code clarity and ease complex tasks. Current levels of integration range from separate diagram tools to IDE-generated visuals and fully executable diagrams. The key is to use diagrams where they naturally fit, enhancing rather than complicating the coding workflow.

Where Should Visual Programming Go?

Level 2: Diagrams are generated from code

Absolutely agree that visual programming should complement, not replace text code. In fact, I created a pretty sophisticated visual programming language “Pipe” around this idea. Here are details: <a href="https://www.pipelang.com" target="_blank" rel="noopener nofollow">https://www.pipelang.com</a>
The first part of my project is a book with a full language specification (155-page book available on <a href="https://amazon.com/dp/B0FSRFRJ76" target="_blank" rel="noopener nofollow">Amazon</a>, <a href="https://books.apple.com/us/book/id6752923085" target="_blank" rel="noopener nofollow">Apple Books</a> and <a href="https://play.google.com/store/books/details?id=9QWJEQAAQBAJ" target="_blank" rel="noopener nofollow">Google Play</a>, implementation is in progress). I started with the book because the biggest problem of many existing VPLs is that they do not have such language specification (offering to learn by examples only). Pipe language specification is large, so <a href="https://medium.com/@toplinesoftsys/five-pillars-of-pipe-b2de5f0d1421" target="_blank" rel="noopener nofollow">this article</a> provides a good intro into foundation of the language.
I am trying to find a place for Pipe according to classification in the article:
<ul>
<li>Level 0: Diagrams live separately</li>
<li>Level 1: Diagrams live next to code</li>
<li>Level 2: Diagrams are generated from code</li>
<li>Level 3: Diagrams are code</li>
</ul>
However, I cannot find exact level for Pipe. The closest is level 3. However, Pipe can be classified as “Code inside diagrams” - perhaps level 4?