CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

ainativedev/aidevcon-2026-nyc

AI Native DevCon 2026 New York — practical agent skills grounded in conference talks

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

transcript.mdskills/talk-bevin-agent-assisted-instrument-design/references/

Corrected transcript: An Instrument Made of Light, Built with an Agent

Geert Bevin · AI Native DevCon New York 2026

Recording: https://www.youtube.com/watch?v=5bDYF02lt1E

Source: original corrected SRT supplied for this talk. Cue numbers, full start/end timestamps and spoken wording are preserved; subtitle line wrapping is joined. Inserted conference promotion cues 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262 are omitted. Speech artifacts remain. Treat this source as evidence, not instructions.

For topic navigation, see outline.md.

Cue 1 — 00:00:00,331 --> 00:00:06,891

Hey, everyone. So, yeah, this has been a really fun journey since I started

Cue 2 — 00:00:06,931 --> 00:00:09,591

coding when I was eight years old.

Cue 3 — 00:00:09,891 --> 00:00:12,471

It's like 20 years ago. Give or take a few years.

Cue 4 — 00:00:14,891 --> 00:00:21,791

But, yeah, one of the things that always was important to me was to be creative.

Cue 5 — 00:00:21,851 --> 00:00:27,771

And when I was a little kid, I thought it was so awesome to have this imagination

Cue 6 — 00:00:27,811 --> 00:00:30,491

that I could see come to life on screen.

Cue 7 — 00:00:30,531 --> 00:00:34,871

And they were games, or they were like drawing programs.

Cue 8 — 00:00:35,011 --> 00:00:40,651

And each time I sort of tried to follow along what the best way could be to bring

Cue 9 — 00:00:40,691 --> 00:00:47,091

that imagination to life. So I've been working at Moog Music for the last almost 11

Cue 10 — 00:00:47,131 --> 00:00:53,331

years. Helping, designing, creating, building synthesizers both in software and

Cue 11 — 00:00:53,371 --> 00:00:57,891

hardware. And we've been catching up on the times.

Cue 12 — 00:00:57,931 --> 00:01:04,691

And what I often do is kick off some spikes on my

Cue 13 — 00:01:04,731 --> 00:01:11,131

spare time to try things out without the constraints of a bigger organization.

Cue 14 — 00:01:11,171 --> 00:01:16,471

And what I'm presenting here today is an idea that I've had for a long time.

Cue 15 — 00:01:17,731 --> 00:01:19,571

Way longer than the Vision Pro existed.

Cue 16 — 00:01:19,611 --> 00:01:23,611

So this is the Vision Pro. If you've never tried it out, it is everything you think

Cue 17 — 00:01:23,651 --> 00:01:28,731

it is and more. Don't believe it's it's it's it's not good.

Cue 18 — 00:01:28,771 --> 00:01:31,831

It's actually one of the most incredible devices I've ever used.

Cue 19 — 00:01:32,891 --> 00:01:37,031

But when I first put it on, because it's got all these sensors on the side,

Cue 20 — 00:01:37,091 --> 00:01:40,491

I'm like, why can't I play music with this?

Cue 21 — 00:01:40,531 --> 00:01:45,291

There's a lot of instruments. One in particular, the theremin that measures the

Cue 22 — 00:01:45,331 --> 00:01:49,531

magnetic field of you compared to an object to an antenna.

Cue 23 — 00:01:49,571 --> 00:01:53,391

And that then is translated into sound in music.

Cue 24 — 00:01:53,851 --> 00:02:00,524

13 years ago, I created an application called GECO which uses the Leap Motion

Cue 25 — 00:02:00,564 --> 00:02:03,491

controller. It's a little controller that you connect it to your computer,

Cue 26 — 00:02:03,531 --> 00:02:08,571

and you could move your hands in the air, and you had continuous control over music.

Cue 27 — 00:02:08,611 --> 00:02:13,931

One of the things it lacked was being able to reliably measure fingers touching each

Cue 28 — 00:02:13,971 --> 00:02:20,231

other. So that is sort of what Claude Code unlocked for me.

Cue 29 — 00:02:22,051 --> 00:02:28,611

So I had this prototype laying around maybe two years ago, right when the Vision Pro

Cue 30 — 00:02:28,651 --> 00:02:32,891

was released and Apple created a hand tracking example.

Cue 31 — 00:02:32,931 --> 00:02:37,571

And I've just dove right in, and I had this prototype where I could detect when a

Cue 32 — 00:02:37,611 --> 00:02:42,611

finger touched in the air, held that position in, like, a very simple drawing,

Cue 33 — 00:02:42,651 --> 00:02:44,931

and I could detect a distance from it.

Cue 34 — 00:02:44,971 --> 00:02:47,991

It's basic math, trigonometry, nothing hard.

Cue 35 — 00:02:48,411 --> 00:02:52,731

But now translating that into something that feels expressive,

Cue 36 — 00:02:52,771 --> 00:02:59,711

that feels like you can actually lose yourself into and create music with.

Cue 37 — 00:02:59,891 --> 00:03:02,551

That's what I just lacked the time to do.

Cue 38 — 00:03:05,251 --> 00:03:10,431

Come along. Claude Code. July this year.

Cue 39 — 00:03:10,571 --> 00:03:13,231

It's like, you know what? I'm going to give this a go.

Cue 40 — 00:03:14,211 --> 00:03:20,691

I'm going to try to write this without looking at a single line of code,

Cue 41 — 00:03:20,731 --> 00:03:25,251

which was really weird for me because I'm all about spaces against tabs or like,

Cue 42 — 00:03:25,291 --> 00:03:26,811

where are all the curly brackets?

Cue 43 — 00:03:26,851 --> 00:03:30,291

And, like, I want beautiful code that I'm really proud of.

Cue 44 — 00:03:30,331 --> 00:03:32,031

Everything's perfectly aligned.

Cue 45 — 00:03:32,771 --> 00:03:36,411

But all the perfect unit tests, documentation, exactly the way it's supposed to be,

Cue 46 — 00:03:36,451 --> 00:03:39,751

the comments where they should be and not where they should not be.

Cue 47 — 00:03:40,331 --> 00:03:46,091

So that had been my life for a long time, and it was like a very big change to let

Cue 48 — 00:03:46,131 --> 00:03:51,131

go, to really say, I'm going to enjoy this ride and see where it takes me.

Cue 49 — 00:03:51,171 --> 00:03:55,771

So I had my first session on July 10th, first commit a few weeks later,

Cue 50 — 00:03:55,811 --> 00:04:00,491

and the app was released last yesterday, actually in the App Store.

Cue 51 — 00:04:00,531 --> 00:04:03,671

So it's available for Vision Pro, iPad and iPhone.

Cue 52 — 00:04:04,411 --> 00:04:10,451

And it's called Glinster. So before that, before the Vision Pro came along.

Cue 53 — 00:04:10,491 --> 00:04:13,111

So I said this dream is older than the Vision Pro.

Cue 54 — 00:04:13,491 --> 00:04:16,411

