Bret Victor Inventing on Principle

Is there some pet peeve you have about the world, which you wish to change? If there is, and you can put your finger on it, making it happen could be a very fulfilling thing to do. I just figured out my pet peeve, the design principle I wish to impart to the world... after watching this video recommended in a different thread Bret Victor Inventing on Principle -- ▶ this video I wish you luck if you find yours.

>Brett Victor - Inventing on principle: ▶ this video This gave me a sharp moment of clarity, thank you so much for this! I'll work on the wording over time, but here's a rough sketch of my principle: My principle is that no person should ever be forced to blindly trust a computer to do the right thing. Computing shouldn't be either blindly trust the black box, or get nothing done. Nobody should have to hand over their wallet to buy an ice cream cone, you can just take the exact change out and pay. Why should you have to give a program access to everything when you just want to edit one text file?

Rich Hickey - Hammock-driven development: link Brett Victor - Inventing on principle: ▶ this video Programming is terrible: link Dave Beazely - Python concurrency from the ground up (applicable to languages in general, with generator and corourine functionality) link Functional programming, with birds: link Short and classic: Wat link

This might be one of the best example of Bret Victor - Inventing on Principle talk [0]. I wish there are a lot of tutorial or course with the same quality as this one. [0] ▶ this video . Original link on Vimeo is dead: link .

>> They continuously run every time you make any change to them. >Which is very much unlike what a program does. You're saying "Program that run continuously every time you make any change are very much unlike what a program does?" That doesn't make any sense to me at all, can you please try to rephrase it? Speaking of program that run continuously, have you ever seen Bret Victor's talks "The Future of Programming" and "Inventing on Principle", or heard of Doug Engelbart's work? The Future of Programming link Inventing on Principle ▶ this video HN discussion: link "I'm totally confident that in 40 years we won't be writing code in text files. We've been shown the way [by Doug Engelbart NLS, Grail, Smalltalk, and Plato]." -Bret Victor Do you still maintain that "Excel sheets in their widely used form are not instructions or behaviour", despite the examples and citation I gave you? If so, I'm pretty sure we're not talking about the same Microsoft Excel, or even using the same Wikipedia. Your definition is arbitrarily gerrymandered because you're trying to drag the editor into the definition of the language, while I'm talking about the representation and structure of the language itself, which defines the language, not the tools you use to edit it, which don't define the language. I'll repeat what I already wrote, defining how you can distinguish a non-visual text programming language like C++ from a visual programming language like a spreadsheet or Max/MSP by the number of dimen