Design of Software Representation Languages: a Historical Perspective
summary
A brisk survey of concrete milestones and tools across decades: assembly and flowcharts give way to high‑level languages and graphical notations that sometimes generate runnable code; PL/I compiler took seven years to produce a working implementation, structure charts and an IDE called Self generate module skeletons from diagrams, Petri‑net and statechart tools like TimeNet and Statemate support concurrency and executable models, and the rise of low‑code/no‑code (~150 tools) plus spreadsheets causes large, real‑world errors.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:26Machine to human-readable languages
- 3:35Programming language diversity
- 7:51Language categorization by purpose
- 11:27Professional to end-user languages
- 16:00Low-code and no-code tools
- 19:55Graphical languages and design notations
- 22:03Language design principles
- 25:35Future directions
- 26:20Q&A
related talks
01h 02mProcedural Programming: It Never Went Away
49mCultures of Programming
01h 00mEngineering Software
01h 27mPlato, Magritte, Sartre & Carroll - Learning Software Design from the Masters
34mLogic in Computer Science, Engineering and Industry
01h 24mProcedural Programming: It’s Back? It Never Went Away
06mHow We Used To Be
50mDesign Patterns for Software Diagramming