1
00:00:00,014 --> 00:00:03,222
50% of the people in the US 
anyway 
 believe that AI is bad,

2
00:00:03,222 --> 00:00:04,444
it's dangerous. 
They're wrong. 

3
00:00:04,484 --> 00:00:07,262
If you're not using AI five 
times an 
 hour, you are behind 

4
00:00:07,262 --> 00:00:09,184
your competition. 
Today's guest is Kevin Surace, 

5
00:00:09,184 --> 00:00:12,113
The 
 Father of the Virtual 
Assistant, an AI pioneer with 95

6
00:00:12,113 --> 00:00:14,714
worldwide patents, 
 and author 
of The Joy Success Cycle. 

7
00:00:14,853 --> 00:00:16,703
How did you end up becoming 
 
The Father of AI Assistant? 

8
00:00:16,703 --> 00:00:19,213
Portico was the first fully AI 
assistant. 

9
00:00:19,293 --> 00:00:21,742
She would answer your phone and 
 book people on your calendar 

10
00:00:21,742 --> 00:00:23,154
and things we can't even do 
today. 

11
00:00:23,233 --> 00:00:25,803
And ended up resulting in 
 
several dozen worldwide patents.

12
00:00:25,823 --> 00:00:28,203
And those got licensed 
ultimately 
 to Apple, 

13
00:00:28,203 --> 00:00:30,947
Microsoft, Google, and Amazon, 
anyone who really 
 wanted to do

14
00:00:30,947 --> 00:00:32,491
voice assistants. 
Software developers' 
 jobs will

15
00:00:32,491 --> 00:00:34,620
change a lot. 
So what do you think the 
 

16
00:00:34,628 --> 00:00:36,978
developer's evolution should be?
We've seen this before, but most

17
00:00:36,978 --> 00:00:39,208

 people just have forgotten 
that because we've been in high 

18
00:00:39,208 --> 00:00:40,783
level 
 languages now for 30 or 
40 years. 

19
00:00:40,823 --> 00:00:42,651
And now we're going to the 
highest level 
 language, which 

20
00:00:42,651 --> 00:00:44,849
is just the way we speak. 
And if we're articulate enough 

21
00:00:44,849 --> 00:00:46,832
and 
 have a good enough 
specification, it'll write all 

22
00:00:46,832 --> 00:00:49,093
of that all the 
 way down to 
machine code for us. 

23
00:00:49,194 --> 00:00:51,595
In talking to so many 
developers, 
 at first the 

24
00:00:51,595 --> 00:00:54,659
developer says, "All of my joy 
came from writing code, 
 and I 

25
00:00:54,659 --> 00:00:56,815
love writing code." 
You never really loved writing 

26
00:00:56,815 --> 00:00:58,794
code. 
What you got the most joy from 

27
00:00:58,794 --> 00:01:00,714
is 
 delivering that feature or 
that bug fix. 

28
00:01:00,714 --> 00:01:03,071
Nobody cares how you got there. 
And in fact, if you can get 

29
00:01:03,071 --> 00:01:04,583
there without 
 writing a line 
of code, even better. 

30
00:01:04,632 --> 00:01:06,743
So what can developers do to 
 
live in the current AI era? 

31
00:01:06,743 --> 00:01:09,063
You have to be an absolute 
expert 
 on using Claude and 

32
00:01:09,063 --> 00:01:11,087
agents, period. 
This is the best time to be 
 

33
00:01:11,095 --> 00:01:13,602
alive in technology ever. 
You've been all doing AI, more 


34
00:01:13,610 --> 00:01:16,047
technical stuff, and you finally
wrote a book not about 

35
00:01:16,047 --> 00:01:17,853
technology. 
It's called Joy Success Cycle. 

36
00:01:17,923 --> 00:01:20,299
The core of the book says that 
joy doesn't 
 come after 

37
00:01:20,299 --> 00:01:22,392
success, it comes before. 
Joy in everything you do 
 will 

38
00:01:22,392 --> 00:01:24,638
lead to more success. 
This is a very critical 

39
00:01:24,638 --> 00:01:26,879
breakthrough in 
 understanding,
and stop worrying about those 

40
00:01:26,879 --> 00:01:45,203
things which you can't impact. 
Hey, quick pause. 

41
00:01:45,383 --> 00:01:47,243
My goal with Tech Lead Journal 
is simple. 

42
00:01:47,753 --> 00:01:50,513
Learn from the best in tech 
 so
we can all grow together. 

43
00:01:50,753 --> 00:01:54,053
If this resonates with you, hit 
 subscribe to follow the 

44
00:01:54,053 --> 00:01:56,027
channel. 
It's the biggest way for you to 

45
00:01:56,027 --> 00:01:58,598
support 
 the show and help us 
keep bringing great guests and 

46
00:01:58,598 --> 00:02:00,893
insights to you. 
Thanks for being here, 
 and 

47
00:02:00,893 --> 00:02:03,880
let's get back to it. 
Hello everyone. 

48
00:02:03,880 --> 00:02:05,980
Welcome back to another new 
episode 
 of the Tech Lead 

49
00:02:05,980 --> 00:02:08,192
Journal podcast. 
Today I have with me Kevin 

50
00:02:08,192 --> 00:02:11,435
Surace. 
He's known as the father of AI 

51
00:02:11,435 --> 00:02:13,458
Assistant. 
So we'll talk a little 
 bit 

52
00:02:13,458 --> 00:02:15,910
more about that. 
But not only that, Kevin is 
 

53
00:02:15,918 --> 00:02:20,448
also publishing his book, his 
first book, if I'm not mistaken,

54
00:02:20,448 --> 00:02:24,090

 called Joy-Success Cycle. 
So Kevin, welcome to the show. 

55
00:02:24,330 --> 00:02:26,855
Thank you so much for your time.
Thanks, Henry, for having me. 

56
00:02:27,971 --> 00:02:29,456
Right. 
Kevin, let's start from this 

57
00:02:29,456 --> 00:02:31,731
title of 
 yours, Father of AI 
Assistant, right? 

58
00:02:31,841 --> 00:02:35,034
I can see also behind you 
there's 
 this, you know, 

59
00:02:35,034 --> 00:02:37,417
picture about Portico. 
I think if I'm not mistaken, 
 

60
00:02:37,425 --> 00:02:39,941
that's kind of like the first 
generation of AI assistant. 

61
00:02:40,191 --> 00:02:43,011
So maybe let's start from there.
Let's tell a story about how 
 

62
00:02:43,019 --> 00:02:45,871
did you end up becoming like the
Father of AI Assistant. 

63
00:02:46,050 --> 00:02:48,530
Yeah, that is right. 
Portico was Portico was the 

64
00:02:48,530 --> 00:02:52,240
first 
 fully AI assistant that 
you could argue with and 

65
00:02:52,240 --> 00:02:55,490
interact with and interrupt. 
And she would answer your phone 

66
00:02:55,490 --> 00:02:58,330
 and book people on your 
calendar and things we can't 

67
00:02:58,330 --> 00:03:01,434
even do today. 
We did that work at a 
 company 

68
00:03:01,434 --> 00:03:04,754
called General Magic. 
General Magic was a spin-off out

69
00:03:04,754 --> 00:03:07,890
of Apple 
 and developed three 
major breakthroughs. 

70
00:03:07,900 --> 00:03:11,100
First was somewhat the 
 
predecessor to the iPhone. 

71
00:03:12,350 --> 00:03:16,050
And the second was a language 
 
called Telescript, so that we 

72
00:03:16,050 --> 00:03:18,110
could create AI agents, and we 
did. 

73
00:03:18,120 --> 00:03:20,392
So we had agent-- We had the 
whole 
 idea of agents came out 

74
00:03:20,392 --> 00:03:23,450
of General Magic that long ago 
in the late '90s. 

75
00:03:23,490 --> 00:03:29,728
And the third was this idea 
 of
an assistant that you could talk

76
00:03:29,728 --> 00:03:33,884
to over the phone. 
And the importance of that at 
 

77
00:03:33,892 --> 00:03:36,900
the time was that people had 
just gotten cell phones, not 

78
00:03:36,900 --> 00:03:38,820
smartphones 
 yet, like Motorola
flip phones. 

79
00:03:39,040 --> 00:03:41,319
And they had just gotten the 
internet, 
 but the internet was

80
00:03:41,319 --> 00:03:44,100
something you had basically at 
your desk at work, and 
 you 

81
00:03:44,100 --> 00:03:46,970
didn't have access to your 
calendar and your contacts and 

82
00:03:46,970 --> 00:03:50,619
every stock 
 quotes, whatever, 
while you were in the car or 

83
00:03:50,619 --> 00:03:52,798
pretty much anywhere else, 
 
because there was no portable 

84
00:03:52,798 --> 00:03:55,566
device. 
But we could get you access to 

85
00:03:55,566 --> 00:03:58,140
all of 
 that via talking to a 
virtual assistant. 

86
00:03:58,150 --> 00:04:00,448
So that's what we did. 
And we ended up having about 
 

87
00:04:00,456 --> 00:04:03,920
three and a half million people 
on the system at the time. 

88
00:04:03,920 --> 00:04:08,406
So it was successful and fun 
and, 
 you know, a big 

89
00:04:08,406 --> 00:04:10,959
development project. 
I think one of the fun things 
 

90
00:04:10,967 --> 00:04:13,290
for your audience is there's no 
such thing as the cloud then. 

91
00:04:13,360 --> 00:04:16,480
So you built your own 
 data 
center, which we did. 

92
00:04:16,480 --> 00:04:19,700
We had to build our own data 
center, 
 and it was a voice and

93
00:04:19,700 --> 00:04:22,340
data center because you had to 
take voice coming 
 in, and you 

94
00:04:22,340 --> 00:04:24,868
had to have voice going out, and
you had to process it in 

95
00:04:24,868 --> 00:04:26,350
between. 
So we did all of that. 

96
00:04:26,400 --> 00:04:32,352
And it was a great team, great 
effort, 
 and ended up resulting

97
00:04:32,352 --> 00:04:36,132
in, oh, you know, more than a 
dozen US patents, 
 several 

98
00:04:36,132 --> 00:04:39,180
dozen worldwide patents. 
And those got licensed 

99
00:04:39,180 --> 00:04:42,774
ultimately 
 to Apple, 
Microsoft, Google and others, 

100
00:04:42,774 --> 00:04:46,670
pretty much, and Amazon. 
Anyone who really wanted 
 to do

101
00:04:46,670 --> 00:04:49,170
voice assistants. 
Lastly, one of the big things 
 

102
00:04:49,178 --> 00:04:51,380
that came out of that is 
something called post-training. 

103
00:04:51,510 --> 00:04:55,062
Post-training is something we do
all the 
 time now with AI, with

104
00:04:55,062 --> 00:04:59,125
Gen AI models. 
And post-training is where you 

105
00:04:59,125 --> 00:05:03,915
have 
 literally rooms of people
looking at how the model reacted

106
00:05:03,915 --> 00:05:07,210
and seeing 
 if it's correct or 
not, and then putting in 

107
00:05:07,210 --> 00:05:10,302
corrections into sort 
 of its 
background programming, if you 

108
00:05:10,302 --> 00:05:13,140
will, or background prompting. 
And we were the first people to 

109
00:05:13,140 --> 00:05:14,180
do that. 
We invented it. 

110
00:05:14,180 --> 00:05:16,060
It was the subject of a patent 
also. 

111
00:05:17,210 --> 00:05:20,990
And we had linguists listening 

to what was being said. 

112
00:05:20,990 --> 00:05:23,606
They didn't know who was saying 
it, 
 but they were listening to

113
00:05:23,606 --> 00:05:27,100
that and making corrections in 
the model so 
 that it would be 

114
00:05:27,100 --> 00:05:29,580
more accurate each time someone 
interacted with it. 

115
00:05:29,610 --> 00:05:34,640
So lots of breakthroughs there 

and, you know, very proud of 

116
00:05:34,640 --> 00:05:38,823
that team and the work we did. 
Wow, so, so many patents. 

117
00:05:38,823 --> 00:05:41,342
If I'm not mistaken, you 
 have 
90 over patents. 95. 

118
00:05:41,423 --> 00:05:43,213
I think you mentioned a coup- 
95. 

119
00:05:43,213 --> 00:05:45,393
Okay, yeah, some of those 
 
related to this AI assistant. 

120
00:05:45,423 --> 00:05:48,823
And it-- I think it's really 
 
cool, every company who wants 

121
00:05:48,823 --> 00:05:51,243
to, you know, invent their own 
AI 
 assistant, you know, it's 

122
00:05:51,243 --> 00:05:53,163
kind of like having the license 
from yours. 

123
00:05:53,873 --> 00:05:57,365
So I think that's… Yeah, and 
more than that, even when 
 

124
00:05:57,373 --> 00:06:01,166
patents expire, you are building
on all of the work that was done

125
00:06:01,166 --> 00:06:02,582
in the past. 
This is true with all 

126
00:06:02,582 --> 00:06:04,386
technology, right? 
You're building on the work of 

127
00:06:04,386 --> 00:06:06,242
the past. 
Patents eventually expire, and 


128
00:06:06,250 --> 00:06:13,742
there were some of these patents
got extended for a variety of 

129
00:06:13,742 --> 00:06:15,108
reasons. 
But most of those patents 
 are 

130
00:06:15,108 --> 00:06:17,209
probably expired by now. 
They've hit the 20-plus year 

131
00:06:17,209 --> 00:06:20,099
mark. 
And-- but still, when you look 

132
00:06:20,099 --> 00:06:23,978
at the 
 architecture of 
systems, you find a lot of what 

133
00:06:23,978 --> 00:06:26,888
we did in terms of how do you 
 
interact with an artificial 

134
00:06:26,888 --> 00:06:29,952
human, what should that look 
like, how should they 
 respond,

135
00:06:29,952 --> 00:06:32,917
what's the range of responses. 
You know, all of that 
 early 

136
00:06:32,917 --> 00:06:36,797
work had to be done. 
And, po- the, you know, the idea

137
00:06:36,797 --> 00:06:38,492
of 
 post-training, that wasn't 
obvious. 