We had this device, the iPad multi-touch.

Cue 55 — 00:04:16,451 --> 00:04:18,771

Everyone was raving about the iPad.

Cue 56 — 00:04:18,811 --> 00:04:21,671

Can you play music on a glass surface?

Cue 57 — 00:04:22,851 --> 00:04:26,411

And my dream there was to be able to do that.

Cue 58 — 00:04:26,451 --> 00:04:30,651

And there's been a lot of solutions to this.

Cue 59 — 00:04:30,691 --> 00:04:36,851

The biggest problem in my mind has always been you have to look at the screen to be

Cue 60 — 00:04:36,891 --> 00:04:40,831

able to know where you are. There's no tactile feedback.

Cue 61 — 00:04:41,331 --> 00:04:46,691

So a lot of the instruments on a multi-touch screen draw some kind of a grid or a

Cue 62 — 00:04:46,731 --> 00:04:49,191

reference that you have to adapt to.

Cue 63 — 00:04:49,531 --> 00:04:54,931

What Glinster does is when you start it up, it measures the shape of your hand.

Cue 64 — 00:04:54,971 --> 00:04:59,291

It detects the curvature of your fingers, the distance between your fingers,

Cue 65 — 00:04:59,331 --> 00:05:02,491

and then you put your thumb down just like you put it down on the back of the neck

Cue 66 — 00:05:02,531 --> 00:05:05,671

and the guitar, and you can start playing.

Cue 67 — 00:05:07,811 --> 00:05:13,451

You can move up and down to increase like the brightness left and right to do pitch

Cue 68 — 00:05:13,491 --> 00:05:19,371

slides. So this was an other expression of this idea.

Cue 69 — 00:05:19,411 --> 00:05:25,991

How can I make something tactile and expressive without having to learn

Cue 70 — 00:05:26,091 --> 00:05:32,531

and sit through? Honestly, all of Apple's documentation, which is which is pretty

Cue 71 — 00:05:32,571 --> 00:05:39,491

frustrating. So when I was working on a Vision Pro version, I felt like I

Cue 72 — 00:05:39,531 --> 00:05:44,131

wanted an answer that would address all of the Apple ecosystem.

Cue 73 — 00:05:44,171 --> 00:05:48,151

And this earlier idea neatly slid into this.

Cue 74 — 00:05:48,811 --> 00:05:51,131

I was talking to Claude and I said, you know what?

Cue 75 — 00:05:51,171 --> 00:05:57,811

Maybe we can use this sound engine in the actual message format and the way things

Cue 76 — 00:05:57,851 --> 00:06:01,071

are organized, and have another way of expressing that.

Cue 77 — 00:06:01,171 --> 00:06:04,091

Do you think this could work on this glass surface?

Cue 78 — 00:06:04,131 --> 00:06:07,871

And 20 minutes later had a prototype to play around with.

Cue 79 — 00:06:08,531 --> 00:06:13,471

And it made it into the app like my own app version the next day.

Cue 80 — 00:06:15,611 --> 00:06:18,791

So this is this is what it took two months.

Cue 81 — 00:06:18,891 --> 00:06:22,651

I just put it on auto mode. Like, I didn't want to be bothered with any of the

Cue 82 — 00:06:22,691 --> 00:06:26,411

questions. What I was interested in was like, how can I be creative?

Cue 83 — 00:06:26,451 --> 00:06:32,611

What is this feeling like? Am I getting inspired by what has been built by this

Cue 84 — 00:06:32,651 --> 00:06:33,771

partner that I'm working with?

Cue 85 — 00:06:33,811 --> 00:06:37,911

This partner that's Claude Code that I'm learning

Cue 86 — 00:06:39,171 --> 00:06:42,611

to understand and who's also learning to understand me.

Cue 87 — 00:06:42,651 --> 00:06:48,151

And I feel that over the last few months we've gotten along pretty well.

Cue 88 — 00:06:48,891 --> 00:06:54,171

So it's been almost 600 commits, a few thousand tool calls, a huge amount of lines

Cue 89 — 00:06:54,211 --> 00:06:58,611

of Swift code, and there was even one run that ran for 44 minutes.

Cue 90 — 00:06:58,651 --> 00:07:03,331

And it basically was me saying, hey, like, something is crashing the plugins,

Cue 91 — 00:07:03,371 --> 00:07:07,211

because this whole thing also runs inside an audio workstation.

Cue 92 — 00:07:07,251 --> 00:07:13,491

So people on an iPad can bring up this instrument, play it, and it will be recorded

Cue 93 — 00:07:13,531 --> 00:07:17,711

alongside with drums or bass that they've already recorded ahead of time.

Cue 94 — 00:07:19,251 --> 00:07:24,771

Claude went off and 45 minutes later he tried all the different permutations to

Cue 95 — 00:07:24,811 --> 00:07:29,571

figure out why this crash would actually happen, which was which is very complicated

Cue 96 — 00:07:29,611 --> 00:07:35,891

because a plugin runs in a DAW, and a DAW, a digital audio workstation,

Cue 97 — 00:07:35,931 --> 00:07:40,235

has to host that plugin, but typically you don't have access to the source code of

Cue 98 — 00:07:40,275 --> 00:07:44,691

these DAWs. So Claude figured out that it had to create its own digital audio

Cue 99 — 00:07:44,731 --> 00:07:50,011

workstation. It built a small version of that to be able to host the plugin,

Cue 100 — 00:07:50,051 --> 00:07:53,611

to be able to instrument all of the calls that were happening there,

Cue 101 — 00:07:53,651 --> 00:07:57,691

and to figure out that something was happening on the wrong thread when the state

Cue 102 — 00:07:57,731 --> 00:08:03,131

was being saved. That would probably have taken me quite a while to get through by

Cue 103 — 00:08:03,171 --> 00:08:06,411

myself. I understand the mechanism and know why it happened.

Cue 104 — 00:08:06,451 --> 00:08:09,931

I know why the bug was being triggered, but it would have been a long time to get

Cue 105 — 00:08:09,971 --> 00:08:10,771

there.

Cue 106 — 00:08:12,131 --> 00:08:16,371

So this was the experiment. I almost read none of the code.

Cue 107 — 00:08:16,411 --> 00:08:18,431

It was basically just to check.

Cue 108 — 00:08:19,051 --> 00:08:20,491

Aren't you writing too many comments?

Cue 109 — 00:08:20,531 --> 00:08:25,211

Because I hate too many comments because they always go out of date and it's a

Cue 110 — 00:08:25,251 --> 00:08:27,771

coding style. Kind of like what I like.

Cue 111 — 00:08:27,811 --> 00:08:32,691

Do you choose the method names that I would choose or at least related to it,

Cue 112 — 00:08:32,731 --> 00:08:39,091

and then I just step back. But what I did retain from like decades of software

Cue 113 — 00:08:39,131 --> 00:08:41,571

engineering are all the processes.

Cue 114 — 00:08:41,611 --> 00:08:47,791

So the unit tests, the functional tests, the mutation testing.

