สำเนาบทสนทนา 🔗
WEBVTT
NOTE
This file was generated by Descript
00:00:04.585 --> 00:00:07.615
Tom: Hello, welcome to the Near Future
Podcast, , where today we have our
00:00:07.665 --> 00:00:12.425
second extra special guest, Domingo
Widen, who is a staff product designer
00:00:12.495 --> 00:00:14.955
at Fin, formerly known as Intercom.
00:00:15.785 --> 00:00:17.865
Domingo works on the front end infra team.
00:00:17.885 --> 00:00:20.075
We're gonna learn more about that
today, and we'll hear about some
00:00:20.075 --> 00:00:23.515
of the exciting, things they're
working on and how they're working.
00:00:24.494 --> 00:00:27.084
I wanted to also set a bit of
context for the start of this
00:00:27.084 --> 00:00:30.984
episode that Domingo and I used to
work together, years ago at Monzo.
00:00:31.344 --> 00:00:35.295
Super fun to work with you, Domingo, and
it's nice that we can return to a light
00:00:35.315 --> 00:00:38.564
touch collaboration like this to, hear
how things have been going since then.
00:00:39.055 --> 00:00:43.325
But also, you shared some really cool
things at a Mostly Working event which
00:00:43.325 --> 00:00:48.194
we ran in January or February earlier
this year, an AI and design morning where
00:00:48.194 --> 00:00:52.255
you came and gave a demo of what you're
working on and how prototyping works at
00:00:52.277 --> 00:00:52.784
Domingo: Nikorov
00:00:52.834 --> 00:00:55.664
Tom: We're gonna, kick off with perhaps a
little bit of an update on how things have
00:00:55.664 --> 00:00:59.714
gone since the start of this year, , in
terms of how the team is working today
00:00:59.714 --> 00:01:01.474
and how you're working on the team today.
00:01:01.554 --> 00:01:03.484
Domingo: Thank you so much
for having me, first of all.
00:01:04.164 --> 00:01:08.074
Things are continuing to evolve in the
sense of we are all using AI more and
00:01:08.084 --> 00:01:14.284
more, and I think designers are getting
really comfortable with actually going
00:01:14.284 --> 00:01:16.254
in and shipping a change to production.
00:01:16.334 --> 00:01:20.544
So that's been the biggest shift that
I've seen in the past six months.
00:01:21.204 --> 00:01:24.994
Designers going from, "Hey, I'm gonna
prototype something in this like sandbox,"
00:01:24.994 --> 00:01:30.614
to, "Actually, I'm just gonna prototype it
directly in, in production, and I'm gonna
00:01:30.614 --> 00:01:34.424
create a PR, and I'm just gonna submit
it, and then it will get approved or I
00:01:34.424 --> 00:01:35.954
will work with Claude to get it approved."
00:01:36.354 --> 00:01:37.614
So that has been the biggest shift.
00:01:37.614 --> 00:01:40.854
If-- Designers are way, way more
comfortable with doing that.
00:01:42.594 --> 00:01:46.494
and yeah, my team basically for context
as well, for everybody, my team is
00:01:46.514 --> 00:01:48.074
called Front-End Infrastructure.
00:01:48.134 --> 00:01:53.404
We own the whole front end of the
application, and our mission is to
00:01:53.414 --> 00:01:57.024
build a platform and tools so all
the teams can ship faster, safer,
00:01:58.564 --> 00:02:03.534
use AI and like just get from
concept to production the fastest.
00:02:03.794 --> 00:02:08.314
Whether it's building prototyping
tools for designers to building
00:02:08.314 --> 00:02:11.194
pipelines for engineers so they can
ship React quicker, quicker as well.
00:02:11.204 --> 00:02:14.244
So we own the design system,
we own security in the front
00:02:14.244 --> 00:02:15.544
end, we own a bunch of stuff.
00:02:16.874 --> 00:02:19.204
so that's kinda what we do
and how things have changed.
00:02:20.999 --> 00:02:24.329
Tom: Domingo, just to clarify, so
your role these days, is it still
00:02:24.329 --> 00:02:25.689
in the world of product design?
00:02:25.699 --> 00:02:30.499
Would you consider it, would you
consider your professional role product
00:02:30.499 --> 00:02:35.639
designer, or has it shifted or evolved
into something more infrastructural
00:02:37.274 --> 00:02:38.604
Domingo: I think it's a mixture of both.
00:02:38.714 --> 00:02:43.084
I do, go and help with
teams, so I float around.
00:02:43.654 --> 00:02:45.784
So over the past few months,
for example, I've been helping
00:02:45.784 --> 00:02:48.194
with a team called, Operator.
00:02:48.204 --> 00:02:51.934
So it's a product that we're
building which allows you to
00:02:51.934 --> 00:02:53.904
configure Fenn directly with AI.
00:02:54.544 --> 00:02:58.764
So because I have a good overview of
all the patterns across the system, I
00:02:58.764 --> 00:03:02.614
tend to get tapped to be like, "Hey,
can you just go and help that team?"
00:03:02.614 --> 00:03:07.154
And like influence how they're building
certain patterns, and it's really helpful
00:03:07.154 --> 00:03:10.074
because then I bring that information
to the infrastructure team and say,
00:03:10.504 --> 00:03:13.084
"Hey, I think we just need to build
a new navigation for these folks."
00:03:13.084 --> 00:03:17.674
Or or, "These folks are, like, taking
way too long to code certain things."
00:03:17.914 --> 00:03:21.754
or, "Actually, we should change
this design so we can help them."
00:03:21.754 --> 00:03:27.354
So I tend to f- split my time
between, like thinking about the
00:03:27.354 --> 00:03:31.164
infrastructure, the skills, the
tooling, the design system, and all
00:03:31.164 --> 00:03:34.844
that stuff, but also going in and,
doing product design and prototyping
00:03:34.844 --> 00:03:36.614
myself and helping others essentially.
00:03:37.124 --> 00:03:40.774
And also a little bit of evangelizing
that I do across the team.
00:03:40.814 --> 00:03:42.424
Just "Use AI.
00:03:43.094 --> 00:03:43.744
Use it now.
00:03:44.074 --> 00:03:44.714
Use it more."
00:03:46.184 --> 00:03:46.374
Yeah.
00:03:47.954 --> 00:03:48.194
yeah
00:03:49.575 --> 00:03:57.125
Tom: Are there any, Slack
reactions in Fin for Domingo AI?
00:03:58.936 --> 00:04:04.546
Domingo: Yeah, there is like a, they
always, the team always makes
Load full transcript
fun of me
00:04:04.546 --> 00:04:08.086
sometimes because they say that, I should,
start having my own YouTube channel,
00:04:08.506 --> 00:04:13.166
because I've been doing, I've been
doing, a few interviews like these ones.
00:04:13.566 --> 00:04:14.156
I enjoy it.
00:04:14.566 --> 00:04:18.506
I enjoy talking about how we're
working, and I have the privilege of
00:04:18.506 --> 00:04:21.696
working in a place that w- allows us to
experiment, so why not talk about it,
00:04:22.896 --> 00:04:23.376
Jonny: Domingo.
00:04:23.706 --> 00:04:24.416
Nice to see you again.
00:04:25.566 --> 00:04:31.046
I was at the Mostly Working session that
we ran in, or I, attended in, I don't
00:04:31.046 --> 00:04:32.366
know, February, something like that.
00:04:33.106 --> 00:04:39.126
that was this crazy time when were
appearing, and the Opus models were
00:04:39.126 --> 00:04:44.576
getting really good, and it feels like
people were moving from-- or designers
00:04:44.576 --> 00:04:48.566
were moving from AI as something
that I should play around with to
00:04:48.606 --> 00:04:51.866
AI can really power things for me.
00:04:53.096 --> 00:04:58.066
And, I think much has changed in
the six months since across the
00:04:58.066 --> 00:05:01.916
industry, but I remember you demoing
what you had built and telling a
00:05:01.916 --> 00:05:07.426
story around what you'd built at
Intercom to get a hundred designers.
00:05:07.456 --> 00:05:09.066
Is it about a hundred
designers, something like that?
00:05:09.566 --> 00:05:16.386
running, prod as part of the infamous
now Q3 or Q4 goal to get every
00:05:16.386 --> 00:05:17.836
designer shipping something in prod.
00:05:18.216 --> 00:05:21.196
I remember it being talked about
last year in twenty twenty-five, and
00:05:21.216 --> 00:05:22.716
everyone was like, that's crazy."
00:05:22.986 --> 00:05:27.246
And now it feels like not that
crazy, But, Intercom have always
00:05:27.246 --> 00:05:28.456
been first to all of this stuff.
00:05:29.696 --> 00:05:33.946
I suppose w- to get to an actual question,
I-- it would be-- I think it'd be really
00:05:33.946 --> 00:05:37.376
interesting to just hear you talk through
the process you went through to get
00:05:37.386 --> 00:05:43.936
from no one can do this, no one-- no
designers feel comfortable, to everyone
00:05:43.936 --> 00:05:47.856
has done it, and how much of that was
hearts and minds in helping designers
00:05:48.616 --> 00:05:51.686
comfortable in the terminal, and h-how
much of that was building infrastructure.
00:05:52.176 --> 00:05:55.726
I think for anyone that want-- any
designer listening to this who's "I really
00:05:55.726 --> 00:06:02.666
w-wanna get everyone going," was your--
how would you, recommend you do it now?
00:06:02.876 --> 00:06:06.146
And maybe it's different to how you did it
because the tools are different, but yeah.
00:06:06.266 --> 00:06:07.216
what was the pain?
00:06:08.443 --> 00:06:14.647
Domingo: So When we started, I was one
of the first ones to do it, and you all
00:06:14.647 --> 00:06:21.637
started because I was working on a big
Intercom thing redesign at the time, and
00:06:21.727 --> 00:06:25.747
my engineer was exploring with a lot of,
color tokens and stuff like that, and I
00:06:25.747 --> 00:06:27.427
just wanted to be able to do it myself.
00:06:27.927 --> 00:06:31.187
we already engineer-- the engineering
team was already dabbling with AI,
00:06:31.237 --> 00:06:35.957
and he, said to me, "Why don't you use
set up your developer environment?"
00:06:36.177 --> 00:06:41.517
And, I was one of the first designers
to go through the process, and it's
00:06:41.517 --> 00:06:43.807
a, complicated process, setting
up your developer environment.
00:06:45.177 --> 00:06:50.637
every engineer that comes in into
Intercom, Finn comes in and needs to
00:06:50.637 --> 00:06:54.927
spend, the first half a day or day
just installing all the things and,
00:06:55.177 --> 00:06:56.437
making sure everything is secure.
00:06:57.047 --> 00:07:01.027
so I did it, and I, saw the
benefit, and I started dabbling
00:07:01.027 --> 00:07:02.987
with AI, and I saw others as well.
00:07:04.557 --> 00:07:10.447
And, it became apparent that when you're
in there and when you have an AI tool,
00:07:10.487 --> 00:07:14.367
you can start a-asking questions about
your code base, not even prototyping.
00:07:14.397 --> 00:07:17.647
You can start asking questions
around what are the edge cases?
00:07:17.647 --> 00:07:18.827
How is this data structure?
00:07:18.887 --> 00:07:19.817
Why should Iâ¦
00:07:20.397 --> 00:07:21.287
How does this work?
00:07:21.517 --> 00:07:24.307
Is there any other file, files
that are using the same component?
00:07:24.377 --> 00:07:26.087
And how many other pages
are called this way?
00:07:27.217 --> 00:07:32.967
You can really use your own code base
as a knowledge base to understand your
00:07:32.967 --> 00:07:35.127
product, to find edge cases and to work.
00:07:36.567 --> 00:07:41.257
so the-- I can't say that
it happened organically.
00:07:41.487 --> 00:07:44.327
I think the leaders within
the organization, theyâ¦
00:07:44.847 --> 00:07:51.447
Some of us did it, and the leaders with
the organization, they saw the potential
00:07:51.467 --> 00:07:53.507
of, everybody being in code as well.
00:07:55.107 --> 00:07:58.797
and Tom, our head of design, he set
up a mandate saying everybody should
00:07:58.927 --> 00:08:03.707
be on-- in-- set up in the developer
environment by, I can't remember
00:08:03.707 --> 00:08:05.437
what it was, but, by a certain date.
00:08:06.557 --> 00:08:08.907
That was stressful, for a lot of people.
00:08:08.907 --> 00:08:14.247
A lot of people didn't want to do it, but
we went through the process of, we s- we
00:08:14.247 --> 00:08:16.177
wrote a lot of guides on how to do it.
00:08:16.217 --> 00:08:17.397
We worked with engineering.
00:08:17.437 --> 00:08:20.407
Engineering was really open
as well, which helped us.
00:08:20.897 --> 00:08:21.767
They
were like, "Yeah, sure.
00:08:21.777 --> 00:08:24.537
Why don't-- We'll help you out,
and then why don't you do it?"
00:08:24.557 --> 00:08:30.827
And they gave us engineers to, help us
write the guides, and, we, we run multiple
00:08:30.827 --> 00:08:36.467
sessions where we will spend, three
hours on a, room with an engineer, and
00:08:36.477 --> 00:08:40.057
everybody will be setting things up, and
somebody will be like, "Oh, it's blocked.
00:08:40.097 --> 00:08:41.337
I don't understand what's happening."
00:08:41.777 --> 00:08:44.127
And then the engineer will be like,
"Actually, you have to run that
00:08:44.127 --> 00:08:46.237
script again," or, "Actually, you
have to run that script again."
00:08:47.247 --> 00:08:49.077
so the process at the
beginning was like that.
00:08:49.167 --> 00:08:56.327
It was very difficult and-- but then
we optimized it and, we worked with
00:08:56.327 --> 00:08:58.417
engineers to, make it a bit easier.
00:08:58.427 --> 00:09:01.357
And we actually spotted problems
because we-- one of the things that
00:09:01.357 --> 00:09:04.867
we told engineers is like, "It's
really difficult to set this up,
00:09:04.907 --> 00:09:06.257
and it's not very user-friendly.
00:09:06.337 --> 00:09:10.535
Why are you forcing your engineers-"
to go through a process that is
00:09:10.535 --> 00:09:14.205
not user-friendly, And we then
influence that back intoâ¦
00:09:14.215 --> 00:09:17.345
We have a team called, Team Builder Tools.
00:09:17.905 --> 00:09:22.785
So Team Builder Tools is the team
that manage all their organization's
00:09:22.815 --> 00:09:27.075
engineering tools and all that
kind of stuff, and then theyâ¦
00:09:27.405 --> 00:09:30.735
or developer environments and stuff
like that, or security, or pipelines.
00:09:30.755 --> 00:09:33.445
So they were like, "Okay,
actually, you, you were right."
00:09:33.625 --> 00:09:38.985
And so they, also im- helped us improve
some of the processes, the scripts, so
00:09:38.985 --> 00:09:42.845
they are shorter, so we have to do less
things, and they helped us write a guide
00:09:42.845 --> 00:09:44.825
that is pretty, is in a pretty good space.
00:09:45.485 --> 00:09:49.715
The thing about all of this is, once
you set it up once, then it's done.
00:09:50.165 --> 00:09:54.755
Then the problem becomes teaching
designers that they need to start
00:09:54.755 --> 00:09:55.985
behaving like the engineers.
00:09:56.225 --> 00:09:59.055
every time you open your developer
environment, you need to pull your
00:09:59.055 --> 00:10:03.985
changes, and and you need to pull
the latest from master, and you need
00:10:03.985 --> 00:10:08.855
to make sure you update because we
might have launched a new version of
00:10:08.855 --> 00:10:10.395
a package that you haven't updated.
00:10:10.915 --> 00:10:11.475
So thatâ¦
00:10:11.695 --> 00:10:14.685
Once we went through the process
of everybody set up, the problems
00:10:14.685 --> 00:10:18.415
after that has been like, "Oh, my
developer environment doesn't work."
00:10:18.715 --> 00:10:21.685
it's because you haven't pulled your
latest from master, and it's because
00:10:21.685 --> 00:10:22.945
you haven't updated your package.
00:10:23.405 --> 00:10:27.825
and now we are l- we went through
the whole process and we are in a
00:10:27.825 --> 00:10:29.255
stage where, designers are likeâ¦
00:10:29.695 --> 00:10:31.075
That nobody's asking about it.
00:10:31.075 --> 00:10:33.635
Nobody's asking it's broken.
00:10:33.745 --> 00:10:39.205
People are using Cloud to, self-serve
or, everybody's kn- knows it.
00:10:39.365 --> 00:10:43.475
So it's mostly, serving the new
designers that are joining that are
00:10:43.475 --> 00:10:45.255
like, "Okay, need to set it up again."
00:10:45.275 --> 00:10:47.525
And then we help those specifically.
00:10:48.195 --> 00:10:52.315
So that was a very long-winded answer, but
I, hope it gives you a sense of the story,
00:10:53.438 --> 00:10:53.978
Jonny: Yeah, it makes sense.
00:10:53.978 --> 00:10:58.158
I think you, you start with Mechanical
Turk or with, human-powered support, and
00:10:58.158 --> 00:11:00.058
then you build infrastructure around it.
00:11:00.058 --> 00:11:02.718
It's cool to hear that the
engineers get to benefit as well.
00:11:04.218 --> 00:11:07.248
it's ridiculous that it takes a
non-technical person to set up a
00:11:07.248 --> 00:11:12.638
good developer, a good DX on, on,
your first day that it's the design
00:11:12.638 --> 00:11:14.408
team that forced that to happen.
00:11:15.375 --> 00:11:18.775
Domingo: Sometimes things break and like
I've, gone into a situation which is
00:11:18.855 --> 00:11:24.065
like something broke for m- for me like
last week, and I couldn't get it to work.
00:11:24.195 --> 00:11:26.145
And my engineer was like,
"Have you asked Claude?"
00:11:27.085 --> 00:11:30.795
And I was like, I, was just like gonna
ask this engineer how to help me out.
00:11:30.795 --> 00:11:33.365
And I'm like, "Yeah, I should ask Claude."
00:11:33.375 --> 00:11:37.075
And obviously Claude has a lot of
knowledge because the infrastructure
00:11:37.075 --> 00:11:41.265
teams have been building a lot of
knowledge into our Claude instance.
00:11:41.265 --> 00:11:42.935
So we-- It's good at it.
00:11:42.945 --> 00:11:46.385
So yeah, it helped me get
out of It, it now works.
00:11:46.405 --> 00:11:47.595
I didn't have to involve anybody.
00:11:47.635 --> 00:11:49.055
Just Claude just fix it.
00:11:50.474 --> 00:11:57.394
Jonny: to ask actually about, your,
in your role as arbiter of consistency
00:11:57.444 --> 00:12:01.314
and using the right components and
using them in the right way and
00:12:01.674 --> 00:12:09.284
leaning on the conventions, how much
of that is hard encoded versus you're
00:12:09.654 --> 00:12:12.814
building a bunch of skills, and
you're getting people to use those
00:12:12.814 --> 00:12:14.764
skills, and most of the time it works?
00:12:15.264 --> 00:12:19.724
like how, much can you guarantee
that you get
that consistency versus,
00:12:20.694 --> 00:12:26.434
it's shaping rather than, like a real
exact craft, if that makes sense?
00:12:27.209 --> 00:12:30.959
Domingo: Yeah, I I stumbled upon this
role, so I've always-- I've never
00:12:31.079 --> 00:12:36.649
have to work on design systems until
now, and I realize that, in a lot of
00:12:36.689 --> 00:12:43.609
companies before or even at Intercom
at the beginning, the-- there is always
00:12:43.699 --> 00:12:47.229
the consistency problem, and there is
always a-- the design system team or
00:12:47.229 --> 00:12:51.219
the person that maintaining it, it feels
like, they're policing pe- policing
00:12:51.219 --> 00:12:54.269
people or slowing people down or saying,
"Hey, you, don't have this component.
00:12:54.289 --> 00:12:58.259
Don't go there because it's not ready
yet, and then you have to build until
00:12:58.259 --> 00:12:59.429
it's ready, so you can build it."
00:12:59.909 --> 00:13:03.709
And I just realized early on, and I told
my team, like when, I kinda started doing
00:13:03.709 --> 00:13:08.399
this, I'm like, "This is not gonna work
because we can't slow down the company.
00:13:08.419 --> 00:13:09.499
We're moving really fast.
00:13:09.509 --> 00:13:10.909
It's something that we're known for,
00:13:11.669 --> 00:13:15.579
so we need to build-- we need
to be open, so like for the
00:13:15.579 --> 00:13:16.729
consistency not to be there."
00:13:17.372 --> 00:13:17.742
Jonny: Yeah
00:13:18.169 --> 00:13:21.159
Domingo: and we need to try to
enforce things in a different way.
00:13:21.169 --> 00:13:25.599
Like the-- I can't tell a team,
"A, you shouldn't do this right now
00:13:26.119 --> 00:13:30.149
because it's not ready," b- if a team
can build it in an hour with Claude.
00:13:30.679 --> 00:13:31.909
They're just gonna do it anyway.
00:13:32.049 --> 00:13:36.379
So I think we've been thinking
a lot about how to en-enforce
00:13:36.379 --> 00:13:37.859
our patterns in a different way.
00:13:37.859 --> 00:13:43.539
So like the thing that we work on
right now a lot is I still go and join
00:13:43.539 --> 00:13:46.219
design critiques, and I tell designers,
"Oh, you should have not used that,"
00:13:46.219 --> 00:13:47.229
or "Have you thought about that?"
00:13:47.229 --> 00:13:50.049
Or "Yeah, maybe use it, but be aware
that you have to change after."
00:13:51.679 --> 00:13:55.109
but what we work right now is we--
our design system is called Surge,
00:13:55.559 --> 00:14:00.769
and we basically started playing with
skills, and we realized that they
00:14:00.769 --> 00:14:02.389
kinda no- don't work all the time.
00:14:02.469 --> 00:14:06.179
So we realized that skills are
only as good as the knowledge
00:14:06.179 --> 00:14:07.349
base that they read from.
00:14:07.919 --> 00:14:11.309
So we've been working on this this
thing that we call Surge Intelligence,
00:14:11.309 --> 00:14:12.909
which is like a collection ofâ¦
00:14:13.039 --> 00:14:18.449
It's-- It basically encodes how
the front end is built, not only
00:14:18.469 --> 00:14:21.259
design-wise, but also e-engineering-wise.
00:14:21.269 --> 00:14:25.869
So it's like the best practices for React,
the best way to do imports, the best
00:14:25.869 --> 00:14:31.059
way to use color, the best way to use
typography, tokens, the best way toâ¦
00:14:31.059 --> 00:14:34.199
when to use a button, when not to use a
button, when do you use an input field.
00:14:34.229 --> 00:14:40.469
And it's all essentially MD files that
are all structured in a way where then
00:14:40.479 --> 00:14:45.459
now what we've done is that we rewrote
those skills to read that, those files.
00:14:45.989 --> 00:14:51.019
And every time those skills run, I
guaran-- I can guarantee that Claude
00:14:51.019 --> 00:14:54.609
will read the design files from Surge
Intelligence, and it will give you
00:14:54.609 --> 00:14:57.049
an answer that is informed by us.
00:14:57.049 --> 00:15:01.679
So that way we can extend our
influence without us being there, So
00:15:01.689 --> 00:15:05.569
if a, if an engineer is like asking,
"Oh, is this page designed well?"
00:15:06.869 --> 00:15:10.629
Then Claude will automatically, with
the word design, will trigger into Surge
00:15:10.629 --> 00:15:13.789
Design, Surge Design skill, and it will
just be like, "Oh, let me just check
00:15:13.789 --> 00:15:15.349
the files from Surge Intelligence."
00:15:15.349 --> 00:15:17.459
And it will be like, "Oh yeah,
actually you didn't use the
00:15:17.779 --> 00:15:19.259
area label for this stuff.
00:15:19.289 --> 00:15:20.769
You should have used this area label."
00:15:21.869 --> 00:15:22.899
and it's okay, cool, done.
00:15:23.929 --> 00:15:28.449
so we're still improving it But
it's how I see the future, where
00:15:29.289 --> 00:15:33.309
I'm building the, not the brain, and
then this thing is going and helping
00:15:33.319 --> 00:15:34.519
you, but I don't have to be there.
00:15:35.149 --> 00:15:37.339
I don't have to, be in
all the conversations.
00:15:37.859 --> 00:15:43.109
And partly we're doing it a lot because
there is engineers working-- There's
00:15:43.139 --> 00:15:46.279
engineers working without designers
because they can just build features on
00:15:46.279 --> 00:15:49.889
their own, and there is designers working
without engineers as well, where they
00:15:49.889 --> 00:15:51.209
are also building features on their own.
00:15:51.659 --> 00:15:55.999
So we need to have, really powerful AI
tools so they can get their job done.
00:15:56.189 --> 00:15:57.299
That's the mission.
00:15:57.911 --> 00:15:59.561
Tom: Surge Intelligence sounds super cool.
00:16:00.471 --> 00:16:03.891
of that audience split that you
mentioned, engineers and designers, do
00:16:03.891 --> 00:16:09.021
you serve them both equally, or do you
find that your time is more spent with
00:16:09.021 --> 00:16:10.941
engineers or more spent with designers?
00:16:11.051 --> 00:16:13.461
How do you think about
that audience for this?
00:16:13.767 --> 00:16:18.357
Domingo: s- we serve them both equally,
but there is more engineers, essentially.
00:16:18.887 --> 00:16:23.077
So we are optimizing things to be
really easy to understand for engineers.
00:16:23.367 --> 00:16:25.317
When it-- especially when it comes toâ¦
00:16:25.947 --> 00:16:31.317
Because one of the things I'm slowly
encoding is decisions on when to, use a
00:16:31.317 --> 00:16:37.107
pattern or not, or like what is a, when
should you use a secondary button and why?
00:16:37.147 --> 00:16:38.727
And like, how big should it be?
00:16:38.747 --> 00:16:42.357
And make sure that it's this big
when this is happening alongside it.
00:16:42.917 --> 00:16:47.337
So there is a lot of design
shared knowledge that we know.
00:16:47.347 --> 00:16:50.807
We like, we look at a page and
we're like, "Yeah, that should
00:16:50.817 --> 00:16:52.257
be a secondar-secondary button.
00:16:52.267 --> 00:16:53.147
That should be primary."
00:16:53.777 --> 00:16:58.257
But our engineers just don't necessarily
train into that, so we have been trying to
00:16:58.517 --> 00:17:05.117
really encode some of those decisions so
an engineer doesn't have to go through it.
00:17:05.117 --> 00:17:06.337
Because I wanna allow
them to just build a page.
00:17:06.637 --> 00:17:12.577
So they, the designers, they don't need
to waste their time QA-ing these pages.
00:17:12.577 --> 00:17:17.377
They can actually put their time
creating vision, and what's next,
00:17:17.417 --> 00:17:20.637
which is what I think designers should
be spending their time, essentially.
00:17:20.637 --> 00:17:20.817
yeah.
00:17:20.817 --> 00:17:24.187
Jonny: Yeah, it's interesting you--
when your audience is engineers,
00:17:24.187 --> 00:17:28.857
you have to layer on an e- an extra
thing that if you were working with
00:17:28.857 --> 00:17:32.517
designers, you could s- fairly safely
assume through the interview process and
00:17:33.017 --> 00:17:36.797
working at Fin that they would be able
to decide which button's appropriate.
00:17:37.497 --> 00:17:40.727
so I suppose if you're building these
skills for designers, it's very much
00:17:40.727 --> 00:17:44.347
about filling in the, engineering
half, like use the right component
00:17:44.347 --> 00:17:49.547
and make it semantically accessible
and, like all of this kind of stuff
00:17:49.547 --> 00:17:54.697
and build, write the code in the
correct way, so coding convention.
00:17:55.177 --> 00:17:57.757
But then if you're working with
engineers, actually the missing
00:17:57.757 --> 00:18:01.537
knowledge is the design process,
so it becomes more about UX.
00:18:02.317 --> 00:18:04.647
so they're quite d- they're probably
quite different skills, and you need
00:18:04.667 --> 00:18:06.597
both for the different audiences.
00:18:07.447 --> 00:18:10.987
suppose it just makes me wonder
if side is seeing this as
00:18:10.987 --> 00:18:13.287
threatening to them in any way.
00:18:13.667 --> 00:18:16.777
if you've got designers like trying
to codify their knowledge so that they
00:18:16.777 --> 00:18:19.647
don't have to do that anymore, do they
see that as "Now I have more leverage,
00:18:19.647 --> 00:18:20.897
I can do more important things"?
00:18:20.897 --> 00:18:23.177
Or is that, not how
they're thinking about it?
00:18:23.177 --> 00:18:25.737
Domingo: I don't think anybody,
here, at least here, is
00:18:25.737 --> 00:18:27.027
thinking about it as a threat.
00:18:27.127 --> 00:18:29.547
And I think it's becomes--
it's because of the way we
00:18:29.547 --> 00:18:31.137
approached AI from the beginning.
00:18:31.547 --> 00:18:33.627
Like, we're building AI agents.
00:18:34.277 --> 00:18:38.357
We were told very early on,
use AI to make it faster.
00:18:38.987 --> 00:18:39.697
It doesn't matter.
00:18:39.747 --> 00:18:40.757
Yeah, just use it.
00:18:40.777 --> 00:18:44.547
And I remember at the beginning, we
were even allowed to have subscri--
00:18:44.577 --> 00:18:45.877
any subscription that we wanted.
00:18:46.477 --> 00:18:50.137
I could just try all the tools and
then fi- figure out the w- the way
00:18:50.137 --> 00:18:51.467
that, that one that was faster.
00:18:51.767 --> 00:18:55.637
Now, obviously, like through the,
through learning, we landed on Claude.
00:18:55.667 --> 00:18:56.457
Claude is way better.
00:18:56.457 --> 00:18:59.407
You can really s- build
infrastructure on Claude.
00:19:01.327 --> 00:19:03.767
but we've always had the men-
the mentality in the company of
00:19:04.467 --> 00:19:05.797
this is not gonna replace you.
00:19:05.807 --> 00:19:08.317
This is just gonna make you faster
to do all the things, and then you
00:19:08.337 --> 00:19:11.427
need to have the critical thinking
to make the decision yourself.
00:19:12.757 --> 00:19:18.357
one of the reasons I One of the, triggers
for me to create certain intelligence is
00:19:18.357 --> 00:19:20.267
because I also saw designers doing this.
00:19:20.677 --> 00:19:25.787
s- designers automatically started
writing their own skills to help their
00:19:25.787 --> 00:19:30.367
engineers in their teams QA things because
they didn't wanna spend time QAing,
00:19:30.896 --> 00:19:31.236
Jonny: right
00:19:31.257 --> 00:19:34.357
Domingo: And so I was like,
that makes sense, right?
00:19:34.357 --> 00:19:37.917
Like they-- nobody wants to
spend time QAing, and they wanna
00:19:37.937 --> 00:19:39.267
just create the new things.
00:19:39.297 --> 00:19:42.657
So it makes us realize
actually, yeah, thisâ¦
00:19:43.677 --> 00:19:46.707
There is a lot of like jobs
that designers don't wanna do
00:19:47.037 --> 00:19:48.617
and that could be automated.
00:19:49.217 --> 00:19:53.777
And there still need to be a
pass, a design pass on everything.
00:19:55.047 --> 00:19:58.697
but if an engineer can get
it like 85%, that's great.
00:19:58.817 --> 00:19:59.557
Then we canâ¦
00:19:59.587 --> 00:20:01.627
We 85%, we can put it
in front of our user,
00:20:03.319 --> 00:20:03.699
Tom: Definitely.
00:20:03.759 --> 00:20:03.869
That
00:20:03.927 --> 00:20:07.647
Domingo: we can start learning, And then,
okay, let's do another pass if we want to.
00:20:08.837 --> 00:20:09.007
yeah.
00:20:09.029 --> 00:20:10.589
Tom: Yeah, that makes a lot of sense.
00:20:10.709 --> 00:20:13.239
And something that hearing you
talk about it makes me think of
00:20:13.269 --> 00:20:16.989
is there are two, two questions.
00:20:17.259 --> 00:20:23.829
One is X number of designers who have,
built their own skills to codify their
00:20:23.829 --> 00:20:30.539
own instincts, what does the pipeline
look like for getting that design insight
00:20:30.569 --> 00:20:32.479
into the stuff that you're building?
00:20:32.569 --> 00:20:37.489
Or is this sort of Domingo-led and
everyone else has to up to that?
00:20:37.679 --> 00:20:41.529
And then I guess related to this is,
have you found there is a line where
00:20:42.399 --> 00:20:46.679
can codify to a certain stage, but then
maybe that's the 85% you're referring
00:20:46.679 --> 00:20:54.839
to, but where is it really difficult
to apply, an AI-defined bar for what
00:20:54.869 --> 00:20:59.129
is good and where does it require
that human input in the process?
00:21:00.871 --> 00:21:05.241
Domingo: so the-- in terms of
skills, designers are-- anybody is
00:21:05.241 --> 00:21:10.481
allowed to create their own skill
and the way the skills work, they
00:21:10.481 --> 00:21:11.881
run on your own machine, basically.
00:21:12.851 --> 00:21:15.081
we do have a team called Team 2X,
which is like 2X, going faster.
00:21:15.081 --> 00:21:15.781
It's like you go-- we go two X faster.
00:21:16.281 --> 00:21:23.231
They basically maintain the skills for
the whole organization, and they have a
00:21:23.241 --> 00:21:28.161
big repository where we have actually--
we've-- what we created for Claude is like
00:21:28.171 --> 00:21:31.871
plugins that then we attach skills to.
00:21:32.041 --> 00:21:36.141
And then those plugins, when you install
your developer environment and you install
00:21:36.151 --> 00:21:39.481
all your things, those skills are there,
and those skills were approved by us.
00:21:39.491 --> 00:21:40.971
So there is like two levels of skills.
00:21:40.971 --> 00:21:43.791
There are skills that are like global
for everybody, like the ones that
00:21:43.801 --> 00:21:45.281
we create for Surge intelligence.
00:21:45.281 --> 00:21:47.571
That's like Surge design,
that's for everybody.
00:21:47.571 --> 00:21:49.051
Surge content, that's for everybody.
00:21:49.131 --> 00:21:50.531
Handoff, that's for everybody.
00:21:51.081 --> 00:21:53.931
But then a designer might have their
own small thing that they created
00:21:53.931 --> 00:21:55.191
for themselves on a day-to-day.
00:21:55.211 --> 00:21:56.411
They should still be allowed to.
00:21:57.291 --> 00:22:01.881
Everybody can contribute to the master
big 2X repository, but they-- there
00:22:01.881 --> 00:22:03.031
is a process where you go through.
00:22:03.031 --> 00:22:07.261
So you actually open a PR and the
Team 2X go-- sees it, and then there's
00:22:07.261 --> 00:22:11.211
a bunch of extra AI review on your
skill to make sure it's as good as
00:22:11.231 --> 00:22:12.991
the skills of the master repository.
00:22:14.021 --> 00:22:16.281
And there is conversation that
happens because designers are
00:22:16.281 --> 00:22:20.351
saying, "Hey, the main intelligence
skills doesn't do this and this.
00:22:20.351 --> 00:22:21.261
Can we have it do this?"
00:22:21.291 --> 00:22:21.991
I'm like, "Okay, cool.
00:22:22.031 --> 00:22:22.501
Let me justâ¦
00:22:23.801 --> 00:22:25.421
you use it in your local for now.
00:22:25.471 --> 00:22:29.201
Let me just put a change for the
master one or like just open a
00:22:29.201 --> 00:22:31.321
PR and then I can upgrade it."
00:22:31.351 --> 00:22:34.381
And then like it basically
works very much like GitHub.
00:22:34.411 --> 00:22:35.921
It's, GitHub basically.
00:22:35.951 --> 00:22:37.171
We're like, "Open a PR.
00:22:37.551 --> 00:22:39.991
I think the skill should be this,"
and then we change the skill because
00:22:39.991 --> 00:22:41.671
it's all kind of a repo basically.
00:22:42.801 --> 00:22:44.881
so that's like the first
part of the question.
00:22:45.011 --> 00:22:45.181
Yeah.
00:22:46.239 --> 00:22:46.539
Tom: Got it.
00:22:46.549 --> 00:22:48.469
And that requires, it
sounds like human judgment.
00:22:48.489 --> 00:22:53.099
Like people are pinging you on Slack or
whatever and saying, a thing," and they
00:22:53.099 --> 00:22:55.809
wanna augment what already exists, and
then you go through that process together.
00:22:55.819 --> 00:22:57.229
It's not fully automated
00:22:57.511 --> 00:22:58.381
Domingo: It's not fully automated.
00:22:58.421 --> 00:23:00.651
You, you-- We go through a
process of should we change it?
00:23:00.651 --> 00:23:01.451
I'll read it.
00:23:02.001 --> 00:23:07.571
And, then the thing that is automated
is once it g-it gets into the
00:23:07.641 --> 00:23:12.501
repository, it doesn't get approved
for everybody until there is a process
00:23:12.501 --> 00:23:16.911
that Claude goes through within those
skills where it improves it based
00:23:16.911 --> 00:23:21.631
on certain criteria that our teams
define for security and for speed and
00:23:21.641 --> 00:23:23.181
for conventions and stuff like that.
00:23:23.951 --> 00:23:24.201
Yeah.
00:23:25.881 --> 00:23:28.021
so that's the first part.
00:23:28.171 --> 00:23:29.551
I can't remember the second
part of the question.
00:23:31.531 --> 00:23:36.571
Tom: it w- it was around the line for
what is codifiable versus will always
00:23:36.571 --> 00:23:44.861
require human judgment, and is the line
you have in your head of what is feasible
00:23:44.881 --> 00:23:48.381
to get that to, or is it a matter of time?
00:23:48.541 --> 00:23:51.711
in, in a few months, will you
be able to get it to 90 or 95%?
00:23:51.711 --> 00:23:56.561
And I guess I'm trying to r- really
understand the
sort of human leverage,
00:23:57.351 --> 00:24:00.421
in the process of getting something
live, especially something that
00:24:00.431 --> 00:24:06.771
is built by an engineer that has
AI judgment into it in some way.
00:24:07.313 --> 00:24:10.913
Domingo: I still think it's,
I think it's a matter of time.
00:24:11.213 --> 00:24:15.913
I still think it's gonna be 85%
for a long time, because humans are
00:24:15.913 --> 00:24:21.203
really good at, creating patterns
between multiple things they see.
00:24:21.493 --> 00:24:26.993
like just spotting, spotting the things
that are related to each other and having
00:24:26.993 --> 00:24:31.043
critical thinking to say, "Actually, I
don't think this is the right thing to
00:24:31.043 --> 00:24:35.743
do for this user, because I've had a
conversation with that user and, and this
00:24:35.743 --> 00:24:37.123
is what they're actually referring to."
00:24:37.153 --> 00:24:41.123
So there is, there is--
the decision-making should
00:24:41.133 --> 00:24:42.853
be like, it's human.
00:24:42.853 --> 00:24:46.783
It's a critical thinking to spot whether
you're tackling the s- the right problem.
00:24:47.673 --> 00:24:51.053
one of the things I tell people sometimes
in this is that you should read.
00:24:51.423 --> 00:24:52.383
Everybody should just read.
00:24:52.423 --> 00:24:54.443
Read books, Read sci-fi.
00:24:54.493 --> 00:24:58.363
Read, because reading, you ha- you're
gonna spend a lot of your pro- time just
00:24:58.363 --> 00:25:02.093
reading and de- decoding information and
figuring out, is this the right thing?
00:25:02.103 --> 00:25:02.923
Is this a bad thing?
00:25:02.933 --> 00:25:06.773
And I've noticed that
also AI tools are veryâ¦
00:25:07.373 --> 00:25:12.083
They wanna please you, so they will go
to great lengths to code the thing that
00:25:12.223 --> 00:25:16.393
you're asking them to code, even if
sometimes you can put as many safeguards
00:25:16.393 --> 00:25:21.933
as you want, but it will still do-- they
will still try to break the rules to
00:25:21.933 --> 00:25:28.203
please you, which will then result in
weird u- design or, duplicated design or
00:25:28.243 --> 00:25:33.703
things that maybe don't make sense or,
things sometimes that if you think about
00:25:33.703 --> 00:25:39.103
them critically, you didn't needed to
build that for V1, You could have built
00:25:39.113 --> 00:25:43.013
half of it, but because you could do it
with AI, AI just build the whole thing,
00:25:43.073 --> 00:25:46.563
and now you're in a position where you
have to "Do we need this whole thing?"
00:25:47.943 --> 00:25:51.683
so I think humans are very good
at, "Maybe we should start smaller.
00:25:51.753 --> 00:25:55.093
We don't need all the, all of
this," when AI will be s- will
00:25:55.123 --> 00:25:56.783
tell you, "I can do everything.
00:25:56.973 --> 00:25:58.403
I can plug in a database.
00:25:58.763 --> 00:26:00.873
I can do it really, fancy for you."
00:26:00.933 --> 00:26:03.333
But that maybe
that's not
what you need, for a user.
00:26:03.333 --> 00:26:05.663
You use-- you might just
need a small, slice.
00:26:06.933 --> 00:26:08.713
and yeah, that's the fight.
00:26:08.823 --> 00:26:11.333
I still think it's gonna
be 85% for a, while.
00:26:11.943 --> 00:26:12.123
Yeah.
00:26:13.289 --> 00:26:13.769
Tom: Makes sense
00:26:15.532 --> 00:26:20.842
Jonny: Domingo, w- I think what you
described yourself as is maybe this
00:26:21.412 --> 00:26:26.622
hybrid type person that lots of people
seem to be talking about, where you're--
00:26:26.622 --> 00:26:32.612
you may be a designer as your first
study, but then you turn into just a
00:26:32.612 --> 00:26:36.852
builder, generally, or you do a little
bit of product thinking and a bit of
00:26:36.852 --> 00:26:39.672
design and then a lot of building,
and that's just what you are now.
00:26:40.002 --> 00:26:47.982
I'm interested to raise it maybe a,
out of Finn-specific, how you feel this
00:26:48.172 --> 00:26:52.652
is gonna drive what a designer does
m-more generally across the industry.
00:26:52.692 --> 00:26:54.622
Like w-what are the
patterns you're seeing?
00:26:54.622 --> 00:26:57.152
What's your predictions
for the future around this?
00:26:57.382 --> 00:27:01.902
will, w-will we all end up in
these, design ops, devopsy roles?
00:27:02.572 --> 00:27:05.422
How many people are gonna be
still shipping products in a more
00:27:05.422 --> 00:27:07.152
traditional product design way?
00:27:08.432 --> 00:27:11.632
d- turning into design engineers, everyone
wants to be one of those at the moment.
00:27:12.552 --> 00:27:16.302
and, what's the role then of, the
pure creativity, divergent thinking,
00:27:16.302 --> 00:27:20.042
all of the stuff that maybe AI
is a bit less good at the moment?
00:27:20.542 --> 00:27:21.787
Domingo: that's a big question, huh?
00:27:22.589 --> 00:27:23.639
Jonny: about seven questions.
00:27:25.227 --> 00:27:25.917
Domingo: theâ¦
00:27:27.537 --> 00:27:32.507
I, think the designers of the
future are all gonna be building.
00:27:33.657 --> 00:27:38.777
Whether the things that they build
goes live to the user, it's unclear.
00:27:38.787 --> 00:27:43.927
You might actually d-don't go live to the
user, But we are all gonna be prototyping
00:27:44.057 --> 00:27:49.537
in the real material, It's just, it's
so much better to be able to join a
00:27:49.537 --> 00:27:53.567
product review or a big presentation
and actually open the product yourself
00:27:53.567 --> 00:27:56.667
and say, "This is what I think the
vision should be, and this is how we're
00:27:56.667 --> 00:28:00.767
gonna help our users," versus showing
a Figma click-through that is gonna
00:28:00.767 --> 00:28:02.987
be like, I don't know if that's true.
00:28:02.997 --> 00:28:03.887
Is that possible?"
00:28:04.317 --> 00:28:08.727
So it really helps designers sell the
vision of the things that they're trying
00:28:08.727 --> 00:28:10.697
to accomplish across the organizations.
00:28:11.177 --> 00:28:13.517
I think everybody sh- will probably beâ¦
00:28:13.837 --> 00:28:19.607
become very comfortable with that
state, being able to just go in and
00:28:19.607 --> 00:28:22.767
ship something to production because
AI tools are gonna be so good that they
00:28:22.767 --> 00:28:27.287
can actually do that, or being able
to just work on vision pieces where
00:28:27.417 --> 00:28:29.847
they can prototype the whole thing
and then give it to the engineers to
00:28:29.847 --> 00:28:31.607
fr- to the engineers to, decode it.
00:28:32.407 --> 00:28:36.207
Some things that I don't think
are gone, are gonna go away are,
00:28:38.067 --> 00:28:39.997
I think designers are veryâ¦
00:28:41.387 --> 00:28:45.737
One of the things I find myself
doing a lot is trying, going back
00:28:45.737 --> 00:28:49.437
to traditional mediums, especially
now that I am using a lot of AI.
00:28:49.947 --> 00:28:54.947
things like paper and pencil and,
trying to, just do some drawing on
00:28:54.947 --> 00:28:58.307
paper and trying to think about, the
future and how things could work.
00:28:59.027 --> 00:29:02.407
I think there is still gonna be a
benefit of designers, especially
00:29:02.647 --> 00:29:07.267
understanding design, and, like, all
of the things that make design good,
00:29:07.317 --> 00:29:09.057
all of the things that make UX good.
00:29:09.637 --> 00:29:14.587
Those fundamental pieces of information,
they should, a designer should still
00:29:15.217 --> 00:29:19.327
know them very deeply, in the same
way a engineer will know very deeply
00:29:19.337 --> 00:29:25.237
when to use a database versus another
database, to code in a certain way for
00:29:25.247 --> 00:29:26.877
it's safe versus another certain way.
00:29:27.117 --> 00:29:30.757
Even if they're not coding, they
have that foundational knowledge
00:29:30.757 --> 00:29:32.307
to be able to do their job better.
00:29:32.817 --> 00:29:35.387
So I think that foundational
knowledge still gonna be
00:29:35.397 --> 00:29:36.797
important for every discipline.
00:29:37.597 --> 00:29:43.317
But when we are now going into the process
of, building, we're all gonna be a bit
00:29:43.317 --> 00:29:46.707
closer to, the things that we're building.
00:29:46.707 --> 00:29:49.927
It's not gonna be like, "Oh, I'm just
gonna pass this design over the fence."
00:29:50.517 --> 00:29:54.197
It's gonna be, I did this yesterday,
which I said to an engineer,
00:29:54.857 --> 00:29:56.297
"I think I can do that myself.
00:29:56.327 --> 00:30:00.117
Why don't you let me design, build
and design that fix myself, and
00:30:00.117 --> 00:30:02.827
then you can get on with the more
complicated pieces of the, work?"
00:30:03.497 --> 00:30:04.367
And he was like, "Yeah, cool.
00:30:04.577 --> 00:30:05.097
Do it."
00:30:05.147 --> 00:30:08.647
And then obviously I used Claude,
and I, previewed it, and it worked.
00:30:08.667 --> 00:30:10.987
And I tested it, and it got shipped.
00:30:11.657 --> 00:30:15.597
But I think- Is
we're all gonna be a bit
closer into that and, we all have to--
00:30:15.597 --> 00:30:20.027
need to have that flexibility to be able
to, lean into each other's, positions.
00:30:20.377 --> 00:30:24.397
I think the foundational knowledge
of, what is good design, what is the
00:30:24.727 --> 00:30:27.737
right problem to solve, that should--
that sh- it shouldn't go away.
00:30:27.737 --> 00:30:31.597
You should still understand this because
that's what gives you the critical
00:30:31.607 --> 00:30:35.247
thinking to examine a prototype and be
like, I think that's not very good."
00:30:36.267 --> 00:30:36.787
or,
00:30:37.267 --> 00:30:37.387
and
00:30:37.887 --> 00:30:39.047
Jonny: Are we talking about taste?
00:30:40.236 --> 00:30:41.086
Domingo: ah, God.
00:30:41.856 --> 00:30:42.086
The
00:30:43.427 --> 00:30:43.917
Jonny: That was a, bit
00:30:43.926 --> 00:30:44.236
Domingo: Yeah.
00:30:44.517 --> 00:30:45.327
Jonny: but also,
00:30:45.366 --> 00:30:45.856
Domingo: Yeah.
00:30:45.946 --> 00:30:46.246
Yeah.
00:30:46.297 --> 00:30:49.517
Jonny: think, everyone is trying to,
decide whether taste is important,
00:30:49.547 --> 00:30:55.187
what taste even is, I wonder if what
you're describing a little bit is you
00:30:55.187 --> 00:31:00.987
can't the hours of looking at stuff
and thinking about things and playing
00:31:00.987 --> 00:31:05.867
with other products and building things
and them being not very good, and you
00:31:05.877 --> 00:31:07.537
thinking, why is that not very good?"
00:31:07.887 --> 00:31:12.827
you just need to go through the reps
enough to be able to build up what
00:31:12.954 --> 00:31:13.474
Domingo: I like that
00:31:13.617 --> 00:31:17.847
Jonny: instant gut on, I can look
at something and just know that it's
00:31:17.847 --> 00:31:19.847
right or wrong, and I can reason why.
00:31:20.147 --> 00:31:21.947
Domingo: I actually love
that way of putting it.
00:31:21.977 --> 00:31:22.777
I might steal it.
00:31:23.297 --> 00:31:26.947
This whole idea of, you just need to spend
time looking at things because I think
00:31:27.007 --> 00:31:34.937
taste is-- There is engineering taste,
there is design taste, there is, strategy
00:31:34.987 --> 00:31:36.857
taste, if you wanna call it taste.
00:31:37.587 --> 00:31:40.667
if you talk to a principal engineer,
when they look at something,
00:31:40.687 --> 00:31:42.027
they can immediately spot.
00:31:42.087 --> 00:31:45.737
They, "Oh, I think that's not gonna
work," or, "I think that's gonna
00:31:45.747 --> 00:31:46.987
give us a problem in the future."
00:31:48.077 --> 00:31:53.497
and that is also a form of taste, in the
sense of, they know what they're talking
00:31:53.497 --> 00:31:55.177
about because they've l- they've seen it.
00:31:55.307 --> 00:32:01.267
And I think I like your framing, which
is we-- people need to use-- we all
00:32:01.267 --> 00:32:05.997
need to develop that knowledge by going
through the process of shipping product,
00:32:05.997 --> 00:32:11.077
of, trying or, and designing more and
designing new things and designing
00:32:11.107 --> 00:32:13.197
multiple things and figuring it out.
00:32:13.547 --> 00:32:14.397
So I like that a lot.
00:32:14.527 --> 00:32:14.737
Yeah.
00:32:15.237 --> 00:32:19.967
Jonny: One thing I have found when,
building-- when designing in code more,
00:32:21.167 --> 00:32:27.797
with, with AI to support is there's a
set of edge cases or, failure states
00:32:27.807 --> 00:32:32.567
and things like that are-- that a
software engineer is uniquely good at
00:32:32.567 --> 00:32:35.747
knowing about that a designer finds it
hard to know about because they just
00:32:35.747 --> 00:32:38.827
don't have the building experience.
00:32:38.957 --> 00:32:43.867
They haven't built the thing, and then
the form needs, failure state or it,
00:32:43.867 --> 00:32:47.357
it-- There needs-- There's some way in
which it can get messed up by some race
00:32:47.357 --> 00:32:51.597
condition, and there needs to be s- The UI
needs to do something in that situation.
00:32:51.597 --> 00:32:54.237
A designer doesn't know that because
they've not ever built it before.
00:32:54.507 --> 00:32:58.357
And I feel like those kind of things,
that is now a superpower that designers
00:32:58.357 --> 00:33:01.417
can have because you'll say to
Claude, "Build this form," and Claude
00:33:01.417 --> 00:33:03.457
will be like, "I built the form,
but I also did all the other stuff
00:33:03.457 --> 00:33:04.367
that you wouldn't have thought of."
00:33:05.357 --> 00:33:07.487
so there's that-- that's amazing.
00:33:07.487 --> 00:33:09.227
You read what Claude's built,
and you're like, "I wouldn't have
00:33:09.387 --> 00:33:10.687
thought of half of those things."
00:33:11.047 --> 00:33:13.817
But then at the same time, you look at
it, and you're like, "This is mental."
00:33:14.267 --> 00:33:19.307
w- no one would enjoy using this at all
because there's way too many things in it.
00:33:19.347 --> 00:33:26.867
And, it's, quite hard to just-- to pin
down exactly one stops and the other
00:33:26.867 --> 00:33:32.767
starts, and one is much more about,
f- and, it's less-- it's harder to
00:33:32.767 --> 00:33:36.337
quantify maybe, and the other one is
very practically like, "Here's how I
00:33:36.337 --> 00:33:39.087
would write the test suite for this,
and I'm gonna make all the tests pass.
00:33:39.517 --> 00:33:42.957
And, I have knowledge of all
the tests ever written, ever.
00:33:43.267 --> 00:33:47.507
So I'm gonna write all the right tests,"
They're, two quite different things.
00:33:48.587 --> 00:33:52.347
but it does feel as a designer,
you s- you get some stuff for free
00:33:52.347 --> 00:33:58.037
straight away, even if some stuff
is, is-- AI's pretty useless at.
00:33:58.537 --> 00:34:01.127
I did have one, one last question
then I'm gonna hand over to Tom 'cause
00:34:01.127 --> 00:34:02.497
I've been asking loads of questions.
00:34:03.637 --> 00:34:09.427
and I'm just curious, in this new
world
that you describe, is Claude enough?
00:34:09.547 --> 00:34:12.757
is Claude the tool that we end up
using as designers, like Claude
00:34:12.787 --> 00:34:15.977
plus, local development server?
00:34:17.377 --> 00:34:18.907
are we gonna go further with tools?
00:34:19.567 --> 00:34:23.577
is there a tool that you wish
existed, for this kind of workflow?
00:34:24.612 --> 00:34:26.452
Domingo: I, yeah, I don't thinkâ¦
00:34:26.532 --> 00:34:27.882
Claude is what we're using right now.
00:34:28.182 --> 00:34:29.182
I think it's gonna change.
00:34:30.032 --> 00:34:31.822
we should al- be open to change as well.
00:34:32.562 --> 00:34:35.132
so if, a new one comes
in, let's just use it.
00:34:36.592 --> 00:34:42.252
I think the, m- I think models
are com- they're gonna converge.
00:34:42.772 --> 00:34:46.702
I, in, in many ways I feel, like this
is getting, they're getting really good.
00:34:47.212 --> 00:34:50.302
But one of the things I've been learning
a lot around is like when to useâ¦
00:34:50.752 --> 00:34:54.202
And partly because I'm paying for my own
Mac subscription on the side, and I wanna
00:34:54.212 --> 00:34:59.392
be, I wanna have some economy in the way
I'm using my tokens, co- token economy.
00:34:59.752 --> 00:35:05.172
So I've been using things like
I'm gonna use Fable to plan, and
00:35:05.172 --> 00:35:08.482
then I'm gonna use Sonnet or 4.0,
00:35:08.482 --> 00:35:08.742
4.8,
00:35:08.762 --> 00:35:12.962
like Opus to execute, and then I'm
gonna use Fable again at the be- at
00:35:12.962 --> 00:35:17.402
the very end to just review as a,
principle, and then you start likeâ¦
00:35:17.782 --> 00:35:19.752
I think that's gonna be very
interesting, like just playing
00:35:19.752 --> 00:35:23.032
with models and you can see like
Sonnet is pretty good at executing.
00:35:24.172 --> 00:35:25.942
so I think things will change.
00:35:25.982 --> 00:35:31.102
The tools that I wish existed, which is
a problem that I find myself having all
00:35:31.112 --> 00:35:36.842
the time, is I go through this whole
process of building things and like I
00:35:36.842 --> 00:35:39.622
just build a bunch of designs and Iâ¦
00:35:40.422 --> 00:35:44.582
it's already in production or like it's
in some pla-playground that I build and
00:35:44.582 --> 00:35:49.262
I have an experimental build, and then
what I find myself going throughâ¦
00:35:49.772 --> 00:35:53.002
I have this discussion on a weekly basis,
which is I talk to some of the designers,
00:35:53.002 --> 00:35:55.652
I'm like, should we put this in Figma?"
00:35:56.332 --> 00:35:58.782
And should we, sh-shâ¦"
00:35:59.172 --> 00:36:01.392
and it's "Sh- should we do it?"
00:36:02.292 --> 00:36:02.632
And, weâ¦
00:36:02.682 --> 00:36:06.412
The thing about it and the, real problem
that we're missing is like Figma is really
00:36:06.412 --> 00:36:12.522
good to sometimes put things on a page and
have a presentation and align, like align.
00:36:12.682 --> 00:36:13.042
Let's align.
00:36:13.532 --> 00:36:14.392
Let's align on this.
00:36:14.672 --> 00:36:16.422
Let's add a couple of comments, align.
00:36:16.442 --> 00:36:17.602
This is version one.
00:36:17.662 --> 00:36:21.032
And then I think builds
and experimental builds and
00:36:21.032 --> 00:36:22.392
prototypes are s- it's not good.
00:36:22.672 --> 00:36:26.752
you still, you're like hunting
for the latest link or or you're
00:36:26.802 --> 00:36:28.432
asking yourself, "Is that live?
00:36:28.832 --> 00:36:29.452
Is it live?
00:36:29.502 --> 00:36:30.642
Let me just go check it."
00:36:31.162 --> 00:36:31.792
It is live.
00:36:31.822 --> 00:36:32.762
It was shipped yesterday.
00:36:32.762 --> 00:36:38.162
And you're like, "Oh, So I think I find
myself, like to-today after this call,
00:36:38.342 --> 00:36:42.612
I have to go to Figma, and I have to map
something because it would be really good
00:36:42.612 --> 00:36:49.692
for our team to align on like the state of
play, And I think nobody has cracked that.
00:36:49.692 --> 00:36:50.812
Like they've, there isâ¦
00:36:50.812 --> 00:36:55.582
Figma has this thing code to Figma
where you can do it automatically.
00:36:55.592 --> 00:36:56.382
It's terrible.
00:36:57.052 --> 00:36:58.052
It doesn't work.
00:36:58.632 --> 00:37:00.152
It, doesn't, it's not true.
00:37:00.162 --> 00:37:02.332
It does, it looks like an,
entirely different thing.
00:37:02.962 --> 00:37:05.592
So s- designers end up taking
screenshots and putting them
00:37:05.592 --> 00:37:07.932
in Figma and annotated them.
00:37:07.932 --> 00:37:13.892
So it's just this kind of this
alignment tool, like this like
00:37:14.105 --> 00:37:14.505
Jonny: Yeah
00:37:14.782 --> 00:37:21.306
Domingo: coding infinite coding canvas
where things are code, but also you can
00:37:21.306 --> 00:37:23.256
comment and you can align and you canâ¦
00:37:24.256 --> 00:37:25.086
Basically, we are trying
00:37:25.221 --> 00:37:25.371
Jonny: it's
00:37:25.406 --> 00:37:26.896
Domingo: to replicate, yeah
00:37:27.001 --> 00:37:31.681
Jonny: it's, slower than the actual
code base to, to put stuff into?
00:37:31.681 --> 00:37:33.311
You actually then do have to wait
00:37:34.554 --> 00:37:36.044
Domingo: Yeah, it's just a pain.
00:37:36.074 --> 00:37:36.504
It's just--
00:37:36.701 --> 00:37:37.421
Jonny: feet all the time.
00:37:37.421 --> 00:37:37.971
Yeah
00:37:38.074 --> 00:37:41.384
Domingo: Yeah, it's a pain, and
it's just oh my God, I, I-- Because
00:37:41.384 --> 00:37:43.494
I do think, whiteboards are great.
00:37:44.094 --> 00:37:44.364
you
00:37:44.784 --> 00:37:49.094
having a whiteboard, running through
things, putting a sticker, and then
00:37:49.094 --> 00:37:51.884
showing it to somebody and being like,
"Hey, I think this is what we should do."
00:37:53.184 --> 00:37:55.474
that doesn't go away, and I
think we've tried to replicate
00:37:55.474 --> 00:37:56.544
that with Figma, with Miro.
00:37:57.054 --> 00:38:01.204
It works really well in those tools,
but
I think now we're all, coding
00:38:01.204 --> 00:38:03.684
and building prototypes, so we're
like, "Okay, but how do I take
00:38:03.684 --> 00:38:05.104
these prototypes and align on them?"
00:38:05.104 --> 00:38:07.684
So you have to take screenshots
of them, put them back into Figma,
00:38:08.074 --> 00:38:09.464
and be like, "This is version one."
00:38:10.214 --> 00:38:12.234
Or some of us, we don't even do that.
00:38:12.244 --> 00:38:14.144
We're like, "Oh, let me just
show you my latest build."
00:38:14.264 --> 00:38:18.594
But then wh- when you don't do
that, then you end up missing
00:38:18.594 --> 00:38:20.404
the, "What was that version again?
00:38:20.404 --> 00:38:21.504
What did we ship last week?"
00:38:22.427 --> 00:38:22.777
Jonny: Yeah
00:38:23.694 --> 00:38:25.234
Domingo: That's-- I wish
something like that existed,
00:38:25.414 --> 00:38:29.754
Tom: when I saw the state of the, of what
you were working on back in February,
00:38:29.774 --> 00:38:34.674
early this year, and specifically, you
walked through an example where you were
00:38:35.554 --> 00:38:43.244
Claude Code to, basically audit your
code base to understand variations of
00:38:43.244 --> 00:38:46.144
design patterns that have been used,
and you were using that as a way to
00:38:46.164 --> 00:38:52.104
consolidate, the design system and the
sort of and, various things like this.
00:38:52.914 --> 00:38:55.574
the team, and what you're doing now
with Surge Intelligence sounds like
00:38:56.364 --> 00:39:03.264
step beyond that in terms of, almost
zooming design judgment out to apply to
00:39:03.274 --> 00:39:07.194
a broader range of people and unifying
things across the wider business.
00:39:07.914 --> 00:39:14.334
I'm curious how much of that you think
is a temporary problem, or a temporary
00:39:14.344 --> 00:39:18.284
infrastructure that needs putting in
place, and in six months you'll move on
00:39:18.284 --> 00:39:25.154
to something else, versus this being a two
or three-year that you think you'll face.
00:39:25.214 --> 00:39:29.704
Do you have a sense of what that future
looks like for the shape of this role
00:39:29.704 --> 00:39:32.024
and this type of infrastructure layer?
00:39:32.945 --> 00:39:34.385
Domingo: I think it w- it willâ¦
00:39:35.295 --> 00:39:38.285
Once we have things in place,
it will be-- There's gonna
00:39:38.285 --> 00:39:39.705
be less time on it, for sure.
00:39:40.495 --> 00:39:45.285
Which means that, Because a lot of the
work that we have to go through right
00:39:45.285 --> 00:39:48.325
now, it's like we have to re-examine
some of those decisions and be like,
00:39:49.475 --> 00:39:51.115
"Why do headers work this way?"
00:39:51.875 --> 00:39:54.365
w-why is-- How should they be composed?
00:39:54.365 --> 00:39:57.935
And we have to write them and, figure
out the best way to write them for
00:39:57.935 --> 00:39:59.825
AI, so AI can do them without us.
00:39:59.875 --> 00:40:03.765
So I think there's gonna be
a big lift to get it set up.
00:40:04.595 --> 00:40:09.975
Then we're gonna see, like maybe less
time put on it, and it's just more of aâ¦
00:40:10.005 --> 00:40:14.925
more about maintaining it, adding new
things, or, doing, big ch-shifts into,
00:40:15.145 --> 00:40:18.245
maybe we're redesigning everything
again, and we need to do it again.
00:40:19.125 --> 00:40:23.915
so it's gonna be less time, but I do
think that there is gonna be some form
00:40:23.915 --> 00:40:28.545
of infrastructure team, like our 2X
team, like a builder's tool team, like
00:40:28.545 --> 00:40:34.125
dedicated in every company to just fig-
ex- Because when I'm not doing that,
00:40:34.125 --> 00:40:38.125
I'm exploring new tools and exploring
new ways to com- use AI for the team.
00:40:38.665 --> 00:40:43.655
so the-- This is gonna be important
because I think the codebase keep
00:40:43.655 --> 00:40:45.795
growing, new patterns keep getting added.
00:40:45.865 --> 00:40:47.155
There is more use cases.
00:40:47.715 --> 00:40:52.605
There is more complexity, so you have
to continually train the tools so
00:40:53.215 --> 00:40:56.185
they kind of-- they understand how
to apply th- certain things better.
00:40:57.375 --> 00:41:01.415
but yeah, it's not gonna be the big, the
biggest lift in the future because it's
00:41:01.415 --> 00:41:06.215
gonna be like a normal thing that we do,
What I don't think is gonna happen is
00:41:06.225 --> 00:41:12.115
that we're just not gonna leave it and
not touch it, which some teams do in, in,
00:41:12.425 --> 00:41:14.565
like in the old school design systems.
00:41:15.175 --> 00:41:17.965
You, build like a bunch of it, and then
you leave it, and then you kinda justâ¦
00:41:18.705 --> 00:41:19.525
You let it die.
00:41:20.085 --> 00:41:24.095
I think we're gonna con- continuously
work on, on, on, the, on this type
00:41:24.095 --> 00:41:30.035
of infrastructure because it makes
AI better at coding, designing.
00:41:30.165 --> 00:41:35.335
So why would you not want to make your
AI better at coding all the time, you can
00:41:35.335 --> 00:41:41.215
help all your engineers, in one go without
even nee- without even-- without them even
00:41:41.215 --> 00:41:42.695
knowing that you're get- helping them.
00:41:43.405 --> 00:41:45.785
It's not like before where we have to
go and enforce it, and we have to say
00:41:45.785 --> 00:41:47.055
to a team, "Hey, you should use this."
00:41:47.535 --> 00:41:51.185
Now we-- It's happening because
Claude is already doing it, so
00:41:51.705 --> 00:41:53.005
I think it's gonna be, likeâ¦
00:41:53.415 --> 00:41:56.335
It makes sense to continue
to train these brains,
00:41:57.378 --> 00:41:58.458
Tom: Yeah Got it.
00:41:58.468 --> 00:42:02.368
So yeah, hearing you talk about it
like that is less of a ship goal of
00:42:02.438 --> 00:42:06.708
establishing this infrastructure for how
you work and more of an outcome, which is
00:42:06.708 --> 00:42:14.278
that you're optimizing for the design team
or accelerating
design at Fin as much as
00:42:14.278 --> 00:42:16.988
you can anyone who is shipping anything,
00:42:17.378 --> 00:42:17.588
which
00:42:17.617 --> 00:42:17.917
Domingo: Yeah.
00:42:18.208 --> 00:42:19.478
Tom: designers and engineers right now.
00:42:20.037 --> 00:42:20.287
Domingo: yeah.
00:42:20.347 --> 00:42:24.807
And also, there is some PMs as well
using this kind of stuff to, prototype.
00:42:24.857 --> 00:42:27.587
Some marketing people using
their stuff to prototype.
00:42:27.587 --> 00:42:29.007
So I, justâ¦
00:42:29.407 --> 00:42:34.397
I would quite a future where a designer--
because e- as much as you hire for them
00:42:34.397 --> 00:42:37.527
and you talk to designers, sometimes
they put things on a page and they
00:42:37.527 --> 00:42:39.497
start questioning comp- components.
00:42:39.497 --> 00:42:43.717
They're like, "Maybe the
input fields should do this."
00:42:44.257 --> 00:42:45.557
And you're like: But
why are you doing that?
00:42:45.767 --> 00:42:46.827
you're wasting your time.
00:42:47.217 --> 00:42:48.577
you're literally wasting your time.
00:42:48.957 --> 00:42:52.807
And I wanna get it to a point where,
AI can just do all of that for them.
00:42:53.287 --> 00:42:55.747
It can just be like, "This is the
optimal page for your use case."
00:42:56.227 --> 00:42:59.637
And then their time is, "Okay, but what
is the use case that we haven't seen?"
00:43:00.087 --> 00:43:03.347
Or, "Do we need to do a different
product entirely because
00:43:03.357 --> 00:43:04.287
this doesn't work for this?"
00:43:04.847 --> 00:43:05.427
And they canâ¦
00:43:05.477 --> 00:43:09.187
All of those low-level decisions, it
could just be done for them, essentially.
00:43:10.237 --> 00:43:13.177
I think this is gonna be different
for more creative disciplines like,
00:43:13.797 --> 00:43:16.317
graphic design, like campaign design.
00:43:16.327 --> 00:43:17.957
Those things will still need theâ¦
00:43:17.957 --> 00:43:22.357
But, if you're just designing a flow
and there is an optimal way to design
00:43:22.357 --> 00:43:26.297
a flow, do you really need to redesign
the flow every time you design the flow?
00:43:26.687 --> 00:43:29.747
Or should AI just design the flow
for you, and then you can just
00:43:29.747 --> 00:43:33.927
focus on, like, where is-- where
are people dropping off and why?
00:43:33.957 --> 00:43:37.507
And, is this the right flow for
this, or should it be another one?
00:43:38.177 --> 00:43:39.597
I don't know if that's a
good way to explain it.
00:43:40.337 --> 00:43:41.127
but yeah.
00:43:41.314 --> 00:43:42.494
Tom: Yeah, that makes sense.
00:43:42.874 --> 00:43:43.374
Excellent.
00:43:44.024 --> 00:43:45.044
Thank you so much, Domingo.
00:43:45.154 --> 00:43:48.314
We will wrap up with a couple
of quick-fire questions.
00:43:49.034 --> 00:43:50.684
have one picked out that I'm gonna ask.
00:43:51.574 --> 00:43:54.074
we started recording, Domingo, you
mentioned about how you just moved
00:43:54.074 --> 00:43:59.874
into a new house, and y- you were
talking about Vitsoe shelving, super
00:44:00.414 --> 00:44:07.374
nice forever lasting shelving for the
house, which inspire this question.
00:44:07.374 --> 00:44:09.364
I'm definitely leading,
you down that path.
00:44:09.374 --> 00:44:10.444
That wasn't actually my intention.
00:44:10.444 --> 00:44:11.664
It was more just to set context.
00:44:11.664 --> 00:44:14.804
But anyway, the question it made
me think of is that, when AGI
00:44:14.824 --> 00:44:21.094
takes over everything, and you no
longer need to design or be coding
00:44:21.134 --> 00:44:25.124
things in for Fin, what will you
be doing with your free time?
00:44:25.434 --> 00:44:26.234
Where will that energy go?
00:44:28.217 --> 00:44:31.447
Domingo: I will be doing two things,
and this, it's just gonna sound the
00:44:31.447 --> 00:44:33.427
most tech bro thing, the first one.
00:44:33.797 --> 00:44:37.897
But the first one will be like, I'll
probably go be making fancy coffee
00:44:37.967 --> 00:44:42.867
somewhere, and going very deep into
what is the right beans to choose.
00:44:44.587 --> 00:44:48.177
and the second thing then, and that
I will probably be using is drawing.
00:44:48.627 --> 00:44:54.497
So I-- You don't see it here, but I do,
like I have I have a whole easel here
00:44:54.597 --> 00:44:56.287
that I have on the side of my desk.
00:44:56.317 --> 00:45:01.147
So where I like, I can, I do
drawing, so I quite like it.
00:45:01.727 --> 00:45:05.737
so either drawing, make- making
coffee, painting miniatures.
00:45:06.047 --> 00:45:06.957
Yeah, stuff like that.
00:45:07.257 --> 00:45:07.427
Yeah.
00:45:07.600 --> 00:45:07.730
Tom: That
00:45:07.799 --> 00:45:07.989
Jonny: Go ahead, man
00:45:08.170 --> 00:45:09.270
Tom: very, yeah,
00:45:09.287 --> 00:45:09.577
Domingo: sir.
00:45:10.077 --> 00:45:12.467
Jonny: you don't subscribe to any
of the stereotypes of someone who
00:45:12.467 --> 00:45:13.717
works in tech at all, Domingo?
00:45:13.790 --> 00:45:14.250
Domingo: I know.
00:45:14.300 --> 00:45:14.710
At all.
00:45:14.770 --> 00:45:15.160
At all.
00:45:15.390 --> 00:45:15.670
At all.
00:45:15.780 --> 00:45:16.340
Yeah, it'sâ¦
00:45:16.410 --> 00:45:16.780
Yeah.
00:45:16.840 --> 00:45:17.180
Wow.
00:45:17.680 --> 00:45:17.880
Tom: Love it
00:45:18.835 --> 00:45:21.205
Jonny: the coffee nerd
arc is alive and well.
00:45:22.215 --> 00:45:29.525
w- quick-fire question is m-maybe
more basic, but what is the product
00:45:29.555 --> 00:45:35.355
that you look at that makes you
think, "I wish I'd designed that"?
00:45:37.235 --> 00:45:38.205
Product you love to use.
00:45:38.555 --> 00:45:38.815
It can
00:45:38.921 --> 00:45:39.121
Domingo: This
00:45:39.435 --> 00:45:39.895
Jonny: product,
00:45:40.821 --> 00:45:41.621
You're not allowed to say
00:45:41.875 --> 00:45:42.395
Vitsoe Shelves
00:45:43.611 --> 00:45:43.761
Domingo: a physical product.
00:45:43.911 --> 00:45:45.271
I'm not allowed to say Vitsoe Shelf.
00:45:45.951 --> 00:45:46.781
That is tough.
00:45:48.141 --> 00:45:52.281
there is a product that I keep coming back
to, and I tried to build this on my own as
00:45:52.281 --> 00:45:53.801
well, but I just keep coming back to it.
00:45:55.491 --> 00:45:56.351
it's called MyMind.
00:45:57.951 --> 00:46:04.921
and I built a version of
it locally that it does it.
00:46:05.371 --> 00:46:08.641
I've used all of the inspiration tool
version things that are in there,
00:46:08.671 --> 00:46:12.531
but I just keep coming back for it
because it's just really simple,
00:46:12.531 --> 00:46:14.031
really nice, really nicely designed.
00:46:14.031 --> 00:46:16.671
It has really nice onboarding,
really nice interactions, and it
00:46:16.681 --> 00:46:22.421
really, promotes, your spaces where
you can save your own inspiration.
00:46:22.441 --> 00:46:26.881
It has, this, after you ser- reach
certain milestones on the things you're
00:46:26.891 --> 00:46:32.551
saving, you get these, 3D cards or
achievements, and then they unlock
00:46:32.571 --> 00:46:36.731
backgrounds, and it just really feels that
you have a s- a garden of inspiration.
00:46:37.231 --> 00:46:38.151
I keep coming back to it.
00:46:38.151 --> 00:46:39.601
I really like it, the product.
00:46:39.991 --> 00:46:43.821
I think it's done by Tobias van Schneider,
which is, the ex-designer of Spotify.
00:46:44.551 --> 00:46:46.591
And I think I've left it.
00:46:46.701 --> 00:46:47.531
I tried to build it.
00:46:47.561 --> 00:46:48.681
I could come back to it.
00:46:48.771 --> 00:46:51.791
I really like it, and I think
it's really important for
00:46:51.791 --> 00:46:53.651
designers to just save things.
00:46:54.321 --> 00:46:57.631
Save, look at things, prune them.
00:46:58.151 --> 00:47:01.251
when, in, six months, look at them
again and be like, "I actually don't
00:47:01.261 --> 00:47:03.681
like this inspiration board anymore.
00:47:03.781 --> 00:47:04.501
Let me just prune it."
00:47:04.531 --> 00:47:09.161
Because that's a part of developing what
you like and what you don't, essentially.
00:47:09.261 --> 00:47:09.551
Jonny: Yeah, I
00:47:09.631 --> 00:47:10.121
Domingo: So Iâ¦
00:47:10.141 --> 00:47:13.071
Jonny: were talking about earlier is like
they're the b- they're the reps, right?
00:47:13.281 --> 00:47:13.851
that's the--
00:47:13.961 --> 00:47:14.261
Domingo: Yeah.
00:47:14.391 --> 00:47:17.601
Jonny: you're exercising your
judgment every day and building
00:47:17.601 --> 00:47:20.011
it and changing it and yeah.
00:47:20.811 --> 00:47:21.091
Domingo: Yep.
00:47:21.181 --> 00:47:21.201
Yeah.
00:47:21.361 --> 00:47:22.061
Jonny: my mind as well.
00:47:22.921 --> 00:47:24.171
Domingo: Yeah, I use it a lot,
00:47:24.471 --> 00:47:25.641
Jonny: building a bookmarking tool
00:47:26.521 --> 00:47:30.761
Domingo: Yeah, I've tried and it just-- it
works, but it's just not it's not as cool.
00:47:31.381 --> 00:47:31.701
yeah.
00:47:31.923 --> 00:47:32.283
Jonny: yeah.
00:47:33.771 --> 00:47:34.181
Domingo: so
00:47:34.213 --> 00:47:34.493
Jonny: do it.
00:47:34.993 --> 00:47:35.663
Tom: he'll do it well
00:47:35.663 --> 00:47:35.963
Jonny: Yeah.
00:47:35.963 --> 00:47:37.373
So are we done?
00:47:37.373 --> 00:47:38.023
Should we wrap?
00:47:38.090 --> 00:47:38.430
Tom: that's it.
00:47:38.560 --> 00:47:38.910
Yeah.
00:47:39.037 --> 00:47:39.297
Domingo: Try it
00:47:39.800 --> 00:47:41.380
Tom: any final things you wanted
to mention that you didn't
00:47:41.390 --> 00:47:42.480
have a chance to, Domingo?
00:47:43.215 --> 00:47:44.625
Domingo: No, just thank
you so much for having me.
00:47:44.625 --> 00:47:45.375
This has been great.
00:47:45.415 --> 00:47:46.545
Jonny: where do we find you online?
00:47:47.045 --> 00:47:51.845
Domingo: I am on X, and on LinkedIn, and
I have a website that I haven't updated
00:47:51.855 --> 00:47:54.555
in a while, but mostly X and LinkedIn.
00:47:54.635 --> 00:47:54.905
Yeah.
00:47:55.335 --> 00:47:56.845
I will answer in those channels.
00:47:56.915 --> 00:47:57.135
Yeah
00:47:57.990 --> 00:47:58.400
Jonny: Awesome.
00:47:58.790 --> 00:47:59.640
Thank you, Domingo.
00:48:00.705 --> 00:48:00.955
Tom: Yeah,
00:48:01.070 --> 00:48:01.630
Jonny: been fascinating
00:48:02.817 --> 00:48:03.547
Domingo: Thank you so much, guys
00:48:08.140 --> 00:48:11.420
Tom: If you have any feedback on the
podcast, good or bad, please drop us
00:48:11.420 --> 00:48:14.550
a note at podcast@nearfuture.works.
00:48:14.550 --> 00:48:15.360
We'd love to hear it.
00:48:16.180 --> 00:48:17.170
Oh, and one final thing.
00:48:17.210 --> 00:48:19.170
Last week, we announced a new
workshop we're opening up to
00:48:19.170 --> 00:48:22.350
individuals to build your own
design tools on the 13th of August,
00:48:22.410 --> 00:48:24.110
find out more and grab your spot
over at nearfuture.works/build.
00:48:26.610 --> 00:48:27.380
Catch you next week.