Another great video from Bret Victor.
Starting from the point that I think is also very important: if you want to invent stuff, come up with new things, you *have* to be able to quickly iterate, what’s more: you have to be able to quickly iterate *and* be able to understand what went wrong in the first place.
Bret comes up with a ‘seeing space’ where every bit of data in an experiment is recorded, and can be investigated and compared, both across time and across different alternative solutions.
Now, before we can record and use data in that much detail, we need smarter materials, ánd an ecosystem that supports receiving data from those materials, and displaying it in meaningful ways.
I’m all for it!
I can imagine building a seeing space for software engineers as well. All those functions, callbacks etc can already be tracked and displayed visually in order to find bugs in software where it doesn’t do what you expect. Sure, we have debuggers, but they assume that you know whén something goes wrong and they also assume that you only want to see the data/state of that very moment. I want to be able to browse through time and see all those variables change, follow the execution paths, understand everything that leads up to an error. Now thát would be cool for software developers like me.
And it might serve as a first step, a ‘proof of concept’ of sorts for building those seeing spaces for the more hardware-oriented projects like the ones that Bret is initially focussing on. Does anyone know if this already exists or if there are projects doing this?