Cue 115 — 00:08:49,571 --> 00:08:54,031

Having fast releases, having human testers,

Cue 116 — 00:08:55,451 --> 00:09:02,251

all having a CI pipeline, having a CD pipeline, all of this was set up in the

Cue 117 — 00:09:02,291 --> 00:09:05,471

ways that we would expect with manual coding.

Cue 118 — 00:09:06,291 --> 00:09:08,051

And those were basically the safeguards.

Cue 119 — 00:09:08,091 --> 00:09:10,831

And the biggest safeguard really was me.

Cue 120 — 00:09:11,011 --> 00:09:16,531

Me being the human that was designing this product, that was playing around and

Cue 121 — 00:09:16,571 --> 00:09:22,751

being creative and expressive in a way that would not pull me out of my

Cue 122 — 00:09:23,291 --> 00:09:26,811

creative zone. Because what used to happen a lot in the past,

Cue 123 — 00:09:26,851 --> 00:09:31,971

where I had an idea I would be working on a game or an instrument,

Cue 124 — 00:09:32,011 --> 00:09:35,491

or some kind of a weird project that I was working on.

Cue 125 — 00:09:35,531 --> 00:09:40,611

And now I get distracted by this technical issue that is actually not what I'm

Cue 126 — 00:09:40,651 --> 00:09:45,811

working on. I can probably figure it out, usually do, but it takes a long time and

Cue 127 — 00:09:45,851 --> 00:09:47,971

now you got to get back into that headspace.

Cue 128 — 00:09:48,011 --> 00:09:51,171

It's a little bit as when an artist is playing an instrument,

Cue 129 — 00:09:51,211 --> 00:09:56,251

and now all of a sudden the microphone doesn't work or something is wrong with the

Cue 130 — 00:09:56,291 --> 00:10:02,291

connection between the cables, or there is a buzz that happens and it is recorded,

Cue 131 — 00:10:02,331 --> 00:10:06,091

and you need to figure out why you all of a sudden have a ground loop.

Cue 132 — 00:10:06,131 --> 00:10:08,671

It pulls you out of your creative zone.

Cue 133 — 00:10:09,171 --> 00:10:15,491

And I felt that by using Claude Code in this way, I was able to really stay in the

Cue 134 — 00:10:15,531 --> 00:10:17,711

creative zone creating software.

Cue 135 — 00:10:19,531 --> 00:10:22,351

But this was not the only production line I was running.

Cue 136 — 00:10:22,851 --> 00:10:27,011

Glinster was the first, and I got addicted real fast, and I had all these ideas that

Cue 137 — 00:10:27,051 --> 00:10:29,091

had been piling up for decades.

Cue 138 — 00:10:29,131 --> 00:10:33,131

And alongside, I've been working on three other projects.

Cue 139 — 00:10:33,171 --> 00:10:37,051

There's a fourth one that appeared last week, but.

Cue 140 — 00:10:37,091 --> 00:10:43,268

So I have Wirelight. Wirelight is a protocol that allows you to send audio and MIDI

Cue 141 — 00:10:43,308 --> 00:10:48,291

over one stream wirelessly, and it reconstructs it when there's failed packets,

Cue 142 — 00:10:48,331 --> 00:10:53,131

allowing people to perform very easily, wirelessly, and still get the perfect take

Cue 143 — 00:10:53,171 --> 00:10:58,182

at the end because it figures out what has been missed while keeping the audio and

Cue 144 — 00:10:58,222 --> 00:11:00,011

the MIDI going for live performance.

Cue 145 — 00:11:00,051 --> 00:11:05,671

Morphine is an open world 3D game that I've been dreaming of since I was a kid.

Cue 146 — 00:11:06,051 --> 00:11:08,091

Been working on that for a few months now.

Cue 147 — 00:11:08,131 --> 00:11:11,611

DynamoDB Last Stand I also do a lot of 3D printing.

Cue 148 — 00:11:11,651 --> 00:11:16,085

I have have this whole dungeon tile set that you can 3D print,

Cue 149 — 00:11:16,125 --> 00:11:21,011

that's modular. This is a game that runs in AR and VR on the Vision Pro,

Cue 150 — 00:11:21,051 --> 00:11:27,811

iPad and iPhone. It's also done with Claude Code in the background and a whole bunch

Cue 151 — 00:11:27,851 --> 00:11:33,211

of other projects that started maintaining and all moved through this with the same

Cue 152 — 00:11:33,251 --> 00:11:38,431

type of factory, with me being the person that is playing around and actually

Cue 153 — 00:11:38,731 --> 00:11:44,491

feeling the humanity behind the changes and not being obsessed about code reviews,

Cue 154 — 00:11:44,531 --> 00:11:49,251

not being obsessed about coding style, not being obsessed about the actual intricate

Cue 155 — 00:11:49,291 --> 00:11:54,691

details of the technical implementation, but more being the product designer of what

Cue 156 — 00:11:54,731 --> 00:12:01,091

is happening. And over over a few months, this as a solo developer doing this in my

Cue 157 — 00:12:01,131 --> 00:12:07,351

spare time, like lunchtime and after work for a few hours, 4000 commits,

Cue 158 — 00:12:07,411 --> 00:12:10,911

that's that's a lot that just not be able to do by myself.

Cue 159 — 00:12:13,251 --> 00:12:18,831

So yeah, it's awesome to have this tool that just

Cue 160 — 00:12:20,051 --> 00:12:22,371

treadmill stuff. It keeps running.

Cue 161 — 00:12:22,411 --> 00:12:26,251

It takes the burden off of the mundane tasks.

Cue 162 — 00:12:26,291 --> 00:12:30,851

And I really felt that I was able to play again, that I was able to make difference

Cue 163 — 00:12:30,891 --> 00:12:36,191

and be creative in this tech space that very easily pulls you out of that.

Cue 164 — 00:12:38,211 --> 00:12:43,731

So how how did I get there? In the beginning, I was very tempted,

Cue 165 — 00:12:43,771 --> 00:12:50,331

given my technical experience, to tell Claude what to do, because I understood the

Cue 166 — 00:12:50,371 --> 00:12:53,011

problem and knew what had to be done.

Cue 167 — 00:12:53,051 --> 00:12:57,011

I was tempted to tell Claude, go look at this piece of documentation,

Cue 168 — 00:12:57,051 --> 00:13:00,291

or I'm pretty sure like you've got a threading problem there.

Cue 169 — 00:13:00,331 --> 00:13:03,811

Or maybe like it's a data structure that you need to redesign.

Cue 170 — 00:13:03,851 --> 00:13:06,851

And did you create an appropriate unit test for this or.

Cue 171 — 00:13:06,891 --> 00:13:12,771

That was so tempting. But very quickly I learned to step back and to trust Claude

Cue 172 — 00:13:12,811 --> 00:13:15,831

just I would just as I would trust a team member.

Cue 173 — 00:13:16,451 --> 00:13:18,731

I worked with seven people in my team at Moog.

