1/ A few observations about the binary number toy I made at @Dynamicland1 yesterday:
2/ "UI" comes for free from physical world. Each bit looks to its left for another bit to combine with, so you can play and create new numbers just by rearranging the bits.
3/ Each bit contains behavior, not just data. The bit looks for bits to its left, figures out the combined bit string, computes the decimal value, and labels itself. Spatial search and illumination taken care of by Realtalk OS so all pretty easy
4/ @acwervo had made a rainbow visualizer powered by a rotating dial. In a couple minutes we were able to easily connect the binary number to the rainbows, just by making the binary thing claim it was a new type of "dial"
5/ The whole thing took very little time to make and was kind of a casual side project we were playing with as we had a conversation at the table. when's the last time you casually programmed while having a conversation?
• • •
Missing some Tweet in this thread? You can try to
force a refresh
A workflow I'm enjoying: "Walk-driven development"
> go on a nice walk outside 🚶
> record a long audio note: ideas, goals, things to build 🎙️
> agent auto-creates docs/tasks, and kicks off cloud coding agents for me 🤖
This is kind of an extension of doing a simple prompt by voice. It's nice because I can capture very broad and deep context, not just a single task at once
Probably many tools that can achieve this setup, but Notion is a pretty sweet way to do it because it's all-in-one. Record a meeting note in mobile app. Ask agent to create docs and tasks in Notion. Done. All on the go.
Hot take: I think it's still important to understand the code that our agents write!
In this mega thread (based on my AIE talk today), I will explain why that's the case, and show some ideas for how to efficiently understand code. Alright, let's dive in. 1/
Agents are writing more and more code for us, and we all know it's getting harder to keep up.
But the good news is: there are many ways to understand code! Reading diffs line by line is not the only way. 2/
Most of this thread will be about techniques I have found helpful to understand systems my agents are building:
> Code explaner docs
> Quizzes to check my understanding.
> Micro worlds that I can play with to understand the system.
But first we have to ask a more basic question... 3/
In the physical world, you can adapt your creative environments, in small and big ways. You can organize your kitchen, mix and match knives and pots and pans, drill some hooks into the ceiling.
You can just naturally tweak things as needs arise!
2/
Unfortunately, software is usually missing this adaptability. Companies build apps that you can't change.
Maybe you can tweak settings or even install plugins, but many changes are off limits...
3/
Siri: responds immediately with a written sentence that I can read in the blink of an eye. Efficient.
ChatGPT: takes a while, slowly speaks out loud the answer
Takeaway for me: if I’m engaged with the task and can look at a screen, voice input + visual output is a nice efficient combo. Voice input is faster than typing but don’t necessarily need voice *output*