138
00:06:38,492 --> 00:06:39,852
We were the first people to do 
it. 

139
00:06:40,212 --> 00:06:42,750
Cause people would look and say,
"Huh, 
 it doesn't always 

140
00:06:42,750 --> 00:06:44,922
respond right. 
Well, we have to do better in 

141
00:06:44,922 --> 00:06:46,546
pre-training. 
We have 
 to do better in 

142
00:06:46,546 --> 00:06:47,472
pre-training." 
I go, stop. 

143
00:06:47,682 --> 00:06:49,562
Why don't we just listen 
 to 
what people say? 

144
00:06:49,562 --> 00:06:51,372
I mean, it was a crazy idea one 
day. 

145
00:06:51,512 --> 00:06:53,142
Why don't we listen to what 
 
they're saying and fix it? 

146
00:06:53,522 --> 00:06:55,774
What do you mean? 
Well, we'll build an interface 

147
00:06:55,774 --> 00:06:59,238
so that 
 our linguists, without
coding, can just go in and say, 

148
00:06:59,238 --> 00:07:01,319
"No, the right… This is 
 what 
it said, and the right answer 

149
00:07:01,319 --> 00:07:03,840
would be this." 
And you keep training it and 
 

150
00:07:03,848 --> 00:07:05,592
putting weights on those new 
answers. 

151
00:07:05,972 --> 00:07:08,652
And it turns out that was a 
 
brilliant idea, but we didn't 

152
00:07:08,652 --> 00:07:09,692
know it was brilliant at the 
time. 

153
00:07:09,692 --> 00:07:11,482
We're just trying to fix the 
thing, right? 

154
00:07:12,392 --> 00:07:18,077
And today that is a stalwart 
 
of what we do in gen AI for sure

155
00:07:18,077 --> 00:07:21,456
and also in AI assistance. 
And, you know, people like Scale

156
00:07:21,456 --> 00:07:24,502
AI 
 and others have tens of 
thousands of people doing 

157
00:07:24,502 --> 00:07:27,002
post-training, right? 
We had seven, I think. 

158
00:07:27,602 --> 00:07:30,032
It wasn't that many, but 
 they 
were busy all the time. 

159
00:07:30,915 --> 00:07:32,975
Remind me again which year is 
that? 

160
00:07:33,620 --> 00:07:37,050
1998, 1999, just before 2000, 
yeah. 

161
00:07:38,447 --> 00:07:41,047
And I think these days people 
associate 
 these kind of 

162
00:07:41,047 --> 00:07:44,537
assistance with, you know, 
GenAI, right, LLM model, right? 

163
00:07:44,702 --> 00:07:47,339
Sure. 
So back then, what was the AI 

164
00:07:47,339 --> 00:07:49,247
technology 
 that actually you 
leverage on? 

165
00:07:50,790 --> 00:07:52,905
Yeah, great question. 
We used hidden Markov models, 
 

166
00:07:52,913 --> 00:07:56,910
so we didn't have an LLM. 
And that is a very traditional 

167
00:07:56,910 --> 00:08:01,064
type 
 of AI model that does 
learn and it can learn every 

168
00:08:01,064 --> 00:08:05,037
time something happens. 
And so you had a combination of 

169
00:08:05,037 --> 00:08:08,514
itself 
 learning and getting 
better and in terms of responses

170
00:08:08,514 --> 00:08:11,748
post-training 
 to make sure 
that we could tell the system 

171
00:08:11,748 --> 00:08:15,900
that even though it thought 
 
that answer was right, it wasn't

172
00:08:15,910 --> 00:08:17,570
the appropriate, you know, 
response. 

173
00:08:18,070 --> 00:08:20,924
And again, that even with Gen 
AI, that's 
 what we're doing 

174
00:08:20,924 --> 00:08:24,462
because you have all this 
pre-training of a trillion or 

175
00:08:24,462 --> 00:08:27,380
more 
 tokens or trillion or 
more phrases. 

176
00:08:28,430 --> 00:08:31,320
And yet still it gets some 
 
things wrong, you know. 

177
00:08:31,320 --> 00:08:35,736
It-- we say hallucinates. 
We never called, Mary was her 
 

178
00:08:35,744 --> 00:08:39,309
name, the first AI assistant. 
We never thought she 

179
00:08:39,309 --> 00:08:40,890
hallucinated. 
She-- You know, we never used 

180
00:08:40,890 --> 00:08:43,535
that term. 
We just said that that wasn't 
 

181
00:08:43,544 --> 00:08:45,790
the, the right response, you 
know? 

182
00:08:47,480 --> 00:08:50,142
So, you know, you always have to
have 
 these breakthroughs at 

183
00:08:50,142 --> 00:08:51,701
the beginning. 
And obviously, I've been part 
 

184
00:08:51,709 --> 00:08:55,575
of this all the way along. 
I run an AI company today, so 

185
00:08:55,575 --> 00:08:58,896
I'm 
 still very busy in AI and,
you know. 

186
00:08:59,616 --> 00:09:04,010
But the frontier models have 
gone down 
 a path because of, 

187
00:09:04,010 --> 00:09:09,290
one, the work that Google did in
2012 to, you know, put 
 out in 

188
00:09:09,290 --> 00:09:13,378
the public how you build a deep 
learning model, basically very 

189
00:09:13,378 --> 00:09:15,968
deep. 
And then by 2017, they published

190
00:09:15,968 --> 00:09:17,776
a 
 seminal paper on the 
transformer. 

191
00:09:18,236 --> 00:09:21,653
And once you had that, 
 you 
could build LLMs. That is almost

192
00:09:21,653 --> 00:09:25,231
ten years ago now, right? 
So we've had ten years of 
 

193
00:09:25,239 --> 00:09:28,786
advances on the transformer and 
it's still giving us paybacks. 

194
00:09:28,786 --> 00:09:31,060
I mean, these models are getting

 better and-- But they're also 

195
00:09:31,060 --> 00:09:32,306
getting better because of 
post-training. 

196
00:09:32,306 --> 00:09:34,946
They're also getting better 
 
because they can self-code. 

197
00:09:34,946 --> 00:09:37,146
So they've got, you know, 
 
reinforcement learning. 

198
00:09:37,146 --> 00:09:41,565
You've got, now basically 
 
self-coding, where a lot of 

199
00:09:41,565 --> 00:09:45,156
these models are being coded by 
the 
 model itself to improve 

200
00:09:45,156 --> 00:09:48,561
itself. 
I think, you know, a lot of 

201
00:09:48,561 --> 00:09:50,066
people 
 never thought we would 
get there. 

202
00:09:50,066 --> 00:09:54,248
And I would say, in this space 
from 
 a coding perspective, we 

203
00:09:54,248 --> 00:09:59,639
weren't there till early 2026 
when Claude 
 finally had a 

204
00:09:59,639 --> 00:10:02,766
release that literally could 
build an entire application. 

205
00:10:02,766 --> 00:10:06,872
If you remember a couple years 
ago, 
 yeah, we were all using 

206
00:10:06,872 --> 00:10:09,346
coding tools, and they were a 
little bit of a help. 

207
00:10:09,586 --> 00:10:12,870
About as much of a help as me, 
you know, 
 searching for some 

208
00:10:12,870 --> 00:10:15,560
open source code. 
But then this breakthrough 

209
00:10:15,560 --> 00:10:20,036
happened 
 that was like, oh, I 
can get up and leave, and six 

210
00:10:20,036 --> 00:10:22,354
hours later 
 it wrote the 
entire application front-end, 

211
00:10:22,354 --> 00:10:26,651
back-end, and it works. 
Once you got to that level of 
 

212
00:10:26,659 --> 00:10:30,774
competency, it changed the game.
And it changed it 

213
00:10:30,774 --> 00:10:34,026
psychologically, where 
 we've 
had programmers going, you know,

214
00:10:34,026 --> 00:10:37,050
for two years on LLMs, "Oh, 
they'll never 
 get rid of me 

215
00:10:37,050 --> 00:10:40,360
'cause I'm still doing eighty or
ninety percent of the work," to,

216
00:10:40,360 --> 00:10:42,656

 "I don't write a line of code 
anymore." 

217
00:10:42,816 --> 00:10:46,212
And, all-- certainly all of my 
coders 
 that work for me, all 

218
00:10:46,212 --> 00:10:48,506
my developers, they don't even 
look at the code anymore. 

219
00:10:48,566 --> 00:10:51,986
They, it… Because this 
 Claude 
will write code so fast. 

220
00:10:53,023 --> 00:10:55,721
And it's written so many lines 
that, 
 you know, you say, "I 

221
00:10:55,721 --> 00:10:58,063
need to build this, and here's 
the ins and here's 
 the out, 

222
00:10:58,063 --> 00:11:00,005
here's the API." 
It goes and does it, you run it,

223
00:11:00,005 --> 00:11:02,471
and it works. 
There's 2,500 lines of code in 

224
00:11:02,471 --> 00:11:03,673
there. 
You're not gonna look at them. 

225
00:11:03,683 --> 00:11:05,333
You're not gonna try to 
 
dissect what's going on. 

226
00:11:05,333 --> 00:11:07,689
You just ship it. 
You know, you gotta test it and 

227
00:11:07,689 --> 00:11:10,355
ship it. 
And so, so I think that's really

228
00:11:10,355 --> 00:11:14,893

 a fascinating thing and a real
impact to developers who, you 

229
00:11:14,893 --> 00:11:19,385
know, 
 who thought that their 
reason for living was to write 

230
00:11:19,385 --> 00:11:22,957
lines of code. 
And maybe that's not gonna be 

231
00:11:22,957 --> 00:11:27,001
the case 
 anymore 'cause the 
people at the frontier of this 

232
00:11:27,001 --> 00:11:29,747
are not writing any code at all,

 and they're not even reviewing

233
00:11:29,747 --> 00:11:31,292
the code. 
Yeah. 

234
00:11:31,622 --> 00:11:34,357
I think putting aside coding, 
you know, 
 I think I can also 

235
00:11:34,357 --> 00:11:37,710
see in the past one year, you 
know, all these AI chatbot, you 

236
00:11:37,710 --> 00:11:40,058
 know, the, for example, 
ChatGPT, Gemini, you know, even 

237
00:11:40,058 --> 00:11:42,840
Claude itself, right? 
I think they are quite good in 

238
00:11:42,840 --> 00:11:44,999
terms 
 of replying, you know, 
answering, brainstorming 

239
00:11:44,999 --> 00:11:47,212
together with you, 
 coming up 
with solutions, right? 

240
00:11:47,332 --> 00:11:49,892
I think less hallucination, 
 at
least from my experience. 

241
00:11:50,431 --> 00:11:52,227
Yeah, that's right. 
But I think it's quite 

242
00:11:52,227 --> 00:11:54,320
fascinating 
 how, yeah, quite 
fascinating how this, you know, 

243
00:11:54,320 --> 00:11:58,300
AI goes. 
But before then, also you were 

244
00:11:58,300 --> 00:12:01,713
involved 
 in these two 
so-called revolutionary AI 

245
00:12:01,713 --> 00:12:05,132
assistant as well back then, 
 
which are Siri and Alexa, right?

246
00:12:05,262 --> 00:12:08,726
So, I think maybe people might 
have 
 forgotten about those 

247
00:12:08,726 --> 00:12:10,992
technologies simply because of 
the current AI chatbot. 

248
00:12:11,472 --> 00:12:14,082
But tell us also these 
breakthrough that 
 you went 

249
00:12:14,082 --> 00:12:17,969
when you work on Alexa and Siri.
I think Alexa back then when it 

250
00:12:17,969 --> 00:12:21,107
 was, you know, first time, you 
know, revealed, it was like 

251
00:12:21,107 --> 00:12:23,199
quite fascinating. 
I didn't work directly on them. 

252
00:12:23,209 --> 00:12:26,759
They licensed our technology 
 
and our patents to build them. 

253
00:12:26,759 --> 00:12:32,039
What I can tell you is that they

 were built very much 

254
00:12:32,039 --> 00:12:34,799
leveraging the sort of the 
models that we put forth. 

255
00:12:34,809 --> 00:12:40,009
This is before LLMs, right? 
So they were all based on what 

256
00:12:40,009 --> 00:12:44,403
we 
 called traditional speech 
recognition, that did use hidden

257
00:12:44,403 --> 00:12:46,453
Markov models. 
A lot of those came from 
 a 

258
00:12:46,453 --> 00:12:49,654
company called Nuance. 
And so those kind of became 
 

259
00:12:49,662 --> 00:12:53,379
the best models in the industry 
until LLMs came along. 

260
00:12:53,869 --> 00:12:57,270
And they used a variety of 
 
text-to-speech, and we got-- we 

261
00:12:57,270 --> 00:12:58,969
kept getting better at 
text-to-speech. 

262
00:12:59,349 --> 00:13:02,997
Early on, our text-to-speech, 
was that 
 is conversion of -- 

263
00:13:02,997 --> 00:13:06,739
say, email, read my email, right
-- was very crude. 

264
00:13:06,739 --> 00:13:11,858
In fact, it was often based on 

concatenating syllables recorded

265
00:13:11,858 --> 00:13:15,405
by humans in a studio and 
putting them 
 all back 

266
00:13:15,405 --> 00:13:18,147
together, and writing the 
algorithms to put them all back 

267
00:13:18,147 --> 00:13:20,757
together. 
Because without that, they 
 

268
00:13:20,765 --> 00:13:24,207
sounded very mechanical. 
And you'll remember, a lot 
 of 

269
00:13:24,207 --> 00:13:27,234
those mechanical things. 
"Hi, this is the train. 

270
00:13:27,234 --> 00:13:29,719
It is leaving for 
 the next 
station." 

271
00:13:29,719 --> 00:13:32,999
And go, take, what? 
Can't you just record that? 

272
00:13:33,259 --> 00:13:37,404
You know, this is terrible. 
So now it's really perfect 

273
00:13:37,404 --> 00:13:40,989
because we can 
 build models on
an actual human voice. 

274
00:13:40,989 --> 00:13:43,679
And as you know, we can build 
 
a model on my voice or your 

