AVS&#x2F;Express [1] had a great visual programming system 20 years ago for building 3D visualisation systems. They called it the Network Editor [2]. It was very similar to the Unreal Engine Blueprint system. I&#x27;ve also played with MIT&#x27;s Scratch environment, which is very visual too, but a little more like a traditional imperative language that the data flow connection style of AVS&#x2F;Express or UE4 Blueprints. So I strongly agree with the author&#x27;s contention that &quot;there are some mistakes that are so appealing they will be made over and over again&quot;. Appealing because visual programming environments hold out the promise of enabling non developers to develop software. They do a good job of hiding the syntactic complexity of traditional programming, but they can&#x27;t hide all the semantic complexity of objects, memory, stacks, variables, processes, threads, databases etc. But there is one functional, grid based visual programming environment that has been hugely successful in enabling end users to create their own software solutions: Microsoft Excel.<p>[1] <a href="http:&#x2F;&#x2F;www.avs.com&#x2F;solutions&#x2F;express&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.avs.com&#x2F;solutions&#x2F;express&#x2F;</a>
[2] <a href="https:&#x2F;&#x2F;cdsweb.cern.ch&#x2F;record&#x2F;400582&#x2F;files&#x2F;p69.pdf" rel="nofollow">https:&#x2F;&#x2F;cdsweb.cern.ch&#x2F;record&#x2F;400582&#x2F;files&#x2F;p69.pdf</a>