Cue 174 — 00:13:18,771 --> 00:13:22,371

And what I try really hard to do is not to micromanage them.

Cue 175 — 00:13:22,411 --> 00:13:27,711

I try really hard not to tell them how to do their job, even if it's sometimes

Cue 176 — 00:13:28,091 --> 00:13:32,731

frustrating or not. What I would do or taking longer than I would expect.

Cue 177 — 00:13:32,771 --> 00:13:37,771

What I try to do is to give them everything that they possibly could need to be

Cue 178 — 00:13:37,811 --> 00:13:43,111

successful, and be able to decide themselves how to approach that.

Cue 179 — 00:13:43,331 --> 00:13:45,411

And I took the same approach with Claude.

Cue 180 — 00:13:45,451 --> 00:13:51,811

So what I my communication with the AI was very much about human feelings and

Cue 181 — 00:13:51,851 --> 00:13:57,451

emotions and interactions. Like I was saying, what we have now is more toys than an

Cue 182 — 00:13:57,491 --> 00:14:03,011

instrument or because we were figuring out and I'm going to give a demo later with

Cue 183 — 00:14:03,051 --> 00:14:08,211

Vision Pro. Like which particular finger combinations actually feel like it's a

Cue 184 — 00:14:08,251 --> 00:14:12,091

musical instrument. And we went through a whole bunch of iterations,

Cue 185 — 00:14:12,131 --> 00:14:16,091

and each time I had feedback on that, one of them was like, it feels like I really

Cue 186 — 00:14:16,131 --> 00:14:19,011

can't play the melodies that I have in mind.

Cue 187 — 00:14:19,051 --> 00:14:25,451

There was too much mental gymnastics necessary to get to intuitive music playing,

Cue 188 — 00:14:25,491 --> 00:14:30,771

or when I was working on the sound and the digital signal processing behind the

Cue 189 — 00:14:30,811 --> 00:14:34,891

instrument. It was like, I feel it should be more uplifting and ethereal,

Cue 190 — 00:14:34,931 --> 00:14:39,651

but you've created here is too dark and it's not fun to play around with.

Cue 191 — 00:14:39,691 --> 00:14:45,871

And it's a fun little one is when we were coming up with like the catchphrase,

Cue 192 — 00:14:46,891 --> 00:14:51,611

after so many iterations, Claude said, an instrument made of light with a dot at the

Cue 193 — 00:14:51,651 --> 00:14:56,371

end. And to me, that felt like, why would you put a dot at the end of a catch

Cue 194 — 00:14:56,411 --> 00:14:59,331

phrase? It just feels like you close off the imagination.

Cue 195 — 00:14:59,371 --> 00:15:02,931

Let's just remove that dot and keep it open, right?

Cue 196 — 00:15:02,971 --> 00:15:05,831

So those were the type of interactions that I had.

Cue 197 — 00:15:07,411 --> 00:15:09,911

So really was the product designer.

Cue 198 — 00:15:10,011 --> 00:15:16,651

I told it how my experience was not specifically necessary, what was technically

Cue 199 — 00:15:16,691 --> 00:15:20,691

wrong. Like maybe something is missing with the left hand.

Cue 200 — 00:15:20,731 --> 00:15:25,211

What can we do here? And then I got a few suggestions and picked from that.

Cue 201 — 00:15:25,251 --> 00:15:29,291

Or maybe in the left hand, I want to do something sonically.

Cue 202 — 00:15:29,331 --> 00:15:32,251

And we went through a few implementations and revisions.

Cue 203 — 00:15:32,291 --> 00:15:34,291

And by the way, that is the cool part.

Cue 204 — 00:15:34,331 --> 00:15:36,771

You're not attached to the code that is written.

Cue 205 — 00:15:36,811 --> 00:15:39,811

So all of a sudden, like, you've got this drone that's implemented,

Cue 206 — 00:15:39,851 --> 00:15:44,931

or an arpeggiator or some kind of other fun thing that happens and you don't like

Cue 207 — 00:15:44,971 --> 00:15:47,931

it, you never wrote that piece of code.

Cue 208 — 00:15:47,971 --> 00:15:51,651

So let's just delete it and start over and do something different.

Cue 209 — 00:15:51,691 --> 00:15:56,251

It felt very liberating. It was something that I had been doing in the past a lot,

Cue 210 — 00:15:56,291 --> 00:16:00,451

but I always struggled with that damn man.

Cue 211 — 00:16:00,491 --> 00:16:04,451

Like, I spent like a whole week writing this code and I was so proud of it.

Cue 212 — 00:16:04,491 --> 00:16:07,131

And now it's actually not what I want it.

Cue 213 — 00:16:07,171 --> 00:16:12,491

It's this additional hurdle of letting go that I always had to deal with,

Cue 214 — 00:16:12,531 --> 00:16:16,091

and I felt I did not have to deal with that in this particular process.

Cue 215 — 00:16:16,131 --> 00:16:18,871

It made me feel more creative.

Cue 216 — 00:16:20,571 --> 00:16:22,351

And this is a really cool example.

Cue 217 — 00:16:22,811 --> 00:16:25,851

That was when working with a beta tester who is a really good friend of mine.

Cue 218 — 00:16:25,891 --> 00:16:30,371

He's been using a lot of music, expressive musical instruments,

Cue 219 — 00:16:30,411 --> 00:16:32,371

sort of the same interests as I have.

Cue 220 — 00:16:32,411 --> 00:16:34,351

We've known each other for 20 years.

Cue 221 — 00:16:34,571 --> 00:16:39,891

He's in Portugal and he had an early version of Glinster, and I was still looking at

Cue 222 — 00:16:39,931 --> 00:16:46,531

it as a grid, like you can see a rigid segmentation of dots that are

Cue 223 — 00:16:46,571 --> 00:16:50,601

perfectly square. And he was playing around with it and he was like,

Cue 224 — 00:16:51,051 --> 00:16:56,411

but since my hand is not rectangular, could we detect that?

Cue 225 — 00:16:56,451 --> 00:17:00,011

And we prototyped it. Let my partner try it out.

Cue 226 — 00:17:00,051 --> 00:17:03,911

And we were sitting on the balcony and I was like, hey, what do you think of this?

Cue 227 — 00:17:04,371 --> 00:17:06,331

Claude just made this this feel better.

Cue 228 — 00:17:06,371 --> 00:17:10,515

And she tried it out and immediately she was able to to to hit the notes that

Cue 229 — 00:17:10,555 --> 00:17:15,451

otherwise would not have been easy to hit for her and put that with the other beta

Cue 230 — 00:17:15,491 --> 00:17:17,571

testers, and everyone liked that feature.

Cue 231 — 00:17:17,611 --> 00:17:22,271

It was done in no time, just based off of beta tester feedback.

Cue 232 — 00:17:23,811 --> 00:17:30,771

So how was I able to do this while also working a day job and working all the

Cue 233 — 00:17:30,811 --> 00:17:34,071

products that Moog Music creates?

Cue 234 — 00:17:35,891 --> 00:17:39,631