275
00:13:43,679 --> 00:13:48,019
voice in a matter of minutes. 
But that technology didn't 

276
00:13:48,019 --> 00:13:51,231
exist. 
And so, you had to concatenate 

277
00:13:51,231 --> 00:13:54,748
all these 
 things and, or 
record real human voices and, 

278
00:13:54,748 --> 00:13:56,059
you know, put them back 
together. 

279
00:13:56,059 --> 00:13:58,169
And a lot of people did that. 
We did that. 

280
00:13:59,479 --> 00:14:01,539
You know, Siri did that 
 for 
the longest time. 

281
00:14:01,539 --> 00:14:03,389
Alexa did that. 
That's what everybody did. 

282
00:14:04,919 --> 00:14:06,609
And we had laid out 
 the 
process to do that. 

283
00:14:06,609 --> 00:14:10,009
So everybody, you know, 
licensed, those 
 two big 

284
00:14:10,009 --> 00:14:11,709
systems licensed that 
technology. 

285
00:14:11,709 --> 00:14:15,137
And today, you know, everybody's

 moving to an LLM backbone, if 

286
00:14:15,137 --> 00:14:19,221
you will. 
And, but still many of the kind 

287
00:14:19,221 --> 00:14:23,154
of 
 human interface issues that
we had to deal with are still 

288
00:14:23,154 --> 00:14:25,746
used today. 
Right. 

289
00:14:26,136 --> 00:14:28,566
So you mentioned about, you 
know, 
 software developers, you

290
00:14:28,566 --> 00:14:31,326
know, their job these days will 
change a lot, right? 

291
00:14:31,326 --> 00:14:34,156
So, no more writing the 
 code, 
that's for sure. 

292
00:14:34,476 --> 00:14:38,280
Even reading the code probably 
is kind of 
 like a very tough 

293
00:14:38,280 --> 00:14:41,022
job these days because of the 
amount of code that AI can 

294
00:14:41,022 --> 00:14:41,816
produce. 
Yeah, it's too much. 

295
00:14:42,476 --> 00:14:45,826
Yeah, so what do you think the 

developer's evolution should be,

296
00:14:45,826 --> 00:14:47,636
right, maybe from your point of 
view? 

297
00:14:47,837 --> 00:14:52,161
So we've seen this before, but 
very 
 few developers alive 

298
00:14:52,161 --> 00:14:55,685
today remember it. 
And so let me take you 
 back to

299
00:14:55,685 --> 00:14:59,057
the '50s and '60s. 
Well, in the '50s and '60s there

300
00:14:59,057 --> 00:15:00,327

 was something called machine 
code. 

301
00:15:00,847 --> 00:15:04,387
That's how you coded a computer.
It was literal ones and zeros. 

302
00:15:04,817 --> 00:15:08,118
Lit-- And you had a table, and 
if you 
 wanted to do this 

303
00:15:08,118 --> 00:15:10,981
particular thing, it was one, 
one, zero, zero, one, zero, one,

304
00:15:10,981 --> 00:15:14,057

 one, and that's what you'd put
in, either on a punch card or 

305
00:15:14,057 --> 00:15:17,407
some other way, right? 
So we started with machine code.

306
00:15:18,547 --> 00:15:22,867
And later, I wanna say it was 
late '50s 
 or sometime in the 

307
00:15:22,867 --> 00:15:27,157
'60s, and it may have been IBM, 
developed an idea of assembler. 

308
00:15:27,697 --> 00:15:32,634
And Assembly would be still an 

extremely crude language, but 

309
00:15:32,634 --> 00:15:36,581
that language would convert 
itself, 
 basically compile into

310
00:15:36,581 --> 00:15:38,647
machine code. 
Okay, great. 

311
00:15:38,957 --> 00:15:41,519
All of a sudden, I didn't have 
to worry 
 about the one, one, 

312
00:15:41,519 --> 00:15:44,689
zero, one, one, zero. 
I could say, move this register 

313
00:15:44,689 --> 00:15:47,537
from 
 here to there, and it 
would, right? 

314
00:15:47,547 --> 00:15:49,697
And it would just put that 
 
into the ones and zeros. 

315
00:15:49,697 --> 00:15:51,307
This wasn't a very 
English-friendly 
 language, and

316
00:15:51,307 --> 00:15:53,827
it wasn't a high-level language.
It was a very low-level 

317
00:15:53,827 --> 00:15:56,836
language, but 
 it works, and 
it's very succinct, and it's 

318
00:15:56,836 --> 00:16:01,409
very much tied to essentially, 

each processor cycle, each 

319
00:16:01,409 --> 00:16:03,887
processor, actual command on the
processor. 

320
00:16:03,887 --> 00:16:06,807
Okay, fine. 
So by the '60s we had that. 

321
00:16:06,917 --> 00:16:10,151
And then later in the '60s 
people 
 started using the two 

322
00:16:10,151 --> 00:16:12,892
first high-level languages, one 
business and one math, 
 Fort-- 

323
00:16:12,892 --> 00:16:16,949
it was COBOL and Fortran. 
And that's the first time, in 

324
00:16:16,949 --> 00:16:19,447
essence, 
 in English, I could 
do something. 

325
00:16:19,447 --> 00:16:22,513
So early coders were coding in a

 language that went away 

326
00:16:22,513 --> 00:16:24,857
because we had a higher level 
language called Assembly. 

327
00:16:24,857 --> 00:16:28,277
And then Assembly basically went

 away for most people, and that

328
00:16:28,277 --> 00:16:30,747
became these higher level 
languages. 

329
00:16:30,747 --> 00:16:33,627
And of course, by the '70s and 
'80s, 
 we had very high-level 

330
00:16:33,627 --> 00:16:36,581
languages that are really 
thoughtful, that 
 are in 

331
00:16:36,581 --> 00:16:41,574
English in essence, right? 
So we have seen developers move 

332
00:16:41,574 --> 00:16:46,890
to 
 higher and higher level 
languages where the language is 

333
00:16:46,890 --> 00:16:52,287
producing, you know, 
 thousands
of lines of machine code for us.

334
00:16:52,467 --> 00:16:54,017
We're not writing those 
 
thousands of lines. 

335
00:16:54,757 --> 00:16:58,607
Now we've progressed one more 
 
time to the actual English 

336
00:16:58,607 --> 00:17:03,051
language of natural language. 
So if I can describe it at this 

337
00:17:03,051 --> 00:17:06,666
 level, it'll write it in 
Python, which actually is 

338
00:17:06,666 --> 00:17:10,385
compiling down 
 to Assembly, 
which ultimately kind of 

339
00:17:10,385 --> 00:17:13,204
converts to machine code. 
And we don't see any of those 

340
00:17:13,204 --> 00:17:15,795
layers. 
So my point is, we've given up 


341
00:17:15,803 --> 00:17:19,025
seeing a variety of layers of 
computer programming over the 

342
00:17:19,025 --> 00:17:20,813
years. 
Most people just have forgotten 

343
00:17:20,813 --> 00:17:23,310
that 
 because we've been in 
high-level languages now for 

344
00:17:23,310 --> 00:17:25,663
thirty or forty years. 
And now we're going to the 

345
00:17:25,663 --> 00:17:27,666
highest level 
 language, which 
is just the way we speak. 

346
00:17:27,666 --> 00:17:30,722
And if we're articulate enough 
and 
 have a good enough 

347
00:17:30,722 --> 00:17:34,417
specification, it'll write all 
of that all the way 
 down to 

348
00:17:34,417 --> 00:17:38,479
machine code for us, right? 
Based on sixty years of effort, 

349
00:17:38,479 --> 00:17:42,327
right? 
And here's what I would portend.

350
00:17:42,337 --> 00:17:46,103
Here's what I would say, in 
 
talking to so many developers. 

351
00:17:46,383 --> 00:17:51,487
At first, the developer has 
sadness and 
 says, "All of my 

352
00:17:51,487 --> 00:17:57,214
joy comes from or came from 
writing code, and I love writing

353
00:17:57,214 --> 00:18:00,623

 code." 
And so my supposition here is 

354
00:18:00,623 --> 00:18:02,833
that you never really loved 
writing code. 

355
00:18:02,833 --> 00:18:04,863
And by the way, you could 
 
still write code if you want. 

356
00:18:05,023 --> 00:18:07,592
No one will pay you for it, but 
 you can write all you want at 

357
00:18:07,592 --> 00:18:11,305
home. 
Actually, what you got the most 

358
00:18:11,305 --> 00:18:15,247
 joy from is delivering that 
feature or that bug fix or 

359
00:18:15,247 --> 00:18:18,203
whatever. 
And notice the person you were 


360
00:18:18,211 --> 00:18:21,955
delivering that to, internal in 
a company or an external 

361
00:18:21,955 --> 00:18:25,263
customer or 
 whatever, never 
cared how you got there. 

362
00:18:26,003 --> 00:18:30,282
What they cared about is did 
 
you do it right, was it on time,

363
00:18:30,282 --> 00:18:34,128
or was it even speedier? 
So they wanted speed and 

364
00:18:34,128 --> 00:18:36,163
quality. 
Speed and quality. 

365
00:18:36,173 --> 00:18:39,634
Nobody cares how you got there. 
And in fact, if you can get 

366
00:18:39,634 --> 00:18:41,633
there without 
 writing a line 
of code, even better. 

367
00:18:41,693 --> 00:18:43,513
Like, to your customer, even 
better. 

368
00:18:43,883 --> 00:18:47,373
And so people have to wake up 
 
and realize the joy is from the 

369
00:18:47,373 --> 00:18:52,409
delivery of the output. 
And I see developers now with 

370
00:18:52,409 --> 00:18:56,298
essentially 
 a screen of, you 
know, eight agents, and each one

371
00:18:56,298 --> 00:18:59,539
is kicking off some feature 
 
upgrade, some bug fix, some, you

372
00:18:59,539 --> 00:19:01,935
know, etc. 
And they're just the robot 

373
00:19:01,935 --> 00:19:03,323
overlord. 
They're coordinating all of 

374
00:19:03,323 --> 00:19:04,573
that. 
They're getting it back. 

375
00:19:04,823 --> 00:19:07,013
They're doing some unit testing.
They're integrating it. 

376
00:19:07,023 --> 00:19:10,223
Someone else probably will do 
full feature 
 testing or full 

377
00:19:10,223 --> 00:19:12,283
functional testing, etc. 
And then they're shipping it. 

378
00:19:12,473 --> 00:19:15,303
And I watch people now, 
including in 
 my companies, 

379
00:19:15,303 --> 00:19:19,022
someone says, "Boy, at 11 
o'clock in the morning, we got a

380
00:19:19,022 --> 00:19:22,413
customer 
 that really needs 
this feature, and I, you know, I

381
00:19:22,413 --> 00:19:24,813
don't know how many weeks 
 
that's gonna take." 

382
00:19:24,813 --> 00:19:28,067
And at one o'clock after lunch, 
you know, the guy comes 
 out or

383
00:19:28,067 --> 00:19:30,973
the gal comes out and says, "You
know, during lunch I ran this 

384
00:19:30,973 --> 00:19:33,153
agent, 
 and it did it for… And 
here it is. 

385
00:19:33,163 --> 00:19:35,113
Here's the feature. 
You know, it's done. 

386
00:19:35,193 --> 00:19:38,198
It's not fully tested yet, but 
it's 
 done." 

387
00:19:38,198 --> 00:19:41,831
That brings, trust me, so much 
joy to everyone involved in 
 

388
00:19:41,839 --> 00:19:43,583
that chain of process there, 
right? 

389
00:19:44,273 --> 00:19:49,095
Lastly, if this was two years 
 
ago, all we heard is coders are 

390
00:19:49,095 --> 00:19:51,162
gonna all lose their jobs. 
We don't need them anymore, 

391
00:19:51,162 --> 00:19:53,241
okay? 
That turns out to not be the 

392
00:19:53,241 --> 00:19:54,979
case. 
Ignoring some companies who've 

393
00:19:54,979 --> 00:19:59,197
laid 
 off and said it's all 
about AI, and it isn't, that's a

394
00:19:59,197 --> 00:20:02,030
longer story. 
Let me tell you why it's not the

395
00:20:02,030 --> 00:20:05,096
case. 
Everyone I know is so excited 

396
00:20:05,096 --> 00:20:10,000
about going 
 so much faster to 
get rid of and reduce their 

397
00:20:10,000 --> 00:20:13,961
feature backlog and their bug 
 
backlog, often is in the 

398
00:20:13,961 --> 00:20:16,268
thousands, right? 
And now they're starting 
 to 

399
00:20:16,268 --> 00:20:19,737
deliver those faster. 
They don't wanna slow down again

400
00:20:19,737 --> 00:20:21,603

 by cutting their dev 
headcount. 

401
00:20:21,963 --> 00:20:26,459
And these devs know their 
product, so no 
 one is cutting 

402
00:20:26,459 --> 00:20:28,863
headcount that matters. 
They really aren't. 

403
00:20:29,663 --> 00:20:33,459
And so this just turned into, 
wow, I 
 can deliver all of this

404
00:20:33,459 --> 00:20:36,393
so much faster. 
That's what it turned into, 
 

405
00:20:36,401 --> 00:20:40,974
and that's really important. 
Yeah, so I think this narrative 

406
00:20:40,974 --> 00:20:43,100
of, you 
 know, we don't need 
software engineers anymore, 

407
00:20:43,100 --> 00:20:47,075
those frontier model companies 

keep saying that over, you know,

408
00:20:47,075 --> 00:20:48,902
the past, I don't know, one year
or so. 

409
00:20:49,732 --> 00:20:52,792
That kind of like creates a lot 
of 
 impact like layoffs, people

410
00:20:52,792 --> 00:20:55,272
are worried, juniors cannot get 
jobs as well. 

411
00:20:55,472 --> 00:20:57,452
I've been hearing it a lot, 
right? 

412
00:20:57,472 --> 00:21:00,012
So I think I understand about 
the 
 moving to the higher 

413
00:21:00,012 --> 00:21:01,872
language, especially now people 
just use prompt. 

414
00:21:02,462 --> 00:21:04,694
But the agentic behavior is 
something 
 that seems, you 

