korrents

korrents · Dive Club

Brian Lovin - How to level up with AI as a designer

Brian Lovin · 55m · youtube.com ↗

20 korrents from this recording

Brian Lovin 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. 8:54 · watch on youtube.com↗

    Like as soon as you realize you can't design half of this stuff in Figma, what you're really designing is the harness for the agent to do longer things and verify its own work. And a lot of that means using AI in your day-to-day work and just getting like a feel.
  2. 1 min later
  3. 9:33 · watch on youtube.com↗

    I think where designers need to be designing right now is like right at the the boundary of the next the current model, like hoping that the next one solves it, right? Like we're all shipping shitty vibe-coded slop just hoping like, "Ah, the next model's definitely going to clean this up, right?" And I think that's probably a good a good place to be right now as a designer is really understanding what's possible, trying to push the edges even if it sucks and you get stuck
  4. 1 min later
  5. 10:54 · watch on youtube.com↗

    if you're really trying to use AI right now to automate knowledge work or simplify your job or like remove a process at your company, you're a very early adopter and the tolerance for those people for like kind of sub-par experiences is actually quite high.
  6. 1 min later
  7. 11:42 · watch on youtube.com↗

    is every 6 months everything that we did before becomes more or less irrelevant.
  8. 4 min later
  9. 15:36 · watch on youtube.com↗

    I think it's totally fine depending on what you're working on, but I would say the barrier to entry to try making something in code is so low that I I think everybody has dabbled with it.
  10. 2 min later
  11. 17:28 · watch on youtube.com↗

    I think it just moves from, "Hey, check out this Figma URL." to, "Hey, check out this deploy preview." I think that's pretty much it. Like what what's the artifact that we're going to point at together and try together and moving that from one domain URL to another, right?
  12. 1 min later
  13. 18:50 · watch on youtube.com↗

    The frustrating thing is like AI is still terrible at last mile fit and finish.
  14. 8 min later
  15. 26:20 · watch on youtube.com↗

    I think the models are still bad enough that if you really care about the final quality of the thing that you're shipping, I think you got to look at code.
  16. 1 min later
  17. 26:50 · watch on youtube.com↗

    I think it's a good time to not have an allegiance and not get tribal about tools. Just try it all. Just try it all, see what works
  18. 3 min later
  19. 29:48 · watch on youtube.com↗

    but feeling like you have a grip on it like oh if I just get my skills in the right order if I just review things in the right right flow and like have this model do this. I think it's a lot of cope for the fact that like the models are still inconsistent.
  20. 1 min later
  21. 31:04 · watch on youtube.com↗

    That means if you have really high quality input tokens, you're going to get higher quality output tokens but those input tokens are where you get to steer where you want the thing to go.
  22. 31:18 · watch on youtube.com↗

    if you want it to pay attention to a certain thing, you have to say the certain thing. Like you actually have to say the thing that you want it to focus on.
  23. 1 min later
  24. 32:07 · watch on youtube.com↗

    These are stupid these are stupid prompts but they work because it just flips the right bits so that the model will extrapolate from there.
  25. 1 min later
  26. 32:51 · watch on youtube.com↗

    anyone who knew how to code before AI is having a way better time using AI than someone who didn't know how to code because guess what? They know the right words to say.
  27. 11 min later
  28. 43:33 · watch on youtube.com↗

    AI is not magic. The underlying systems are very complicated. I don't think anybody would claim they know what an LLM's doing under the hood. But it is doing things on your computer like writing files and writing scripts and like invoking bash commands that were invented in the 70s. And those are knowable things.
  29. 7 min later
  30. 50:44 · watch on youtube.com↗

    I think that our obsession with titles is what will screw people over.
  31. 51:07 · watch on youtube.com↗

    And you want to be the kind of person that can move between those types of working very fluidly and not get caught up in, but what's my what's the box I'm in at this company, right?
  32. 51:27 · watch on youtube.com↗

    You want a PM who can design around their spec to see if their spec holds up to reality. You want an engineer that really cares about building great visual component systems so that they can prototype beautiful things without needing a designer to come in and tell them to nudge stuff around, which is really annoying.
  33. 1 min later
  34. 52:05 · watch on youtube.com↗

    if you can just focus on making things for real people, that solve a real problem, iterate quickly, try and make the thing as good as you can and stop worrying about but I don't know how to code. I don't know how to write a PRD. Like who cares? Just like ship the thing and solve the problem and learn how to do that faster. Uh you'll be fine.
  35. 3 min later
  36. 54:39 · watch on youtube.com↗

    I think the ability to focus and be undistractable for 2 hours a day is like a meaningful competitive advantage right now