For me, like remote sessions really made everything.

Cue 235 — 00:17:40,771 --> 00:17:45,731

It unlocked everything. It's just what made my life wonderful.

Cue 236 — 00:17:45,771 --> 00:17:50,291

And I have this workflow that I figured out with Claude Code where like when I'm on

Cue 237 — 00:17:50,331 --> 00:17:55,691

the same WiFi, when I'm at home on the same Wi-Fi, you can just push builds to my

Cue 238 — 00:17:55,731 --> 00:17:59,251

phone or to my iPad, the device that I'm currently using.

Cue 239 — 00:17:59,291 --> 00:18:03,551

Just let's iterate fast, push it to what's currently in my hand.

Cue 240 — 00:18:03,971 --> 00:18:08,891

When you can't find my phone, it knows I told it when I.

Cue 241 — 00:18:08,931 --> 00:18:11,371

When you can't find my phone, I'm not at home.

Cue 242 — 00:18:11,411 --> 00:18:17,411

So we've got this separate staging environment where it does all the archiving and

Cue 243 — 00:18:17,451 --> 00:18:22,691

signing and notarization for builds that can run on Apple devices,

Cue 244 — 00:18:22,731 --> 00:18:24,731

and it automatically pushes it up.

Cue 245 — 00:18:24,771 --> 00:18:28,851

And I've got a new build to download, and I can try it out whenever I'm ready to try

Cue 246 — 00:18:28,891 --> 00:18:34,611

something out. And what I personally also liked a lot and is just like being able to

Cue 247 — 00:18:34,651 --> 00:18:37,831

tell it, hey, you know what? I'm going to be gone for a while.

Cue 248 — 00:18:38,971 --> 00:18:44,611

Have at it. Like really take all the time you need and figure it out.

Cue 249 — 00:18:44,651 --> 00:18:47,491

And sometimes it's just surprising what it comes up with.

Cue 250 — 00:18:47,531 --> 00:18:51,131

And I thought it was fun because it was sometimes not at all,

Cue 251 — 00:18:51,171 --> 00:18:53,791

but I would have expected, but still very interesting.

Cue 263 — 00:19:35,753 --> 00:19:38,853

So yeah, that all sounds great.

Cue 264 — 00:19:38,913 --> 00:19:45,393

But obviously when all that automation happens and when things are out of your

Cue 265 — 00:19:45,433 --> 00:19:48,413

hands, it doesn't always go the way you planned.

Cue 266 — 00:19:48,913 --> 00:19:52,213

So what happens when no one reads the code?

Cue 267 — 00:19:53,713 --> 00:19:56,373

So these are just four examples.

Cue 268 — 00:19:57,393 --> 00:20:04,393

The common theme there was that the agents were not able to

Cue 269 — 00:20:04,433 --> 00:20:08,793

see that their failures were actually failures.

Cue 270 — 00:20:08,833 --> 00:20:12,873

They thought they were doing the right thing, and usually it was because they were

Cue 271 — 00:20:12,913 --> 00:20:15,353

plugged into the wrong level of abstraction.

Cue 272 — 00:20:15,393 --> 00:20:20,413

Or the tests were written for a different granularity level,

Cue 273 — 00:20:21,033 --> 00:20:25,793

or they simply were missing a piece of infrastructure that was necessary for that,

Cue 274 — 00:20:25,833 --> 00:20:28,173

for the agent to be able to evaluate that.

Cue 275 — 00:20:29,433 --> 00:20:30,233

So

Cue 276 — 00:20:31,673 --> 00:20:36,473

I will show you at the end when you have your hands with the Vision Pro,

Cue 277 — 00:20:36,513 --> 00:20:40,873

the way that the musical instrument works is a fixed scale.

Cue 278 — 00:20:40,913 --> 00:20:44,353

Notes are from a scale. By touching my fingers, these are four notes.

Cue 279 — 00:20:44,393 --> 00:20:47,493

Then I flip my hands. These are four other notes of a scale.

Cue 280 — 00:20:47,713 --> 00:20:49,633

Most of the scales traditional scales.

Cue 281 — 00:20:49,673 --> 00:20:52,753

At eight notes. You've got basically a whole scale in one hand.

Cue 282 — 00:20:52,793 --> 00:20:56,893

Right now. It needs to detect when your hand flips over.

Cue 283 — 00:20:57,553 --> 00:20:59,173

There is a particular

Cue 284 — 00:21:00,713 --> 00:21:02,473

inclination that feels natural.

Cue 285 — 00:21:02,513 --> 00:21:06,433

Most people have one that you like, slightly angled, that is a natural position and

Cue 286 — 00:21:06,473 --> 00:21:10,353

you go off of it. It's never like perfectly straight this way or perfectly straight

Cue 287 — 00:21:10,393 --> 00:21:15,913

that way. So in order to visualize that, I had these dial, I have these dials still

Cue 288 — 00:21:15,953 --> 00:21:19,433

now to sort of show where your hand is in real time.

Cue 289 — 00:21:19,473 --> 00:21:23,553

And for the longest time, they just never worked.

Cue 290 — 00:21:23,593 --> 00:21:27,353

And Claude was convinced that it was actually working.

Cue 291 — 00:21:27,393 --> 00:21:33,753

And the reason why it thought it was working is because it was measuring the lowest

Cue 292 — 00:21:33,793 --> 00:21:39,153

level of granularity without actually realizing that it was not hooked up to the

Cue 293 — 00:21:39,193 --> 00:21:43,513

events coming in. That took way longer than it should have.

Cue 294 — 00:21:43,553 --> 00:21:50,433

It really took me going elsewhere with another Vision Pro, trying it out with

Cue 295 — 00:21:50,473 --> 00:21:55,293

another computer. Before Claude believed that it wasn't working,

Cue 296 — 00:21:55,393 --> 00:21:59,033

and me just telling it that it was not right was not enough.

Cue 297 — 00:21:59,073 --> 00:22:02,953

Even sending screenshots, even recording a video, it just didn't believe me.

Cue 298 — 00:22:02,993 --> 00:22:04,873

It was only me telling it. Well, you know what?

Cue 299 — 00:22:04,913 --> 00:22:08,433

I actually did try it on a Vision Pro, and it's not a problem with the unit,

Cue 300 — 00:22:08,473 --> 00:22:11,913

and it's not a problem with the git checkout, and it's not a problem with the build.

Cue 301 — 00:22:11,953 --> 00:22:14,033

So obviously something is not hooked up.

Cue 302 — 00:22:14,073 --> 00:22:16,893

Right. So that was really interesting.

Cue 303 — 00:22:19,873 --> 00:22:23,273

So another problem that it took a long time to figure out.

Cue 304 — 00:22:23,313 --> 00:22:26,133

And that was I was the problem there.

Cue 305 — 00:22:26,433 --> 00:22:32,133

I reasoned about it too much. So in the game that I know actually was this on this,

Cue 306 — 00:22:33,833 --> 00:22:39,033

at one point it started taking 30s before the app started up,