415
00:21:04,694 --> 00:21:06,886
know, kind of like really 
potentially can replace 

416
00:21:06,886 --> 00:21:09,832
developers 
 because they can do
this looping and keep on 

417
00:21:09,832 --> 00:21:12,622
building things until it 
 can 
even turn out into applications.

418
00:21:12,732 --> 00:21:15,682
So what do you think these 
agentic 
 behaviors, should it 

419
00:21:15,682 --> 00:21:19,336
be something that we worry about
or should it 
 be something that

420
00:21:19,336 --> 00:21:21,988
naturally… No. 
Because the people running the 

421
00:21:21,988 --> 00:21:23,843
agentic 
 behavior are 
developers, right? 

422
00:21:23,913 --> 00:21:25,863
You don't want your 
 business 
manager doing that. 

423
00:21:25,863 --> 00:21:28,123
You don't want someone in 
 
accounting doing that, right? 

424
00:21:28,343 --> 00:21:31,095
You want your developers doing 
that 
 because they're 

425
00:21:31,095 --> 00:21:34,847
responsible for the product and 
the quality of the 
 product and

426
00:21:34,847 --> 00:21:38,747
how the product works and did it
meet the specs and all 
 that is

427
00:21:38,747 --> 00:21:43,519
on the developer's back. 
So again, what I see is no one 

428
00:21:43,519 --> 00:21:47,383
that 
 I know of is letting 
developers go. it would be 

429
00:21:47,383 --> 00:21:49,137
laughable. 
And I know some big companies 

430
00:21:49,137 --> 00:21:51,223
did 
 it, and they checked the 
box, and they said it was 

431
00:21:51,223 --> 00:21:52,903
because of AI. 
No one's really doing that. 

432
00:21:52,913 --> 00:21:55,219
The-- I will tell you, the only 
 developers that are getting let

433
00:21:55,219 --> 00:21:57,223
go are developers that say, "I'm
not using AI. 

434
00:21:58,133 --> 00:22:00,493
It's, I don't wanna use it. 
I don't agree with it. 

435
00:22:00,523 --> 00:22:03,045
I think it's wrong. 
I think…" They're never 
 gonna 

436
00:22:03,045 --> 00:22:04,843
work again, right? 
I'm sorry, right? 

437
00:22:04,843 --> 00:22:07,899
This technology's here. 
That's like saying, you know, "I

438
00:22:07,899 --> 00:22:10,155

 don't wanna code in Python." 
And then the company goes, "But 

439
00:22:10,155 --> 00:22:11,630
we 
 only code in Python." 
"Well, I refuse." 

440
00:22:11,630 --> 00:22:13,685
"Okay, well then you don't 
 
work here anymore." 

441
00:22:13,685 --> 00:22:16,793
I-- you know. 
So, I'm not worried about it. 

442
00:22:16,923 --> 00:22:18,303
I'm not worried about… 
 I'm not
seeing it. 

443
00:22:18,323 --> 00:22:21,696
Now the junior developer thing 
is 
 an issue because what's 

444
00:22:21,696 --> 00:22:24,413
happening is companies are not 
hiring as many. 

445
00:22:24,413 --> 00:22:27,553
They're hiring some, as many 
 
developers right out of, coders 

446
00:22:27,573 --> 00:22:32,035
right out of college, right? 
As they go, I really don't need 

447
00:22:32,035 --> 00:22:35,437
this 
 entry-level person 
because my staff here is now 

448
00:22:35,437 --> 00:22:37,796
handling everything and 
 
delivering things so much 

449
00:22:37,796 --> 00:22:40,275
faster. 
I don't have this backlog to 
 

450
00:22:40,283 --> 00:22:42,353
do." 
It's not about, well, AI is 

451
00:22:42,353 --> 00:22:43,563
better than the junior 
developers. 

452
00:22:43,563 --> 00:22:47,613
Like I don't have this backlog 

of things that keeps growing. 

453
00:22:47,613 --> 00:22:49,353
The backlog's finally shrinking,
right? 

454
00:22:49,443 --> 00:22:52,513
Finally catching up. 
So I don't have a need for more 

455
00:22:52,513 --> 00:22:55,320
people. 
That said, there's an overriding

456
00:22:55,320 --> 00:22:59,195

 macro situation, which is 
there are 18 million people 

457
00:22:59,195 --> 00:23:01,725
leaving the workforce 
 over the
next five years, and there's 13 

458
00:23:01,725 --> 00:23:05,357
million available to come in. 
So we are going to be at a 

459
00:23:05,357 --> 00:23:07,397
workforce 
 deficit, in the 
United States anyway, workforce 

460
00:23:07,397 --> 00:23:10,389
deficit for the forever, 
 
right, for the foreseeable 

461
00:23:10,389 --> 00:23:13,435
future. 
And so we need AI to increase 
 

462
00:23:13,443 --> 00:23:16,125
our productivity or else we 
won't have any company at all 

463
00:23:16,125 --> 00:23:17,203
because 
 there'll be no one to 
work. 

464
00:23:18,293 --> 00:23:21,423
So I think overall it's 
 gonna 
work out quite well. 

465
00:23:22,486 --> 00:23:24,640
Right. 
So what can developers do to 

466
00:23:24,640 --> 00:23:27,516
kind 
 of like, yeah, I don't 
know, improve themselves, live 

467
00:23:27,516 --> 00:23:29,896
in the current AI 
 era, 
especially for those juniors, 

468
00:23:29,896 --> 00:23:33,697
how they can survive in this… 
You have to be an absolute, 

469
00:23:33,697 --> 00:23:36,193
absolute 
 expert on using 
Claude and agents, period. 

470
00:23:36,403 --> 00:23:39,483
And you got six, eight agents, 

and they're all, you know, 

471
00:23:39,483 --> 00:23:44,743
running coding tasks for you. 
And that's your job. 

472
00:23:45,103 --> 00:23:48,641
Your job is to coordinate these.
Now there's a lot you have to 

473
00:23:48,641 --> 00:23:51,535
know, 
 right, because we always
think of, "Oh, I'm gonna go 

474
00:23:51,535 --> 00:23:53,730
build an application." 
 
Developers rarely build an 

475
00:23:53,730 --> 00:23:55,708
application. 
What they're building is an 
 

476
00:23:55,716 --> 00:24:00,043
additional feature that has to 
bolt in or a bug fix or 

477
00:24:00,043 --> 00:24:02,320
something else. 
And that has to be 

478
00:24:02,320 --> 00:24:06,043
well-described. 
The APIs have to be well 

479
00:24:06,043 --> 00:24:10,163
specified, 
 you know, the range
of data inputs. 

480
00:24:10,243 --> 00:24:13,343
So all of that has to be 
 done 
and done thoughtfully. 

481
00:24:13,773 --> 00:24:16,253
And you actually have to be 
 a 
good developer to do that. 

482
00:24:16,323 --> 00:24:18,473
Otherwise, you can't 
 even read
an API spec. 

483
00:24:19,073 --> 00:24:21,373
You don't know what an 
 OpenAPI
spec is, right? 

484
00:24:21,373 --> 00:24:23,447
You don't know what it is. 
But so you have to know what it 

485
00:24:23,447 --> 00:24:26,241
is. 
You have to know how to use it 

486
00:24:26,241 --> 00:24:29,678
in these 
 specifications so 
that when the code is delivered 

487
00:24:29,678 --> 00:24:33,139
that interfaces with that API, 

it actually works and it makes 

488
00:24:33,139 --> 00:24:35,951
sense. 
So that's why I think it's 

489
00:24:35,951 --> 00:24:39,130
still… 
 This is a technical 
field that requires technical 

490
00:24:39,130 --> 00:24:44,923
people, that know the process 
 
of now DevOps probably more than

491
00:24:44,933 --> 00:24:46,703
Agile, but understand that 
process. 

492
00:24:47,113 --> 00:24:49,915
I think we're all moving from 
what 
 was a two-week Agile 

493
00:24:49,915 --> 00:24:53,478
process to more of a DevOps 
process, which is 
 like one 

494
00:24:53,478 --> 00:24:56,563
hour and very small things. 
I'm gonna just fix this one bug.

495
00:24:56,933 --> 00:25:00,475
We're gonna put it into a build.
That build might become a 

496
00:25:00,475 --> 00:25:02,401
release. 
And then we do that again 
 

497
00:25:02,409 --> 00:25:04,903
another hour or two from now and
everybody contributes, right? 

498
00:25:04,903 --> 00:25:07,323
So I think we're gonna move 
 
more to DevOps, finally. 

499
00:25:07,393 --> 00:25:10,857
I mean, we've been talking about
DevOps 
 for 20 years, 15 years,

500
00:25:10,857 --> 00:25:13,228
Gene Kim. 
But I think we're actually 

501
00:25:13,228 --> 00:25:15,739
moving there. 
And so this is all good, and 

502
00:25:15,739 --> 00:25:18,633
it's gonna 
 be fast, and it's 
gonna be furious, and people are

503
00:25:18,633 --> 00:25:21,545
gonna get great joy from being 

able to deliver product much 

504
00:25:21,545 --> 00:25:23,833
faster and have happier 
customers of that product. 

505
00:25:25,566 --> 00:25:28,456
I think currently you also are 

still working in a company that 

506
00:25:28,476 --> 00:25:31,660
builds AI for testing, right? 
So tell us what kind of 

507
00:25:31,660 --> 00:25:33,506
revolutionary 
 thing that 
you're doing with testing. 

508
00:25:33,723 --> 00:25:37,753
Yeah, so, Appvance is the name 
of the company. 

509
00:25:37,753 --> 00:25:40,863
Appvance has a, a test 
 
platform that is AI-based. 

510
00:25:40,863 --> 00:25:42,783
It's alway- it's always been AI 
first. 

511
00:25:43,043 --> 00:25:45,683
Obviously, there's, you know, 
LLMs, 
 transformers all over 

512
00:25:45,683 --> 00:25:50,013
the thing today. 
But for, since 2017, that 

513
00:25:50,013 --> 00:25:54,485
technology 
 pretty much by 
itself, you have to be a really 

514
00:25:54,485 --> 00:25:57,153
a developer or a 
 really good 
QA person to set it up. 

515
00:25:57,463 --> 00:26:00,908
But once you've set it up and 
you told 
 it what your business

516
00:26:00,908 --> 00:26:04,643
requirements are, it goes off, 
writes all the tests, 
 writes 

517
00:26:04,643 --> 00:26:07,768
the scripts, literally write, 
codes the scripts, runs the 

518
00:26:07,768 --> 00:26:10,879
scripts, 
 and it will do 
thousands of them, many more 

519
00:26:10,879 --> 00:26:15,356
than you could ever think of. 
And people say, why do I wanna 

520
00:26:15,356 --> 00:26:18,441
test 
 12,000 user flows through
this application as an 

521
00:26:18,441 --> 00:26:21,133
integrated functional test? 
Why don't I just do the 100 that

522
00:26:21,133 --> 00:26:23,461
matter? 
Because actually 12,000 matter, 

523
00:26:23,461 --> 00:26:29,751
because 
 your users are not 
going to go to just one state to

524
00:26:29,751 --> 00:26:33,223
check that particular outcome. 
They're gonna go to 
 whatever 

525
00:26:33,223 --> 00:26:35,701
states they get to. 
Hundreds, thousands of 
 states 

526
00:26:35,701 --> 00:26:38,493
maybe, right? 
And so you wanna test that way. 

527
00:26:38,833 --> 00:26:42,883
And that's something called AI 

Script Generation Bug Hunter. 

528
00:26:43,133 --> 00:26:47,393
A long title, but it finds 
 
bugs that nobody else finds. 

529
00:26:47,743 --> 00:26:50,911
And so we've been doing that 
since 
 2017, and it's very, 

530
00:26:50,911 --> 00:26:53,123
very good, and it's gotten 
better over the years. 

531
00:26:53,123 --> 00:26:54,623
It's gotten easier to set up, 
right? 

532
00:26:55,603 --> 00:26:58,674
It can also generate your test 

cases, just base level test 

533
00:26:58,674 --> 00:27:01,954
cases, and turn those directly 
into 
 scripts and run those 

534
00:27:01,954 --> 00:27:05,328
and, you know. 
So, for years we've got 

535
00:27:05,328 --> 00:27:09,613
customers on 
 this that the 
vast majority of their test 

536
00:27:09,613 --> 00:27:11,473
scripts were written by a 
machine. 

537
00:27:11,953 --> 00:27:13,703
They were not written by the 
humans. 

538
00:27:13,703 --> 00:27:15,933
They did not have a team of 
 
three hundred writing these. 

539
00:27:16,233 --> 00:27:18,633
They had a robot overlord 
 of 
one or two people. 

540
00:27:19,883 --> 00:27:24,520
So what's interesting is you'd 

say, why doesn't everyone use 

541
00:27:24,520 --> 00:27:26,373
this? 
This is a breakthrough. 

542
00:27:26,543 --> 00:27:28,255
You mean AI finds all my bugs?" 
 

543
00:27:28,263 --> 00:27:32,743
You know, it's kind of like the 
Mythos for every application. 

544
00:27:33,513 --> 00:27:37,303
And the answer is yes, it does. 
But here's what you, here's 
 

545
00:27:37,311 --> 00:27:40,501
what you have to know. 
A lot of people have ingrained 


546
00:27:40,509 --> 00:27:43,267
culture, ingrained teams. 
They've got hundreds or 

547
00:27:43,267 --> 00:27:44,993
thousands 
 of people writing 
scripts. 

548
00:27:45,243 --> 00:27:48,173
How do you tell them the machine

 does their job completely? 

549
00:27:48,253 --> 00:27:51,113
How do you do that? 
'Cause in this case, it really 

550
00:27:51,113 --> 00:27:53,061
does. 
You need a manager, but you 

551
00:27:53,061 --> 00:27:55,933
probably don't 
 need people 
manual testing or any of that. 

552
00:27:56,163 --> 00:27:59,793
You really don't. 
And so that's been the 
 biggest

553
00:27:59,793 --> 00:28:02,151
challenge there. 
And the companies, huge 

