TRANSCRIPT 🔗
WEBVTT
NOTE
This file was generated by Descript
00:00:04.283 --> 00:00:07.423
Tom: Hello, welcome to the Near
Future Podcast with, Tom and Jonny.
00:00:07.943 --> 00:00:12.253
This is a solo episode or a duo
episode, I guess is the correct term.
00:00:12.813 --> 00:00:16.433
It's September, we're catching
up after the summer holidays.
00:00:16.433 --> 00:00:17.663
It's back to school week.
00:00:17.743 --> 00:00:19.213
It's raining here in London.
00:00:19.883 --> 00:00:23.823
but we're back to share a roundup of
what we've been up to, who we've been
00:00:23.823 --> 00:00:27.483
speaking with, and some other overall
themes, that are happening right now.
00:00:27.923 --> 00:00:31.233
So, Jonny, any quick thoughts following
your, your back to school week?
00:00:31.233 --> 00:00:31.853
How's it going?
00:00:32.985 --> 00:00:37.805
Jonny: So after a sweltering hot
summer, I'm looking out the window,
00:00:37.825 --> 00:00:44.235
it's raining, feeling a certain
amount of hygge, and, feeling cozy.
00:00:44.635 --> 00:00:45.975
Let's have a cozy episode, Tom.
00:00:45.975 --> 00:00:46.595
That's what I think.
00:00:47.321 --> 00:00:47.651
Tom: Yeah.
00:00:48.271 --> 00:00:51.511
I'm excited to see what the,
automated transcript does with
00:00:51.521 --> 00:00:53.031
that, pronunciation there.
00:00:53.281 --> 00:00:53.801
We'll see.
00:00:54.485 --> 00:00:55.435
Jonny: I'm sure it'll get it right.
00:00:55.545 --> 00:00:55.815
Yeah.
00:00:55.971 --> 00:00:57.531
Tom: You, you, you nailed it, I think.
00:00:57.755 --> 00:00:58.105
Jonny: Thank you.
00:00:58.825 --> 00:00:59.075
Thank you
00:00:59.651 --> 00:01:00.811
Tom: yeah, I, I agree with that.
00:01:01.871 --> 00:01:06.821
So, yeah, so I figured we could start off
by doing a little bit of a roundup, of
00:01:06.871 --> 00:01:09.811
some of the guests we spoke to throughout
August, 'cause we-- there were four of
00:01:09.811 --> 00:01:13.911
them, I think, and then both of us were
on holiday at different points and,
00:01:14.451 --> 00:01:18.531
sort of dropped off the social media
landscape, so we didn't really talk
00:01:18.541 --> 00:01:19.881
about any of these posts going live.
00:01:20.281 --> 00:01:22.821
so if you don't subscribe to this
podcast, you might have missed them.
00:01:23.641 --> 00:01:27.101
but yeah, I thought we could just talk
a- talk about, some any-- some high-level
00:01:27.101 --> 00:01:28.881
takeaways from, from them first.
00:01:29.541 --> 00:01:35.001
How about, our first episode at the early
part of August was James Storer of Monzo.
00:01:35.721 --> 00:01:36.741
any takeaways from that, Jonny?
00:01:38.375 --> 00:01:42.915
Jonny: Feels like a decade ago, being
the other side of summer holidays.
00:01:43.015 --> 00:01:48.035
And yeah, we're, we're really showing
our, age by being terrible at clipping and
00:01:48.075 --> 00:01:52.105
getting our clip- our interesting tidbits
out into the world and talking about them.
00:01:52.105 --> 00:01:55.425
So, please everyone
Load full transcript
do go
and look at back issues.
00:01:55.425 --> 00:01:56.930
some really, good stuff in there.
00:01:57.255 --> 00:01:58.165
yeah, James.
00:01:58.565 --> 00:02:00.585
Oh man, I've, I've known
James for a long time.
00:02:00.865 --> 00:02:03.365
It was a really fun chat for me.
00:02:04.145 --> 00:02:10.005
think in terms of what he's been doing,
he is-- he's always designed fast.
00:02:10.005 --> 00:02:13.285
He's always had, had 100 ideas an hour.
00:02:15.045 --> 00:02:19.315
we're quite similar in that way, and he's
always, to just create and create and
00:02:19.315 --> 00:02:21.685
create and create, since way before AI.
00:02:21.995 --> 00:02:26.995
And hearing him now at Monzo just
being unleashed, he is the biggest
00:02:27.045 --> 00:02:29.235
token spender in the company.
00:02:29.235 --> 00:02:34.135
and him talking about their of fake
version of the Monzo app that they use
00:02:34.135 --> 00:02:39.235
for prototyping and for getting confident
about things that they're gonna ship.
00:02:39.315 --> 00:02:44.025
You know, the, the design process
or the discovery process resulting
00:02:44.025 --> 00:02:47.975
in higher level of, of confidence
when you go and put something out,
00:02:48.695 --> 00:02:51.985
by building this extraordinarily
deep, prototype, basically.
00:02:52.035 --> 00:02:57.225
Including data, including different
state, that they can, manipulate.
00:02:57.265 --> 00:02:59.095
Anyone can manipulate and
build anything they want.
00:02:59.905 --> 00:03:05.165
It's a really good example, I think,
of a design team on a really ambitious
00:03:05.175 --> 00:03:09.595
project around vibe coding, which
is basically what this is, and using
00:03:09.595 --> 00:03:13.115
it for real business value rather
than just fun stuff at the side.
00:03:13.115 --> 00:03:17.475
So yeah, it was really great to hear
about that alongside his silly experiments
00:03:17.475 --> 00:03:22.435
at home, forcing the rest of his family
to use his harebrained apps and taking
00:03:22.435 --> 00:03:23.735
over the telly and stuff like that.
00:03:23.775 --> 00:03:26.305
So, yeah, a really fun episode.
00:03:26.995 --> 00:03:31.145
next up we had Randy, Notion legend, SVA.
00:03:32.645 --> 00:03:33.745
Tom, what were your thoughts?
00:03:35.129 --> 00:03:39.549
Tom: Yeah, I really enjoyed the chat
with, with Randy and how he balances
00:03:39.549 --> 00:03:44.419
everything, how he manages to fit in
what appears to be a full-time role
00:03:44.439 --> 00:03:49.029
as head of design at Notion, alongside
a full-time role of chair of the MFA
00:03:49.029 --> 00:03:51.399
in design program at SVA in New York.
00:03:52.359 --> 00:03:54.389
That's a lot of tasks on his plate.
00:03:55.059 --> 00:03:58.899
but it seemed like they were very
complementary, like the, the practical
00:03:58.899 --> 00:04:05.409
aspects of understanding the intricacies
of working on building tooling around
00:04:05.419 --> 00:04:10.029
agentic workflows in Notion directly
contributed
to how he set up the
00:04:10.539 --> 00:04:18.069
operational aspects of SVA and having
SVA become a, a Notion customer.
00:04:19.269 --> 00:04:26.619
I think the, the one thought I've been
left thinking about is around ⦠He,
00:04:26.629 --> 00:04:32.559
he gave this reference to thinking like
a, a, an old school graphic designer
00:04:33.169 --> 00:04:37.349
going to a printing press and speaking
to the printer around, or the, the
00:04:37.349 --> 00:04:43.229
person who is in charge of the printer,
around how to get the best translation
00:04:43.249 --> 00:04:48.739
of a design from a graphic designer's
intent into the actual output of the
00:04:48.739 --> 00:04:53.049
work, and really involving them early
in the process and collaborating with
00:04:53.049 --> 00:04:55.079
the printer to get that great execution.
00:04:55.439 --> 00:04:59.279
And he made a reference to this as it
re- relates to an engineering perspective
00:04:59.279 --> 00:05:01.419
for digital product design today.
00:05:01.509 --> 00:05:04.959
And I really like that, that framing
because I think there's a lot of
00:05:05.419 --> 00:05:10.199
talk at the moment around how AI is
turning everyone into a design engineer
00:05:10.409 --> 00:05:13.109
because every designer is writing code.
00:05:13.349 --> 00:05:18.729
But there is quite a big difference
between having an AI agent write that code
00:05:18.809 --> 00:05:25.099
versus understanding the, the constraint
of the medium and the grain of the
00:05:25.099 --> 00:05:27.409
medium on which you're designing against.
00:05:28.049 --> 00:05:30.819
And so yeah, I like that example
from Randy, but I think it's also
00:05:30.819 --> 00:05:36.749
just a, a theme for us to, to take
into how we're pushing back against
00:05:36.849 --> 00:05:41.589
the constraints of engineering with
respect and understanding for the
00:05:41.599 --> 00:05:46.009
medium, rather than trying to overcome
it through AI as this magical tool.
00:05:47.975 --> 00:05:48.295
Jonny: Yeah.
00:05:49.505 --> 00:05:53.745
Yeah, I just also love nerding
out about Notion with, with him.
00:05:55.475 --> 00:05:55.795
Tom: Yeah.
00:05:55.855 --> 00:05:56.355
So true
00:05:56.375 --> 00:05:59.425
Jonny: yeah, as, as Notion fans,
to be able to talk Notion and hear
00:05:59.425 --> 00:06:04.825
how they their agents inside Notion
in the open and, yeah, really cool.
00:06:06.115 --> 00:06:10.305
to, to-- Yeah, that-- It's like an
iconic-- Especially as designers,
00:06:10.305 --> 00:06:12.365
I feel like every designer signs
up for Notion personally, even
00:06:12.365 --> 00:06:13.415
if they don't use it at work.
00:06:13.415 --> 00:06:17.585
So have someone talking about how they use
it internally is, is really fascinating.
00:06:18.445 --> 00:06:25.925
up, we had Patrick, from Klay, who
is a four times founding designer.
00:06:27.475 --> 00:06:30.075
so, you know, glutton for punishment.
00:06:33.845 --> 00:06:38.065
you know, if, if you wanna join a company
as, as
the first designer, then you
00:06:38.075 --> 00:06:43.555
gotta, you gotta know that you're gonna
be subject to the full force of, of
00:06:43.695 --> 00:06:47.425
founders being like, "It doesn't feel
right," basically over and over again
00:06:47.435 --> 00:06:48.985
for however many years you're there.
00:06:50.295 --> 00:06:54.105
and, variants of that, you know,
get-getting into something, building
00:06:54.105 --> 00:06:57.545
something beautiful, and then it hitting
the cutting room floor immediately.
00:06:58.845 --> 00:07:03.985
there's so many challenges building
with, really no walls to lean against.
00:07:03.985 --> 00:07:07.925
So, know, you could-- I, I feel
like you could feel the scar
00:07:07.925 --> 00:07:12.655
tissue coming out through the, the
microphone, as Patrick was talking.
00:07:16.305 --> 00:07:22.425
but yeah, how he, how he thinks about his
work, I think how he conscious of what he
00:07:22.425 --> 00:07:28.955
keeps to himself versus what he's willing
to give away, and seeing the role of
00:07:28.965 --> 00:07:32.255
the human in the design process, I think
it was j- really fascinating to hear.
00:07:34.015 --> 00:07:38.815
and, yeah, Tom, Tom, what did you
think of, of the Patrick conversation?
00:07:40.819 --> 00:07:41.519
Tom: I thought it was great.
00:07:41.599 --> 00:07:42.449
I thought it was really interesting.
00:07:42.449 --> 00:07:46.759
And you mentioned the framing there of a
glutton for punishment, and he gave this,
00:07:47.109 --> 00:07:54.319
story about, throwing discus and doing
hammer throw in school, and his body not
00:07:54.319 --> 00:08:01.569
necessarily being the right optimal shape
for being naturally gifted in that area.
00:08:02.729 --> 00:08:05.679
he described himself as having
T-Rex arms and throwing, throwing
00:08:05.679 --> 00:08:08.139
the discus, which, funny imagery.
00:08:08.909 --> 00:08:12.949
but I think there's something about
the, the persistence and discipline and,
00:08:14.359 --> 00:08:19.149
even if you're not naturally well-suited
to something, like knowing what you're
00:08:19.149 --> 00:08:21.549
passionate about, knowing where you
get energy, knowing what you really
00:08:21.549 --> 00:08:25.579
enjoy doing and leaning into that, I
think the role of a founding designer
00:08:26.369 --> 00:08:31.089
can really be shaped around that if
you're-- if there's enough alignment
00:08:31.089 --> 00:08:34.279
between what that is for you and what
a company needs or a founder needs.
00:08:35.119 --> 00:08:40.413
so I think that really, really
resonated And then the last guest,
00:08:40.743 --> 00:08:44.753
the most recent guest, which we, the
episode went out last week, was Matt
00:08:44.753 --> 00:08:53.613
Webb, of Inanimate, or currently of
Inanimate, but of various, exciting
00:08:54.383 --> 00:08:57.163
legendary design practices in London.
00:08:58.213 --> 00:09:03.873
And there were so many good nuggets
in that episode, everything from, how
00:09:03.883 --> 00:09:08.783
he built a book vending machine that
was toured around London and what he
00:09:08.783 --> 00:09:15.223
learned about refrigeration or lack of
refrigeration in having labels stick on
00:09:15.243 --> 00:09:21.353
each book, through to agentic workflows
with AI and various other things around
00:09:21.353 --> 00:09:27.603
how he's reignited his passion for hi-
the, the practice, the sort of invention
00:09:27.603 --> 00:09:30.633
practice he goes through as a, as a
designer, which I thought was really
00:09:30.633 --> 00:09:31.983
interesting to hear his perspective on.
00:09:32.733 --> 00:09:38.513
but the, the one thing that I still think
about today from that conversation is
00:09:38.553 --> 00:09:48.803
the way he used agentic loops to create
a self-learning system for fulfillment,
00:09:50.103 --> 00:09:54.863
of his Kickstarter art project, Poem/1.
00:09:55.953 --> 00:10:00.983
And if you haven't yet listened to
the episode, he describes, sending out
00:10:00.993 --> 00:10:06.733
these 700 units, and then customers
would write in with, questions or things
00:10:06.743 --> 00:10:08.113
that weren't quite working as expected.
00:10:08.863 --> 00:10:14.863
And he essentially built this agent
that, or built a set of standards
00:10:14.863 --> 00:10:18.413
and princip- or standard operating
procedures to resolve each of
00:10:18.413 --> 00:10:20.923
these questions as they came in.
00:10:21.493 --> 00:10:24.673
And so when a new one would come
in that hadn't been read before, he
00:10:24.673 --> 00:10:27.233
would manually respond to it himself.
00:10:27.543 --> 00:10:31.363
But then over time, this body of, this
source of truth of how these decisions
00:10:31.363 --> 00:10:34.113
are made would be established, and
it would keep learning and growing
00:10:34.353 --> 00:10:38.433
so that over time, the agent would
be able to respond to customers and
00:10:38.433 --> 00:10:41.033
resolve their queries without him
needing to be in the loop at all.
00:10:41.833 --> 00:10:46.333
And that's something that I've been
really fascinated with as an area
00:10:46.373 --> 00:10:51.463
generally, and finding the opportunities
for where are loops appropriate in
00:10:52.423 --> 00:11:00.383
these self-healing, use cases that can
have human input to train and improve
00:11:00.383 --> 00:11:05.549
and refine them, but Ultimately there,
the human input is about improving
00:11:05.799 --> 00:11:11.769
the output of that system to create
greater value or speed or efficiency
00:11:11.769 --> 00:11:14.619
or whatever it is for the customers
who are on the receiving end of that.
00:11:14.649 --> 00:11:20.149
And I've been thinking about building,
I haven't yet built a email triage
00:11:20.959 --> 00:11:25.089
learning, self-learning loop, built on
top of Gmail, but it's been on my to-do
00:11:25.109 --> 00:11:29.109
list to do, and maybe I'll get to it this
week, based on those same principles of
00:11:29.109 --> 00:11:35.759
how can I create this nice UI
that feels
like it's productive for me, but it's
00:11:35.759 --> 00:11:39.159
actually about teaching an agent how
to do these things and, and learn more
00:11:39.159 --> 00:11:43.969
about my tone of voice and how I make
decisions so that the small stuff can
00:11:43.969 --> 00:11:49.769
be taken over or outsourced a bit more,
giving me more time and head space to,
00:11:49.839 --> 00:11:51.209
to work on the more meaningful things.
00:11:51.449 --> 00:11:51.799
Anyway,
00:11:51.917 --> 00:11:52.367
Jonny: Mm-hmm.
00:11:52.889 --> 00:11:55.289
Tom: I'm sure you have some thoughts
about Matt's, Matt's conversation as well.
00:11:55.319 --> 00:11:56.119
It was a really good one.
00:11:56.439 --> 00:11:57.329
any takeaways for you?
00:11:58.087 --> 00:11:58.587
Jonny: Yeah.
00:11:58.937 --> 00:12:05.087
I mean, just, just on, on that,
Yeah, I'm, I'm a big Matt fanboy.
00:12:05.097 --> 00:12:08.737
If-- You'll know if you listen
to my intro to the Matt episode,
00:12:08.807 --> 00:12:10.317
which went on for about 15 minutes.
00:12:12.377 --> 00:12:16.977
yeah, on, on the, the, the learning
loops, yes, he-- I think he gave a
00:12:16.977 --> 00:12:22.547
really practical example of how an agent,
I think is basically what a learning
00:12:22.547 --> 00:12:27.097
loop, a sort of self-learning and
self-healing loop is, is, is, is an agent.
00:12:27.107 --> 00:12:32.497
You know, if, if you think of, something
like OpenClaw back in February,
00:12:32.497 --> 00:12:33.717
all of that stuff was coming out.
00:12:34.657 --> 00:12:38.727
really at the heart of what they were
doing, what that technology was doing
00:12:38.727 --> 00:12:43.737
was it would take some input, it would
perform an action, and it would then
00:12:43.737 --> 00:12:46.727
do it repeatedly, and each time it did
it, it would get a little bet- better
00:12:46.727 --> 00:12:51.857
because it would update its markdown
files, its soul or, and its memory to,
00:12:52.927 --> 00:12:55.907
support, a better execution next time.
00:12:56.657 --> 00:13:01.557
that's sort of at the heart of this
technology, but it's so hard to-- I
00:13:01.557 --> 00:13:04.597
found it very difficult to describe
in the abstract unless there's a
00:13:04.597 --> 00:13:07.327
very clear use case to do it, and
I think Matt's was really good.
00:13:08.887 --> 00:13:14.527
this week I lobotomized my main
agent that I run, a- and sort of
00:13:14.597 --> 00:13:17.527
rebooted it on a slightly more
modern version of the technology
00:13:17.527 --> 00:13:19.027
it's built on, which is NanoClaw.
00:13:19.217 --> 00:13:22.497
It was on NanoClaw version one, and I
decided to put it on NanoClaw version two.
00:13:23.537 --> 00:13:23.847
And,
00:13:24.517 --> 00:13:24.737
Tom: in
00:13:24.737 --> 00:13:28.427
Jonny: doing so, I was working away
with, with Claude, who was SSH'd into
00:13:28.537 --> 00:13:32.257
my VPS, for the people that know what--
love their three-letter acronyms.
00:13:33.487 --> 00:13:36.017
and we were looking through
the guts of what it had built.
00:13:36.097 --> 00:13:42.987
And, you know, when I first set this
thing up in March, and, all I've
00:13:42.987 --> 00:13:44.257
really been doing is talking to it.
00:13:45.187 --> 00:13:49.207
And we looked through this week all of
the different files it had created, all
00:13:49.207 --> 00:13:53.567
the routines, all of the, notes it had
basically made to itself, like, "Don't do
00:13:53.567 --> 00:13:55.137
this this way because that didn't work.
00:13:55.167 --> 00:13:55.857
Do it that way."
00:13:56.277 --> 00:13:59.547
And, there was a lot of cruft, so
we really managed to slim it down.
00:13:59.837 --> 00:14:04.487
You know, deleted half of that stuff
to just make it concise instructions
00:14:04.487 --> 00:14:08.177
rather than of conflicting things
that were built up over time.
00:14:08.387 --> 00:14:11.457
So, you know, you have to prune these
things, but, it was just fascinating
00:14:11.477 --> 00:14:16.807
to see built up institutional
knowledge over six months that had
00:14:16.807 --> 00:14:20.887
just been happening of, some of it
through me, some of it through itself.
00:14:21.777 --> 00:14:24.677
you know, it tries an API endpoint
and is like, "Oh, that's changed.
00:14:24.677 --> 00:14:27.747
I'm gonna go and look, and now
I'm gonna update myself so that I
00:14:27.757 --> 00:14:29.097
don't make that mistake next time."
00:14:30.157 --> 00:14:32.887
and, and that one is, is,
an agent that mainly runs a
00:14:32.887 --> 00:14:34.867
website for me, designtools.fyi.
00:14:35.607 --> 00:14:40.527
and, I decided after a summer
of ignoring it that I was going
00:14:40.527 --> 00:14:41.867
to pay it some attention again.
00:14:41.887 --> 00:14:45.387
So now, he's happy and
up and running and, and,
00:14:45.927 --> 00:14:46.527
Tom: continuing
00:14:46.527 --> 00:14:47.707
Jonny: with, with his work.
00:14:48.847 --> 00:14:55.157
so but, yeah, always l- looking for r-
real examples of this kind of thing in
00:14:55.157 --> 00:14:58.707
the wild because in the abstract everyone
should have agents isn't very useful.
00:15:00.583 --> 00:15:04.373
the other thing I got from Matt's episode,
I think, that has really stuck with me is
00:15:04.373 --> 00:15:10.553
his-- is how he-- We were talking about,
writing with AI and our experimentation
00:15:10.563 --> 00:15:16.363
with doing that, description of why it
doesn't work, I think is just the best
00:15:16.393 --> 00:15:22.603
that I've heard, which is you can give
it all of your writing, and Matt's got a
00:15:22.603 --> 00:15:27.733
lot on- online, so, the models have been
trained on his writing already, I'm sure.
00:15:29.163 --> 00:15:32.963
But-- And you can tell it to write
something as you, but as you read
00:15:32.963 --> 00:15:34.343
it, it doesn't mean anything.
00:15:34.343 --> 00:15:35.313
It feels thin.
00:15:35.323 --> 00:15:37.613
It feels like you can't it.
00:15:37.613 --> 00:15:39.993
You know, you couldn't
an argument
around it.
00:15:39.993 --> 00:15:40.933
It's not your thinking.
00:15:40.933 --> 00:15:42.893
It's thinking that has been
done by something else.
00:15:43.133 --> 00:15:49.663
So even if for everyone else it looks
convincing, for Matt, and I think why
00:15:49.663 --> 00:15:51.353
this resonated is I feel the same way.
00:15:51.623 --> 00:15:53.463
I just don't feel like
I can stand behind it.
00:15:53.463 --> 00:15:55.783
Like I can't point at
it and say it was mine.
00:15:56.963 --> 00:16:02.603
so yeah, just a g- quite a sort of
nuanced take on, on creating stuff
00:16:02.623 --> 00:16:05.963
with AI, that has stuck with me.
00:16:05.963 --> 00:16:09.123
And I feel like there's, there was
a bit of a theme throughout everyone
00:16:09.923 --> 00:16:13.703
actually this fall, but probably every
interview we've done, which is what
00:16:13.703 --> 00:16:15.443
do I keep and what do I let go of?
00:16:15.853 --> 00:16:22.053
What's okay for me to give away, and
what's important to me and, and part of my
00:16:22.063 --> 00:16:26.623
craft and part of-- part of what I enjoy,
but also what is my value, my ultimate
00:16:26.623 --> 00:16:33.113
value in this, that I want to, I want to
or believe that I should keep hold of?
00:16:34.843 --> 00:16:36.573
yeah, so as a, as a theme that sort of
00:16:38.887 --> 00:16:42.557
Something that we've talked about
before in various contexts, I think too
00:16:43.097 --> 00:16:43.757
Tom: Yeah.
00:16:43.847 --> 00:16:44.697
Yeah, so true.
00:16:44.707 --> 00:16:49.347
And I feel like every guest had a
different flavor of that answer, or
00:16:49.347 --> 00:16:53.487
there was a different, a different
line, or they drew a different
00:16:53.487 --> 00:16:58.567
line on what was the thing that was
required or they need to keep hold of.
00:16:59.507 --> 00:17:04.137
And I think there was, But
yeah, definitely a, a question
00:17:04.137 --> 00:17:05.457
of how blurry is that line?
00:17:05.497 --> 00:17:09.787
How much does it vary based on your
environment versus the sort of innate
00:17:09.827 --> 00:17:13.227
human quality of m- making decisions
and feeling ownership over those
00:17:13.227 --> 00:17:18.457
decisions, and perhaps that extends to
feeling ownership of the, the clarity
00:17:18.457 --> 00:17:20.917
of thought produced through writing.
00:17:21.887 --> 00:17:22.197
Yeah.
00:17:23.477 --> 00:17:24.697
Yeah, very interesting.
00:17:26.557 --> 00:17:30.257
there is actually a related topic to
that which we're gonna g- jump to a bit
00:17:30.257 --> 00:17:35.427
later, but are we losing our leverage
by giving our design work to agents?
00:17:35.537 --> 00:17:38.067
And it feels very much in this vein.
00:17:38.867 --> 00:17:41.117
Curious if you have any thoughts
on that as a topic, Jonny.
00:17:43.569 --> 00:17:45.809
Jonny: it was a good tee up because
you know I have thoughts on this.
00:17:46.529 --> 00:17:52.119
but what I think, the-- Tom, you
organized this Mostly Working,
00:17:54.189 --> 00:17:59.459
and there is a WhatsApp group which
is fairly active that people that
00:17:59.459 --> 00:18:01.369
have come to the meetup can, can join.
00:18:01.619 --> 00:18:02.789
And people should, by the way.
00:18:02.789 --> 00:18:06.769
If you've, if you've been to a Mostly
Working event and you want to join the
00:18:06.769 --> 00:18:12.039
conversation outside the room, then, you
should definitely check that out, and
00:18:12.079 --> 00:18:13.269
maybe we can put that in the show notes.
00:18:13.269 --> 00:18:21.569
But, a conversation started around
how cool, this new-- these new models
00:18:21.599 --> 00:18:26.579
are that, you know, GPT-6 Astra, which
is OpenAI's new model that's just
00:18:26.579 --> 00:18:32.199
come out, and the internet is abuzz
with how amazing it is at 3D, and,
00:18:33.359 --> 00:18:38.039
people are one-shotting games and,
or cloning games that already exist.
00:18:39.419 --> 00:18:47.119
And, it started a conversation around how
magical it is to be able to just create
00:18:47.129 --> 00:18:51.879
this stuff and how much it would've
cost to have created it in the past
00:18:51.899 --> 00:18:53.489
versus how quickly you can do it now.
00:18:55.209 --> 00:19:01.439
And I think the conversation was
interesting in the sense that
00:19:03.969 --> 00:19:08.479
on one level it is amazing, and on
another level, as soon as everyone can
00:19:08.479 --> 00:19:10.219
do something, is it amazing anymore?
00:19:10.419 --> 00:19:17.499
I think that w-where sort of I was
arguing, that you look at these
00:19:17.499 --> 00:19:21.259
incredible tools that are, that are
being created, these amazing visuals,
00:19:21.309 --> 00:19:27.839
whatever it is, you know, whether it's
interesting shaders or 3D effects or,
00:19:29.889 --> 00:19:35.029
motion, all of this kind of stuff,
feels magical because five years
00:19:35.029 --> 00:19:38.599
ago none of us could do this very
well or definitely very quickly.
00:19:39.689 --> 00:19:45.189
And now suddenly we can all do it, and
the, I don't know if it's an Overton
00:19:45.189 --> 00:19:49.729
window or equivalent, but it sort
of shifted towards this being kind
00:19:49.729 --> 00:19:55.289
of normal or less impressive, and so
therefore what is the new impressive?
00:19:55.459 --> 00:20:00.179
You know, what is, what is now a designer
can deliver that no one else can?
00:20:00.189 --> 00:20:04.239
Now everyone can deliver
extraordinary technical ability,
00:20:05.069 --> 00:20:07.099
and code is cheap to free.
00:20:08.139 --> 00:20:09.679
what, what is our value anymore?
00:20:13.167 --> 00:20:14.247
And where do we have leverage?
00:20:14.247 --> 00:20:18.897
You know, let's assume that the technology
continues to get more powerful and easier.
00:20:19.237 --> 00:20:28.047
So the trend for really anything you
can create technically is, is to zero.
00:20:28.187 --> 00:20:29.977
You know, the cost of it is to zero.
00:20:30.307 --> 00:20:34.497
You need-- The, the amount of ability
you need to create it trends to zero.
00:20:38.001 --> 00:20:43.181
my dad, who is a vicar, I keep picking on
him, I think, on this podcast, but, you
00:20:43.181 --> 00:20:48.701
know, I could, I could text him now and
say, "Go on this website create a video,
00:20:48.981 --> 00:20:54.501
a demo video for product," he probably,
using natural language, would be able
00:20:54.501 --> 00:20:58.431
to get further than I could have got
five years ago, technically, you know?
00:21:01.031 --> 00:21:03.531
so what do we keep?
00:21:03.691 --> 00:21:05.621
What, what is the magical thing?
00:21:06.001 --> 00:21:07.091
People talk about taste.
00:21:09.501 --> 00:21:10.081
is it taste?
00:21:10.091 --> 00:21:10.921
Is it constraint?
00:21:10.971 --> 00:21:17.281
Is it just the buildup of,
both domain expertise and,
00:21:19.951 --> 00:21:23.181
knowledge of the goals of the project
that we're working on or the, the,
00:21:23.201 --> 00:21:27.101
the task that we have at hand that is
unique to us and can't be replicated?
00:21:27.931 --> 00:21:28.141
know.
00:21:29.841 --> 00:21:35.001
but one thing that I feel quite
strongly is, and I think has been
00:21:35.001 --> 00:21:38.941
reflected in these, these conversations,
is being deliberate about what
00:21:38.941 --> 00:21:40.341
you give away and what you keep.
00:21:41.501 --> 00:21:44.831
and even if it's slower and even if
it feels like you're worse at it than
00:21:44.831 --> 00:21:50.931
an AI could be, sure that decisions
that are made, that you're making are,
00:21:53.611 --> 00:21:54.681
are yours to make still.
00:21:55.421 --> 00:22:00.201
thing that I find, as I design
with AI is I will want to make one
00:22:00.201 --> 00:22:02.861
decision and then 50 will be made,
00:22:03.649 --> 00:22:03.949
Tom: Mm-hmm
00:22:04.021 --> 00:22:05.561
Jonny: and that they're all interlinked.
00:22:06.281 --> 00:22:08.221
You know, t- too much stuff has happened.
00:22:08.261 --> 00:22:09.991
The prompt, the-- it ran away with it.
00:22:10.461 --> 00:22:15.631
Too much was added or too many different
things were changed, and at that point,
00:22:17.051 --> 00:22:21.851
it's far harder to unpick it and work
out what worked well and what didn't
00:22:21.851 --> 00:22:26.211
and why decisions were made than it
is to just crack on and add another
00:22:26.211 --> 00:22:28.291
prompt and pile, pile more stuff on top.
00:22:29.181 --> 00:22:33.171
I think that's true in design,
true in really any, any vertical.
00:22:37.765 --> 00:22:41.215
And that then means there's this buildup,
a bit like Matt was talking about.
00:22:41.215 --> 00:22:46.175
There's this buildup of work that has been
done that is technically done by you, but
00:22:46.175 --> 00:22:51.875
that you have no synapses connecting in
your brain as to why it was done really.
00:22:52.795 --> 00:22:57.105
You can sort of paint a broad
brushstroke, but individually,
00:22:57.385 --> 00:23:02.825
you know, w- we used to perfect
every pixel, and that was too slow.
00:23:02.955 --> 00:23:07.215
And I think, you know, we're, we're
not going back there, but you at least
00:23:07.215 --> 00:23:08.445
knew why you were doing everything.
00:23:09.571 --> 00:23:09.721
Tom: Mm-hmm.
00:23:10.075 --> 00:23:11.165
Jonny: there's this sort of balance.
00:23:13.705 --> 00:23:17.355
and I, I think I don't-- I haven't
been convinced by any of the
00:23:17.355 --> 00:23:21.375
technology, even GPT-6 Astra, that
00:23:26.611 --> 00:23:32.301
the models without any human
support can beat humans at
00:23:35.541 --> 00:23:35.871
soon.
00:23:37.351 --> 00:23:43.881
And so I feel confident that if we keep
some of that leverage to ourselves, then,
00:23:44.881 --> 00:23:48.821
we will survive all of this and maintain
our value and all of that kind of stuff.
00:23:49.151 --> 00:23:49.731
But, you know, I'm
00:23:49.981 --> 00:23:50.001
Tom: Yeah
00:23:51.031 --> 00:23:52.131
Jonny: talking my book, but
00:23:53.635 --> 00:23:59.305
Tom: Well, I think that raises a
few interesting questions of the,
00:23:59.705 --> 00:24:02.185
is design an art or a science?
00:24:02.605 --> 00:24:04.895
And how
00:24:08.377 --> 00:24:15.397
predictable is the outcome and how
testable is the outcome versus how
00:24:15.407 --> 00:24:21.967
much is it shaped by opinion and
individual voice or the voice of a team.
00:24:23.217 --> 00:24:28.047
And, I remember from various teams
I've-- design teams I've been a, a
00:24:28.047 --> 00:24:34.507
part of in the past, there has been
this consistent theme of however
00:24:34.507 --> 00:24:40.417
large the team gets, the experience
a customer or user should experience
00:24:40.457 --> 00:24:46.267
the product as if it was created from
a, a single individual or a single
00:24:46.727 --> 00:24:48.967
hand that is crafting that experience.
00:24:49.817 --> 00:24:53.697
And I think that speaks to design
systems and consistency and making
00:24:53.697 --> 00:24:57.757
the same types of UI choices across
and throughout an experience.
00:24:58.637 --> 00:25:05.567
But I do think that raises, yeah,
there are, there are aspects of that
00:25:05.637 --> 00:25:11.307
that I could imagine being-- once
the direction and standards are set,
00:25:11.387 --> 00:25:16.067
I could imagine AI being a really
valuable tool in executing against that.
00:25:16.427 --> 00:25:23.257
But there is this, human perspective,
this op- strong opinion, this
00:25:23.327 --> 00:25:29.337
originality that I think is really
a core part of the equation of a
00:25:29.337 --> 00:25:34.817
great product experience that I don't
think is possible to achieve through,
00:25:35.157 --> 00:25:38.007
purely through prompting, at least not
right now in the state of the models.
00:25:38.007 --> 00:25:42.597
And, and to me, that's
less about technical use.
00:25:42.597 --> 00:25:47.877
I think we're on this interesting
wave of these micro trends that, keep
00:25:47.877 --> 00:25:53.247
appearing every time a new model drops
and, and yeah,
amazingly impressive
00:25:53.257 --> 00:25:58.267
for a month, and then it feels like,
oh, that sort of style is everywhere.
00:25:59.227 --> 00:26:03.987
And I don't think we should steer away
from that, but I think there's probably
00:26:03.997 --> 00:26:11.607
an even greater need for originality and
human creativity that should be tapped
00:26:11.607 --> 00:26:15.527
into and applied to all the creative
possibilities that are now out there.
00:26:16.347 --> 00:26:21.027
But it's really hard to create distance
from the trend versus what is the
00:26:21.027 --> 00:26:25.247
originality that is maybe tapping into the
technology that's now available but is--
00:26:25.487 --> 00:26:28.237
sort of sits adjacent to the trend piece.
00:26:28.897 --> 00:26:29.127
I don't know.
00:26:30.613 --> 00:26:34.763
Jonny: Yeah, I think what the, what
the, the trends show is a, a sort of
00:26:34.763 --> 00:26:38.893
technology first approach where we
can now do this stuff and everyone's
00:26:38.893 --> 00:26:40.543
doing it, so now I'm gonna do it too.
00:26:42.473 --> 00:26:47.013
And a problem centric approach is
what designers should be focused on.
00:26:47.013 --> 00:26:50.563
So I will invent-- I like the idea
of us being inventors, you know?
00:26:50.633 --> 00:26:56.333
Or I will invent based on the
problem that I'm trying to solve or
00:26:56.353 --> 00:27:01.373
the context that I operate in, and
maybe I should pull in some of these
00:27:01.463 --> 00:27:08.043
extraordinary technologies or, I should
leverage AI as part of the production
00:27:08.043 --> 00:27:10.323
process to get to the final result.
00:27:11.213 --> 00:27:12.573
But the-- I am the inventor.
00:27:12.623 --> 00:27:18.843
I'm Caractacus Potts, is Ch-Chitty
Chitty Bang Bang reference for
00:27:19.225 --> 00:27:19.655
Tom: It's cool.
00:27:20.063 --> 00:27:20.733
Jonny: as a deep cut.
00:27:22.223 --> 00:27:28.843
w- I, I am the inventor and, only I
really know exactly why something needs
00:27:28.843 --> 00:27:33.513
to exist and exactly how it should feel,
and I can't even really describe it in
00:27:33.513 --> 00:27:35.083
a way that I could write in a prompt.
00:27:39.905 --> 00:27:41.885
And so maybe
00:27:44.647 --> 00:27:45.747
Yeah, that's the art, right?
00:27:45.757 --> 00:27:50.257
That's the art, and then the science might
be we've-- we have a robust design system
00:27:50.257 --> 00:27:58.657
now in component lib- components in, in
code, and we have our brand guidelines
00:27:58.687 --> 00:28:02.337
and our colors and et cetera, et cetera,
and all of the things that it's hard
00:28:02.357 --> 00:28:06.717
because it's zero to one stuff to get to
the point where that's-- happy with it.
00:28:06.727 --> 00:28:10.877
But then once we're happy with it, that
production process moves a lot faster.
00:28:12.377 --> 00:28:14.117
that maybe feels like a good balance.
00:28:15.127 --> 00:28:15.267
But
00:28:15.287 --> 00:28:15.387
Tom: Ja
00:28:15.727 --> 00:28:19.847
Jonny: I mean, as always, I would say I
reserve my right to change my opinion.
00:28:19.847 --> 00:28:22.867
I think I've changed my opinion multiple
times while we've been recording this
00:28:22.947 --> 00:28:25.587
podcast over the last three months odd.
00:28:25.597 --> 00:28:25.867
So,
00:28:27.929 --> 00:28:28.199
Tom: Yeah.
00:28:28.229 --> 00:28:33.879
I, I also do want to give a, a shout-out
for pushing the technology, and
00:28:33.879 --> 00:28:39.279
designers experimenting, and, that might
not be the right long-term solution
00:28:39.289 --> 00:28:43.959
for a everyday product application.
00:28:44.049 --> 00:28:47.959
But getting your hands dirty,
experimenting, trying these new models
00:28:47.959 --> 00:28:53.639
out as soon as they're released, trying
all of these fancy, shiny demos, I think
00:28:53.639 --> 00:28:57.049
is really important to understand where
the limits are and what's possible here.
00:28:57.079 --> 00:29:01.929
So I would embrace anyone and
encourage anyone to try, try
00:29:01.939 --> 00:29:03.329
these things, myself included.
00:29:03.379 --> 00:29:07.429
I'm close to downloading Blender
and, and trying, trying myself.
00:29:08.629 --> 00:29:10.419
because I think without that,
it's really hard to makeâ¦
00:29:10.499 --> 00:29:14.879
And I think that's something we've come
back to time and time again, throughout
00:29:14.879 --> 00:29:18.229
this podcast and through our, our work
together, has been you can't really
00:29:18.229 --> 00:29:22.279
understand what these models are capable
of from just seeing demos online.
00:29:22.279 --> 00:29:25.199
You need to, like, build something
yourself, and maybe there's a project
00:29:25.199 --> 00:29:28.989
on your to-do list that might lend
itself well to playing with this stuff.
00:29:29.759 --> 00:29:34.389
that doesn't necessarily mean that
doesn't change who you are or how you
00:29:34.389 --> 00:29:36.229
approach design problems generally.
00:29:36.229 --> 00:29:39.959
It's more just having a deeper
understanding of the technical landscape
00:29:39.959 --> 00:29:44.289
that you could be working with and
having a, a broader, deeper set of
00:29:44.289 --> 00:29:48.849
tools to draw upon in your everyday
design work, which I think is a really
00:29:48.849 --> 00:29:51.859
useful thing to, to have access to.
00:29:53.269 --> 00:29:58.169
as long as it doesn't necessarily change
you into only chasing the latest trends.
00:29:58.169 --> 00:30:01.769
It's more of a s- complement to
the core foundations you have
00:30:01.769 --> 00:30:03.469
as a, as a strong designer.
00:30:04.167 --> 00:30:04.487
Jonny: Yeah.
00:30:04.777 --> 00:30:07.377
Goes back to what you were saying
about Randy, I think, or, or that
00:30:07.377 --> 00:30:10.587
Randy was talking about, which is
understanding the grain of the paper,
00:30:10.597 --> 00:30:13.217
understanding the printer works.
00:30:15.297 --> 00:30:19.427
you have to understand th-this
technology, and the only way to
00:30:19.457
--> 00:30:20.637
really understand it is to use it.
00:30:20.647 --> 00:30:28.587
So building silly projects is
essential, I would say, just to sort
00:30:28.597 --> 00:30:30.717
of get a feel and a bit of confidence.
00:30:31.097 --> 00:30:35.917
And then, you know, all the impressionists
came out of photography turning
00:30:35.917 --> 00:30:40.377
up and suddenly, you know, exact
landscapes weren't needed anymore.
00:30:40.697 --> 00:30:46.807
And so the impressionists used their
ability with paint and their, what they
00:30:46.807 --> 00:30:51.207
already knew and their mastery of, of
that technique, and then chose to break
00:30:51.207 --> 00:30:53.477
it and chose to invent within that.
00:30:54.267 --> 00:30:58.987
It feels like we're in that sort
of moment again, where the best
00:30:59.177 --> 00:31:03.437
people at the next phase will really
understand the technology underpinning
00:31:03.437 --> 00:31:08.487
it and, we are, and be able to sort
of master that, but also find ways to
00:31:08.547 --> 00:31:11.657
adapt it a-and use it appropriately.
00:31:13.187 --> 00:31:18.857
we're in our toddler phase, I think,
with working out how to use, use
00:31:18.857 --> 00:31:24.077
this, AI in a way that is meaningful
and actually matters rather than
00:31:24.077 --> 00:31:32.337
just slap, slap some more motion or
some more, interesting effects on it.
00:31:33.657 --> 00:31:35.147
Tom: Yeah, absolutely.
00:31:35.967 --> 00:31:38.487
I th- I think this is, actually
potentially an interesting segue
00:31:38.487 --> 00:31:42.447
to, to, if you're happy to move
on, to some feedback we've gotten.
00:31:42.527 --> 00:31:44.117
Jonny: I was gonna suggest the same thing.
00:31:44.677 --> 00:31:45.087
Tom: Okay.
00:31:45.217 --> 00:31:45.927
Okay, perfect.
00:31:46.097 --> 00:31:49.687
Well, we have, we, we are open
to feedback on the podcast,
00:31:50.147 --> 00:31:51.917
podcast at nearfuture.works,
00:31:52.257 --> 00:31:58.417
and we have received some f- some
feedback, which has been, really great,
00:31:59.667 --> 00:32:04.377
and I think it asks a, a specific question
that I think would be a good one for us
00:32:04.377 --> 00:32:05.787
to, us to actually talk about together.
00:32:07.157 --> 00:32:10.897
it says various complimentary things,
and then it says, "Can you branch
00:32:10.897 --> 00:32:12.637
out beyond the senior design folks?"
00:32:13.287 --> 00:32:15.417
And I'm curious, Jonny, what do you think?
00:32:15.417 --> 00:32:17.787
Should we branch out beyond
sen- senior design folks?
00:32:18.691 --> 00:32:18.951
Jonny: Mm-hmm.
00:32:19.451 --> 00:32:19.791
Yeah.
00:32:20.371 --> 00:32:25.981
Thanks, Tim, longtime listener, first
time caller for, giving us this feedback.
00:32:26.181 --> 00:32:28.061
And please everyone else have your say.
00:32:28.111 --> 00:32:32.771
This is an opportunity as we have
this conversation, and react to it,
00:32:33.061 --> 00:32:38.651
you can also tell us what you think
and it will help us to decide
which
00:32:38.651 --> 00:32:40.211
guests to get in, et cetera, et cetera.
00:32:42.871 --> 00:32:44.261
yeah, what's this podcast about, Tom?
00:32:44.501 --> 00:32:44.521
We,
00:32:46.841 --> 00:32:50.531
we started it and, and you know,
we've called it sort of design and
00:32:50.721 --> 00:32:58.261
AI, a sort of overarching theme, and
it's sort of by talking to people and
00:32:58.261 --> 00:33:04.281
working out what we're most excited
about and where the combination of
00:33:04.311 --> 00:33:11.391
our interests and, abilities probably,
combines with our network and, you
00:33:11.391 --> 00:33:18.231
know, who we get excited about bringing
on into the, what the podcast is.
00:33:19.331 --> 00:33:24.511
But that feels-- I suppose that could
feel a little bit like haphazard and
00:33:27.391 --> 00:33:27.761
or
00:33:27.929 --> 00:33:28.369
Tom: Yeah
00:33:28.991 --> 00:33:31.731
Jonny: it, it does feel like a
nice moment to just reflect on
00:33:33.551 --> 00:33:39.251
have, have the topics we've covered
so far felt directionally right?
00:33:39.391 --> 00:33:41.211
Like is there anything
else we can jump into?
00:33:42.911 --> 00:33:50.301
and personally I would give
us a 8 out of 10 so far
00:33:51.083 --> 00:33:51.653
Tom: Nice.
00:33:52.043 --> 00:33:53.713
On, on what, what scale is this?
00:33:53.971 --> 00:33:54.701
Jonny: seven and a half.
00:33:54.891 --> 00:33:55.531
Seven and a half.
00:33:55.863 --> 00:33:56.913
Tom: What is the scale?
00:33:57.283 --> 00:33:58.093
What is the scale of,
00:33:58.851 --> 00:33:59.581
Jonny: Scale.
00:34:00.113 --> 00:34:01.563
Tom: of, quality?
00:34:02.621 --> 00:34:03.471
Jonny: putting me on the spot here.
00:34:05.311 --> 00:34:10.031
think a mixture of, I mean, well, I
will duck, maybe I should go lower
00:34:10.031 --> 00:34:14.891
because I'm gonna dock myself points
for both mic quality at various points
00:34:14.911 --> 00:34:20.081
and also a range of extraordinary
backdrops in strange, strange places
00:34:20.521 --> 00:34:22.771
and, camera angles looking at my nose.
00:34:23.581 --> 00:34:25.901
So, know, that's one issue
00:34:26.023 --> 00:34:26.553
Tom: a feature.
00:34:26.623 --> 00:34:27.713
That's a feature, not a bug
00:34:28.131 --> 00:34:29.221
Jonny: No, maybe it is, yeah.
00:34:30.121 --> 00:34:36.291
and for our video watchers, video
audience, 36 YouTube subscribers.
00:34:36.301 --> 00:34:37.771
I think that is about
00:34:37.975 --> 00:34:38.395
Tom: Whoop, whoop
00:34:39.021 --> 00:34:39.341
Jonny: yep.
00:34:41.411 --> 00:34:42.451
guys, stop subscribing.
00:34:42.911 --> 00:34:43.581
It's too many.
00:34:46.061 --> 00:34:46.701
anyway, yes.
00:34:46.941 --> 00:34:51.541
well, I think, I, I mean this is-- And
maybe we've been just been allows our--
00:34:51.641 --> 00:34:56.411
allowed ourselves to be selfish, about who
we, what we talk about and who we get on
00:34:56.821 --> 00:35:01.681
and hope that we're interested in is what
enough other people are interested in.
00:35:02.581 --> 00:35:05.671
But I suppose I would give, to answer
your question, what is the scale?
00:35:06.001 --> 00:35:06.921
The scale is
00:35:09.775 --> 00:35:12.605
conversations that have
personally interested me.
00:35:15.415 --> 00:35:18.635
All killer, no filler in terms of content
that I would personally want to listen to.
00:35:21.915 --> 00:35:25.635
but, but I think opportunity-- I
think there is an opportunity to
00:35:25.645 --> 00:35:33.535
branch mildly out of design because--
or designers, I should say, because
00:35:34.355 --> 00:35:38.065
design is not just done by designers,
and increasingly this is true.
00:35:38.995 --> 00:35:44.525
And so, you know, creative technologists
and engineers and product folks and,
00:35:45.725 --> 00:35:50.935
founders, we've got a guest coming
up who is building a venture-backed
00:35:50.945 --> 00:35:53.935
design tool, as a founder.
00:35:54.055 --> 00:36:00.625
I think, you know, they all add to
the conversation and add a perspective
00:36:00.635 --> 00:36:02.795
that I think will be valuable.
00:36:02.795 --> 00:36:05.545
But personally, I think we
should have design at the core,
00:36:08.665 --> 00:36:11.575
because that keeps it
clear what we're about.
00:36:11.985 --> 00:36:12.515
What do you think?
00:36:12.825 --> 00:36:13.305
Tom: Yeah.
00:36:13.435 --> 00:36:14.445
I, I agree.
00:36:14.485 --> 00:36:20.105
I think, I think if it-- the only
guests we had on had design in their
00:36:20.105 --> 00:36:25.545
job title or were head of design
at X, Y, Z, I think it could get a
00:36:25.545 --> 00:36:27.315
bit repetitive, a bit, a bit samey.
00:36:27.855 --> 00:36:28.825
But I doâ¦
00:36:29.235 --> 00:36:37.715
I think the core reason I am most enjoying
doing this is the exploration of what
00:36:37.785 --> 00:36:40.785
design, is evolving into as a craft.
00:36:41.175 --> 00:36:46.065
And as you say, a lot of what might
be considered design output isn't
00:36:46.075 --> 00:36:47.705
necessarily created by designers.
00:36:48.715 --> 00:36:52.805
but I think designers are obviously
probably the, the majority of the
00:36:52.805 --> 00:36:54.435
guests we'd have on this podcast.
00:36:56.055 --> 00:36:58.925
But w- if, if there is someone who
brings an interesting perspective on
00:36:59.325 --> 00:37:03.365
what that, design-- what the shape of
design is becoming and what that craft
00:37:03.415 --> 00:37:07.055
is evolving into, then I think that
would be fair game from my perspective.
00:37:07.195 --> 00:37:08.535
And yeah.
00:37:08.585 --> 00:37:13.905
And I think that could be the sort of
practical executional level of, like
00:37:13.955 --> 00:37:18.235
as you say, engineering and design
engineering or brand engineering even.
00:37:19.095 --> 00:37:23.895
but then there's the sort of macro
view of what shifts are happening in
00:37:23.905 --> 00:37:28.005
the overall landscape and what is the
role of a designer evolving into and
00:37:28.015 --> 00:37:30.105
the role design
plays within companies.
00:37:30.115 --> 00:37:33.265
So yeah, I would strongly agree with that.
00:37:33.285 --> 00:37:36.325
So, so Tim, thank you so
much for your feedback.
00:37:36.725 --> 00:37:41.565
Y-yes, I think we answered your
question that, we, we, we may branch
00:37:41.565 --> 00:37:45.775
out a bit beyond people with design
in their job title, but the lens
00:37:45.775 --> 00:37:52.355
will still be how does AI shift the
role and evolving craft of design?
00:37:53.639 --> 00:37:53.969
Jonny: Yeah.
00:37:54.969 --> 00:37:56.339
I think-- I don't think
we're gonna turn intoâ¦
00:37:56.479 --> 00:38:01.959
I mean, o-one example just to sort of
round this off is Lenny's Podcast, which
00:38:01.969 --> 00:38:04.589
is overtly like a product management.
00:38:04.599 --> 00:38:07.249
He was a PM, product.
00:38:09.959 --> 00:38:12.039
but he gets designers on, he
gets engineers on, he gets
00:38:12.039 --> 00:38:13.929
founders on, he gets all sorts.
00:38:15.089 --> 00:38:20.519
And it's more-- It feels like it's
more content for product managers or,
00:38:20.859 --> 00:38:23.239
senior product people that-- to enjoy.
00:38:24.339 --> 00:38:26.399
And of course, senior product
people don't just want to
00:38:26.399 --> 00:38:27.279
hear about product management.
00:38:27.289 --> 00:38:30.399
My God, that sounds deathly dull.
00:38:31.629 --> 00:38:35.659
but actually, they're m- the product
managers and product folks love thinking
00:38:35.659 --> 00:38:39.739
about strategy more broadly around, you
know, how, how companies are built and,
00:38:40.759 --> 00:38:42.459
macro trends and all that kind of stuff.
00:38:42.829 --> 00:38:51.149
I would say we do sometimes talk about
macro trends, but, mm, I suspect we--
00:38:51.269 --> 00:38:54.529
it'll be a little bit more tactical
than that, would be my, my gut.
00:38:54.529 --> 00:38:57.269
But just like what would
designers be interested in?
00:38:57.289 --> 00:39:00.629
And that will probably capture
people adjacent as well.
00:39:02.899 --> 00:39:03.189
so
00:39:04.089 --> 00:39:04.319
Tom: Yeah.
00:39:04.429 --> 00:39:05.939
So if you're listening to this,
00:39:06.139 --> 00:39:06.729
Jonny: you think.
00:39:06.739 --> 00:39:07.129
Yeah
00:39:07.239 --> 00:39:09.129
Tom: yeah, if you have an opinion,
we'd love to hear from you,
00:39:09.639 --> 00:39:10.019
Jonny: Yeah
00:39:10.499 --> 00:39:12.059
Tom: podcast@nearfuture.works.
00:39:12.729 --> 00:39:17.299
And now I think we're coming to
the end of this conversation.
00:39:17.919 --> 00:39:18.709
let's check in.
00:39:18.749 --> 00:39:19.729
What have we built this month?
00:39:19.899 --> 00:39:21.459
Jonny, you've built a few things.
00:39:21.619 --> 00:39:22.329
Tell us about them
00:39:23.399 --> 00:39:27.749
Jonny: Yeah, I, my, my proudest
achievement, I think, over
00:39:27.749 --> 00:39:31.209
the last month was built very
quickly in, like, two hours.
00:39:33.745 --> 00:39:39.925
When I was a kid, we used to play this
board
game Labyrinth a lot, it's, game
00:39:39.925 --> 00:39:43.905
where you have tiles on a board, and
you basically have to go and collect all
00:39:43.905 --> 00:39:48.965
your treasures and then go back to your
home tile faster than everyone else.
00:39:49.235 --> 00:39:53.725
And you push the tiles along the board
so it changes shape of the labyrinth,
00:39:53.745 --> 00:39:57.725
and the maze changes, and you can block
other people, or you can open up new
00:39:57.945 --> 00:39:59.535
corridors for yourself to get through.
00:40:00.445 --> 00:40:02.575
Anyway, childhood game.
00:40:03.235 --> 00:40:05.405
This summer went camping with,
00:40:07.425 --> 00:40:11.505
There were about 35 of us, I
think, They're all-- Huge family
00:40:11.505 --> 00:40:18.075
camping trip, with a dozen odd
children under the age of 10.
00:40:19.245 --> 00:40:22.675
And I brought along our, our
Labyrinth game second year in a
00:40:22.675 --> 00:40:25.685
row, and once again, huge hit.
00:40:26.585 --> 00:40:27.895
the next generation are getting into it.
00:40:27.895 --> 00:40:28.935
It is timeless.
00:40:28.955 --> 00:40:32.725
It's a, it's a complete classic,
and anything that gets people
00:40:32.725 --> 00:40:38.835
away from screens and, and whatnot
and, is, is good in my book.
00:40:38.905 --> 00:40:43.875
Ironically, what I built was on a screen,
but, I thought, "Wouldn't it be cool
00:40:43.915 --> 00:40:45.735
if you could play Labyrinth online?"
00:40:45.815 --> 00:40:47.025
And there's no way to do that.
00:40:47.035 --> 00:40:52.795
So, I sort of, as they say,
one-shotted, Labyrinth online.
00:40:54.255 --> 00:40:59.445
and it work- It, it built a full sort of
3D board that you could navigate around.
00:41:01.125 --> 00:41:04.725
and a couple more prompts got
me, you know, online multiplayer.
00:41:04.725 --> 00:41:07.745
So Tom and I, we could have
a, have a game remotely.
00:41:08.415 --> 00:41:13.465
it's got leaderboards for solo mode,
so you can pick how many gems you
00:41:13.465 --> 00:41:17.975
wanna-- how many treasures you wanna
find, and then see if you can beat the
00:41:17.975 --> 00:41:19.725
high score in terms of number of turns.
00:41:20.435 --> 00:41:24.385
Anyway, it's just a complete, jolly,
00:41:26.765 --> 00:41:29.765
com- you know, n-no value
really beyond my own enjoyment.
00:41:31.055 --> 00:41:34.875
played a few test games with some people,
and it worked really nicely, very smooth.
00:41:35.715 --> 00:41:37.705
And so, yeah.
00:41:37.715 --> 00:41:41.635
I'll, I'll-- It's
labyrinth.jonny.ooda.run,
00:41:41.865 --> 00:41:44.035
but we can drop it in the,
in the show notes as well.
00:41:44.035 --> 00:41:48.435
If you play a game of Labyrinth,
please let me know because, you know,
00:41:48.435 --> 00:41:51.255
the leaderboard is full of my name
at the moment, and I need some other
00:41:51.255 --> 00:41:52.545
people to go and, go and beat me.
00:41:55.355 --> 00:42:00.925
and, that's-- I mean, I, been,
been working hard on, on
production
00:42:01.045 --> 00:42:04.965
stuff for, for Ooda and getting
that ready for a launch actually.
00:42:04.965 --> 00:42:10.165
So, that's the other thing I've been
working on, including attempting
00:42:10.175 --> 00:42:13.615
to create a demo video entirely
with AI which is comically bad.
00:42:14.905 --> 00:42:18.305
and you know, the-- It turns out
all of those guys one-shotting
00:42:18.305 --> 00:42:21.145
demo videos are full of shit.
00:42:22.145 --> 00:42:23.165
Or at least I'm doing it wrong.
00:42:23.185 --> 00:42:24.185
Maybe it's a skill issue.
00:42:25.925 --> 00:42:26.685
but yeah, that's me.
00:42:26.685 --> 00:42:27.135
How about you?
00:42:28.965 --> 00:42:31.975
Tom: well, well, I didn't think
I'd really built, built much
00:42:31.975 --> 00:42:36.895
this month because of the summer
holidays, being away, various things.
00:42:38.165 --> 00:42:42.965
but I did manage to burn
through m-my Claude Fable 5.1
00:42:43.745 --> 00:42:49.365
credits in about half an hour yesterday
morning, building, building some skills.
00:42:50.035 --> 00:42:56.015
Very inefficient use for Fable, and then
I had to pay for some extra credits just
00:42:56.025 --> 00:42:57.985
to get some basic stuff done after that.
00:42:59.085 --> 00:43:01.665
but I think I've probably learnt
a valuable lesson about building
00:43:01.665 --> 00:43:06.515
skills, which is before I was just,
like, almost, like, one-shotting.
00:43:06.525 --> 00:43:07.935
Like, "Oh, I have this
idea for this thing.
00:43:07.935 --> 00:43:09.395
I need to complete this task.
00:43:09.395 --> 00:43:10.945
Why don't I just do it as a skill?"
00:43:12.795 --> 00:43:16.755
quickly realizing or generally realizing
I sort of never really got great results
00:43:16.795 --> 00:43:22.035
from that approach, and so now I'm
trying to double down a bit on if I have
00:43:22.035 --> 00:43:28.545
a, an idea for a skill, I will try and
try my best to not just one-shot it but
00:43:28.545 --> 00:43:30.805
actually get the, get the resultingâ¦
00:43:30.875 --> 00:43:33.945
And these two were sort of
research-oriented skills, so I'd get
00:43:33.945 --> 00:43:38.755
the result back, and then I'd basically
completely rewrite the result by hand
00:43:38.775 --> 00:43:44.125
based on what the AI produced, and then I
could feed that back into the, the model.
00:43:44.125 --> 00:43:49.095
So it's sort of a form of eval, I
guess, but just, but using the actual
00:43:49.095 --> 00:43:52.575
content that was found through this
research from the AI and manually
00:43:52.635 --> 00:43:56.055
getting it, massaging it into the
right format and right template.
00:43:57.115 --> 00:44:02.505
the key value for me is it's taken the
result that comes back from a skill from
00:44:02.505 --> 00:44:08.925
this 10,000-word essay that I will never
read that repeats itself 20 times, into
00:44:08.965 --> 00:44:12.025
a 400-word bullet point list of links.
00:44:12.065 --> 00:44:16.745
It feels much closer to a Wikipedia
entry, a sort of concise Wikipedia
00:44:16.755 --> 00:44:22.065
entry, rather than a sprawling mess
of words that probably make a lot
00:44:22.065 --> 00:44:24.955
of sense but I don't have time to
read or the interest in reading.
00:44:26.545 --> 00:44:29.065
and also there's just such a
strong bias from the sources that
00:44:29.375 --> 00:44:31.335
information is out there around.
00:44:31.585 --> 00:44:39.781
So, one of these research skills I
was making was around understanding A
00:44:39.781 --> 00:44:51.291
company's health in terms of financial
team, team growth, various aspects
00:44:51.291 --> 00:44:54.911
like this, but all the information
around that is released in PR
00:44:54.921 --> 00:44:59.691
statements or press releases, from VC
companies, mostly in investment firms.
00:44:59.841 --> 00:45:04.091
So this report was coming
back with like heavily talking
00:45:04.101 --> 00:45:05.261
about all these VC companies.
00:45:05.261 --> 00:45:05.961
I'm like, "Not interested.
00:45:05.961 --> 00:45:07.321
I don't care."
00:45:07.841 --> 00:45:09.651
Like, I don't care about that stuff.
00:45:10.351 --> 00:45:12.511
or at least for the purposes of the
skill, I don't care about that stuff.
00:45:13.121 --> 00:45:17.721
so sort of interesting taking this sort of
heavily biased data set and then trying to
00:45:17.801 --> 00:45:22.871
correct it into something that is actually
the use that was more relevant for me.
00:45:23.821 --> 00:45:25.421
So anyway, that was the thing I built.
00:45:25.951 --> 00:45:29.271
also coming back from holiday,
I decided to finally give upâ¦
00:45:29.541 --> 00:45:33.941
Jonny, you and I have been talking for a
while now about having so many different
00:45:33.941 --> 00:45:37.581
domain names, different Gmail accounts,
different browser identities that
00:45:37.591 --> 00:45:41.031
are attached to each one of them, and
I've basically consolidated everything
00:45:41.031 --> 00:45:44.601
into a single Dia browser instance.
00:45:44.971 --> 00:45:49.631
We had a Mostly Working event in the
middle of August with Christine Røde from
00:45:49.631 --> 00:45:54.611
The Browser Company talking about the
Daily Brief, which is a feature in Dia.
00:45:54.611 --> 00:45:57.761
It's like the most loved feature
there, which kind of gives you
00:45:57.761 --> 00:46:00.261
a summary each morning of what's
happening across your day.
00:46:00.961 --> 00:46:04.991
I was hooked, and it made me like
decide to, okay, I'm gonna solve
00:46:04.991 --> 00:46:07.981
this identity problem and just do
everything in one browser instance.
00:46:08.301 --> 00:46:14.051
And then that has meant I've, I've been
redirecting my email into a single inbox.
00:46:14.051 --> 00:46:16.871
I've been like having one-
a single calendar view set
00:46:16.871 --> 00:46:17.911
up so I can view everything.
00:46:18.621 --> 00:46:23.911
Yeah, so it's, it's probably not the
most efficient long-term solution,
00:46:24.141 --> 00:46:29.611
but my
brain is significantly calmer
by just having a single place where
00:46:29.611 --> 00:46:31.541
I can see everything in one place.
00:46:31.641 --> 00:46:35.051
Jonny: forwarding emails from different
places into one central inbox?
00:46:35.705 --> 00:46:36.275
Tom: Yes
00:46:36.391 --> 00:46:38.641
Jonny: that I would, thinking
about it, that's the bit I'd be
00:46:38.641 --> 00:46:40.021
like, "How would I even do that?"
00:46:40.581 --> 00:46:40.861
But
00:46:41.263 --> 00:46:42.413
Tom: It's actually very easy to do.
00:46:42.493 --> 00:46:46.723
I mean, there's, there's probably a
separate, privacy and security question
00:46:46.723 --> 00:46:50.533
to resolve before doing it, but, but
technically it's quite easy to do.
00:46:51.031 --> 00:46:51.331
Jonny: Right.
00:46:51.443 --> 00:46:54.143
Tom: If you use Gmail, at least,
you can, you can set it up to
00:46:54.483 --> 00:46:58.923
automatically forward, and then
you can set up your email to reply
00:46:58.973 --> 00:47:00.853
as that email address as well.
00:47:01.003 --> 00:47:02.583
So in theory
00:47:02.719 --> 00:47:06.799
Jonny: 200 pounds to Cursor, and
then you get a Grok Bot, and bot
00:47:06.839 --> 00:47:08.919
can have multiple Gmail accounts.
00:47:08.919 --> 00:47:10.339
That's the big thing I've been reading.
00:47:10.759 --> 00:47:12.969
Maybe, maybe next month we'll
have tried out Grok Bot.
00:47:13.785 --> 00:47:18.535
Tom: Yeah, maybe, or maybe Claude will
add that capability or, or I don't know,
00:47:18.554 --> 00:47:19.094
Jonny: come on Claude.
00:47:19.275 --> 00:47:19.815
Tom: ChatGPT.
00:47:20.534 --> 00:47:20.814
Jonny: Ja.
00:47:22.875 --> 00:47:26.105
Tom: w- w- one other quick, quick
shout-out I wanted to give out when I
00:47:26.295 --> 00:47:30.775
said I hadn't really built anything with
AI, I did launch a design leadership
00:47:30.795 --> 00:47:34.615
circles, which I've been-- I started
running the first one last week.
00:47:35.085 --> 00:47:37.575
this is completely unrelated to AI.
00:47:37.575 --> 00:47:43.405
It's just running a series of, peer
group community of practice sessions
00:47:43.405 --> 00:47:49.165
with design leaders who are, navigating
this current moment, some with big
00:47:49.305 --> 00:47:52.335
challenges they're facing, others
just curious to meet and connect with
00:47:52.345 --> 00:47:53.905
other design leaders in the space.
00:47:54.255 --> 00:47:57.855
But it's been really insightful to
understand, like, what the temperature
00:47:57.995 --> 00:48:00.055
is across design leadership right now.
00:48:00.085 --> 00:48:04.635
And although it's not focused on
AI, AI is the backdrop for a lot
00:48:04.635 --> 00:48:07.105
of these conversations and the
change that that's encouraging.
00:48:07.105 --> 00:48:10.085
So I've been really enjoying those
conversations, and that's sort of
00:48:10.115 --> 00:48:13.935
quickly come about, and I'm running
those sessions throughout September,
00:48:13.945 --> 00:48:17.165
and I'm hoping to do some more exciting
things with that, in October, which I'll
00:48:17.165 --> 00:48:19.305
talk about in our next episode as well.
00:48:20.207 --> 00:48:20.727
Jonny: Awesome.
00:48:21.837 --> 00:48:22.787
Yeah, they sound mega.
00:48:24.297 --> 00:48:25.977
get-- I, I've got FOMO, you know.
00:48:26.077 --> 00:48:28.507
I know what, what's being said.
00:48:28.577 --> 00:48:31.567
What's, what, what are we coming--
What are we-- What are the conclusions?
00:48:31.787 --> 00:48:32.517
Maybe you can share.
00:48:32.557 --> 00:48:33.617
Maybe you probably can't share.
00:48:33.617 --> 00:48:34.007
It's all,
00:48:35.779 --> 00:48:36.569
Tom: I, I,
00:48:36.647 --> 00:48:37.147
Jonny: coming from that?
00:48:38.689 --> 00:48:42.109
Tom: I obviously can't share any
names or companies, but I'd say
00:48:44.859 --> 00:48:48.999
I've, I've not prepared any themes
to, to play back at this time.
00:48:50.399 --> 00:48:51.339
Maybe I won't answer that.
00:48:51.569 --> 00:48:52.359
Yeah, next month.
00:48:52.367 --> 00:48:52.847
Jonny: it next month.
00:48:53.287 --> 00:48:53.457
Yeah,
00:48:53.529 --> 00:48:54.599
Tom: Yeah, yeah, definitely
00:48:55.317 --> 00:48:55.607
Jonny: Right.
00:48:55.617 --> 00:48:56.337
Let's wrap up.
00:48:56.337 --> 00:49:03.207
So, we got coming up, we've got, we've got
a few, few things happening, haven't we?
00:49:03.903 --> 00:49:05.063
Tom: you're, you're heading to Berlin
00:49:05.747 --> 00:49:08.757
Jonny: I'm going to Berlin on, what is it?
00:49:09.257 --> 00:49:10.217
A couple of weeks' time.
00:49:10.487 --> 00:49:14.867
On the 18th, I'm speaking on main stage
at Hatch, so if anyone listening to
00:49:14.867 --> 00:49:21.797
this is gonna be there, please do, yeah,
drop me an email or, or like DM me on
00:49:22.217 --> 00:49:27.207
LinkedIn or something "Hey, I'm gonna
be there," and then we can hang out.
00:49:28.057 --> 00:49:28.717
That would be nice.
00:49:30.377 --> 00:49:30.637
yeah,
00:49:30.699 --> 00:49:31.509
Tom: I'm excited for your talk
00:49:31.937 --> 00:49:32.677
Jonny: my talk.
00:49:32.757 --> 00:49:38.757
I s- I feel like it's been like nailing
jelly to the wall trying to get this talk
00:49:41.107 --> 00:49:44.897
clear because the technology moves so
fast, and I feel like I've got this
00:49:44.957 --> 00:49:46.817
enormous wealth of things I could say.
00:49:46.817 --> 00:49:50.837
And how do you say one thing concisely
in 20 minutes when your brain is so
00:49:50.837 --> 00:49:52.417
full of all of the things you could say?
00:49:52.557 --> 00:49:55.437
But luckily, that's why we have
a podcast that I can just blah,
00:49:55.437 --> 00:49:57.747
blah, blah, just get it all out.
00:49:58.817 --> 00:50:01.717
so but yes, final prep for that.
00:50:02.617 --> 00:50:06.977
And then the week after, we are running
a workshop, which is actually sold
00:50:06.977 --> 00:50:11.867
out, I believe, at, in Brighton at
the Design and AI Summit on the 24th.
00:50:14.007 --> 00:50:18.877
really excited
about that one as well,
and planning our travel and whatnot,
00:50:18.887 --> 00:50:19.977
so that's starting to feel real.
00:50:22.297 --> 00:50:30.037
and then in October, is shrouded in
mystery, but all we would say is save the
00:50:30.037 --> 00:50:37.627
date on the 22nd of October, especially if
you're a Londoner or adjacent, because we
00:50:37.627 --> 00:50:41.607
will be running an event, a bigger thing.
00:50:42.857 --> 00:50:46.977
and we're w- it doesn't have a
name yet, and it doesn't have,
00:50:49.357 --> 00:50:53.527
yet for us to fully announce it right now,
but we do know it's gonna be on the 22nd.
00:50:53.527 --> 00:50:56.897
So, Tom, is there anything else
that we can say about that?
00:50:59.371 --> 00:51:04.111
Tom: I think you have sufficiently
disclosed the details we can say.
00:51:04.591 --> 00:51:08.661
and when Jonny says we haven't
got a name, there are a small
00:51:08.661 --> 00:51:09.851
shortlist of possible names.
00:51:09.871 --> 00:51:11.621
It's not like we're starting
completely from scratch.
00:51:11.671 --> 00:51:13.421
Like, we know generally
what this is going to be.
00:51:13.891 --> 00:51:19.241
And if you're a designer or a
design leader who is-- Well, if
00:51:19.241 --> 00:51:22.551
you've made it this par- far in the
podcast, then you, you're, you're the
00:51:26.131 --> 00:51:26.311
kind of person who should come to this.
00:51:26.321 --> 00:51:26.381
but it is an in-person event.
00:51:26.381 --> 00:51:27.631
It will be lots of fun.
00:51:27.661 --> 00:51:31.131
It will be potentially the, the
biggest thing we've done to date
00:51:31.151 --> 00:51:32.801
in terms of people in a room.
00:51:33.415 --> 00:51:33.665
Jonny: Ja
00:51:35.061 --> 00:51:37.201
Tom: yeah, keep your eyes peeled.
00:51:37.631 --> 00:51:39.751
We will reveal more in
an episode coming soon.
00:51:40.451 --> 00:51:44.481
But yeah, very excited for, for this
to come together and, it's gonna be fun
00:51:45.351 --> 00:51:45.621
Jonny: Yep.
00:51:45.791 --> 00:51:46.571
Yep, yep, yep.
00:51:47.391 --> 00:51:54.061
And more big announcements about the Near
Future podcast, I think coming soon too.
00:51:54.331 --> 00:51:55.761
That one's even more mysterious.
00:51:56.825 --> 00:51:57.125
Tom: Yeah.
00:51:57.151 --> 00:52:00.321
Jonny: so unsatisfying
this, this news bulletin.
00:52:00.321 --> 00:52:02.131
We can't really say
anything about anything.
00:52:02.181 --> 00:52:06.641
But, yeah, that I, I think, watch
this space in the next month, I
00:52:06.671 --> 00:52:11.951
think that there's gonna be some
evolution and things happening, for us.
00:52:14.081 --> 00:52:15.731
but the podcast's not going anywhere.
00:52:16.811 --> 00:52:19.561
Really excited to get toâ¦
00:52:20.391 --> 00:52:21.131
What's the milestone?
00:52:21.131 --> 00:52:25.251
Maybe, I think 52 episodes c- if
we do it every week, 52 episodes,
00:52:25.321 --> 00:52:26.301
that means we've done a year.
00:52:27.101 --> 00:52:27.811
What are we up to?
00:52:27.811 --> 00:52:28.251
Like
00:52:29.017 --> 00:52:30.837
Tom: This is probably 16 or 17.
00:52:31.131 --> 00:52:31.611
Jonny: Yeah.
00:52:32.361 --> 00:52:32.681
Yeah,
00:52:32.867 --> 00:52:37.137
Tom: And we, and we have a few,
a few guests booked in who we're
00:52:37.137 --> 00:52:41.507
speaking to soon, so yeah, I think
we're on track for one a week for
00:52:42.627 --> 00:52:43.727
the rest of the year at least.
00:52:43.887 --> 00:52:48.577
Jonny: Yeah, and we will endeavor to
tell people about episodes in the future.
00:52:49.017 --> 00:52:53.207
We have not done a good job over summer of
telling people episodes exist, so please
00:52:53.247 --> 00:52:54.897
do go back through the back catalog.
00:52:55.577 --> 00:52:56.457
there's really good stuff in there.
00:52:57.567 --> 00:52:58.517
Right, that's it.
00:52:59.642 --> 00:53:00.232
Tom: Let's wrap up.
00:53:00.417 --> 00:53:01.067
Jonny: shall we skedaddle?
00:53:02.162 --> 00:53:02.732
Tom: Yes.
00:53:03.242 --> 00:53:04.682
Thank you for listening
and making it this far.
00:53:04.682 --> 00:53:06.502
Jonny, great to chat.
00:53:07.292 --> 00:53:07.802
Let's wrap up
00:53:07.897 --> 00:53:08.287
Jonny: You too Tom.