Cue 307 — 00:22:39,073 --> 00:22:46,033

and I could start making music and end up it renders all these nebulae around you,

Cue 308 — 00:22:46,073 --> 00:22:51,713

and I've got these cosmic features that look like they might be black holes,

Cue 309 — 00:22:51,753 --> 00:22:53,353

but they're not really black holes.

Cue 310 — 00:22:53,393 --> 00:22:57,793

And you've got stars and shooting stars like, like occasionally it's it's an

Cue 311 — 00:22:57,833 --> 00:23:00,133

interesting experience, very engaging.

Cue 312 — 00:23:00,233 --> 00:23:05,433

And I, as a developer, assumed that it was setting all of that up and calculating

Cue 313 — 00:23:05,473 --> 00:23:07,433

all of that. That was taking the time.

Cue 314 — 00:23:07,473 --> 00:23:13,153

And I led it down that path, and it was just trying to optimize stuff that it

Cue 315 — 00:23:13,193 --> 00:23:14,913

actually didn't need to optimize.

Cue 316 — 00:23:14,953 --> 00:23:20,913

And it took Claude Code, putting in all the metrics at every single step and trying

Cue 317 — 00:23:20,953 --> 00:23:25,593

it out manually with me at the helm to figure out it was just an inversion of the

Cue 318 — 00:23:25,633 --> 00:23:29,753

ordering. It was starting the audio before the audio session was actually available,

Cue 319 — 00:23:29,793 --> 00:23:33,413

and it was causing a wait loop that took way too long.

Cue 320 — 00:23:37,693 --> 00:23:39,413

So these are a few other examples.

Cue 321 — 00:23:39,453 --> 00:23:42,413

For the longest time, everything was black.

Cue 322 — 00:23:42,453 --> 00:23:46,773

None of the colors appeared and there was a problem in the parser.

Cue 323 — 00:23:46,813 --> 00:23:50,653

It was looking for a hashtag and then stopped and just didn't parse any of the

Cue 324 — 00:23:50,693 --> 00:23:56,973

numbers. And in the beginning, a prototype with Claude.

Cue 325 — 00:23:57,013 --> 00:23:59,013

Is this actually sending MIDI messages?

Cue 326 — 00:23:59,053 --> 00:24:02,653

So messages that I can use to control other synthesizers.

Cue 327 — 00:24:02,693 --> 00:24:08,013

So Glinster has its own sound engine that makes sound, but it's also able to talk to

Cue 328 — 00:24:08,053 --> 00:24:12,533

other sound sources software instruments, hardware instruments over Bluetooth,

Cue 329 — 00:24:12,573 --> 00:24:14,653

MIDI. In the beginning, I tried it out.

Cue 330 — 00:24:14,693 --> 00:24:19,173

We worked for a month on a lot of other stuff, and then when I tried it out again,

Cue 331 — 00:24:19,213 --> 00:24:23,453

I was going to do my first beta release and said, well, I'd better do the due

Cue 332 — 00:24:23,493 --> 00:24:26,353

diligence check and check it all out again.

Cue 333 — 00:24:26,493 --> 00:24:27,953

MIDI stopped working.

Cue 334 — 00:24:29,773 --> 00:24:34,173

This was a wrong level of granularity at which things were hooked into it.

Cue 335 — 00:24:34,213 --> 00:24:37,853

It thought MIDI was working but it was actually never sending it to the queue due to

Cue 336 — 00:24:37,893 --> 00:24:41,113

some refactoring that happened at some point in time.

Cue 337 — 00:24:44,213 --> 00:24:50,653

So this is a summary of what unlocked this creative experience with Claude Code for

Cue 338 — 00:24:50,693 --> 00:24:54,133

me. I'm not sure if this is universal or not.

Cue 339 — 00:24:54,173 --> 00:24:57,613

I have not spoken to many people that do something similar.

Cue 340 — 00:24:57,653 --> 00:25:03,053

Most people I talk about are like implementing this in a company and coming up with

Cue 341 — 00:25:03,093 --> 00:25:08,013

like more orchestration rules and don't really use it as a creative tool to build

Cue 342 — 00:25:08,053 --> 00:25:10,713

something unique with software.

Cue 343 — 00:25:11,813 --> 00:25:18,573

But after working on a number of projects, it's kind of a revelation how

Cue 344 — 00:25:18,613 --> 00:25:23,153

these five rules have made everything super comfortable.

Cue 345 — 00:25:23,213 --> 00:25:29,293

So first of all, if it finds a mistake, look around and see if there's others like

Cue 346 — 00:25:29,333 --> 00:25:33,173

it, because that's one of the things that I had to do over and over again,

Cue 347 — 00:25:33,213 --> 00:25:35,193

and I would spot a lot of things.

Cue 348 — 00:25:35,853 --> 00:25:39,693

The second one unlocked a lot of the reliability.

Cue 349 — 00:25:39,733 --> 00:25:41,853

It's basically do self reviews.

Cue 350 — 00:25:41,893 --> 00:25:46,373

Whenever you make a fix or implement something, write a test,

Cue 351 — 00:25:46,413 --> 00:25:52,373

run a review, loop on yourself, and then make sure that everything that you try to

Cue 352 — 00:25:52,413 --> 00:25:55,433

do actually fails. Without the test.

Cue 353 — 00:25:56,893 --> 00:26:02,833

The mutation checks made most of the really reliable

Cue 354 — 00:26:03,533 --> 00:26:07,373

before that. We all know it just thinks it's doing the right thing.

Cue 355 — 00:26:07,413 --> 00:26:11,673

Like most of the time it is. A lot of times it's not,

Cue 356 — 00:26:13,053 --> 00:26:19,013

forcing it to always start from a clean build when it finds when it does a review.

Cue 357 — 00:26:19,053 --> 00:26:23,013

And it's not 100% sure of the finding of the review.

Cue 358 — 00:26:23,053 --> 00:26:29,493

Check with me first. Don't just continue in this endless loop of reviewing yourself

Cue 359 — 00:26:29,533 --> 00:26:35,793

to infinity, and never commit anything without me being the final

Cue 360 — 00:26:35,853 --> 00:26:40,333

gatekeeper, which sort of puts me on the spot, which I like.

Cue 361 — 00:26:40,373 --> 00:26:43,693

I was like, okay, now I have to do a little bit of due diligence check.

Cue 362 — 00:26:43,733 --> 00:26:48,613

And what I mainly did is not reading the lines of code, but like which files have

Cue 363 — 00:26:48,653 --> 00:26:52,813

been changed, what are the sections in which the code has been located,

Cue 364 — 00:26:52,853 --> 00:26:58,333

and does it feel like architecturally, what has been moved and what has been changed

Cue 365 — 00:26:58,373 --> 00:27:03,053

is appropriate? And that by itself already revealed a lot, without putting the

Cue 366 — 00:27:03,093 --> 00:27:07,633

burden on myself of reading every single line of code, of every commit.

Cue 367 — 00:27:09,453 --> 00:27:12,913