554
00:28:02,151 --> 00:28:04,384
companies, 
 you know, 
Stellantis, the largest car 

555
00:28:04,384 --> 00:28:07,693
company in the world, this is 
 
their standard platform, and 

556
00:28:07,693 --> 00:28:09,303
Liberty Mutual, and many other 
companies. 

557
00:28:11,033 --> 00:28:14,068
Yet other companies, they go, 
"Oh, 
 wow, that… What do you 

558
00:28:14,068 --> 00:28:17,728
mean you found 282 bugs in our 
production system that 
 we 

559
00:28:17,728 --> 00:28:19,493
never found?" 
"Well, they're real. 

560
00:28:19,523 --> 00:28:22,887
Here they are." 
"Well, I think 
 we should think

561
00:28:22,887 --> 00:28:25,593
about this more." 
You know, it's very scary. 

562
00:28:25,883 --> 00:28:29,279
It's, you know, this is one of 
those 
 technologies that to the

563
00:28:29,279 --> 00:28:32,692
CIO, they love it, and the lower
you get on 
 the totem pole, the

564
00:28:32,692 --> 00:28:35,773
less they love it, the more it 
scares them, right? 

565
00:28:35,953 --> 00:28:41,224
And so, look, I think that will 
 pass, because in the end, 

566
00:28:41,224 --> 00:28:43,623
technology always wins, just 
always wins. 

567
00:28:44,083 --> 00:28:47,963
And unlike coding where you need

 those developers, you know, we

568
00:28:47,963 --> 00:28:51,107
employed millions of people 
doing 
 simple manual testing 

569
00:28:51,107 --> 00:28:53,999
across the world or simple 
scripting, writing 
 Selenium 

570
00:28:53,999 --> 00:28:57,723
scripts and things like that. 
Yeah, that's probably gone. 

571
00:28:57,813 --> 00:29:01,493
You know, those tasks are not 
 
needed anymore, and haven't been

572
00:29:01,493 --> 00:29:05,553
needed for almost ten years. 
But it takes, a long… Sometimes 

573
00:29:05,553 --> 00:29:08,460
 change takes a long time. 
Right. 

574
00:29:08,770 --> 00:29:11,190
And does it do… what's the 
approach? 

575
00:29:11,190 --> 00:29:14,164
Is it white box testing, black 
box 
 testing, or is it a gray 

576
00:29:14,164 --> 00:29:17,722
box thing? 
No, It is complete fun-- 
 it's 

577
00:29:17,722 --> 00:29:21,005
a large platform. 
It's functional, performance, 
 

578
00:29:21,013 --> 00:29:26,161
security, mobile, web, API, etc.
But true functional testing. 

579
00:29:26,171 --> 00:29:31,175
So, you know, true at the UX and
at the 
 API, but usually at the

580
00:29:31,175 --> 00:29:35,651
UX, mimicking what you expect 
users to do and based 
 on your 

581
00:29:35,651 --> 00:29:38,401
business requirements and your 
data-driven outcomes, right? 

582
00:29:38,401 --> 00:29:42,475
So if a user does this and this,
they 
 better get the number 

583
00:29:42,475 --> 00:29:44,511
forty-seven out the other side 
kind of thing, right? 

584
00:29:44,901 --> 00:29:51,225
And so it will create thousands 
of those 
 flows for you based 

585
00:29:51,225 --> 00:29:55,155
on, kind of heuristics based on 
what it thinks users are going 


586
00:29:55,163 --> 00:29:58,472
to do, and based on what your 
business requirements say that 

587
00:29:58,472 --> 00:30:02,191
must work, right? 
And that's what it does. 

588
00:30:02,361 --> 00:30:06,841
And that is the ultimate test. 
Look, all I want in testing is 


589
00:30:06,849 --> 00:30:08,761
one thing: visibility to the 
bugs. 

590
00:30:09,051 --> 00:30:11,391
There will be bugs. 
There will be things that don't 

591
00:30:11,391 --> 00:30:14,579
 work the way I expect them to. 
I just want that visibility, and

592
00:30:14,579 --> 00:30:16,291
I 
 can still decide to release 
it, right? 

593
00:30:16,291 --> 00:30:20,926
But I need the visibility. 
And our testing QA tools never 


594
00:30:20,934 --> 00:30:25,358
gave us very much visibility. 
They gave us, at best, about ten

595
00:30:25,358 --> 00:30:26,561

 percent visibility to all 
bugs. 

596
00:30:26,561 --> 00:30:29,506
And then your users would find 

and report bugs, and then you'd 

597
00:30:29,506 --> 00:30:32,351
go round and they're very 
expensive 
 to fix once the user

598
00:30:32,351 --> 00:30:34,121
finds them. 
So you wanna find them early. 

599
00:30:34,121 --> 00:30:38,626
So, you know, the idea of 
leveraging AI 
 to find all your

600
00:30:38,626 --> 00:30:42,139
bugs, you know, at the 
integration functional testing 

601
00:30:42,139 --> 00:30:44,077
level. 
So this is way beyond unit 

602
00:30:44,077 --> 00:30:45,301
testing. 
You've done your unit test. 

603
00:30:45,311 --> 00:30:47,959
Now you put it all together. 
It's talking to twenty-two 
 

604
00:30:47,967 --> 00:30:50,658
backend systems. 
What's the situation there look 

605
00:30:50,658 --> 00:30:54,125
like? 
And, you know, the idea of using

606
00:30:54,125 --> 00:30:57,221

 AI for that is a really smart 
idea. 

607
00:30:57,341 --> 00:30:59,831
It's not a great use of human 
skills. 

608
00:31:00,211 --> 00:31:03,387
It's something that AI can do, 
and 
 in a few hours it will 

609
00:31:03,387 --> 00:31:06,855
deliver, even on your production
system, 
 more bugs than you've 

610
00:31:06,855 --> 00:31:08,581
ever found. 
But your users have found 
 

611
00:31:08,589 --> 00:31:10,991
them, I can guarantee it. 
They didn't report them, but 

612
00:31:10,991 --> 00:31:13,615
they 
 ran into them, and they 
started over, or they did 

613
00:31:13,615 --> 00:31:16,011
whatever, right? 
So yeah. 

614
00:31:16,911 --> 00:31:19,584
I, you know, Appvance has 
 been
breakthrough after breakthrough,

615
00:31:19,584 --> 00:31:22,806
lots of patents. 
It's a great company, great 

616
00:31:22,806 --> 00:31:25,671
team, and 
 huge customers, so I
can't complain. 

617
00:31:26,928 --> 00:31:29,793
Just to clarify, is this 
 based
on LLM model as well or is this 

618
00:31:29,793 --> 00:31:32,355
something different? 
Ah, some are-- Yeah, some is LLM

619
00:31:32,355 --> 00:31:34,481
and 
 some is traditional AI and
ML. 

620
00:31:34,481 --> 00:31:37,477
It's kind of a mix of both for a
lot of reasons. 

621
00:31:37,497 --> 00:31:40,837
Some things the LLM or 
 
transformer is really good at or

622
00:31:40,847 --> 00:31:46,559
frontier model, some it isn't. 
But it's a mix of all of that 

623
00:31:46,559 --> 00:31:50,045
and-- 
 but frontier models are 
used where they are appropriate 

624
00:31:50,045 --> 00:31:53,313
to use them for sure. 
And there-- And more and more of

625
00:31:53,313 --> 00:31:56,476
that 
 is replacing some of the 
older ML as the frontier models 

626
00:31:56,476 --> 00:32:00,086
get better at very 
 specific 
tasks which they might not have 

627
00:32:00,086 --> 00:32:04,163
been good at just a year ago. 
So yeah, hopefully people 
 can 

628
00:32:04,163 --> 00:32:06,248
also check it out. 
So sounds really cool, right? 

629
00:32:06,248 --> 00:32:09,504
Being able to find bugs, you 
know, 
 independently, 

630
00:32:09,504 --> 00:32:12,583
automatically, right? 
And yeah, so hopefully, it- 
 

631
00:32:12,591 --> 00:32:16,168
the software gets more quality. 
So let's maybe move on the next,

632
00:32:16,168 --> 00:32:17,418

 conversation about your book, 
right? 

633
00:32:17,897 --> 00:32:20,440
Sure. 
You've been all doing AI, you 

634
00:32:20,440 --> 00:32:24,186
know, 
 more technical stuff, 
and you finally wrote a book not

635
00:32:24,186 --> 00:32:27,028
about technology. 
It's called Joy-Success Cycle. 

636
00:32:27,188 --> 00:32:29,798
So tell us what's the background

 behind this book actually? 

637
00:32:29,951 --> 00:32:32,859
Yeah, for tho- for those 
 
actually watching, they can see 

638
00:32:32,859 --> 00:32:39,581
the Joy-Success Cycle. 
Look… People have asked me for a

639
00:32:39,581 --> 00:32:41,817
long time, 
 "Why do you have 
such high dopamine? 

640
00:32:41,817 --> 00:32:45,529
Why are you always so joyful?" 
And 
 so I began writing that 

641
00:32:45,529 --> 00:32:49,317
down and writing down a method 
to be like that. 

642
00:32:49,317 --> 00:32:54,040
And I'll tell you, the… So the 
core 
 of the book says that joy

643
00:32:54,040 --> 00:32:56,217
doesn't come after success, it 
comes before. 

644
00:32:56,847 --> 00:32:59,717
And if you have joy in 
everything you 
 do, you're more

645
00:32:59,717 --> 00:33:02,741
likely to be successful. 
Joy in everything you do 
 will 

646
00:33:02,741 --> 00:33:06,124
lead to more success. 
This is a very critical 
 

647
00:33:06,132 --> 00:33:09,141
breakthrough in understanding. 
And there's a whole chapter on 

648
00:33:09,141 --> 00:33:10,927
the 
 science that proves this 
out as well. 

649
00:33:11,197 --> 00:33:15,447
So the Joy-Success Cycle lays 
out a method 
 that allows you 

650
00:33:15,447 --> 00:33:20,293
to look at every single task you
do every single day and make it 

651
00:33:20,293 --> 00:33:22,885
a 
 joyful task, even if it's 
firing someone. 

652
00:33:22,925 --> 00:33:25,105
How do I bring joy to this 
moment? 

653
00:33:25,415 --> 00:33:28,070
And it turns out you can. 
You-- and we tell you how to do 

654
00:33:28,070 --> 00:33:31,483
that. 
And it looks at, you know, 
 

655
00:33:31,491 --> 00:33:34,755
human, natural human behavior. 
Natural human behavior is humans

656
00:33:34,755 --> 00:33:38,345

 tend to complain a lot, both 
internally and externally. 

657
00:33:38,345 --> 00:33:40,875
In fact, we complain 
 about 
everything in life. 

658
00:33:41,615 --> 00:33:45,763
We complain the moment we get 
up, 
 all the way to when we go 

659
00:33:45,763 --> 00:33:49,531
to bed, and the average person 
in the United 
 States complains

660
00:33:49,531 --> 00:33:52,469
internally and externally about 
100 times a day. 100. 

661
00:33:52,469 --> 00:33:55,909
And every time you complain, you

 take yourself further away 

662
00:33:55,909 --> 00:34:00,562
from success because you have to
dig yourself out 
 of this hole 

663
00:34:00,562 --> 00:34:03,455
of complaints, basically, which 
we call the positive quotient. 

664
00:34:03,455 --> 00:34:05,914
It goes to zero, and then you 
 
have to dig yourself out and dig

665
00:34:05,914 --> 00:34:10,351
yourself on the way back. 
So one of the things we teach 
 

666
00:34:10,360 --> 00:34:14,309
is the one-complaint-a-day rule.
And so you, tomorrow, everybody 

667
00:34:14,309 --> 00:34:18,315
on this 
 show that's listening 
or watching, you will count up 

668
00:34:18,315 --> 00:34:21,484
the number of complaints 
 you 
have, and you're gonna find it's

669
00:34:21,484 --> 00:34:24,617
60 or 100 or 110 or whatever. 
It's gonna shock you, 
 whatever

670
00:34:24,617 --> 00:34:27,235
the number is. 
You have to keep honest track. 

671
00:34:27,255 --> 00:34:28,635
And these are internal 
complaints, too. 

672
00:34:29,324 --> 00:34:31,975
And then the next day, you start
to 
 work towards the 

673
00:34:31,975 --> 00:34:34,335
one-complaint-a-day rule, where 
you can only have one. 

674
00:34:34,355 --> 00:34:37,306
And I can guarantee you're gonna
burn 
 that one up first thing 

675
00:34:37,306 --> 00:34:39,521
in the morning. 
You're gonna get out of bed and 

676
00:34:39,521 --> 00:34:41,938
 say, "Oh, my knees hurt," or, 
"The weather sucks," or 

677
00:34:41,938 --> 00:34:44,469
something. 
And then, you know, you're gonna

678
00:34:44,469 --> 00:34:46,885
hear 
 the buzzer in your head 
going, "Eh! 

679
00:34:47,725 --> 00:34:51,585
You've used up your one 
 
complaint for the entire day. 

680
00:34:51,795 --> 00:34:54,388
You have no more." 
So it's a way 
 of gamifying 

681
00:34:54,388 --> 00:34:57,467
this and getting your brain to 
start thinking, "I 
 gotta get 

682
00:34:57,467 --> 00:35:00,265
out of complaint mode. 
That is never gonna help me." 

683
00:35:00,445 --> 00:35:02,265
By the way, no one wants 
 to 
hear me complain. 

684
00:35:02,505 --> 00:35:04,747
No one. 
And it turns out very quickly 

685
00:35:04,747 --> 00:35:06,335
you don't 
 wanna hear yourself 
complain anymore. 

686
00:35:06,385 --> 00:35:08,815
You think it's a total 
 waste 
of energy, and it is. 

687
00:35:09,255 --> 00:35:12,431
And so then you start working 
towards, 
 I've gotta find joy 

688
00:35:12,431 --> 00:35:14,755
in this moment. 
I've gotta-- it's raining out. 

689
00:35:15,145 --> 00:35:17,265
I was gonna go on a bike 
 ride,
but that's okay. 

