Why Brian still writes code by hand

When it comes to tools and workflows, Brian Lovin (https://x.com/brian_lovin) is someone I pay very close attention to.

He’s actually the one who first got me hooked on Conductor (https://www.conductor.build/).

But times are changing (again 😅)…

So today’s episode is a deep dive into his design process and all of the ways he’s iterating on his approach to both using AI tools as well as building AI tools at Notion.

If you like getting into the weeds of how the best designers are wrangling AI then you’re going to love this episode.

Some highlights:

- Why his first Notion design offsite was so impactful

- How Brian built Notion’s prototyping playground

- Why Brian has started using Cursor again

- Practical tips for prompting AI more effectively

- Behind-the-scenes of Brian’s new side project

- How to stay relevant as a designer in an AI world

- + a lot more

- Agentation and Dialkit for frontend ([https://agentation.com](https://agentation.com/), https://joshpuckett.me/dialkit)

- Cursor and Conductor for coding ([https://conductor.build](https://conductor.build/))

- Brian’s side project Shiori ([https://shiori.sh](https://shiori.sh/))

- Max Schoening nerd snipes Brian (https://x.com/mschoening)

- Karri’s issue tracking is dead article (https://linear.app/next)