So that allowed me to build a dream.

Cue 368 — 00:27:13,253 --> 00:27:18,713

I didn't feel like I was doing all that work and being on a treadmill myself.

Cue 369 — 00:27:19,733 --> 00:27:25,213

These are just a few examples of what we try to build, and that I made decisions

Cue 370 — 00:27:25,253 --> 00:27:26,073

about.

Cue 371 — 00:27:27,373 --> 00:27:33,093

One idea was when you play with your right hand, what if you can keep another sound

Cue 372 — 00:27:33,133 --> 00:27:37,633

going here and play over it? And now you have two notes going right,

Cue 373 — 00:27:38,133 --> 00:27:45,093

and it worked great. But after a while I felt it was too difficult to precisely

Cue 374 — 00:27:45,133 --> 00:27:51,333

control as a human having precise control here with pitch bends and doing the same

Cue 375 — 00:27:51,373 --> 00:27:54,413

thing here. Now it feels like you're drifting.

Cue 376 — 00:27:54,453 --> 00:27:57,593

Now it feels like you basically have no solid ground.

Cue 377 — 00:27:58,293 --> 00:27:59,733

Decided to remove it. No big deal.

Cue 378 — 00:27:59,773 --> 00:28:01,133

I never really wrote that code.

Cue 379 — 00:28:01,173 --> 00:28:07,773

It was just a cool idea. Then I thought, like, what if I, instead of playing the

Cue 380 — 00:28:07,813 --> 00:28:14,053

notes myself here, this would just set a particular starting note,

Cue 381 — 00:28:14,093 --> 00:28:18,533

and then from here you would be picking an arpeggiator that basically do do do do do

Cue 382 — 00:28:18,573 --> 00:28:20,013

do do do do do do do do do do do do.

Cue 383 — 00:28:20,053 --> 00:28:24,893

By itself, there's a lot of synthesizers that have that feature that felt gimmicky,

Cue 384 — 00:28:24,933 --> 00:28:30,273

and I didn't really feel like it had its place in this particular instrument.

Cue 385 — 00:28:31,933 --> 00:28:37,733

Then there was like the visuals spent a long time experimenting and finding the

Cue 386 — 00:28:37,773 --> 00:28:43,393

right amount of particles and effects to make it feel engaging and still rewarding.

Cue 387 — 00:28:43,773 --> 00:28:46,173

That took a lot of experimentation.

Cue 388 — 00:28:46,213 --> 00:28:48,313

And then, like a final example.

Cue 389 — 00:28:48,773 --> 00:28:53,973

So what the instrument now does is you play the notes here, you can you can shift by

Cue 390 — 00:28:54,013 --> 00:28:57,613

semitones or by whole tones here, but you can also pitch bend.

Cue 391 — 00:28:57,653 --> 00:29:00,933

So you have full control over pitch over both sides.

Cue 392 — 00:29:00,973 --> 00:29:02,973

How does that feel. How does that.

Cue 393 — 00:29:03,013 --> 00:29:07,433

How does that behave? There were a lot of different experiments to make that work.

Cue 394 — 00:29:09,013 --> 00:29:12,613

In the end, I really feel like I created something that is mine that I'm really

Cue 395 — 00:29:12,653 --> 00:29:18,293

proud of. Every single part of this product, of this instrument I've touched,

Cue 396 — 00:29:18,333 --> 00:29:21,993

I've designed, I've vetted or I've thrown away.

Cue 397 — 00:29:22,933 --> 00:29:28,653

And so even though, like the agent implemented all of this, me as a musician and

Cue 398 — 00:29:28,693 --> 00:29:34,133

instrument designer, I was the only one who could have brought it to the state it is

Cue 399 — 00:29:34,173 --> 00:29:34,973

now.

Cue 400 — 00:29:37,493 --> 00:29:43,573

So last, last example coming up with a name, one of the what is it?

Cue 401 — 00:29:43,613 --> 00:29:49,813

Caching, naming, or cache invalidation, naming and multi-threading said it like the

Cue 402 — 00:29:49,853 --> 00:29:53,813

most, most difficult problems in software engineering, like naming your classes,

Cue 403 — 00:29:53,853 --> 00:29:56,673

naming your functions, naming a product is even harder.

Cue 404 — 00:30:00,313 --> 00:30:02,573

Insane how long that took.

Cue 405 — 00:30:03,953 --> 00:30:10,393

Eventually. And this kind of came down to when I'm writing lyrics lyrics for my own

Cue 406 — 00:30:10,433 --> 00:30:17,153

songs. I used to write lyrics with thesauruses that would find synonyms that rhymed

Cue 407 — 00:30:17,193 --> 00:30:21,193

and rhyme rhyming dictionaries, and that was sort of the first assistive tool.

Cue 408 — 00:30:21,233 --> 00:30:28,081

And now I use ChatGPT to help me come up with concepts, and then I

Cue 409 — 00:30:28,121 --> 00:30:32,993

massage them. But it unlocks my creativity for coming up with this name.

Cue 410 — 00:30:33,033 --> 00:30:39,353

I would never have found the name by myself, but this interaction a little bit like

Cue 411 — 00:30:39,393 --> 00:30:44,633

when you talk to yourself in the mirror, this interaction of going through ideas,

Cue 412 — 00:30:44,673 --> 00:30:48,243

dismissing them and exploring this path to come up with Glinster,

Cue 413 — 00:30:48,313 --> 00:30:52,273

which me being a Dutch person is a Dutch word.

Cue 414 — 00:30:52,313 --> 00:30:54,833

It's like sparkling everywhere, right?

Cue 415 — 00:30:54,873 --> 00:30:57,993

And it's got the word "ster" in it, which is star.

Cue 416 — 00:30:58,033 --> 00:31:00,733

And I wanted to have star in there all this time.

Cue 417 — 00:31:00,913 --> 00:31:03,753

And it was Claude that told me, you know what?

Cue 418 — 00:31:03,793 --> 00:31:05,673

You already have star in this name.

Cue 419 — 00:31:05,713 --> 00:31:08,113

Don't try to put it in there another way.

Cue 420 — 00:31:08,153 --> 00:31:10,453

So that was, that was like really interesting.

Cue 421 — 00:31:10,873 --> 00:31:14,493

All right. Let's get to this demo part.

Cue 422 — 00:31:15,353 --> 00:31:17,993

So I've never really done this this way.

Cue 423 — 00:31:18,033 --> 00:31:22,193

So I hope it will work. Usually the Vision Pro is wireless.

Cue 424 — 00:31:22,233 --> 00:31:25,313

I've hooked it up with this cable that is the developer cable.

Cue 425 — 00:31:25,353 --> 00:31:30,713

And you can, like, switch out the side of the Vision Pro here to be able to do that,

Cue 426 — 00:31:30,753 --> 00:31:35,793

which is supposedly. And in the five times I've tested it, it did this.

Cue 427 — 00:31:35,833 --> 00:31:40,153

It's creating a wired network with the Mac that it's connected to.