690
00:35:17,295 --> 00:35:19,784
Instead, I'm going to get this 
other 
 task done that I wasn't 

691
00:35:19,784 --> 00:35:21,665
going to do for a while, and 
isn't that great? 

692
00:35:21,845 --> 00:35:24,607
That's going to bring me joy. 
So you need to find the joy 

693
00:35:24,607 --> 00:35:26,812
moment in 
 everything rather 
than, "Oh, this is awful." 

694
00:35:26,812 --> 00:35:30,535
This is actually a positive. 
I can turn it into a positive. 

695
00:35:30,915 --> 00:35:32,315
And it's not being stupid about 
it. 

696
00:35:32,315 --> 00:35:34,285
It's like, it turns out that's 
what I do. 

697
00:35:34,325 --> 00:35:37,203
I mean, I had to write it all 
 
down and say, what do I do? 

698
00:35:37,203 --> 00:35:42,165
Why is it that I can see all of 
these 
 pain points out there 

699
00:35:42,165 --> 00:35:45,103
and things to work on and ways 
to solve them? 

700
00:35:45,113 --> 00:35:46,983
Why is it that I can do that, 
right? 

701
00:35:47,463 --> 00:35:50,233
And it's because I've got an 
open 
 mind, and I've got an 

702
00:35:50,233 --> 00:35:52,093
open mind because I'm not 
complaining all the time. 

703
00:35:52,103 --> 00:35:55,189
My mind is open and ready to, 
you 
 know, ready to go solve 

704
00:35:55,189 --> 00:35:57,793
the world's problems every 
minute of the day. 

705
00:35:58,343 --> 00:36:01,549
That is a-- that's a great place
to be, 
 and that's where I want

706
00:36:01,549 --> 00:36:04,037
everyone to be. 
So the people who've… I've been 

707
00:36:04,037 --> 00:36:08,103
 giving, you know, I do about 40
keynotes a year, and so many of 

708
00:36:08,103 --> 00:36:10,063
my keynotes 
 have been the 
Joy-Success Cycle. 

709
00:36:10,093 --> 00:36:14,266
And I have consistently gotten 

calls weeks later that it 

710
00:36:14,266 --> 00:36:18,275
changed entire teams, it changed
the work 
 environment, it 

711
00:36:18,275 --> 00:36:21,224
changed people. 
It, you know… And so, it was 

712
00:36:21,224 --> 00:36:23,233
important-- 
 It's an important 
book to publish. 

713
00:36:23,503 --> 00:36:26,989
Lastly, the timing is right. 
Because the one thing I hear 

714
00:36:26,989 --> 00:36:30,283
across 
 the board, you know, 
something like fifty percent of 

715
00:36:30,283 --> 00:36:34,369
the people 
 in the US anyway, 
believe that AI is bad, it's 

716
00:36:34,369 --> 00:36:37,173
dangerous, and they 
 don't like
AI data centers, right? 

717
00:36:37,633 --> 00:36:40,303
Well, let me start out with 
this. 

718
00:36:40,493 --> 00:36:44,693
They're wrong, right? 
And AI is not going away. 

719
00:36:45,023 --> 00:36:48,229
So how do you find the joy? 
They say, it took all 
 the joy 

720
00:36:48,229 --> 00:36:49,693
out of my life. 
Okay, stop. 

721
00:36:50,073 --> 00:36:51,693
AI didn't take the joy out of 
your life. 

722
00:36:51,693 --> 00:36:56,957
You misconstrued what your sense
of 
 purpose was, and you 

723
00:36:56,957 --> 00:36:58,353
misconstrued what was bringing 
you joy. 

724
00:36:58,363 --> 00:37:00,523
You thought that was it because 
 that's what you were doing. 

725
00:37:00,853 --> 00:37:06,431
But now we've got to look at it 
in a new era where AI is going 

726
00:37:06,431 --> 00:37:08,243
to 
 take away a lot of the 
joyless tasks. 

727
00:37:08,643 --> 00:37:10,133
And that's what you have to look
at. 

728
00:37:10,413 --> 00:37:14,400
When you really step back, 
really step 
 back, fussing 

729
00:37:14,400 --> 00:37:18,922
around for a day to fix three 
lines of code that you can't 
 

730
00:37:18,930 --> 00:37:22,703
quite get the logic right on, 
we've all done this, any of you 

731
00:37:22,703 --> 00:37:24,731
coders, you know. 
And you really, the whole day 

732
00:37:24,731 --> 00:37:26,281
goes 
 by and you go, "I got 
nothing done. 

733
00:37:26,281 --> 00:37:29,748
I can't get this little teeny, 
you know, 
 set of logic to 

734
00:37:29,748 --> 00:37:31,891
work." 
It's a, it's an if-then else 

735
00:37:31,891 --> 00:37:34,503
else else else or something. 
You know, it's one of these 

736
00:37:34,503 --> 00:37:36,529
things, 
 and the logic isn't 
working, and you, your mind 

737
00:37:36,529 --> 00:37:38,993
isn't figuring it. 
You no longer spend time doing 

738
00:37:38,993 --> 00:37:39,923
that. 
That is a waste. 

739
00:37:39,923 --> 00:37:41,503
There is a machine that does 
that. 

740
00:37:41,883 --> 00:37:44,963
And we should not spend our time

 doing anything that we don't 

741
00:37:44,963 --> 00:37:49,202
add maximum value to anymore. 
You add no value to fixing that 

742
00:37:49,202 --> 00:37:51,818
logic. 
A machine can fix that logic in 

743
00:37:51,818 --> 00:37:54,291
 one minute, literally a minute.
As long as you can describe 
 

744
00:37:54,299 --> 00:37:57,468
it, it will fix it. 
And so this is fascinating, 

745
00:37:57,468 --> 00:37:59,661
right? 
So I can guarantee you you're 

746
00:37:59,661 --> 00:38:02,483
gonna have 
 more joy because of
that, not less joy. 

747
00:38:02,793 --> 00:38:05,433
And that's what we want. 
And so this Joy-Success Cycle 
 

748
00:38:05,441 --> 00:38:08,521
hits at the right time and 
allows people to find their 

749
00:38:08,521 --> 00:38:10,743
sense of 
 purpose and where 
they can get joy. 

750
00:38:10,793 --> 00:38:13,573
Even though the work they were 

doing is being taken away from 

751
00:38:13,573 --> 00:38:16,581
them, they're doing more 
important 
 work now, work that 

752
00:38:16,581 --> 00:38:19,733
they really add value to, and 
that is very exciting. 

753
00:38:20,608 --> 00:38:24,714
Yeah, so I think you 
 said it, 
I think this is kind of the 

754
00:38:24,714 --> 00:38:27,750
right time, because I 
 think it
happened if I- from my 

755
00:38:27,750 --> 00:38:29,907
experience at least, right? 
It happened since the pandemic, 

756
00:38:29,907 --> 00:38:32,463
right? 
Where when people started to 

757
00:38:32,463 --> 00:38:35,828
feel more 
 anxiety, you know, 
more sadness, right? 

758
00:38:36,088 --> 00:38:39,563
Feeling kind of like depressed 
and 
 then so many layoffs, then

759
00:38:39,563 --> 00:38:41,648
political situation, war and all
that. 

760
00:38:41,888 --> 00:38:44,679
Now AI coming, right? 
So obviously we are in kind of 

761
00:38:44,679 --> 00:38:47,144
like, I 
 don't know, like doom 
and gloom kind of a thing, and 

762
00:38:47,144 --> 00:38:51,594
the news doesn't help as well. 
So I think maybe from 
 your 

763
00:38:51,594 --> 00:38:53,893
perspective, right? 
Because it seems like our 

764
00:38:53,893 --> 00:38:56,908
positive emotion 
 is kind of 
like eroding day by day, right? 

765
00:38:56,908 --> 00:39:00,190
So how can we actually bring 
back 
 our positive emotion 

766
00:39:00,190 --> 00:39:02,448
regardless of what is happening 
in the world? 

767
00:39:04,639 --> 00:39:06,281
Right. 
And I think The Joy-Success 
 

768
00:39:06,289 --> 00:39:09,959
Cycle lays out a, you know, lays
out a process to do that. 

769
00:39:10,369 --> 00:39:12,759
And it's only 200 pages, 
 so 
it's not a big read. 

770
00:39:12,759 --> 00:39:14,971
It's an easy read. 
It's available on Amazon 
 and 

771
00:39:14,971 --> 00:39:17,669
Barnes & Noble. 
You can order it today. 

772
00:39:17,669 --> 00:39:19,709
It comes out September 1st, 
 so
you can pre-order it. 

773
00:39:21,529 --> 00:39:24,389
You know, there's a lot 
 of 
pieces to this process. 

774
00:39:24,389 --> 00:39:30,777
For example, we have a whole 
chapter on the 
 joy killers and

775
00:39:30,777 --> 00:39:32,929
things that take away joy from 
your life. 

776
00:39:33,309 --> 00:39:37,365
By the way, this could be a 
family 
 member that you don't 

777
00:39:37,365 --> 00:39:40,279
want in your life, you didn't 
ask to be in your life. 

778
00:39:40,519 --> 00:39:43,108
Could be people at work. 
It could be work that you're 

779
00:39:43,108 --> 00:39:45,307
doing. 
It could be a variety of things 

780
00:39:45,307 --> 00:39:48,543
and how 
 you either have to 
turn-- you either have to find 

781
00:39:48,543 --> 00:39:51,449
joy in them or you have 
 to get
them out of your life, right? 

782
00:39:51,449 --> 00:39:54,545
There are things in all of our 
lives 
 that were never gonna 

783
00:39:54,545 --> 00:39:56,219
bring you joy, and I'll give you
an example. 

784
00:39:56,499 --> 00:39:59,079
You're at the office, if you 
work in an 
 office, you're at 

785
00:39:59,079 --> 00:40:02,963
the office and every time you, 
you know, go to fill your 
 

786
00:40:02,971 --> 00:40:06,469
thing with water, you know, 
Betty's there, and Betty's just 

787
00:40:06,469 --> 00:40:08,949
complaining 
 about every, "Oh, 
I hate the management. 

788
00:40:09,089 --> 00:40:10,969
I hate this person. 
I hate that. 

789
00:40:11,009 --> 00:40:13,502
I hate this." 
You know, buy 
 Betty a copy of 

790
00:40:13,502 --> 00:40:15,369
the book and bless her out of 
your life. 

791
00:40:15,479 --> 00:40:16,999
You don't need to see Betty 
anymore. 

792
00:40:17,209 --> 00:40:19,569
She's not gonna help you succeed
at all. 

793
00:40:19,889 --> 00:40:23,409
You know, all of this kind of 
 
talk of, oh, let's just talk 

794
00:40:23,419 --> 00:40:25,209
about how bad management is. 
Really? 

795
00:40:25,579 --> 00:40:28,079
Is that gonna change it somehow?
No. 

796
00:40:28,269 --> 00:40:31,835
You have two choices: to never 

participate in that talk anymore

797
00:40:31,835 --> 00:40:35,198
or-- and just do your job and do
a great 
 job and get joy from 

798
00:40:35,198 --> 00:40:37,825
it, or leave and get a job 
somewhere else where 
 maybe you

799
00:40:37,825 --> 00:40:40,249
like the management better. 
You already have two choices. 

800
00:40:40,619 --> 00:40:43,979
But the third choice of let me 
just 
 complain about them 

801
00:40:43,979 --> 00:40:47,349
doesn't allow you to attain your
highest level of success ever. 

802
00:40:47,539 --> 00:40:49,689
It brings you down. 
It brings them down. 

803
00:40:49,699 --> 00:40:50,949
It brings everyone around you 
down. 

804
00:40:50,979 --> 00:40:53,559
It pokes holes in the boat 
 
when you're all trying to cross 

805
00:40:53,559 --> 00:40:55,419
the river at the same time. 
It's just bad. 

806
00:40:55,849 --> 00:40:58,519
And so that doesn't say 
 that 
all management is good. 

807
00:40:58,539 --> 00:41:00,929
It certainly isn't. 
It just says you complaining 

808
00:41:00,929 --> 00:41:03,389
about it 
 isn't the way to deal
with it, right? 

809
00:41:03,399 --> 00:41:07,415
The way to deal with it is to 
leave 
 or to ignore it and do 

810
00:41:07,415 --> 00:41:09,089
your job. 
I mean, tho- that's it. 

811
00:41:09,099 --> 00:41:11,693
That's all there is. 
You know, so there's a… I'm 

812
00:41:11,693 --> 00:41:15,389
picking 
 on that one, but there
are a hundred examples of these 

813
00:41:15,389 --> 00:41:19,847
kinds of things, 
 right, where 
this is the stuff that happens 

814
00:41:19,847 --> 00:41:24,454
and it just takes you down. 
And once you're spiraling 
 

815
00:41:24,462 --> 00:41:27,409
downward, you can't even think. 
You look at a blank page. 

816
00:41:27,419 --> 00:41:30,479
You can't do your job. 
You waste all this time. 

817
00:41:30,739 --> 00:41:32,179
You're not moving towards 
success. 

818
00:41:32,389 --> 00:41:35,303
You're not looking at the next 
pain 
 point out there and 

819
00:41:35,303 --> 00:41:37,752
going, "Huh, I wonder if I can 
build a virtual assistant. 

820
00:41:37,752 --> 00:41:40,743
I 
 wonder if I can have AI find
all the bugs in my software. 

821
00:41:40,743 --> 00:41:43,609
I wonder if I 
 can retrofit the
Empire State Building with 

822
00:41:43,609 --> 00:41:46,129
energy-efficient window." 
Like 
 I'm thinking of those 

823
00:41:46,129 --> 00:41:48,729
things because I'm not dwelling 
down in the gutter. 

824
00:41:48,739 --> 00:41:51,921
I don't need to be down there. 
Let someone else be down there, 

825
00:41:51,921 --> 00:41:54,899
right? 
And so, you know, joy breeds 
 

826
00:41:54,907 --> 00:41:58,281
success, which gives you more 
joy, which gives you more 

827
00:41:58,281 --> 00:42:00,253
success. 
You need to have joy every 

