ブライアンイーノが「Ambient for airport」で用いた手法である、いくつかのフレーズの再生スピードを変えてジェネラティブにアンビエントを作る手法参考に、視覚要素を入れてみた。ランダムネスに飛び交うボールが壁や互いにぶつかると中央でサークルに記録されたフレーズの再生速度が変わるオーディオビジュアルスケッチ。
I tried to add visual elements as a reference to the method of changing the playback speed of some phrases and creating an ambient to the generator, which is the method used by Brian Eino in "Ambient for airport". An audio-visual sketch that changes the playback speed of the phrase recorded in the circle in the center when the balls flying around the randomness collide with the wall or each other.
https://t.co/chPlFgPA3N
@yanirnulman 100%
just got my @sandbar stream ring and this fits the bill - amazing device that does something no other device can do
superb iOS integation and a fairly reasonable $250 price point
Love Max’s project that lets you surf the amazing, hand-curated images of https://t.co/VOkgUvttzh by clicking through visually similar content— feels like surfing embedded Wikipedia links/wikirace
Also thankfully low on AI images bc of https://t.co/VOkgUvttzh’s human user base
In July we open-sourced a dynamic graph of everything a child learns in primary school. 1,590 concepts, 3,221 dependencies.
Now we’re turning every concept into interactive experiments kids can play and learn from.
First one, age 7: heat and water.
Everything that used to be a boring textbook can now be an engaging experience, potentially tailored to every child.
Kids education just got a massive upgrade.
@yanirnulman@reed i still use mine and it's wild what you guys built - the hardware has all it needs to ride the wave of serverside LLM improvements - it's nuts
i'm using it for plant identification w/ Gemini + photos of my kids + tornado siren facts for my tornado siren obsessed toddler lol
@daylightco the drawing tool staying the same size is brilliant for the notes overlay when you zoom - your thought's "volume" (which you feel via writing size) doesn't change but it's relationship to the whole collection of ideas captured in the picture plane does. WOOF. love it
Quick rant and thoughts on the state of software design & engineering. It comes as no surprise that the models have allowed designers to implement and explore their wildest dreams. But I cannot explain enough how much more important that makes understanding the lowest levels of the stack
Take for example these demos. It turns out that instant launch, a fast + instantly zoomable grid, and morphing photo clusters onto the surface of a globe are actually all underpinned by the same technical component: a really fast image thumbnail cache (and cache management). There is a lot more detail that goes into making each experience independently high quality, but that cache is the biggest performance bottleneck for each one - because ultimately they all depend on extremely fast data retrieval to even exist. You can’t use a globe that doesn’t spin and you can’t use a grid you can’t see or scroll. Therefore they never get built and die in imagination land. Achieving your design goals requires being able to identify their core infrastructural overlap
Obviously you don’t need to know every detail, but it’s now your responsibility now to use the models to help you uncover your unknown unknowns about the hidden connections in any system you are building. The proper solution is latent in your unoptimized code. Its complexity is the raw material you need to chisel away at and navigate to the “correct” side of the solution space
Will the models be able to come to conclusions like this autonomously soon? Yes. I think there will need to be advancements in the ability to quickly reason about and quantify the complexity (whatever that means) of a given piece of software and instantly determine what to chop up / refactor / redesign as it develops into its simplest possible form. That might not mean the fewest or tersest LOC but perhaps how few turns it takes a model to achieve a verified solution to any given task, or how tangled its code reference graph is.
But I think it will always be an advantage to know where to poke