korrents

korrents · Dive Club

Kyle Zantos - Our AI design workflows have changed (again)

Kyle Zantos · 51m · youtube.com ↗

12 korrents from this recording

Kyle Zantos did not write this page.

Every claim below is a statement made in this recording, quoted word for word and linked to the second it was said, so you can hear it rather than take our word for it. The wording comes from the transcript published alongside the recording; the sentence above each quote is our reading of the claim, not their wording.

  1. 3:42 · watch on youtube.com↗

    So just visualizing everything from your agents has been huge.
  2. 1 min later
  3. 4:26 · watch on youtube.com↗

    my directive is always give me the closest possible representation of the thing so that when I say, "Yeah, that's a good idea. Implement that." I'm doing it from a not best guess, but like I can tell that this is the direction we want to do.
  4. 17 min later
  5. 21:16 · watch on youtube.com↗

    I didn't want to keep telling it to fix stuff like you would tell like an intern. Let's hit the bar of solid and then I'm working from what I like and don't like, not just like this is an obvious poor visual design decision.
  6. 3 min later
  7. 24:40 · watch on youtube.com↗

    instead of having the black box of like I told you to go through all these iterations now I see V3, but I don't know what happened along the way. And seeing it visually like this, especially while I'm developing this pipeline, lets me find like, man, review between one and two, the review is too weak.
  8. 2 min later
  9. 26:20 · watch on youtube.com↗

    I'm just thinking differently of like yeah it's like an eval. It's like a visual eval that us not being in the code, we can make more complex tooling and flows like this and autonomous runs that we still get to manifest and tweak and control basically the same way that we're used to.
  10. 5 min later
  11. 31:03 · watch on youtube.com↗

    We're continuously trying to describe and like put something into the agents hands quote unquote or or make it something they can touch so that the touch identifier of exactly this thing and you can see all the code and what it is that I'm talking about and my talking about it that combo is seems like a theme in a lot of the stuff we've been building.
  12. 3 min later
  13. 33:51 · watch on youtube.com↗

    I think you keep reminding me I need to not assume how good it might be or might not be at this thing that I want it to do.
  14. 7 min later
  15. 41:05 · watch on youtube.com↗

    I mean one of the things was building a lot of custom tooling. The HTML shortcut like takes care of so much of that. Like you said the the show me the options and approved and I discuss like that whole area would have been a tool in your case was a tool for a minute uh that now we don't have to do.
  16. 4 min later
  17. 45:04 · watch on youtube.com↗

    like the ideation happened like in v 0ero on top of like a full react web app which is like now just like laughable. It's like that's so inefficient.
  18. 45:25 · watch on youtube.com↗

    and going wide now cheaply with HTML stuff and then getting into now let's make the real app because we actually kind of have a sketch of what the app will look like is is so much better.
  19. 3 min later
  20. 48:03 · watch on youtube.com↗

    there was a a period of time that being early to the AI game was an attribute to itself that is becoming less and less true already. Like so many people have caught up and it doesn't take all that.
  21. 1 min later
  22. 49:19 · watch on youtube.com↗

    If I am primarily designing something, like it makes all the sense in the world to me to own the front end. Of course, if I'm the one designing it, why wouldn't I own that? That it's insane. I want to play the songs that I write, you know?