828
00:42:00,253 --> 00:42:01,959
minute 
 in every task in 
everything you do. 

829
00:42:02,209 --> 00:42:04,571
Forget Betty at the water 
cooler, and 
 my apologies to 

830
00:42:04,571 --> 00:42:06,634
someone named Betty. 
I am not-- I just grabbed 
 the 

831
00:42:06,634 --> 00:42:08,269
name out of the air. 
It's not you. 

832
00:42:09,888 --> 00:42:13,408
So, another thing that I think 

from my experience, is like the 

833
00:42:13,408 --> 00:42:17,378
source of joy killer is actually

 news and social media, right? 

834
00:42:17,378 --> 00:42:19,828
So if you're always following 
the news. 

835
00:42:20,249 --> 00:42:23,479
Yeah, doom scrolling. 
Don't doom scroll. 

836
00:42:24,127 --> 00:42:26,555
What we deal with that a little 
bit 
 and, actually we deal with

837
00:42:26,555 --> 00:42:29,667
it quite well is you're welcome 
to hear the news. 

838
00:42:29,667 --> 00:42:32,501
I'm not telling you to never 
listen 
 to the news and never… 

839
00:42:32,501 --> 00:42:35,119
However, you have to stop 
worrying about 
 those things 

840
00:42:35,119 --> 00:42:39,921
which you can't impact. 
Spend no energy on it, right? 

841
00:42:39,931 --> 00:42:42,685
So today you open the paper and 
you 
 go, "Oh, there's a war and

842
00:42:42,685 --> 00:42:45,663
people are getting bombed, and 
people are 
 getting…" Unless 

843
00:42:45,663 --> 00:42:49,315
you're going to go there and 
solve it, or you're going to 
 

844
00:42:49,323 --> 00:42:51,571
run for president or I don't 
know, right? 

845
00:42:51,951 --> 00:42:54,031
You actually have no impact on 
that. 

846
00:42:54,351 --> 00:42:56,401
You can note it. 
You're educated on it. 

847
00:42:56,401 --> 00:42:59,801
You wanna be educated on world 

politics, world-- that's great. 

848
00:43:00,281 --> 00:43:02,541
But it-- you can't worry about 
it. 

849
00:43:02,641 --> 00:43:06,949
And it's the worrying about it 
that 
 puts people in bed in a 

850
00:43:06,949 --> 00:43:09,927
depressed state. 
I have met more people say, "Oh,

851
00:43:09,927 --> 00:43:12,903

 because of this, I can't even 
get out of bed." 

852
00:43:12,903 --> 00:43:17,036
I said, that, that's going on, 

you know, twelve thousand miles 

853
00:43:17,036 --> 00:43:19,631
away, and you can't have any 
impact on it. 

854
00:43:19,631 --> 00:43:20,929
"But I just can't get out of 
bed." 

855
00:43:20,929 --> 00:43:23,111
Okay. 
So it's having an impact on 
 

856
00:43:23,119 --> 00:43:25,981
you where you're no longer going
to be successful today. 

857
00:43:26,541 --> 00:43:29,761
And if that's what you choose to
do, 
 I, you know, that is your 

858
00:43:29,761 --> 00:43:31,963
life choice. 
It's not the choice I choose to 

859
00:43:31,963 --> 00:43:33,741
make. 
I wanna be educated on it. 

860
00:43:34,091 --> 00:43:36,878
I can't fix it. 
I don't have the power to fix 

861
00:43:36,878 --> 00:43:38,626
it. 
I don't have the power to 
 

862
00:43:38,634 --> 00:43:41,959
start wars or end wars. 
But I wanna be educated on it, 

863
00:43:41,959 --> 00:43:44,191
but I can't 
 get depressed 
about it because… So stop 

864
00:43:44,211 --> 00:43:46,391
worrying about the things you 
can't fix. 

865
00:43:46,721 --> 00:43:49,141
Do not spend any energy on 
 the
things you can't fix. 

866
00:43:49,401 --> 00:43:50,841
And that doesn't have to be just
a war. 

867
00:43:50,841 --> 00:43:52,980
It could be something at work. 
It could be something in your 

868
00:43:52,980 --> 00:43:54,411
family. 
It could be some religious 

869
00:43:54,411 --> 00:43:56,635
thing. 
It could be a tree fell 
 that 

870
00:43:56,635 --> 00:43:59,225
you loved so much. 
"Oh my God, it's just-- it's 

871
00:43:59,225 --> 00:44:00,881
ruined 
 my life 'cause I love 
that tree." 

872
00:44:01,041 --> 00:44:04,851
It ruined your… It's a tree. 
They all fall eventually, right?

873
00:44:04,921 --> 00:44:08,011
I'm-- I don't mean to be mean 
 
about it, but, like, you can't 

874
00:44:08,021 --> 00:44:11,434
have any emotion over that. 
That isn't the place to sort of 

875
00:44:11,434 --> 00:44:14,771
 waste your time if you wanna be
the most successful you can be. 

876
00:44:15,311 --> 00:44:18,917
'Cause every minute you spend 
crying 
 about the tree is a 

877
00:44:18,917 --> 00:44:22,033
minute that's not being-- that 
not moving you 
 towards the, 

878
00:44:22,033 --> 00:44:25,181
your maximum success. 
By the way, your maximum success

879
00:44:25,181 --> 00:44:28,145

 could be money, obviously, 
could be career, could be 

880
00:44:28,145 --> 00:44:30,561
family, could 
 be religion, 
could be sports. 

881
00:44:30,561 --> 00:44:33,031
I don't know what it is, right? 
So whatever, however you 
 

882
00:44:33,039 --> 00:44:37,497
define success in your life. 
Lots of people define it as 
 a 

883
00:44:37,497 --> 00:44:40,129
certain monetary freedom. 
I get that, and then that's 
 

884
00:44:40,137 --> 00:44:42,757
the most common, right? 
I wanna get to a point where I, 

885
00:44:42,757 --> 00:44:44,411
you 
 know, great, where I can 
retire early. 

886
00:44:44,411 --> 00:44:45,941
I don't have to work. 
I, you know, whatever. 

887
00:44:46,391 --> 00:44:48,154
Good. 
You define it the way you wanna 

888
00:44:48,154 --> 00:44:50,917
define it. 
Every minute you spend doing 
 

889
00:44:50,925 --> 00:44:54,155
something negative is a minute 
that doesn't move you towards 

890
00:44:54,155 --> 00:44:56,321
that, and 
 you will never get 
that time back. 

891
00:44:57,771 --> 00:45:00,801
I spent three days just 
 
worrying about a war. 

892
00:45:01,451 --> 00:45:04,366
That's three days you can never 
get 
 back, and you didn't 

893
00:45:04,366 --> 00:45:08,386
impact the war. 
I spent three days protesting 
 

894
00:45:08,394 --> 00:45:11,821
against this data center. 
Oh, okay. 

895
00:45:11,821 --> 00:45:14,021
Well, the data center 
 will get
built somewhere. 

896
00:45:14,391 --> 00:45:17,094
You won't have had an impact. 
It might not get built in your 

897
00:45:17,094 --> 00:45:18,341
town, 
 but it's gonna get built
somewhere. 

898
00:45:18,351 --> 00:45:21,989
I guarantee it. 
And that's three days you won't 

899
00:45:21,989 --> 00:45:24,167
get back. 
Like you can't move towards your

900
00:45:24,167 --> 00:45:26,044
success. 
And, you know, everybody's 
 got

901
00:45:26,044 --> 00:45:27,891
their own drive. 
Maybe their sense of purpose is 

902
00:45:27,891 --> 00:45:30,443
to 
 protest, in which case, all
right, I guess you should go do 

903
00:45:30,443 --> 00:45:33,071
that, right? 
But, you know, the book just 

904
00:45:33,071 --> 00:45:36,489
tries 
 to say if you wanna be 
the most successful, you have to

905
00:45:36,489 --> 00:45:39,333
push a lot of 
 that stuff out 
of your life, 'cause you only 

906
00:45:39,333 --> 00:45:43,397
get so many hours a day. 
And a lot of us spend those 

907
00:45:43,397 --> 00:45:46,663
hours 
 complaining, you know, 
bitching, moaning, arguing, all 

908
00:45:46,663 --> 00:45:50,948
kinds of negative stuff. 
And then weeks go by and you 
 

909
00:45:50,956 --> 00:45:52,703
go, "I didn't get to accomplish 
a thing." 

910
00:45:52,703 --> 00:45:55,319
Of course you didn't. 
I could've told you that. 

911
00:45:55,679 --> 00:45:58,519
You can't accomplish anything. 
You're down in the gutter. 

912
00:45:58,939 --> 00:46:01,499
You know, don't do it. 
Anyway, obviously, 200 pages 
 

913
00:46:01,507 --> 00:46:04,619
talks about this in great detail
and gives a great method. 

914
00:46:05,879 --> 00:46:07,449
People have bought it for their 
teams. 

915
00:46:08,489 --> 00:46:11,319
We had draft versions 
 that I 
used with teams. 

916
00:46:12,339 --> 00:46:15,639
It's game-changing for teams. 
We've watched sales teams, you 

917
00:46:15,639 --> 00:46:18,121
know, 
 increase their 
productivity almost overnight by

918
00:46:18,121 --> 00:46:21,200
following this method. 
So it is coming at the right 

919
00:46:21,200 --> 00:46:24,672
time 
 where AI and other things
have really impacted people's 

920
00:46:24,672 --> 00:46:27,642
psyche. 
And we're gonna pull you out of 

921
00:46:27,642 --> 00:46:31,519
that 
 and move you forward and 
I hope make you rich with 

922
00:46:31,519 --> 00:46:33,794
success, whatever that means. 
Yeah. 

923
00:46:34,264 --> 00:46:36,750
I think it's a great advice, 
 
right, to focus on really what 

924
00:46:36,750 --> 00:46:38,939
we can control, right? 
Obviously, if we cannot control,

925
00:46:38,939 --> 00:46:40,454

 we don't care so much about 
it. 

926
00:46:40,454 --> 00:46:43,454
I think if we dwell on it, I 
 
think we waste so much time. 

927
00:46:43,604 --> 00:46:44,289
Yeah. 
Yep. 

928
00:46:44,304 --> 00:46:47,494
And I like the, I think I'd like

 to ask you the next question. 

929
00:46:47,604 --> 00:46:49,364
You mentioned a few times about 
purpose. 

930
00:46:49,414 --> 00:46:52,456
And there's this, you know, like
one 
 line in your book that I 

931
00:46:52,456 --> 00:46:56,282
really like, like purpose as the
foundation and 
 curiosity as 

932
00:46:56,282 --> 00:46:59,674
your stepping stone, right? 
So tell us about this concept 
 

933
00:46:59,682 --> 00:47:02,341
because I think some people may 
not even know what's their 

934
00:47:02,341 --> 00:47:04,469
purpose. 
They'll just live in the motion,

935
00:47:04,469 --> 00:47:07,831
right? 
Curiosity is your friend, right?

936
00:47:08,011 --> 00:47:10,191
I think, when we're curious, we 
learn. 

937
00:47:10,411 --> 00:47:13,031
And when we learn, we find 
 
pain points we can solve. 

938
00:47:13,271 --> 00:47:15,891
And when we learn more, 
 we try
to solve them. 

939
00:47:16,921 --> 00:47:20,221
You know, the most successful 
people, 
 I-- you know, Elon 

940
00:47:20,221 --> 00:47:23,697
Musk, you can like him or 
dislike him, but he's a 

941
00:47:23,697 --> 00:47:25,749
trillionaire. 
So give or take, maybe a little 

942
00:47:25,749 --> 00:47:27,949
less now. 
But the point is he's 
 curious 

943
00:47:27,949 --> 00:47:30,026
all the time. 
He's curious about, "Huh, I 

944
00:47:30,026 --> 00:47:32,811
wonder 
 if I can make rockets 
way, way, way cheaper." 

945
00:47:32,811 --> 00:47:35,371
Nobody ever bothered 
 to really
think about that. 

946
00:47:35,381 --> 00:47:37,820
They just got the government 
contract 
 and built it to the 

947
00:47:37,820 --> 00:47:39,524
contract. 
And if the price went up, there 

948
00:47:39,524 --> 00:47:41,961
was 
 more margin, and then, you
know, there's more money for 

949
00:47:41,961 --> 00:47:43,251
everybody. 
That was good, more profit. 

950
00:47:43,621 --> 00:47:48,221
So I think, you know, someone 
 
rethinking these fields is 

951
00:47:48,221 --> 00:47:51,137
fantastic. 
And Elon, if nothing else, is 

952
00:47:51,137 --> 00:47:54,209
curious. 
You know, can I build a car out 

953
00:47:54,209 --> 00:47:57,847
of 
 existing batteries where I 
don't have to make brand-new 

954
00:47:57,847 --> 00:48:00,241
batteries? 
Can I build rockets cheaply? 

955
00:48:00,971 --> 00:48:03,475
Can I provide internet by 
putting 
 thousands of 

956
00:48:03,475 --> 00:48:05,501
satellites up? 
Nobody's ever done that before. 

957
00:48:05,601 --> 00:48:08,291
Is it even possible? 
Well, if you drive the launch 
 

958
00:48:08,299 --> 00:48:10,856
cost down, it's possible. 
So staying curious is what 
 

959
00:48:10,864 --> 00:48:13,911
keeps your mind open and allows 
you to learn your whole life. 

960
00:48:14,131 --> 00:48:17,259
So many people, they leave 
school, and 
 they go, well, I'm

961
00:48:17,259 --> 00:48:19,231
done learning now. 
Well that sucks. 

962
00:48:19,681 --> 00:48:22,046
What are you gonna do? 
I mean, you know, I 
 love 

963
00:48:22,046 --> 00:48:25,023
learning every day. 
I read voraciously, and I-- you 

964
00:48:25,023 --> 00:48:27,621
know, 
 really information in 
our field, right? 

965
00:48:27,651 --> 00:48:30,341
I need to know what's going 
 on
and who's doing it. 

966
00:48:30,341 --> 00:48:32,231
It's hard to keep up 
 with 