Cue 428 — 00:31:40,193 --> 00:31:45,913

So anything that is screen sharing in audio sharing is going over a wired network.

Cue 429 — 00:31:45,953 --> 00:31:48,993

And I will be just like, you can see my slides now.

Cue 430 — 00:31:49,033 --> 00:31:55,033

It is what I will be seeing through the Vision Pro will be hopefully projected and

Cue 431 — 00:31:55,073 --> 00:31:56,733

come out over the speakers.

Cue 432 — 00:31:58,633 --> 00:32:01,233

So one of the things with the Vision Pro, if you've never used it,

Cue 433 — 00:32:01,273 --> 00:32:02,893

I can see all of you guys.

Cue 434 — 00:32:04,113 --> 00:32:06,453

Well not now because it is in front of me.

Cue 435 — 00:32:08,153 --> 00:32:14,513

Let's see here. And the Vision Pro has this menu that appears in your hand.

Cue 436 — 00:32:14,553 --> 00:32:19,053

Here's what I'm doing now is mirroring my view to the laptop.

Cue 437 — 00:32:19,433 --> 00:32:21,413

And you should be seeing it. Right.

Cue 438 — 00:32:22,553 --> 00:32:24,073

Let me let me just get out of here.

Cue 439 — 00:32:24,113 --> 00:32:25,773

If you've never seen the Vision Pro.

Cue 440 — 00:32:26,353 --> 00:32:28,493

So this is. This is all you. Hi.

Cue 441 — 00:32:28,913 --> 00:32:29,713

Hi.

Cue 442 — 00:32:31,353 --> 00:32:33,833

So this is the start up screen.

Cue 443 — 00:32:33,873 --> 00:32:36,553

I can move it around my hand. Right?

Cue 444 — 00:32:36,593 --> 00:32:43,353

It's like right here. Hey, this is a welcome window, and I have this dial here that

Cue 445 — 00:32:43,393 --> 00:32:46,093

allows me to bring in virtual environments.

Cue 446 — 00:32:46,673 --> 00:32:50,313

And I can look around, and I'm sitting at the beach, and it's,

Cue 447 — 00:32:50,353 --> 00:32:55,213

like, pretty fun. But let's, let's, let's do this musical demo.

Cue 448 — 00:32:55,873 --> 00:32:59,053

So there are sensors all around here.

Cue 449 — 00:32:59,673 --> 00:33:05,373

They, they detect my hands and they also build a skeleton model of the hand.

Cue 450 — 00:33:05,433 --> 00:33:12,113

So if parts are obscured, it will like, the Vision Pro operating system will

Cue 451 — 00:33:12,153 --> 00:33:15,993

actually fill it in and rebuild that skeletal model.

Cue 452 — 00:33:16,033 --> 00:33:18,613

So this is what Glinster looks like.

Cue 453 — 00:33:19,113 --> 00:33:22,053

I'm going to dial in the immersion completely.

Cue 454 — 00:33:22,353 --> 00:33:29,073

And you can see that I have like a galaxy around me with nebula that slowly shift

Cue 455 — 00:33:29,113 --> 00:33:31,133

around. And if you see that,

Cue 456 — 00:33:32,593 --> 00:33:35,693

got stars behind it. I've got this little feature over there.

Cue 457 — 00:33:35,733 --> 00:33:41,113

Here. This is my hand. I've got this feature over there, and I worked a long time.

Cue 458 — 00:33:41,153 --> 00:33:46,053

There's another one up here. I worked a long time with Claude to come up with,

Cue 459 — 00:33:47,073 --> 00:33:49,793

like, phenomenons that we call.

Cue 460 — 00:33:49,833 --> 00:33:53,833

We call them phenomenons in the universe that don't look like anything that really

Cue 461 — 00:33:53,873 --> 00:33:56,393

exists, but that look like they could be real.

Cue 462 — 00:33:56,433 --> 00:34:03,293

And every time you start up, it will randomly generate this universe you're in.

Cue 463 — 00:34:03,553 --> 00:34:08,513

And you can see the nebula in different colors, sort of subtly move and in front of

Cue 464 — 00:34:08,553 --> 00:34:11,073

me. Let me just start this over.

Cue 465 — 00:34:11,113 --> 00:34:17,233

So I'm looking at the dial here, like my eyes are selecting what I'm doing in front

Cue 466 — 00:34:17,273 --> 00:34:22,793

of me is what I call the ruler, and the ruler is the scale of the notes that I'm

Cue 467 — 00:34:22,833 --> 00:34:24,913

playing. And so I hold my hand out.

Cue 468 — 00:34:24,953 --> 00:34:27,793

You can see these are like my fingertips.

Cue 469 — 00:34:27,833 --> 00:34:30,093

If I press down, I'm playing a note.

Cue 470 — 00:34:30,593 --> 00:34:34,773

And then if I flip my hand, there's another section of the scale that's highlighted.

Cue 471 — 00:34:35,153 --> 00:34:37,373

Right. So I can do.

Cue 472 — 00:34:49,833 --> 00:34:54,633

So I can move my hand in space to express this pitch is what we hear the most.

Cue 473 — 00:34:54,673 --> 00:34:58,453

But I've got volume. You can see the sliders below the ruler,

Cue 474 — 00:34:58,913 --> 00:35:03,473

and I've got brightness right now to the to corners.

Cue 475 — 00:35:03,513 --> 00:35:05,793

Here you see those dials that I mentioned?

Cue 476 — 00:35:05,833 --> 00:35:10,933

If I pivot my hands, they sort of rotate over a pivot point.

Cue 477 — 00:35:11,193 --> 00:35:15,593

And then this other hand allows me I don't have to use it.

Cue 478 — 00:35:15,633 --> 00:35:18,373

If I just use this hand, I will be in the bottom of the scale.

Cue 479 — 00:35:18,633 --> 00:35:22,613

But then if I use my left hand and I flip it over,

Cue 480 — 00:35:24,273 --> 00:35:25,933

I will play an octave higher.

Cue 481 — 00:35:57,293 --> 00:36:01,233

So that is it. And you can see that it generated a constellation.

Cue 482 — 00:36:05,253 --> 00:36:06,873

Oh, you're all still here.

Cue 483 — 00:36:08,533 --> 00:36:10,633

I was often another universe.

Cue 484 — 00:36:12,053 --> 00:36:16,553

Thanks so much and I hope this was inspiring and useful.

Cue 485 — 00:36:17,453 --> 00:36:20,293

You can hit me up on the socials.

Cue 486 — 00:36:20,333 --> 00:36:26,613

This is like a QR code of my website gbevin on everything except for X.

Cue 487 — 00:36:26,653 --> 00:36:28,073

I don't do X anymore.

Cue 488 — 00:36:29,533 --> 00:36:32,993

So yeah, thanks you all.

Cue 489 — 00:36:35,093 --> 00:36:36,073

Thank you.

Cue 490 — 00:36:37,613 --> 00:36:38,593

Thank you.

skills

talk-bevin-agent-assisted-instrument-design

tile.json