everything going on. 

967
00:48:33,081 --> 00:48:37,591
But stay curious on everything 

and, and you will continue to 

968
00:48:37,591 --> 00:48:40,026
learn throughout your life. 
Yeah. 

969
00:48:40,496 --> 00:48:43,086
So definitely curiosity, 
 
follow your curiosity, right? 

970
00:48:43,096 --> 00:48:46,161
Even if you cannot find your 
purpose 
 now, I think maybe the

971
00:48:46,161 --> 00:48:47,876
curiosity will lead you to 
there, right? 

972
00:48:48,161 --> 00:48:49,776
That's right. 
Yeah. 

973
00:48:50,236 --> 00:48:53,302
So I think another thing that is
quite 
 kind of like fun in your

974
00:48:53,302 --> 00:48:55,926
book, one of the chapter is 
called The Joy of To-Do Lists. 

975
00:48:56,306 --> 00:48:59,556
I think many people may not feel

 joy when they see their to-do 

976
00:48:59,556 --> 00:49:02,653
list. 
So us why this to-do list 
 is 

977
00:49:02,653 --> 00:49:06,523
powerful for your joy. 
Yeah, so I do to-do lists every 

978
00:49:06,523 --> 00:49:08,679
day. 
I do them by hand. 

979
00:49:08,999 --> 00:49:12,829
And to-do lists are great 
 for 
a lot of reasons. 

980
00:49:12,839 --> 00:49:15,579
One, it tells you what you gotta
do 
 today or the next day or 

981
00:49:15,579 --> 00:49:17,073
whenever you've done it, if 
you've done it the night 
 

982
00:49:17,081 --> 00:49:18,039
before, you did it in the 
morning. 

983
00:49:19,359 --> 00:49:22,419
The other thing it does is it 
gives 
 you small wins during 

984
00:49:22,419 --> 00:49:24,614
the day. 
You get to literally cross 

985
00:49:24,614 --> 00:49:26,939
something 
 off or check it off 
when it's done. 

986
00:49:27,489 --> 00:49:30,679
You go, "So I have to 
 prepare 
for this podcast. 

987
00:49:31,179 --> 00:49:33,199
Check." 
I go, "Win!" 

988
00:49:33,199 --> 00:49:36,577
Small wins are great. 
You need small wins all during 

989
00:49:36,577 --> 00:49:38,265
the day. 
And by the way, every time you 


990
00:49:38,273 --> 00:49:40,659
check something off the list, 
it's a little dopamine hit, and 

991
00:49:40,659 --> 00:49:42,779
it gives 
 you more energy to 
keep going. 

992
00:49:43,689 --> 00:49:46,133
And when you don't make a list, 
you're 
 just wandering through 

993
00:49:46,133 --> 00:49:49,999
the day just, you know, dealing 
with what comes, 
 and that's 

994
00:49:49,999 --> 00:49:53,125
just not as satisfying. 
So the other thing is writing a 

995
00:49:53,125 --> 00:49:56,341
 list with a pen is a great 
thing, and I write lists with 

996
00:49:56,341 --> 00:49:58,343
pens. 
And I highly recommend 
 doing 

997
00:49:58,343 --> 00:50:01,053
that, pen or pencil. 
And it's much better than 

998
00:50:01,053 --> 00:50:03,925
keeping 
 lists on a computer, 
which I tend to never get to and

999
00:50:03,925 --> 00:50:06,479
never do. 
So write them every day. 

1000
00:50:06,799 --> 00:50:09,009
Do your to-do list. 
I don't get through my 
 to-do 

1001
00:50:09,009 --> 00:50:10,776
list every day. 
Some things on that to-do list 


1002
00:50:10,784 --> 00:50:13,579
are a month kind of a thing. 
They're gonna take a lot longer.

1003
00:50:13,579 --> 00:50:15,529
That's okay. 
But I know it's there. 

1004
00:50:15,529 --> 00:50:18,314
I see it every day. 
I work out a little bit 
 to try

1005
00:50:18,314 --> 00:50:20,420
to make progress. 
Yeah. 

1006
00:50:20,890 --> 00:50:24,872
So maybe you said that you have 
been 
 in kind of like this joy,

1007
00:50:24,872 --> 00:50:27,130
I don't know, like journey for 
many years. 

1008
00:50:27,490 --> 00:50:30,342
Maybe after writing your book or
after 
 spreading this in your 

1009
00:50:30,342 --> 00:50:32,451
keynotes, are there some 
inspiring stories that you 
 can

1010
00:50:32,451 --> 00:50:35,665
share with us, you know, about, 
you know, some people who have 

1011
00:50:35,665 --> 00:50:37,940
changed, used 
 your methodology
and really succeed? 

1012
00:50:38,503 --> 00:50:41,157
Yeah, you know, there was a-- 
this great 
 sales 

1013
00:50:41,157 --> 00:50:44,496
reorganization that happened in 
a very big company that I came 

1014
00:50:44,496 --> 00:50:47,273
in and 
 spoke to and spoke The 
Joy-Success Cycle. 

1015
00:50:47,273 --> 00:50:51,333
It was my keynote on that. 
They specifically asked me to 

1016
00:50:51,333 --> 00:50:55,119
come, 
 because the mess they 
had was they had reorganized and

1017
00:50:55,119 --> 00:50:57,715
everybody was mad. 
The salespeople didn't like 
 

1018
00:50:57,723 --> 00:51:01,090
the new groups they were in. 
They didn't like anything about 

1019
00:51:01,090 --> 00:51:03,050
anything. 
And all they were doing was 

1020
00:51:03,050 --> 00:51:05,073
moaning 
 every single day 
rather than selling. 

1021
00:51:05,383 --> 00:51:07,443
And, you know, selling 
 
attitude is very important. 

1022
00:51:07,443 --> 00:51:09,813
So if your attitude isn't 
 
good, you don't sell anything. 

1023
00:51:10,533 --> 00:51:14,267
And sure enough, after The 
Joy-Success 
 Cycle, and I 

1024
00:51:14,267 --> 00:51:17,516
customized some things in my-- I
customize my keynotes all the 

1025
00:51:17,516 --> 00:51:20,285
time. 
So for them, I said, "Let's say 

1026
00:51:20,285 --> 00:51:23,803
 there was a reorganization," 
which I know there was, and I 

1027
00:51:23,803 --> 00:51:26,743
know it's very 
 easy to be 
negative on all of this. 

1028
00:51:26,843 --> 00:51:29,201
"Oh, I liked my other team. 
 
I worked… Da-da-da." 

1029
00:51:29,201 --> 00:51:30,693
Okay, let's look at the 
positives. 

1030
00:51:30,733 --> 00:51:32,603
First of all, you knew 
everything there 
 was to know 

1031
00:51:32,603 --> 00:51:34,933
about your other team members. 
There was nothing new to learn. 

1032
00:51:35,223 --> 00:51:38,649
Here's a whole new group of 
twenty-eight 
 people you don't 

1033
00:51:38,649 --> 00:51:41,233
know anything about that you can
learn from. 

1034
00:51:41,423 --> 00:51:44,142
There's twenty-eight people that
you 
 can go and have a drink 

1035
00:51:44,142 --> 00:51:47,547
with or a coffee with or a tea 
with or whatever 
 it is, or a 

1036
00:51:47,547 --> 00:51:50,111
lunch with, right? 
This is a whole new learning 
 

1037
00:51:50,119 --> 00:51:53,213
opportunity for you where you 
can open your mind, be curious 

1038
00:51:53,213 --> 00:51:55,679
about them 
 and their 
experiences, and probably learn 

1039
00:51:55,679 --> 00:51:59,103
a whole new set of experiences, 
 whole new set of skills, right?

1040
00:51:59,103 --> 00:52:02,123
And when you look at it that 
way, 
 all of a sudden this is, 

1041
00:52:02,123 --> 00:52:05,419
what a great opportunity, rather
than, "I 
 hate this, I wanna go

1042
00:52:05,419 --> 00:52:07,973
back to my old group," which is 
what everybody said. 

1043
00:52:07,973 --> 00:52:10,155
"I hate it, I wanna go back to 
my old 
 group." 

1044
00:52:10,155 --> 00:52:14,199
And the second thing is, when 
you come in with that kind of 

1045
00:52:14,199 --> 00:52:18,207
mindset, 
 then what's great 
about it is that you go out to 

1046
00:52:18,207 --> 00:52:20,063
sell and you've got a 
 great 
selling attitude 'Cause you're 

1047
00:52:20,063 --> 00:52:21,423
excited to be with this new 
group. 

1048
00:52:21,453 --> 00:52:23,143
You still love your old group, 
but 
 you're excited to be with 

1049
00:52:23,143 --> 00:52:25,723
the new group. 
So that's an example of people 

1050
00:52:25,723 --> 00:52:29,639
who 
 called me a few weeks 
later and said, you know, not 

1051
00:52:29,639 --> 00:52:32,291
everybody picked it up, but 
 
those who did are gonna be here 

1052
00:52:32,291 --> 00:52:35,513
a long time and they're excited 
about it, and 
 they stopped all

1053
00:52:35,513 --> 00:52:38,963
the water cooler talk and it 
changed their entire attitude. 

1054
00:52:40,186 --> 00:52:42,392
Right. 
So Kevin, I think it's 
 been a 

1055
00:52:42,392 --> 00:52:44,466
great things. 
Any things that you think, can 

1056
00:52:44,466 --> 00:52:47,322
be also 
 shared by you, like 
before we wrap up to the last 

1057
00:52:47,322 --> 00:52:51,387
questions that I have? 
No, I think we covered a lot 

1058
00:52:51,387 --> 00:52:54,385
today. 
All right, so in that case, I'll

1059
00:52:54,385 --> 00:52:57,078

 ask you this one last question
that I always ask in my podcast.

1060
00:52:57,078 --> 00:52:58,978
It's called the three 
 
technical leadership wisdom. 

1061
00:52:59,028 --> 00:53:01,368
Just think of it like advice you
wanna 
 give to the listeners to

1062
00:53:01,368 --> 00:53:04,539
wrap up. 
Well, the advice, we 
 probably 

1063
00:53:04,539 --> 00:53:07,858
covered all of it. 
One, use AI all the time, 
 

1064
00:53:07,866 --> 00:53:11,189
period, full stop, done. 
That's at the leadership level, 

1065
00:53:11,189 --> 00:53:13,604
 it's at the coding level, and 
it's everywhere else. 

1066
00:53:14,354 --> 00:53:17,714
If you're not using AI five 
times an 
 hour, you are behind 

1067
00:53:17,714 --> 00:53:19,554
your competition. 
It's really important. 

1068
00:53:19,874 --> 00:53:21,514
And, you know, listen to that, 
right? 

1069
00:53:21,514 --> 00:53:25,508
It's really, critical. 
You know, the second thing is 
 

1070
00:53:25,516 --> 00:53:27,174
that AI isn't taking any joy 
away. 

1071
00:53:27,174 --> 00:53:29,084
You thought it was, 
 but trust 
me, it isn't. 

1072
00:53:29,594 --> 00:53:31,934
Buy the book. 
It'll take you through a method 

1073
00:53:31,934 --> 00:53:35,786
that 
 I guarantee you, you and 
your workers are gonna be far 

1074
00:53:35,786 --> 00:53:39,191
more joyful about. 
And lastly, this is the best 

1075
00:53:39,191 --> 00:53:41,354
time 
 to be alive in technology
ever. 

1076
00:53:41,664 --> 00:53:45,428
We are able to achieve and write
more 
 and produce more 

1077
00:53:45,428 --> 00:53:48,454
incredible output than we've 
ever been able to do in our 

1078
00:53:48,454 --> 00:53:50,274
lives. 
It's unbelievable. 

1079
00:53:50,454 --> 00:53:52,604
And so this isn't the 
 worst 
time to be in tech. 

1080
00:53:52,904 --> 00:53:54,634
It's the best time to be in 
tech. 

1081
00:53:54,644 --> 00:53:56,574
And it's always how you look at 
it. 

1082
00:53:56,864 --> 00:54:00,148
And I know some people are gonna
look at 
 this and go, "Oh, you 

1083
00:54:00,148 --> 00:54:01,878
know, it's change. 
I don't like change. 

1084
00:54:01,878 --> 00:54:05,310
I don't…" Okay, this 
 is the 
best time to ever be in this 

1085
00:54:05,310 --> 00:54:07,072
field. 
You could not have come at a 

1086
00:54:07,072 --> 00:54:09,774
better time. 
And so how lucky you are. 

1087
00:54:11,353 --> 00:54:12,533
Wow, I think it's quite 
inspiring, right? 

1088
00:54:12,533 --> 00:54:15,437
So I think the best time ever in
the 
 tech, if you always see it

1089
00:54:15,437 --> 00:54:17,833
from the positive side, I think 
you can really 
 feel that this 

1090
00:54:17,833 --> 00:54:20,943
is the really the best time ever
in the technology world, right? 

1091
00:54:20,943 --> 00:54:23,565
Where things are kind of like 
 
being invented all the time, 

1092
00:54:23,565 --> 00:54:24,353
right? 
Every day. 

1093
00:54:24,763 --> 00:54:27,063
So Kevin, if people love this 
 
conversation, they wanna reach 

1094
00:54:27,063 --> 00:54:29,926
out to you, find more about your
resources, your 
 books, is 

1095
00:54:29,926 --> 00:54:34,702
there a place they can find you?
Yeah, my website is 

1096
00:54:34,702 --> 00:54:39,714
kevinsurace.com, and 
 the book 
website is joysuccesscycle.com. 

1097
00:54:40,777 --> 00:54:41,677
Right. 
All right. 

1098
00:54:41,677 --> 00:54:42,817
Thank you so much for your time 
today. 

1099
00:54:42,817 --> 00:54:45,356
I hope people learn a thing or 
two 
 about finding their joy, 

1100
00:54:45,356 --> 00:54:47,247
right? 
And hopefully that leads 
 them 

1101
00:54:47,247 --> 00:54:50,029
to their success. 
So thanks again for the time 

1102
00:54:50,029 --> 00:54:51,514
today. 
Thanks for having me.

