1
00:00:00,120 --> 00:00:02,800
Creating code has become 
incredibly easy. 

2
00:00:02,840 --> 00:00:06,400
You ask something to a magical 
box and the output is code. 

3
00:00:06,640 --> 00:00:08,720
Engineering has not become 
easier. 

4
00:00:08,800 --> 00:00:12,360
Creating code has become easier.
So yes, we can engineer more, 

5
00:00:12,440 --> 00:00:14,840
but engineering is still the 
same challenge. 

6
00:00:14,840 --> 00:00:18,160
What you know necessarily is not
as valuable as it used to be 

7
00:00:18,160 --> 00:00:19,960
because you can look up so much 
more. 

8
00:00:20,080 --> 00:00:22,800
It is easily accessible 
knowledge nowadays. 

9
00:00:23,080 --> 00:00:25,840
So also how you behave and how 
you look up is a lot more 

10
00:00:25,840 --> 00:00:28,520
valuable than it used to be. 
Do you stay for the financial 

11
00:00:28,520 --> 00:00:31,840
aspect regardless of the 
toxicity that you experience or 

12
00:00:31,960 --> 00:00:35,120
do you remove yourself from that
position, therefore giving away 

13
00:00:35,120 --> 00:00:36,960
the gold but taking off the 
handcuffs? 

14
00:00:37,080 --> 00:00:39,800
You have to decide. 
I have to do the things that 

15
00:00:39,800 --> 00:00:42,280
give me the most energy, 
otherwise it is not going to be 

16
00:00:42,280 --> 00:00:44,960
sustainable if I don't enjoy it 
anymore. 

17
00:00:45,040 --> 00:00:47,640
The whole thing like a House of 
Cards, just it crumbles. 

18
00:00:48,000 --> 00:00:51,120
Yes, Q&A time, I have my 
questions. 

19
00:00:51,200 --> 00:00:59,040
Let's do this now. 
How should one navigate a 

20
00:00:59,040 --> 00:01:02,240
corporate environment that is 
resistant to adopting new 

21
00:01:02,240 --> 00:01:06,640
technologies or insisting on 
sticking strictly to legacy 

22
00:01:06,640 --> 00:01:10,680
slash mainstream stacks? 
Yeah, this is really hard, 

23
00:01:10,680 --> 00:01:13,200
right? 
Because you want to innovate as 

24
00:01:13,200 --> 00:01:17,080
part of a bigger organization. 
But in essence, innovation might

25
00:01:17,080 --> 00:01:19,200
not be what the big organization
needs. 

26
00:01:19,520 --> 00:01:23,240
They might need stability and 
they might need reliability, and

27
00:01:23,240 --> 00:01:26,240
typically with stuff that they 
already have in production, 

28
00:01:26,720 --> 00:01:32,800
which can still be legacy or 
kind of proven technologies is 

29
00:01:32,800 --> 00:01:34,720
the safe option for an 
organization. 

30
00:01:35,080 --> 00:01:37,120
So if you want to experiment, 
where do you go? 

31
00:01:37,520 --> 00:01:39,360
Typically those big 
organizations, they have 

32
00:01:39,360 --> 00:01:42,840
experimentation departments 
where you can experiment with 

33
00:01:42,840 --> 00:01:46,720
new technologies and once you 
have shown results compared to 

34
00:01:46,720 --> 00:01:51,360
older technologies or what the 
new technology offers, then you 

35
00:01:51,360 --> 00:01:53,880
might be able to roll it out 
throughout the organization. 

36
00:01:54,480 --> 00:01:58,640
In essence, when something new 
pops up like CHA, GBT or Claude 

37
00:01:58,640 --> 00:02:01,360
Code, for example, there are 
people that are trailblazing. 

38
00:02:01,600 --> 00:02:03,440
So how can you be one of those 
people? 

39
00:02:03,840 --> 00:02:06,720
Typically they are the people 
that are more senior, sometimes 

40
00:02:06,720 --> 00:02:10,240
even staff, and that are in 
departments that are responsible

41
00:02:10,240 --> 00:02:13,040
for that. 
I don't feel like if you are in 

42
00:02:13,040 --> 00:02:16,160
a product team and responsible 
for delivery, you might not get 

43
00:02:16,160 --> 00:02:18,840
much room for experimentation 
for new tooling. 

44
00:02:19,240 --> 00:02:22,880
So if you're not in that 
department specifically, find 

45
00:02:22,880 --> 00:02:26,240
them, find the people that are 
doing that and learn from them 

46
00:02:26,720 --> 00:02:30,320
or join them. 
That's one that is with 

47
00:02:30,320 --> 00:02:33,400
specifically the example of Gen.
AI for example. 

48
00:02:33,920 --> 00:02:38,440
But when it comes to moving from
Java to Kotlin, or from Java to 

49
00:02:38,440 --> 00:02:43,120
Go or from Kotlin to Go, it can 
be that in the end you have to 

50
00:02:43,120 --> 00:02:46,360
agree to disagree where you 
think something is better but 

51
00:02:46,360 --> 00:02:49,520
the organization doesn't agree. 
And then either you stay in the 

52
00:02:49,520 --> 00:02:53,040
organization or you find 
yourself a start up where 

53
00:02:53,040 --> 00:02:56,480
experimentation is just goes a 
little bit more hand in hand 

54
00:02:56,840 --> 00:03:00,640
with the culture and you can 
afford to take more risk because

55
00:03:00,640 --> 00:03:03,000
taking risk also comes with big 
rewards. 

56
00:03:03,440 --> 00:03:05,960
And some bigger organizations, 
they do not have to take the 

57
00:03:05,960 --> 00:03:09,800
risk, so they don't take it. 
It really depends on what 

58
00:03:09,800 --> 00:03:14,640
environment you are in. 
So it can be really frustrating 

59
00:03:14,920 --> 00:03:17,200
if you want to work with a 
specific technology and you're 

60
00:03:17,200 --> 00:03:20,880
not allowed in the organization,
so you have to make a choice. 

61
00:03:20,880 --> 00:03:25,720
Is the frustration for you big 
enough to look outwards or can 

62
00:03:25,720 --> 00:03:28,800
you actually work with those 
newer technologies in hackathon 

63
00:03:28,800 --> 00:03:31,840
days that you get or outside of 
your work in the personal 

64
00:03:31,840 --> 00:03:34,600
projects that you can build? 
It really depends on your 

65
00:03:34,600 --> 00:03:37,760
context, but you have to make a 
decision in the end. 

66
00:03:37,760 --> 00:03:41,320
If the organization does not 
move and you have tried, you've 

67
00:03:41,320 --> 00:03:44,560
talked to people, you understand
the organization, you understand

68
00:03:44,560 --> 00:03:48,320
how this might have benefits, 
but you cannot get the 

69
00:03:48,320 --> 00:03:50,920
organization to move, then you 
have to decide. 

70
00:03:51,360 --> 00:03:55,520
I will say with AI tooling 
nowadays, it is much more 

71
00:03:55,520 --> 00:03:58,640
possible to modernize from 
certain technologies. 

72
00:03:59,120 --> 00:04:00,880
So you can also play the cost 
route. 

73
00:04:01,280 --> 00:04:04,480
If you're saying this legacy 
Oracle infrastructure that we 

74
00:04:04,480 --> 00:04:06,960
have, yes, we are quite 
dependent on it. 

75
00:04:06,960 --> 00:04:10,680
But have you looked at the 
licensing costs and we can 

76
00:04:10,680 --> 00:04:13,680
modernize and I've shown in a 
little small proof of concept 

77
00:04:13,680 --> 00:04:17,160
that through this tooling we can
modernize to an existing 

78
00:04:17,440 --> 00:04:21,160
language that we already have. 
Can we actually do this? 

79
00:04:21,160 --> 00:04:24,640
Because in the end, you have a 
business case and people when it

80
00:04:24,720 --> 00:04:26,600
comes to money, all of a sudden 
they listen. 

81
00:04:26,920 --> 00:04:31,320
So the cost saving aspect for 
modernizing might be the route 

82
00:04:31,320 --> 00:04:34,200
to go. 
If it is literally one language 

83
00:04:34,200 --> 00:04:37,200
to another and there is no 
business case, there is no cost 

84
00:04:37,200 --> 00:04:39,240
savings, then that's a very hard
1. 

85
00:04:39,600 --> 00:04:42,880
So think of what your use case 
is before having those 

86
00:04:42,880 --> 00:04:45,360
conversations. 
See if there is an angle and if 

87
00:04:45,360 --> 00:04:48,840
there is not, make a decision. 
How can I build mental 

88
00:04:48,840 --> 00:04:52,000
resilience and avoid 
internalizing negativity when 

89
00:04:52,000 --> 00:04:55,920
working in a toxic team 
environment or with a toxic 

90
00:04:55,920 --> 00:05:00,640
manager? 
Toxic relationships at work? 

91
00:05:01,640 --> 00:05:04,200
I mean in essence, what do you 
do when you have a toxic friend?

92
00:05:05,160 --> 00:05:09,200
You can only go so far in 
dealing with toxic behaviour. 

93
00:05:09,800 --> 00:05:11,960
People end friendships if people
are toxic. 

94
00:05:12,040 --> 00:05:15,120
People end friendships for much 
less than toxicity. 

95
00:05:15,440 --> 00:05:19,280
So if you find yourself in an 
organization like that, but the 

96
00:05:19,280 --> 00:05:22,640
organization has a lot of 
benefits which means you want to

97
00:05:22,640 --> 00:05:26,040
stay regardless of the toxic 
behaviour, Find something that 

98
00:05:26,040 --> 00:05:28,960
works for you. 
If your work is your whole life,

99
00:05:29,280 --> 00:05:32,960
then this can really affect you.
If you have many hobbies, you go

100
00:05:32,960 --> 00:05:35,680
on holidays, you take time off, 
you spend time with friends and 

101
00:05:35,680 --> 00:05:41,480
family, you put your mind out of
the work context, then you can 

102
00:05:41,480 --> 00:05:44,800
probably build up the resilience
and it's not going to matter as 

103
00:05:44,800 --> 00:05:47,000
much to you. 
But if you're a person that is 

104
00:05:47,000 --> 00:05:49,480
very much, they care about their
career, they want to grow as 

105
00:05:49,480 --> 00:05:52,560
fast as possible, and they are 
encountering a toxic 

106
00:05:52,560 --> 00:05:55,440
environment, then this is going 
to be very challenging because 

107
00:05:55,440 --> 00:05:57,760
it is in the way of what you 
want to achieve. 

108
00:05:58,400 --> 00:06:02,200
And I'm very sorry. 
It is very hard to change toxic 

109
00:06:02,200 --> 00:06:04,680
culture, right? 
I've spoken before on the 

110
00:06:04,680 --> 00:06:08,240
podcast that me as an 
individual, if I was in an 

111
00:06:08,240 --> 00:06:11,920
organization where it was not a 
meritocracy, people were not 

112
00:06:11,920 --> 00:06:14,920
promoted based on what they 
deliver in results, based on 

113
00:06:14,920 --> 00:06:18,320
their merit, But it is based on 
how much they preach, how much, 

114
00:06:18,440 --> 00:06:20,560
how much they promote 
themselves, how much they 

115
00:06:20,560 --> 00:06:24,560
basically blow themselves up. 
I would not be happy because my 

116
00:06:24,560 --> 00:06:27,080
personal values prevent me from 
being that person. 

117
00:06:27,600 --> 00:06:31,240
And if the only way I can get a 
promotion is by doing so, I 

118
00:06:31,240 --> 00:06:34,360
would be unhappy because I would
feel like I would show results 

119
00:06:34,840 --> 00:06:37,080
or I would accomplish certain 
things and they would not be 

120
00:06:37,080 --> 00:06:41,040
valued as much as people that 
show results similar or lesser 

121
00:06:41,040 --> 00:06:42,920
than and then blow themselves 
up. 

122
00:06:43,400 --> 00:06:46,040
So I would need to remove myself
from that situation. 

123
00:06:46,040 --> 00:06:49,720
Or there is also the concept of 
golden handcuffs. 

124
00:06:49,760 --> 00:06:54,600
If you get paid so much that you
looking for a job elsewhere 

125
00:06:54,600 --> 00:06:57,960
where you get paid equal level, 
it's just not out there, it's 

126
00:06:57,960 --> 00:07:00,720
non existent, then you have to 
make a choice, right? 

127
00:07:00,880 --> 00:07:03,040
But then you cannot be the 
person that wants to grow as 

128
00:07:03,040 --> 00:07:04,600
fast as possible within their 
career. 

129
00:07:04,760 --> 00:07:07,760
You already earn above and 
beyond apparently. 

130
00:07:08,000 --> 00:07:09,920
So then you have golden 
handcuffs. 

131
00:07:10,120 --> 00:07:11,920
Do you stay for the financial 
aspects? 

132
00:07:11,920 --> 00:07:14,840
For the benefits? 
Regardless of the toxicity that 

133
00:07:14,840 --> 00:07:18,360
you experience, you can 
definitely put your mind at ease

134
00:07:18,360 --> 00:07:20,080
with regards to anything outside
of work. 

135
00:07:20,680 --> 00:07:24,960
Or do you remove yourself from 
that position, therefore giving 

136
00:07:24,960 --> 00:07:27,280
away the gold but taking off the
handcuffs? 

137
00:07:27,880 --> 00:07:31,640
You have to decide, looking back
on your journey, what does 

138
00:07:31,640 --> 00:07:35,000
thinking in systems actually 
mean in practice and how can I 

139
00:07:35,000 --> 00:07:39,160
deliberately start applying that
in my day-to-day systems 

140
00:07:39,160 --> 00:07:40,720
thinking? 
I don't think I do it 

141
00:07:40,720 --> 00:07:43,200
deliberately. 
I think it is a way to solve 

142
00:07:43,200 --> 00:07:47,640
problems instead of looking at 
individual components, thinking 

143
00:07:47,640 --> 00:07:50,760
of the bigger whole, the system 
and not just looking at the 

144
00:07:50,760 --> 00:07:54,320
parts of it, but trying to 
digest the whole thing is 

145
00:07:54,320 --> 00:07:57,640
something that when you are 
problem solving, if you did, 

146
00:07:57,680 --> 00:08:00,600
definitely if you go to root 
causes and you don't just battle

147
00:08:00,600 --> 00:08:04,080
symptoms, I feel like maybe 
that's the biggest start in the 

148
00:08:04,080 --> 00:08:05,800
problems that you solve. 
Are they system? 

149
00:08:05,880 --> 00:08:11,000
Are they systematic, which is 
also quite vague, but are they 

150
00:08:11,000 --> 00:08:13,920
repeating for example, because 
then you might be battling 

151
00:08:13,920 --> 00:08:15,880
symptoms. 
I can give you an example. 

152
00:08:15,880 --> 00:08:21,080
The first job I ever had, it was
in operations and my team was 

153
00:08:21,080 --> 00:08:24,360
showing me a routine, something 
they were doing on a daily 

154
00:08:24,360 --> 00:08:26,920
basis, and it had to do with 
order management. 

155
00:08:27,200 --> 00:08:29,720
Some orders automatically did 
not get processed. 

156
00:08:30,320 --> 00:08:32,360
This came from the e-commerce 
team. 

157
00:08:32,600 --> 00:08:34,480
We didn't really speak to the 
e-commerce team. 

158
00:08:34,880 --> 00:08:38,520
The order just had issues and 
the protocol was you go to the 

159
00:08:38,520 --> 00:08:42,039
order, you manually open the 
order which was a file, you 

160
00:08:42,480 --> 00:08:45,440
change some things that allows 
the order to then be 

161
00:08:45,440 --> 00:08:49,240
automatically processed again. 
And me being very young and very

162
00:08:49,240 --> 00:08:53,480
naive and very stubborn to be 
honest, I had the mindset of 

163
00:08:53,480 --> 00:08:56,480
there is no way in hell that I'm
doing this on a day-to-day basis

164
00:08:56,480 --> 00:08:59,920
because I feel like this is 
useless and I'm not learning 

165
00:08:59,920 --> 00:09:02,600
anything, I'm just doing 
something and it doesn't make 

166
00:09:02,600 --> 00:09:04,000
any sense. 
Why aren't these orders 

167
00:09:04,000 --> 00:09:08,120
automatically being processed? 
So I didn't say that to my 

168
00:09:08,120 --> 00:09:10,960
colleagues, but I genuinely 
wanted to understand why these 

169
00:09:10,960 --> 00:09:13,520
orders were just not 
automatically processed for me. 

170
00:09:13,520 --> 00:09:16,960
It seems like seemed like 
nonsense, so I asked my team 

171
00:09:16,960 --> 00:09:19,640
members how often does this 
happen? 

172
00:09:19,640 --> 00:09:21,080
Well, it happens a few times a 
week. 

173
00:09:21,360 --> 00:09:24,080
We just check the the error 
directory and if it's nothing 

174
00:09:24,080 --> 00:09:27,560
there, there's nothing there. 
So I could have been happy and I

175
00:09:27,560 --> 00:09:31,280
could have just solved the 
issues, which is the orders 

176
00:09:31,600 --> 00:09:35,280
ending up in an error directory.
I would manipulate them manually

177
00:09:35,280 --> 00:09:38,560
and I would put them through and
then the next day I would do 

178
00:09:38,560 --> 00:09:40,120
that again. 
And the next day there might not

179
00:09:40,120 --> 00:09:42,960
be an order, but the next day, 
if there's an order again, I 

180
00:09:42,960 --> 00:09:45,720
would have to do the same thing.
Those are symptoms of an 

181
00:09:45,720 --> 00:09:47,800
underlying problem. 
And my colleagues apparently, 

182
00:09:48,440 --> 00:09:50,400
and I was a little bit 
disappointed because this was my

183
00:09:50,400 --> 00:09:52,520
first job. 
They had no problem doing that. 

184
00:09:53,280 --> 00:09:56,360
And I did. 
So I learned what the issues 

185
00:09:56,360 --> 00:09:58,920
were. 
They were only issues in 

186
00:09:58,920 --> 00:10:01,720
specific customer data spaces 
here and there. 

187
00:10:01,720 --> 00:10:03,880
And with the knowledge that I 
have, I was like, we should 

188
00:10:03,880 --> 00:10:07,200
definitely be able to prevent 
this from a data entry 

189
00:10:07,200 --> 00:10:09,080
perspective. 
So I went to the e-commerce 

190
00:10:09,080 --> 00:10:11,480
team. 
I was also new, so I introduced 

191
00:10:11,480 --> 00:10:13,640
myself. 
And I did not think of all of 

192
00:10:13,640 --> 00:10:15,520
this by myself. 
By the way, I had a mentor. 

193
00:10:15,520 --> 00:10:19,000
And I was like, I don't think I 
can do this. 

194
00:10:19,000 --> 00:10:22,200
Like this is literally week #2 
and I already think this is not 

195
00:10:22,200 --> 00:10:24,200
something I can see myself doing
sustainably. 

196
00:10:24,680 --> 00:10:26,080
And he was like, I absolutely 
agree. 

197
00:10:26,400 --> 00:10:27,800
So let's go to the e-commerce 
team. 

198
00:10:28,520 --> 00:10:30,480
Beautiful. 
I introduced myself. 

199
00:10:30,480 --> 00:10:32,400
I was like, OK, this is the 
issue that we have from 

200
00:10:32,400 --> 00:10:35,000
operations. 
Who can I speak to that knows a 

201
00:10:35,000 --> 00:10:37,040
little bit more about this and 
this and data entry. 

202
00:10:37,440 --> 00:10:40,760
And it turns out that the data 
entry did have the validation I 

203
00:10:40,760 --> 00:10:44,200
was looking for. 
So there is no way that new data

204
00:10:44,200 --> 00:10:48,120
entry can have the issues that 
were causing the error orders 

205
00:10:48,120 --> 00:10:50,520
not actually automatically being
processed. 

206
00:10:51,280 --> 00:10:53,840
But we had old customer 
information, customer 

207
00:10:53,840 --> 00:10:56,760
information that was already 
there in a database before the 

208
00:10:56,760 --> 00:11:00,120
validation was in place. 
So it took us a while to figure 

209
00:11:00,120 --> 00:11:01,800
that out. 
And with a while, I mean 

210
00:11:01,800 --> 00:11:04,640
literally half an hour, and then
I asked the person that managed 

211
00:11:04,640 --> 00:11:06,120
the database can we do a clean 
up? 

212
00:11:06,120 --> 00:11:10,200
Because as a result of that we 
will never have orders ending up

213
00:11:10,200 --> 00:11:14,200
in that same error directory or 
there will be new issues and we 

214
00:11:14,200 --> 00:11:16,600
will still be able to fix them 
if we look at root cause 

215
00:11:16,600 --> 00:11:19,680
problems. 
So I learned that in the second 

216
00:11:19,680 --> 00:11:24,080
week of my first job, not 
fighting symptoms but genuinely 

217
00:11:24,080 --> 00:11:25,640
figuring out what the problem 
was. 

218
00:11:26,000 --> 00:11:29,400
We fixed it by making a 
connection with a different 

219
00:11:29,400 --> 00:11:32,520
team, explaining the issue to 
the world that I could to the 

220
00:11:32,520 --> 00:11:36,120
best that I could at the time, 
by not being afraid of doing 

221
00:11:36,120 --> 00:11:40,040
something that my colleagues 
hadn't done before and therefore

222
00:11:40,160 --> 00:11:42,240
actually figuring out what the 
problem was. 

223
00:11:42,440 --> 00:11:45,880
I also learned a little bit more
about the system because we have

224
00:11:45,880 --> 00:11:49,520
data entry, then it goes to a 
database and we also have older 

225
00:11:49,520 --> 00:11:52,120
account information which can 
also be used to fill in an 

226
00:11:52,120 --> 00:11:54,000
order. 
Makes sense now that I'm 

227
00:11:54,000 --> 00:11:56,240
communicating it like this and 
likely this is something you 

228
00:11:56,240 --> 00:12:00,520
already knew, but me starting 
out in E com, I had no clue how 

229
00:12:00,520 --> 00:12:02,960
e-commerce operated. 
And then OK, once an order 

230
00:12:02,960 --> 00:12:06,120
actually gets submitted, it goes
to our order management system 

231
00:12:06,440 --> 00:12:09,080
and before being able to be 
processed, it's going to go 

232
00:12:09,080 --> 00:12:11,440
through validation. 
And if the validation doesn't 

233
00:12:11,800 --> 00:12:14,680
work, if the validation fails, 
it ends up in this error 

234
00:12:14,680 --> 00:12:16,960
directory where my other 
colleagues were always looking. 

235
00:12:18,760 --> 00:12:22,520
Yeah, this is the smallest 
possible example, and it was the

236
00:12:22,520 --> 00:12:24,600
first one that I had in my 
career. 

237
00:12:24,600 --> 00:12:27,040
It is the most concrete one 
because I feel like it was that 

238
00:12:27,040 --> 00:12:30,800
early. 
And I'm so happy that I actually

239
00:12:30,800 --> 00:12:33,120
did something with it. 
I will forever remember that. 

240
00:12:33,640 --> 00:12:35,840
Now, a lot of other examples 
have probably happened 

241
00:12:35,840 --> 00:12:39,240
throughout my career. 
Thinking of what is not just the

242
00:12:39,240 --> 00:12:42,680
solution here, but what is the 
underlying problem and can we 

243
00:12:42,680 --> 00:12:44,840
solve that? 
And that for me is systems 

244
00:12:44,840 --> 00:12:47,200
thinking. 
So I don't know what your 

245
00:12:47,200 --> 00:12:48,680
context is. 
I don't know what problems 

246
00:12:48,680 --> 00:12:52,600
you're facing, but try and think
big picture. 

247
00:12:53,960 --> 00:12:58,040
That's my advice. 
At what point there's a strong 

248
00:12:58,040 --> 00:13:01,680
engineer or developer become a 
solutions architect? 

249
00:13:02,080 --> 00:13:05,240
Is it competency or more of a 
mindset shift? 

250
00:13:06,560 --> 00:13:10,440
I feel like it is both. 
Solution Architects in essence, 

251
00:13:10,840 --> 00:13:13,920
I did an episode with Gregor 
Hope and on the day of recording

252
00:13:13,920 --> 00:13:15,680
it's coming out next week. 
But when you're listening to 

253
00:13:15,680 --> 00:13:17,720
this, the episode is already 
out. 

254
00:13:17,720 --> 00:13:20,080
So definitely check that one out
because it is one of the best 

255
00:13:20,080 --> 00:13:23,320
conversations I have had about 
software architecture. 

256
00:13:23,840 --> 00:13:27,760
In essence, you can have a 
different background while still

257
00:13:27,760 --> 00:13:31,080
being or responsible for 
architecture. 

258
00:13:31,400 --> 00:13:33,960
You can be a product minded 
architect, software minded 

259
00:13:33,960 --> 00:13:36,040
architect, security minded 
architect, doesn't really 

260
00:13:36,040 --> 00:13:38,920
matter. 
In essence, you do have to know 

261
00:13:38,920 --> 00:13:43,880
your heart skills. 
So on enterprise, what does it 

262
00:13:43,880 --> 00:13:47,240
mean for us to adopt A new 
system or suite of applications 

263
00:13:47,240 --> 00:13:50,040
throughout our landscape? 
And if we have a scala of 

264
00:13:50,040 --> 00:13:53,360
already existing applications, 
do we consolidate or do we 

265
00:13:53,360 --> 00:13:56,400
consciously choose to adopt new 
systems within this landscape 

266
00:13:56,400 --> 00:13:58,760
that we have? 
Those are things that you will 

267
00:13:58,760 --> 00:14:02,120
be responsible for as an 
enterprise architect or one of 

268
00:14:02,120 --> 00:14:04,280
the things I think you can be 
responsible for. 

269
00:14:04,280 --> 00:14:09,360
Let me paraphrase it like that. 
Now you can think along from a 

270
00:14:09,440 --> 00:14:10,920
software engineering 
perspective. 

271
00:14:11,160 --> 00:14:14,160
Depending on the type of 
organization you are in, some 

272
00:14:14,240 --> 00:14:17,400
architects are within teams and 
some are within an architecture 

273
00:14:17,400 --> 00:14:19,560
team. 
So depending on the size of the 

274
00:14:19,560 --> 00:14:23,120
organization and their appetite 
for risk, architecture might be 

275
00:14:23,120 --> 00:14:26,000
applied differently. 
In essence, you need both hard 

276
00:14:26,000 --> 00:14:29,200
skills, so everything with 
regards to good architecture 

277
00:14:29,200 --> 00:14:32,160
fundamentals, both in software, 
but also if you're talking 

278
00:14:32,160 --> 00:14:36,280
enterprise on an application 
level and on a, let's say 

279
00:14:36,280 --> 00:14:38,120
longevity and sustainability 
level. 

280
00:14:39,000 --> 00:14:44,720
And beyond that, the soft skills
to actually persuade teams and 

281
00:14:44,720 --> 00:14:47,600
take people along with you, not 
just technical people, but 

282
00:14:47,600 --> 00:14:51,840
especially non-technical people.
Those, I feel like that's going 

283
00:14:51,840 --> 00:14:55,720
to be a recipe for success and 
how you do that and how you can 

284
00:14:55,720 --> 00:14:59,080
distinguish bad architecture 
versus good architecture or the 

285
00:14:59,080 --> 00:15:00,400
people that are responsible for 
that. 

286
00:15:00,400 --> 00:15:02,400
I would highly recommend 
checking out that episode. 

287
00:15:03,200 --> 00:15:06,200
As an engineer, how can I 
improve at communicating 

288
00:15:06,200 --> 00:15:09,800
architectural slash technical 
decisions to non-technical 

289
00:15:09,800 --> 00:15:12,560
audiences without 
oversimplifying? 

290
00:15:13,440 --> 00:15:17,040
The only way to get good at that
is to know your audience. 

291
00:15:17,280 --> 00:15:20,880
Who am I communicating to? 
non-technical audience is not 

292
00:15:20,880 --> 00:15:23,440
good enough. 
So are you talking to the CFO? 

293
00:15:23,760 --> 00:15:26,480
Because the CFO might want to 
know about the cost 

294
00:15:26,720 --> 00:15:29,600
specifically, that is what 
they're responsible for or how 

295
00:15:29,600 --> 00:15:33,520
this is going to impact revenue 
or operations. 

296
00:15:33,760 --> 00:15:36,840
If you're talking to the CMO, 
they might want to know, OK, how

297
00:15:36,840 --> 00:15:40,360
can we make this marketable or 
what are opportunities here if 

298
00:15:40,360 --> 00:15:42,920
we actually built this? 
Depends on what you're pitching 

299
00:15:42,920 --> 00:15:45,920
and it depends on the context. 
But knowing your audience is, 

300
00:15:45,920 --> 00:15:50,880
for me, step #1 secondly, get 
feedback before actually doing 

301
00:15:50,880 --> 00:15:52,680
the conversation. 
If you have room for that. 

302
00:15:53,120 --> 00:15:59,240
You don't have to ask feedback 
for ACFO or of ACFO or of ACMO, 

303
00:15:59,680 --> 00:16:02,000
but people that you know in 
marketing are people that you 

304
00:16:02,000 --> 00:16:03,880
know in finance. 
They can give you feedback 

305
00:16:03,880 --> 00:16:06,280
because they are also the 
audience, maybe not at the 

306
00:16:06,280 --> 00:16:10,360
highest level, but in essence, 
asking for feedback cannot harm 

307
00:16:10,360 --> 00:16:14,480
you. 
And lastly, experience builds. 

308
00:16:14,880 --> 00:16:18,720
Experience compounds. 
So the more often you do this, 

309
00:16:19,000 --> 00:16:24,440
the better you will get at it, 
especially in how much you drill

310
00:16:24,440 --> 00:16:27,800
down the technical concepts and 
how much in the end you 

311
00:16:27,800 --> 00:16:30,040
simplify. 
It is a skill. 

312
00:16:30,880 --> 00:16:33,920
The really good engineers, they 
know how to simplify and how 

313
00:16:33,920 --> 00:16:37,000
much to simplify. 
And they don't just use 

314
00:16:37,000 --> 00:16:40,640
buzzwords and fluff words in 
simplifying, but they still make

315
00:16:40,640 --> 00:16:42,120
it concrete. 
They still make it land. 

316
00:16:42,120 --> 00:16:45,560
They know how to communicate it,
One, because they've done it 

317
00:16:45,560 --> 00:16:48,240
enough. 
But also secondly, I feel like 

318
00:16:48,680 --> 00:16:50,640
after you've done it, ask for 
feedback. 

319
00:16:51,360 --> 00:16:53,920
Did you understand what I said? 
And that's kind of 

320
00:16:53,920 --> 00:16:57,520
confrontational and direct. 
But in essence, did the person 

321
00:16:57,520 --> 00:16:59,280
understand what you were going 
for? 

322
00:16:59,440 --> 00:17:03,880
Or is their opinion that it's 
too simple and it is still one 

323
00:17:03,880 --> 00:17:07,400
opinion. 
So ask for feedback from a few 

324
00:17:07,400 --> 00:17:10,240
people and then see what you can
change, what you want to change,

325
00:17:10,240 --> 00:17:11,599
and what you don't want to 
compromise on. 

326
00:17:12,200 --> 00:17:17,440
In the end, you're responsible. 
So doing your homework, doing it

327
00:17:17,440 --> 00:17:21,319
many times, both homework and 
the picture of the presentation,

328
00:17:21,680 --> 00:17:24,960
the simplification, and then 
asking for feedback, learning 

329
00:17:24,960 --> 00:17:28,560
and adapting and doing it again 
continuously. 

330
00:17:29,000 --> 00:17:32,360
As someone who would like to 
take on a more leadership role 

331
00:17:33,040 --> 00:17:35,760
and wants to progress in their 
career, what are some of the 

332
00:17:35,760 --> 00:17:40,720
responsibilities I should take? 
Interesting if you want to grow 

333
00:17:40,720 --> 00:17:42,920
in leadership. 
Leadership is not just a title. 

334
00:17:42,920 --> 00:17:45,440
So you can show leadership in 
whatever position you have. 

335
00:17:45,880 --> 00:17:48,520
Doesn't matter if you are early 
in career, mid or senior. 

336
00:17:49,000 --> 00:17:52,080
In essence, leaders can come 
from everywhere and I believe 

337
00:17:52,080 --> 00:17:56,320
that they are the people that 
somehow magically get people on 

338
00:17:56,320 --> 00:17:58,200
board. 
They build relationships and 

339
00:17:58,200 --> 00:18:00,680
when they are there, things just
are smoother. 

340
00:18:00,920 --> 00:18:05,120
In essence, they are also people
that they do not butt heads with

341
00:18:05,120 --> 00:18:08,640
people, but they managed to get 
everything just up and running 

342
00:18:08,640 --> 00:18:10,600
smoothly. 
It's also kind of a 

343
00:18:10,600 --> 00:18:12,120
characteristics of good 
architects. 

344
00:18:12,480 --> 00:18:15,360
But in essence, let's say you 
start within a team, product, 

345
00:18:15,360 --> 00:18:18,280
team, right? 
If I'm responsible for product, 

346
00:18:18,560 --> 00:18:22,000
one of the things I love telling
my team is I want to know what 

347
00:18:22,000 --> 00:18:23,480
your ambitions are, what do you 
want to grow? 

348
00:18:23,480 --> 00:18:25,280
What do you want to achieve 
within this team? 

349
00:18:25,280 --> 00:18:29,440
Because me responsible for 
product, I am better equipped to

350
00:18:29,440 --> 00:18:32,800
put you in a position to thrive 
and to put you in a position to 

351
00:18:32,800 --> 00:18:35,960
achieve those things. 
I do that because I genuinely 

352
00:18:35,960 --> 00:18:38,800
enjoy it. 
I'm curious and I think people 

353
00:18:38,800 --> 00:18:42,440
will be more motivated in how 
they deliver and what outcomes 

354
00:18:42,440 --> 00:18:44,280
we are working more towards 
together. 

355
00:18:44,680 --> 00:18:48,240
So it's both strategic but also 
definitely personal because I 

356
00:18:48,240 --> 00:18:51,240
like helping people. 
Now, not every product person 

357
00:18:51,240 --> 00:18:54,200
does that. 
However, you as person within 

358
00:18:54,200 --> 00:18:56,040
that team, you can take the 
initiative. 

359
00:18:56,520 --> 00:18:59,560
You can have a conversation with
your product person and say this

360
00:18:59,560 --> 00:19:02,680
is really what I'm looking for 
within this project that we're 

361
00:19:02,680 --> 00:19:04,560
building. 
I want to grow more towards 

362
00:19:04,880 --> 00:19:08,640
front and back and any type of 
hard skill that you have or I 

363
00:19:08,640 --> 00:19:11,040
want to grow more towards more 
leadership roles. 

364
00:19:11,440 --> 00:19:14,760
So if you are starting early in 
conversations with stakeholders,

365
00:19:15,240 --> 00:19:19,400
can I be there observing or can 
I tag along or can I have a 

366
00:19:19,400 --> 00:19:23,040
certain level of responsibility 
within a project that we have, 

367
00:19:23,640 --> 00:19:24,880
right? 
You can do that to your product 

368
00:19:24,880 --> 00:19:27,280
person. 
And secondly, you can also do 

369
00:19:27,280 --> 00:19:30,200
that to your manager, have the 
same type of conversation with 

370
00:19:30,200 --> 00:19:33,360
him or her. 
But in essence, you're in 

371
00:19:33,360 --> 00:19:36,440
control of your career. 
So you need to know what you 

372
00:19:36,440 --> 00:19:38,280
want to do, what you want to 
grow into. 

373
00:19:38,280 --> 00:19:39,920
It can't just be I want to be a 
leader. 

374
00:19:40,760 --> 00:19:43,400
It has to be somewhere within 
the organization that you can 

375
00:19:43,400 --> 00:19:46,440
point at and say this is what I 
want to do, how do I get there? 

376
00:19:46,640 --> 00:19:49,320
Right, I want to be engineering 
manager, how do I get there? 

377
00:19:49,640 --> 00:19:52,800
Or in the end, if it's not 
within the organization, I want 

378
00:19:52,800 --> 00:19:55,000
to be an enterprise architect, 
how do I get there? 

379
00:19:55,360 --> 00:19:59,240
It also is a signal that if you 
want that and it's not in the 

380
00:19:59,240 --> 00:20:01,760
organization, your engineering 
manager damn well if they want 

381
00:20:01,760 --> 00:20:05,760
to keep you, make sure that they
have a conversation with you on 

382
00:20:05,760 --> 00:20:08,160
what you can do within the 
organization that has similar 

383
00:20:08,160 --> 00:20:10,960
responsibilities. 
As the title you're aiming for, 

384
00:20:11,320 --> 00:20:13,120
but all of this is a 
conversation starter. 

385
00:20:13,480 --> 00:20:17,080
Then you have to put up your 
effort. 

386
00:20:17,080 --> 00:20:20,040
Basically, you have to do it. 
You have to walk the walk of 

387
00:20:20,040 --> 00:20:23,840
leadership. 
Now, it's not a one thing that 

388
00:20:23,840 --> 00:20:27,680
you can do, but within your 
sphere of influence, you 

389
00:20:27,680 --> 00:20:31,200
probably have people that you 
think are leaders or are showing

390
00:20:31,200 --> 00:20:34,320
some of the leadership qualities
and based on that, what you 

391
00:20:34,320 --> 00:20:37,920
admire, you can see and even 
have a conversation with them 

392
00:20:38,280 --> 00:20:40,320
with regards to a learning path 
for yourself. 

393
00:20:41,000 --> 00:20:45,720
I had someone in my team, his 
name is Robert, Dutch guy, 

394
00:20:45,720 --> 00:20:47,240
Robert Dion. 
He's not going to listen to 

395
00:20:47,240 --> 00:20:51,200
this, but I learned so much from
this person and I never expected

396
00:20:51,200 --> 00:20:52,920
that. 
He was not my mentor, but 

397
00:20:52,920 --> 00:20:56,240
somehow I always went to him 
with specific questions because 

398
00:20:56,240 --> 00:20:59,240
I just loved the way he 
interacted with people. 

399
00:20:59,560 --> 00:21:02,320
It wasn't even what he knew on a
hard scale level, even though 

400
00:21:02,320 --> 00:21:06,440
that was solid. 
It was just his charisma and he 

401
00:21:06,440 --> 00:21:08,480
was super social, very 
extroverted. 

402
00:21:08,880 --> 00:21:11,720
He would just talk to people and
make people feel at ease. 

403
00:21:11,720 --> 00:21:14,480
And when you work with Robert, 
you would just be like, man, 

404
00:21:14,480 --> 00:21:16,080
things are going to be OK 
because he's here. 

405
00:21:16,440 --> 00:21:18,800
And in essence, he did not do 
all the work himself. 

406
00:21:19,320 --> 00:21:24,160
He definitely also delegated and
make sure that other people knew

407
00:21:24,160 --> 00:21:27,120
what they had to do. 
But I really just liked his 

408
00:21:27,120 --> 00:21:30,040
approach. 
So I stuck to him. 

409
00:21:30,440 --> 00:21:33,080
I basically asked as many 
questions to him and he was 

410
00:21:33,080 --> 00:21:35,760
completely open to that and I 
learned a lot from his approach,

411
00:21:36,200 --> 00:21:39,000
right? 
One of his mantras was act nice 

412
00:21:39,000 --> 00:21:40,520
to everyone. 
OK, show kindness. 

413
00:21:40,520 --> 00:21:43,080
It doesn't matter if it's your 
colleagues or a person that's 

414
00:21:43,080 --> 00:21:45,520
there to actually clean the 
toilets, It does not matter. 

415
00:21:45,840 --> 00:21:48,280
You are kind to everyone. 
That is one of his fundamentals,

416
00:21:48,280 --> 00:21:51,040
one of his base principles, and 
he builds on top of that. 

417
00:21:51,640 --> 00:21:54,880
And I could see that, right? 
The guy is genuinely kind to 

418
00:21:54,880 --> 00:21:56,720
everyone, and I always admired 
that. 

419
00:21:57,120 --> 00:22:00,640
And I feel like I'm not at that 
level, but I want to be there. 

420
00:22:00,640 --> 00:22:05,200
So I try and do that daily, 
basically showing the same type 

421
00:22:05,200 --> 00:22:07,400
of kindness. 
And hopefully people think, OK, 

422
00:22:07,400 --> 00:22:08,800
Patrick's here, it's going to be
all right. 

423
00:22:09,080 --> 00:22:11,520
I will never know. 
I can ask for feedback, and I 

424
00:22:11,520 --> 00:22:13,880
have to believe that. 
But yeah, imposter syndrome. 

425
00:22:14,560 --> 00:22:17,000
But in essence, those are some 
of the leadership qualities I 

426
00:22:17,040 --> 00:22:19,240
really liked and I wanted to 
learn from. 

427
00:22:19,440 --> 00:22:23,600
So that was my approach. 
Speaking of imposter syndrome, I

428
00:22:23,600 --> 00:22:25,920
sometimes experience imposter 
syndrome. 

429
00:22:26,440 --> 00:22:29,320
How can I overcome it and build 
confidence over time? 

430
00:22:30,200 --> 00:22:33,440
I also still feel imposter 
syndrome. 

431
00:22:33,920 --> 00:22:36,520
I shared this previously. 
The biggest feeling I had of the

432
00:22:36,520 --> 00:22:41,480
imposter syndrome was when I 
landed a job that I felt like 

433
00:22:42,320 --> 00:22:45,120
was not for me. 
Like for some reason they hired 

434
00:22:45,120 --> 00:22:46,840
me. 
I don't have no clue how I got 

435
00:22:46,840 --> 00:22:50,600
here and everyone around me is 
way better at executing than I 

436
00:22:50,600 --> 00:22:52,320
am, and I'm just lucky to be 
here. 

437
00:22:53,080 --> 00:22:54,640
That was genuinely the feeling I
had. 

438
00:22:54,840 --> 00:22:58,800
And thinking back, I still feel 
like that genuinely was valid to

439
00:22:58,800 --> 00:23:01,040
be honest. 
Because one of the things I 

440
00:23:01,040 --> 00:23:05,200
noticed was I was learning how 
to swim and people around me 

441
00:23:05,200 --> 00:23:08,440
were already swimming, serving, 
diving, doing whatever in the 

442
00:23:08,440 --> 00:23:11,040
water they could. 
And I was like, man, like I 

443
00:23:11,040 --> 00:23:13,040
really have to learn the basics 
here. 

444
00:23:13,560 --> 00:23:17,960
But in essence, The funny thing 
is everyone around me knew that 

445
00:23:17,960 --> 00:23:21,480
that was the case and that was 
fine. 

446
00:23:21,760 --> 00:23:25,320
And they were more than willing 
to help me learn how to swim, 

447
00:23:25,320 --> 00:23:27,000
how to do whatever I needed in 
the water. 

448
00:23:27,360 --> 00:23:28,920
And this analogy has gotten 
quite far. 

449
00:23:29,440 --> 00:23:33,520
So that really helped because I 
had the conversations with them.

450
00:23:33,520 --> 00:23:36,880
I also said I have, I feel like 
I have imposter syndrome, 

451
00:23:36,880 --> 00:23:39,720
especially when these things 
happen and especially when I 

452
00:23:39,720 --> 00:23:44,480
work with you, one of the people
basically because of XY and Z. 

453
00:23:44,480 --> 00:23:46,960
And then we deepened that out 
and then they gave me 

454
00:23:46,960 --> 00:23:49,800
perspective and it really helped
because they showed me that it 

455
00:23:49,800 --> 00:23:53,720
is OK for me to not know things 
and it is OK for me to learn. 

456
00:23:53,720 --> 00:23:56,000
And in the end, we are 
responsible as a team. 

457
00:23:56,640 --> 00:23:59,960
A lot of that has to do with the
environment I was in and the way

458
00:23:59,960 --> 00:24:01,680
that the people around me 
approached it. 

459
00:24:01,680 --> 00:24:04,840
So I feel like I just got lucky 
in the end. 

460
00:24:05,760 --> 00:24:09,080
But if you have the feeling of 
imposter syndrome, reflect. 

461
00:24:09,520 --> 00:24:12,760
You can be your best person if 
you reflect on your own 

462
00:24:12,760 --> 00:24:16,200
behaviour and what made you feel
that in a certain way and how 

463
00:24:16,200 --> 00:24:19,160
can you accommodate for that. 
But also give yourself some 

464
00:24:19,160 --> 00:24:22,120
grace like it is OK to not know 
things. 

465
00:24:22,640 --> 00:24:25,200
It should not be a culture of 
you need to know everything 

466
00:24:25,200 --> 00:24:27,680
otherwise you're an idiot. 
That's just not reality. 

467
00:24:27,960 --> 00:24:31,360
Especially in tech when things 
evolve so quickly, it is OK to 

468
00:24:31,360 --> 00:24:35,880
say I don't know and slowly if 
you say I don't know. 

469
00:24:35,960 --> 00:24:38,760
More often you will also have 
the responsibility to figure 

470
00:24:38,760 --> 00:24:41,280
things out. 
The more you figure things out, 

471
00:24:41,280 --> 00:24:44,720
the more you will build up the 
confidence of, I don't know, but

472
00:24:44,720 --> 00:24:46,800
I have the confidence we'll get 
there. 

473
00:24:47,360 --> 00:24:50,120
Even if it's not just me, but 
especially as a team, I have the

474
00:24:50,120 --> 00:24:54,720
confidence that we can do this. 
That really is valuable. 

475
00:24:54,920 --> 00:24:57,480
And even though you can still 
feel imposter syndrome here and 

476
00:24:57,480 --> 00:25:00,400
there, it never goes away in the
essence. 

477
00:25:00,400 --> 00:25:03,960
But you might be able to manage 
it differently than right now. 

478
00:25:04,800 --> 00:25:07,240
It's funny because this reminded
me of a conversation I had about

479
00:25:07,240 --> 00:25:10,720
consultancy. 
This is a minor minor segue, but

480
00:25:10,720 --> 00:25:13,520
within my friend group some 
people disagreed with how I view

481
00:25:13,520 --> 00:25:16,080
consultancy and they are also 
consultants themselves. 

482
00:25:16,960 --> 00:25:20,040
They said consultants cannot 
necessarily afford not to know. 

483
00:25:20,600 --> 00:25:23,960
And I disagree with that because
I do believe that saying I don't

484
00:25:23,960 --> 00:25:26,920
know really builds and shows 
character. 

485
00:25:27,160 --> 00:25:31,480
I would appreciate it if someone
says I don't know versus I know 

486
00:25:31,680 --> 00:25:35,200
because if I found out that's 
bullshit then it just harms the 

487
00:25:35,200 --> 00:25:37,520
relationship and the trust I 
have in a person. 

488
00:25:37,840 --> 00:25:41,320
Don't lie to my face basically. 
So if you don't know, tell me. 

489
00:25:42,000 --> 00:25:43,920
But I also want to see the 
confidence that you'll be able 

490
00:25:43,920 --> 00:25:46,160
to figure it out. 
So that's what I show in 

491
00:25:46,160 --> 00:25:48,120
conversations where I genuinely 
don't know. 

492
00:25:48,760 --> 00:25:52,560
And if in the end then it's not 
a good fit, then it's just not a

493
00:25:52,560 --> 00:25:54,480
good fit. 
But that's how I view 

494
00:25:54,480 --> 00:25:56,600
consultancy. 
I don't want to seem like the 

495
00:25:56,600 --> 00:26:00,000
expert of knowing everything. 
I feel like what you know 

496
00:26:00,000 --> 00:26:03,200
necessarily is not as valuable 
as it used to be because you can

497
00:26:03,200 --> 00:26:06,680
look up so much more. 
It is easily accessible 

498
00:26:07,000 --> 00:26:09,760
knowledge nowadays. 
So also how you behave and how 

499
00:26:09,760 --> 00:26:12,200
you look up is a lot more 
valuable than it used to be. 

500
00:26:12,880 --> 00:26:16,080
In tech, there's so much to 
learn that I often worry about 

501
00:26:16,080 --> 00:26:18,920
forgetting things. 
What are the best ways to learn 

502
00:26:18,920 --> 00:26:21,840
effectively and retain knowledge
long term? 

503
00:26:23,040 --> 00:26:26,160
I've mentioned this before. 
I'm practicing this Tetra custom

504
00:26:26,160 --> 00:26:27,920
method and I haven't done it for
long. 

505
00:26:28,240 --> 00:26:31,440
But the idea of this is you make
notes and you make them in a 

506
00:26:31,440 --> 00:26:35,320
specific way and in a specific 
system in which your knowledge 

507
00:26:35,320 --> 00:26:38,120
will compound. 
And the idea of this note taking

508
00:26:38,120 --> 00:26:42,080
system is that you also build 
relationships between your notes

509
00:26:42,880 --> 00:26:45,560
and in outcomes. 
You can have a graph where 

510
00:26:45,560 --> 00:26:49,000
certain topics that you've taken
notes on can interconnect. 

511
00:26:49,400 --> 00:26:53,520
And because they are your notes 
and you distill contents and put

512
00:26:53,520 --> 00:26:57,000
them in your own words in a note
taking system, therefore you 

513
00:26:57,000 --> 00:26:59,440
might be able to retain 
knowledge over time. 

514
00:27:00,080 --> 00:27:02,480
I'm very early in my note taking
career. 

515
00:27:02,480 --> 00:27:04,960
In my note taking system, I was 
taking notes and they were just 

516
00:27:04,960 --> 00:27:06,840
scattered. 
And then I had a note taking 

517
00:27:06,840 --> 00:27:09,400
system which was not really a 
note taking system, but it was 

518
00:27:09,400 --> 00:27:12,320
just chaos and I wanted some 
structure in there. 

519
00:27:13,520 --> 00:27:15,720
And I still have the same 
feeling of wanting some 

520
00:27:15,720 --> 00:27:18,080
structure in there and I'm doing
my best. 

521
00:27:18,400 --> 00:27:22,160
So that with regards to note 
taking, I feel like the better 

522
00:27:22,160 --> 00:27:24,840
of a system you have in place 
the system that works for you, 

523
00:27:25,960 --> 00:27:28,160
Just try it. 
It's a lot of trial and error, 

524
00:27:28,200 --> 00:27:30,560
but if you have something that 
works for you, retaining 

525
00:27:30,560 --> 00:27:32,440
knowledge is going to be easier 
and easier. 

526
00:27:32,880 --> 00:27:35,720
There is still crucial 
information that is just better 

527
00:27:35,720 --> 00:27:38,880
if you retain it. 
But again, I am of the opinion 

528
00:27:39,120 --> 00:27:42,080
that knowledge and looking up 
knowledge is incredibly valuable

529
00:27:42,080 --> 00:27:44,840
as well. 
Finding gaps though in your 

530
00:27:44,840 --> 00:27:47,480
knowledge, in what you already 
know and where there are blind 

531
00:27:47,480 --> 00:27:50,720
spots can be just as valuable, 
especially when you're having a 

532
00:27:50,720 --> 00:27:53,600
conversation. 
There are very apparent blind 

533
00:27:53,600 --> 00:27:57,200
spots if you're talking about a 
very specific topic with someone

534
00:27:57,200 --> 00:28:00,680
that is well educated and knows 
that topic like the back of 

535
00:28:00,680 --> 00:28:03,680
their hand. 
So yeah, definitely also spar 

536
00:28:03,680 --> 00:28:07,640
with people, reflect afterwards,
figure out where you want to 

537
00:28:07,880 --> 00:28:11,440
bridge the gap in the knowledge 
that you have and a system might

538
00:28:11,440 --> 00:28:14,800
help with that. 
There is no definitive finite 

539
00:28:14,800 --> 00:28:17,920
answer of how much should you 
know versus how much can you 

540
00:28:17,920 --> 00:28:21,640
learn on the fly or when there 
is a task at hand. 

541
00:28:22,400 --> 00:28:27,280
Experience builds and I am just 
not a person that loves studying

542
00:28:27,280 --> 00:28:29,920
for the sake of studying. 
I like studying when there are 

543
00:28:29,920 --> 00:28:32,080
outcomes. 
That's also why I feel like I 

544
00:28:32,080 --> 00:28:34,600
struggled at school. 
Like I finished my bachelor and 

545
00:28:34,600 --> 00:28:37,240
I genuinely had the mindset of I
just need to finish this because

546
00:28:37,240 --> 00:28:38,680
I need the piece of paper to get
a job. 

547
00:28:39,240 --> 00:28:43,680
And that might not be nowadays, 
especially in tech, the most 

548
00:28:43,680 --> 00:28:46,200
effective career path. 
It might be the most safe career

549
00:28:46,200 --> 00:28:48,080
path when we're talking about 
risks. 

550
00:28:48,600 --> 00:28:52,040
But in the end, what you show in
results is incredibly valuable. 

551
00:28:52,040 --> 00:28:55,880
What you show in skills or how 
you applied those skills is 

552
00:28:55,880 --> 00:28:59,760
incredibly valuable. 
So yeah, knowledge is an 

553
00:28:59,760 --> 00:29:02,360
accelerator for outcomes I feel 
like. 

554
00:29:03,200 --> 00:29:07,480
What mindset or habit has helped
you the most in your personal 

555
00:29:07,480 --> 00:29:10,280
and professional journey? 
Habits and mindset. 

556
00:29:10,320 --> 00:29:13,360
I feel like I have the mindset. 
I'm a pretty chill person. 

557
00:29:13,560 --> 00:29:16,480
I don't know how much it comes 
across In this podcast, people 

558
00:29:16,480 --> 00:29:18,720
say they like listening to my 
voice because it's relaxing. 

559
00:29:19,200 --> 00:29:20,960
I am genuinely quite a chill 
person. 

560
00:29:21,800 --> 00:29:24,760
I've had a lot of learnings 
throughout my childhood, 

561
00:29:24,760 --> 00:29:27,680
throughout my upbringing with 
regards to friends and families 

562
00:29:27,680 --> 00:29:30,840
and things that have happened 
and people that have passed away

563
00:29:30,840 --> 00:29:34,280
and my mom being I'll having 
cancer twice and going through 

564
00:29:34,280 --> 00:29:36,600
all of that. 
It has shaped me and turned me 

565
00:29:36,600 --> 00:29:40,800
into the person I am now. 
And throughout that also 

566
00:29:40,800 --> 00:29:43,280
probably how specifically my mom
raised me. 

567
00:29:43,800 --> 00:29:47,480
I have this feeling of no matter
what happens, it's going to be 

568
00:29:47,480 --> 00:29:50,320
OK. 
So when work gets really tough 

569
00:29:50,800 --> 00:29:54,680
and there are deadlines and I'm 
feeling pressure, in my head, no

570
00:29:54,680 --> 00:29:56,640
matter what happens, I'm going 
to be OK. 

571
00:29:57,000 --> 00:30:00,640
So worst case scenario, I fuck 
up, what happens, they're going 

572
00:30:00,640 --> 00:30:02,760
to fire me. 
It's very hard to fire someone 

573
00:30:02,760 --> 00:30:05,360
in the Netherlands. 
So even worst case, if they will

574
00:30:05,360 --> 00:30:08,800
fire me, I will have severance 
and I will have several months 

575
00:30:08,800 --> 00:30:10,920
to figure out what I want to do 
with my life and what the next 

576
00:30:10,920 --> 00:30:14,280
job is going to be. 
And if I never get another job 

577
00:30:14,320 --> 00:30:18,160
ever again, there is 
unemployment benefits that the 

578
00:30:18,160 --> 00:30:20,880
Netherlands offers. 
So no matter what happens, it's 

579
00:30:20,880 --> 00:30:22,960
going to be OK. 
I might not like it might not be

580
00:30:22,960 --> 00:30:24,920
the best case scenario because 
yeah, we were talking about 

581
00:30:24,920 --> 00:30:28,400
worst case, but if it is even a 
little bit better than the worst

582
00:30:28,400 --> 00:30:32,400
case scenario, it is still OK. 
I feel like with that mindset, 

583
00:30:32,440 --> 00:30:34,840
I'm never a person that likes to
doom think. 

584
00:30:35,560 --> 00:30:39,680
I also am very much a person 
that was raised in a way where 

585
00:30:39,680 --> 00:30:43,720
if I said I could not do things,
yeah, my environment around me 

586
00:30:43,720 --> 00:30:46,360
would get angry and would say 
you can do whatever you put your

587
00:30:46,360 --> 00:30:48,520
mind to, OK, Don't say you can't
do things. 

588
00:30:48,520 --> 00:30:51,120
You can definitely do things and
that require effort. 

589
00:30:51,320 --> 00:30:53,480
So if you want to do it, put in 
the effort. 

590
00:30:53,920 --> 00:30:56,720
Otherwise you can still do it, 
but you choose not to. 

591
00:30:56,720 --> 00:30:58,480
It's your decision. 
You are in control. 

592
00:30:59,240 --> 00:31:03,720
That's kind of also with that 
directness and with that vigor 

593
00:31:03,720 --> 00:31:05,680
and passion. 
Yeah, it's kind of how I was 

594
00:31:05,680 --> 00:31:07,160
raised. 
That's how it feels like. 

595
00:31:07,560 --> 00:31:10,640
So I take that with me and it 
might not be a habit. 

596
00:31:11,280 --> 00:31:14,320
It's definitely part of core 
values and a perspective and 

597
00:31:14,320 --> 00:31:18,520
maybe a mindset, but I feel like
that has helped me a lot. 

598
00:31:18,880 --> 00:31:22,720
In essence, I've covered on this
podcast salary negotiations. 

599
00:31:22,960 --> 00:31:25,080
In essence, no matter what 
happens, it's going to be OK. 

600
00:31:25,480 --> 00:31:29,480
You're going to learn. 
I feel like also, whatever 

601
00:31:29,480 --> 00:31:32,560
happens, there are learnings to 
take away from. 

602
00:31:32,840 --> 00:31:35,960
You might not understand your 
learnings now, but maybe as you 

603
00:31:35,960 --> 00:31:40,120
grow, as time passes by, you 
will reflect and you will then 

604
00:31:40,120 --> 00:31:42,840
appreciate maybe the learnings 
that you did not realise existed

605
00:31:42,840 --> 00:31:46,360
earlier, which is also fine. 
I'm a person that reflects a 

606
00:31:46,360 --> 00:31:49,040
lot. 
Not much by myself to be honest,

607
00:31:49,040 --> 00:31:52,520
but because I talk to a lot of 
people, I'm also very open and 

608
00:31:52,520 --> 00:31:54,600
honest. 
Maybe sometimes too honest and 

609
00:31:54,600 --> 00:31:57,720
too open, but that helps a lot 
with reflection to be honest. 

610
00:31:57,720 --> 00:32:01,800
So yeah, maybe not as concrete 
of an answer as I would have 

611
00:32:01,800 --> 00:32:04,320
liked to give, but maybe a 
little bit of insight in how I 

612
00:32:04,320 --> 00:32:07,480
operate. 
I also don't like to blame other

613
00:32:07,480 --> 00:32:11,360
people or other things, tools, 
environments, people blaming. 

614
00:32:12,480 --> 00:32:15,040
I don't like that I take 
ownership even though if I think

615
00:32:15,040 --> 00:32:20,320
the fault is not mine, I take 
ownership because otherwise it's

616
00:32:20,320 --> 00:32:21,640
out of my hand, it's out of my 
control. 

617
00:32:21,640 --> 00:32:24,640
If I take ownership, it means I 
do feel like I could have 

618
00:32:24,640 --> 00:32:27,120
changed some things or I could 
have acted differently. 

619
00:32:27,120 --> 00:32:29,800
And even if I don't believe 
that, still, by taking ownership

620
00:32:30,040 --> 00:32:33,560
I'm convincing myself that next 
time there are always options 

621
00:32:33,840 --> 00:32:38,080
and my behaviour influences all 
those parts, my environment, my 

622
00:32:38,080 --> 00:32:39,640
team, the people I interact 
with. 

623
00:32:40,040 --> 00:32:41,800
So ownership is a big thing for 
me as well. 

624
00:32:42,240 --> 00:32:44,560
I take ownership. 
I don't like blaming other 

625
00:32:44,560 --> 00:32:46,280
people. 
I don't like blaming tools. 

626
00:32:46,520 --> 00:32:48,200
I should have done something 
differently. 

627
00:32:48,200 --> 00:32:50,680
It's not a tool that goes 
randomly and does something. 

628
00:32:50,680 --> 00:32:53,320
I am the operator. 
I take ownership. 

629
00:32:53,960 --> 00:32:56,600
I would be curious to know how 
you would train a software 

630
00:32:56,600 --> 00:33:00,400
developer starting today who had
no technical experience, but 

631
00:33:00,400 --> 00:33:03,560
lots of product, PM and design 
experience. 

632
00:33:04,280 --> 00:33:06,600
There's two parts to this. 
Because if I were to train a 

633
00:33:06,600 --> 00:33:09,760
software engineer that has no 
experience, that is slightly 

634
00:33:09,760 --> 00:33:12,520
different from the PM slash 
design experience. 

635
00:33:12,520 --> 00:33:16,960
Because with PM responsible for 
product, you are very much 

636
00:33:16,960 --> 00:33:20,440
thinking of business outcomes 
and priorities and why should we

637
00:33:20,440 --> 00:33:22,920
work on these things and not on 
these things. 

638
00:33:22,920 --> 00:33:26,480
And specifically in the order 
that is laid out right now, that

639
00:33:26,480 --> 00:33:28,640
is really helpful from an 
engineering perspective. 

640
00:33:28,800 --> 00:33:32,360
You leverage that experience 
when you are responsible for 

641
00:33:32,560 --> 00:33:35,280
delivering as an engineer. 
Same for design. 

642
00:33:35,640 --> 00:33:38,720
You are thinking way differently
about your end users and what 

643
00:33:38,720 --> 00:33:41,920
they think is important. 
You might have interviews with 

644
00:33:41,920 --> 00:33:44,000
them. 
You have definitely researched 

645
00:33:44,000 --> 00:33:47,920
everything from accessibility to
best practices with regards to 

646
00:33:47,920 --> 00:33:50,440
visual design or whatever. 
Design design is kind of 

647
00:33:50,440 --> 00:33:52,200
abstract and has a lot of 
responsibilities. 

648
00:33:52,200 --> 00:33:55,560
But somewhere in there you have 
experience that you can leverage

649
00:33:55,560 --> 00:33:58,480
when you are responsible as an 
engineer for building. 

650
00:33:59,760 --> 00:34:02,280
If you come from a blank canvas 
and you don't have anything, 

651
00:34:02,680 --> 00:34:04,880
then there is still experience 
that you can leverage. 

652
00:34:05,200 --> 00:34:07,440
Your upbringing, your values, 
how you were raised, the 

653
00:34:07,440 --> 00:34:11,920
education that you had or the 
the practice that you've done on

654
00:34:11,920 --> 00:34:14,960
personal projects, that's all 
the experience you bring to the 

655
00:34:14,960 --> 00:34:16,800
table, they are not worth 
nothing. 

656
00:34:17,120 --> 00:34:19,320
You always have something to 
bring to the table, even though 

657
00:34:19,320 --> 00:34:24,280
you might not realize it now. 
Learning good software 

658
00:34:24,280 --> 00:34:28,400
engineering fundamentals. 
Funny thing is, it is evolving. 

659
00:34:29,120 --> 00:34:32,159
With the tools we have now, 
coding has become much much 

660
00:34:32,159 --> 00:34:34,320
easier. 
So that is not where I would 

661
00:34:34,320 --> 00:34:37,840
start. 
Maybe I want you to understand 

662
00:34:38,360 --> 00:34:41,000
coding, and I definitely want 
you to be able to read coding. 

663
00:34:41,000 --> 00:34:46,760
But writing code is not going to
be as much of A topic in the 

664
00:34:46,760 --> 00:34:50,600
education that I foresee. 
So I want you to be able to read

665
00:34:50,600 --> 00:34:52,960
code, digest code. 
I want you to be able to 

666
00:34:52,960 --> 00:34:56,880
understand code patterns and 
certain behaviors, and AI 

667
00:34:56,880 --> 00:34:59,240
tooling can help with all of 
that by the way, because it will

668
00:34:59,240 --> 00:35:03,120
be the tutor for you. 
I feel like hallucinations have 

669
00:35:03,120 --> 00:35:06,880
gotten to a point where it's 
negligible and the information 

670
00:35:06,880 --> 00:35:09,600
that you gain is dense enough 
and it's going to accelerate you

671
00:35:09,600 --> 00:35:13,880
enough in combination with human
interaction that you basically 

672
00:35:14,160 --> 00:35:16,840
have a software engineer on your
computer that you can ask 

673
00:35:16,840 --> 00:35:19,720
questions to. 
What does this mean or why is it

674
00:35:19,720 --> 00:35:22,600
written in this way or I 
actually have read this. 

675
00:35:22,600 --> 00:35:24,960
Is this comparable to this or is
this something else? 

676
00:35:25,080 --> 00:35:28,760
Those are all questions that you
don't have to wait when someone 

677
00:35:28,760 --> 00:35:29,960
is available. 
You don't have to book a 

678
00:35:29,960 --> 00:35:34,600
calendar slot, you can ask them 
as they pop up quite quickly. 

679
00:35:34,680 --> 00:35:37,240
I wish I had this when I was 
learning. 

680
00:35:37,720 --> 00:35:41,800
I asked so many questions to the
people around me because first 

681
00:35:41,800 --> 00:35:43,840
of all because I felt 
comfortable enough to do so. 

682
00:35:44,040 --> 00:35:47,000
Second of all, they also wanted 
me to learn as fast as possible.

683
00:35:47,000 --> 00:35:50,600
That was the environment. 
But in essence I could have also

684
00:35:50,600 --> 00:35:53,280
done that and asked it to 
whatever AI tooling I'm using. 

685
00:35:53,840 --> 00:35:57,200
I like my experience but I feel 
like if I were to grow up now 

686
00:35:57,880 --> 00:36:00,400
and had to learn software 
engineering, I would leverage 

687
00:36:00,400 --> 00:36:03,400
the hell out of that. 
Ask whatever and if things don't

688
00:36:03,400 --> 00:36:07,080
make sense, don't stop thinking.
I feel like that's my biggest 

689
00:36:07,080 --> 00:36:09,280
take away. 
You still have to do your own 

690
00:36:09,280 --> 00:36:12,800
critical thinking and you will 
be good at pattern recognition 

691
00:36:12,800 --> 00:36:15,760
and you will be better at 
strategic thinking the more you 

692
00:36:15,760 --> 00:36:18,160
do it. 
But I feel like specifically 

693
00:36:18,760 --> 00:36:23,080
problem solving skills, pattern 
recognition will be very helpful

694
00:36:23,320 --> 00:36:26,520
in your learning process and you
will be able to ask whatever 

695
00:36:26,520 --> 00:36:29,560
question you have, which is 
incredibly valuable. 

696
00:36:30,000 --> 00:36:33,000
Now the coding part, why I don't
want that to be as much of A 

697
00:36:33,000 --> 00:36:36,840
focal point is because right now
creating code has become 

698
00:36:37,280 --> 00:36:39,880
incredibly easy. 
You ask something to a magical 

699
00:36:39,880 --> 00:36:43,800
box and the output is code. 
And if you look at the total 

700
00:36:43,800 --> 00:36:47,600
lines of code that are executed 
in a piece of software right 

701
00:36:47,600 --> 00:36:50,440
now, a lot of people are 
creating software that only gets

702
00:36:50,440 --> 00:36:54,880
executed once because it's way 
easier to build something that 

703
00:36:54,880 --> 00:36:58,400
is custom for your own use case.
And sure, there might be 

704
00:36:58,640 --> 00:37:02,840
products out there, SAS products
out in the market, but typically

705
00:37:03,240 --> 00:37:07,720
because it is so custom, either 
they are paywalling you or it's 

706
00:37:07,720 --> 00:37:10,240
just not out there. 
So people are way more often 

707
00:37:10,240 --> 00:37:12,480
building something custom, 
executing it once and then 

708
00:37:12,480 --> 00:37:15,200
throwing it away because they 
just needed it once. 

709
00:37:15,320 --> 00:37:17,160
And it's now more easier than 
ever. 

710
00:37:17,800 --> 00:37:22,560
Now architecting good software 
systems is very different, even 

711
00:37:22,560 --> 00:37:25,400
though we are also moving from 
vibe coding to vibe engineering.

712
00:37:26,280 --> 00:37:28,560
Creating good systems or what 
does that look like? 

713
00:37:28,600 --> 00:37:31,000
Those are the fundamentals. 
I want new people to have 

714
00:37:31,800 --> 00:37:33,600
everything with regards to 
system design. 

715
00:37:34,040 --> 00:37:37,920
Also starting out small, how to 
expand, when does it make sense?

716
00:37:38,960 --> 00:37:41,120
Those would be, I think the 
focus points. 

717
00:37:41,360 --> 00:37:44,880
So no matter if you start with a
blank canvas or you have product

718
00:37:44,880 --> 00:37:48,600
and design experience, figuring 
out what good software systems 

719
00:37:48,600 --> 00:37:52,360
are, how do they operate, 
looking at your competitors or 

720
00:37:52,360 --> 00:37:55,680
already environments that you 
can read on online, read 

721
00:37:55,680 --> 00:37:59,280
incident reports because those 
typically give a lot of 

722
00:37:59,280 --> 00:38:02,440
information. 
They are very, very dense with 

723
00:38:02,440 --> 00:38:05,280
learnings can give you a 
perspective. 

724
00:38:05,320 --> 00:38:07,960
And in the end you will have to 
join a team. 

725
00:38:08,200 --> 00:38:11,920
You will be responsible for a 
suite of components and systems 

726
00:38:11,920 --> 00:38:15,120
and applications and you will be
tasked with delivery. 

727
00:38:15,640 --> 00:38:18,880
I from product, don't really 
care how you do it, but I do 

728
00:38:18,880 --> 00:38:21,400
care that you are responsible 
and that you understand what is 

729
00:38:21,400 --> 00:38:24,040
running and how it's running and
how things kind of are 

730
00:38:24,040 --> 00:38:25,800
interwoven in the system that we
have. 

731
00:38:26,480 --> 00:38:31,360
So yeah, some stuff you can 
learn from, some stuff you can 

732
00:38:31,360 --> 00:38:35,400
read, definitely theoretical and
educational, and a lot of stuff 

733
00:38:36,040 --> 00:38:39,320
you will have to experience. 
Have you ever worked with 

734
00:38:39,360 --> 00:38:42,800
Brazilian developers? 
What is your opinion on hiring 

735
00:38:42,800 --> 00:38:47,600
engineers from Brazil or Latham?
Yes, yes, I have Brazilian 

736
00:38:47,600 --> 00:38:49,320
colleagues. 
I would even call them my 

737
00:38:49,320 --> 00:38:51,280
friends. 
Some of the Brazilian colleagues

738
00:38:51,280 --> 00:38:54,640
and friends, we've done podcast 
episodes and I really enjoyed 

739
00:38:54,640 --> 00:38:58,640
them actually. 
Brazilian LATAM people coming 

740
00:38:58,640 --> 00:39:02,720
from Asia, North America, South 
America, Europe, they're people.

741
00:39:03,000 --> 00:39:04,880
They're all people. 
We need to connect as humans 

742
00:39:05,280 --> 00:39:09,080
before we can connect as team 
mates, colleagues, anything else

743
00:39:09,080 --> 00:39:12,320
like that. 
And I feel like, yeah, I connect

744
00:39:12,320 --> 00:39:14,280
quite quickly with my Brazilian 
colleagues. 

745
00:39:14,280 --> 00:39:16,600
It might have to do with the 
culture, might have to do with 

746
00:39:16,600 --> 00:39:20,160
the friendliness or the 
openness, or also them really 

747
00:39:20,160 --> 00:39:22,600
wanting to connect. 
Because I mean, if you're 

748
00:39:23,640 --> 00:39:26,400
outside your home country and 
you come to a new culture, you 

749
00:39:26,400 --> 00:39:28,560
just also are very curious and 
you want to learn. 

750
00:39:30,040 --> 00:39:33,160
So yeah, it's nothing to do with
specifically people coming from 

751
00:39:33,160 --> 00:39:35,080
abroad, which is connected 
really well. 

752
00:39:35,640 --> 00:39:37,600
I don't have a preference for 
where you are from. 

753
00:39:38,000 --> 00:39:40,720
I do see that some cultures just
get each other more. 

754
00:39:42,640 --> 00:39:45,080
Some has to do with hierarchy, 
some has to do with work 

755
00:39:45,080 --> 00:39:47,360
culture. 
That can be a benefit or it can 

756
00:39:47,360 --> 00:39:51,600
be a curse. 
So yeah, I like open mindedness.

757
00:39:51,600 --> 00:39:54,840
I like open perspectives and 
that can come from any culture 

758
00:39:54,880 --> 00:39:57,040
to be honest, can come from any 
person. 

759
00:39:57,440 --> 00:40:01,480
So I feel like the more open our
perspective is, the more we are 

760
00:40:01,480 --> 00:40:04,320
open to learnings and learning 
from each other and the better 

761
00:40:04,320 --> 00:40:07,000
the outcomes are in the end. 
So that's what I look for. 

762
00:40:07,840 --> 00:40:11,280
My plan is to work as a software
engineer in the interim, 

763
00:40:11,440 --> 00:40:14,200
building strong coding skills 
while preparing for my 

764
00:40:14,200 --> 00:40:18,280
transition into cybersecurity 
slash penetration testing. 

765
00:40:18,800 --> 00:40:21,120
Does this sound like a strategic
path to you? 

766
00:40:21,640 --> 00:40:23,320
Would you recommend any 
adjustments? 

767
00:40:23,320 --> 00:40:26,600
This is a hard one. 
Like I'm not a cybersecurity 

768
00:40:26,600 --> 00:40:29,960
expert, I'm not a penetration 
testing expert. 

769
00:40:30,920 --> 00:40:35,160
I feel like whatever experience 
you leverage, whatever 

770
00:40:35,160 --> 00:40:37,800
experience you have built up, 
you can leverage in whatever you

771
00:40:37,800 --> 00:40:40,680
do. 
So I know a person that hired a 

772
00:40:40,680 --> 00:40:46,240
dentist who went to boot camps 
and re educated himself to be a 

773
00:40:46,240 --> 00:40:48,600
software engineer. 
This was a he in this case. 

774
00:40:49,040 --> 00:40:53,680
And the person hiring said 
already this person has shown 

775
00:40:53,680 --> 00:40:57,800
that they can go through lots of
educational curriculum to be 

776
00:40:57,800 --> 00:41:01,120
able to be a dentist in practice
and they have done that for a 

777
00:41:01,120 --> 00:41:03,720
few years. 
For them to move and re educate 

778
00:41:03,720 --> 00:41:07,400
themselves to a different 
career, They really admired 

779
00:41:07,400 --> 00:41:10,520
that, right? 
They are giving up a huge salary

780
00:41:11,040 --> 00:41:13,480
to kind of start from scratch in
a new career. 

781
00:41:13,920 --> 00:41:16,520
And they admired that so much 
that they gave this person a 

782
00:41:16,520 --> 00:41:19,520
chance, right? 
It wasn't just a OK, based on 

783
00:41:19,520 --> 00:41:23,080
the context and the papers and 
the the theory, here's a job. 

784
00:41:23,080 --> 00:41:25,120
You know, they actually had a 
conversation with this person. 

785
00:41:25,440 --> 00:41:27,880
But still the fact that this 
person had gone through that 

786
00:41:28,360 --> 00:41:31,440
showed ambition shows what the 
person wants. 

787
00:41:31,880 --> 00:41:35,400
So I feel like whatever you do, 
either if you are still early in

788
00:41:35,400 --> 00:41:38,120
career or you come from a 
different career path, there's 

789
00:41:38,120 --> 00:41:39,760
always experience that you 
bring. 

790
00:41:40,360 --> 00:41:43,480
Now, is being a software 
engineer going to help in 

791
00:41:43,480 --> 00:41:45,280
cybersecurity and penetration 
testing? 

792
00:41:45,440 --> 00:41:48,160
If you were to ask me a black 
and white answer, my answer 

793
00:41:48,160 --> 00:41:50,480
would be yes. 
I do feel like it will help. 

794
00:41:50,760 --> 00:41:52,840
It doesn't mean that it's the 
only path. 

795
00:41:53,200 --> 00:41:56,400
If there are junior 
cybersecurity consultancy roles 

796
00:41:56,400 --> 00:42:01,480
for example, then I think doing 
that compared to 1st building up

797
00:42:01,480 --> 00:42:03,920
a career in software engineering
would be better. 

798
00:42:04,160 --> 00:42:05,680
But in the end, I haven't done 
it. 

799
00:42:05,680 --> 00:42:09,400
So this is very theoretical. 
If you are already a software 

800
00:42:09,400 --> 00:42:13,480
engineer or you're already an 
engineer, then figuring out how 

801
00:42:13,480 --> 00:42:17,440
you can apply some of the 
responsibilities that 

802
00:42:17,440 --> 00:42:20,200
cybersecurity people are 
responsible for in your 

803
00:42:20,200 --> 00:42:23,560
day-to-day as a software 
engineer to building secure 

804
00:42:23,560 --> 00:42:26,000
systems or thinking about 
security, privacy and risk, for 

805
00:42:26,000 --> 00:42:31,120
example, or data protection can 
already help and can show what 

806
00:42:31,120 --> 00:42:34,000
you've done on the job. 
So I'm assuming you're the 

807
00:42:34,000 --> 00:42:38,000
software engineer figuring out 
in your domain what you can do 

808
00:42:38,000 --> 00:42:41,280
for any of those topics, safety,
risk, personal data, etcetera, 

809
00:42:41,280 --> 00:42:43,840
etcetera. 
That's going to really help 

810
00:42:43,960 --> 00:42:46,880
because then you are already 
applying probably what you will 

811
00:42:46,880 --> 00:42:50,680
be responsible for to a certain 
degree and it's something to 

812
00:42:50,680 --> 00:42:52,800
talk about when you actually 
apply for a job fully. 

813
00:42:53,760 --> 00:42:57,800
What market slash industry slash
area do you see the most 

814
00:42:57,800 --> 00:43:01,920
potential for at the moment 
specifically for solopreneurs to

815
00:43:01,920 --> 00:43:05,200
look into to find problems that 
can be solved? 

816
00:43:05,960 --> 00:43:09,800
Right now I feel like everyone 
is trying to figure out where 

817
00:43:09,800 --> 00:43:11,760
the gold is for Gen. 
AI. 

818
00:43:12,320 --> 00:43:16,400
So The funny thing is there is a
lot of educational content that 

819
00:43:16,400 --> 00:43:20,440
can be created for that. 
I feel like if you are have a 

820
00:43:20,440 --> 00:43:24,200
way of communicating either 
online and likely this is going 

821
00:43:24,200 --> 00:43:28,320
to be through video or even 
through newsletters and you know

822
00:43:28,320 --> 00:43:31,520
what the fundamentals are versus
what is specific to tooling and 

823
00:43:31,520 --> 00:43:34,480
you can really teach and 
educate, educate fundamentals, 

824
00:43:35,080 --> 00:43:38,320
then you probably are pretty 
well off if you're able to 

825
00:43:38,320 --> 00:43:41,000
package that. 
There are many platforms that 

826
00:43:41,000 --> 00:43:44,440
offer courses, structured 
courses for X amount of weeks 

827
00:43:44,440 --> 00:43:46,880
that will teach you a lot 
specifically in tech. 

828
00:43:47,480 --> 00:43:51,280
And the people facilitating 
those courses, they are making 

829
00:43:51,280 --> 00:43:54,840
bank, to be honest. 
Because me, for example, I get a

830
00:43:54,840 --> 00:43:57,520
study budget, I'm responsible 
for finishing that study budget 

831
00:43:57,520 --> 00:44:00,400
within the year. 
It means that I will be looking 

832
00:44:00,400 --> 00:44:05,560
for courses or conferences or 
specific things to spend that 

833
00:44:05,560 --> 00:44:08,080
money on. 
So any offerings that do that, 

834
00:44:08,080 --> 00:44:10,120
and if they're more companies 
like mine, which likely there 

835
00:44:10,120 --> 00:44:13,040
are, it just means that there is
money available to go to 

836
00:44:13,040 --> 00:44:15,880
education for people either for 
upskilling, reskilling or 

837
00:44:15,880 --> 00:44:20,000
whatever purpose. 
So I feel like education for AI 

838
00:44:20,120 --> 00:44:25,640
right now is, yeah, equivalent 
to people selling shovels in a 

839
00:44:25,640 --> 00:44:27,920
gold rush. 
Now that is it. 

840
00:44:27,920 --> 00:44:31,640
But for solar entrepreneurs then
specifically, it's quite 

841
00:44:31,640 --> 00:44:33,480
interesting. 
And it's not something I'm good 

842
00:44:33,480 --> 00:44:35,960
at. 
I'm not good at finding problems

843
00:44:35,960 --> 00:44:39,080
that in the end will be 
interesting for a multitude of 

844
00:44:39,080 --> 00:44:41,120
people. 
It's just not something I'm good

845
00:44:41,120 --> 00:44:43,160
at. 
I do know that a lot of people 

846
00:44:43,160 --> 00:44:45,560
are trailblazing. 
They are trying to figure out 

847
00:44:46,080 --> 00:44:48,040
where there is good product 
market fit. 

848
00:44:48,240 --> 00:44:50,760
And I feel like right now I'm 
not building enough. 

849
00:44:50,800 --> 00:44:52,160
I'm definitely not building 
enough. 

850
00:44:52,440 --> 00:44:54,600
Right now. 
It is easier than ever to build 

851
00:44:55,080 --> 00:44:59,160
to get a Moat. 
Not to get a Moat, but to build 

852
00:44:59,160 --> 00:45:02,600
something and then to find the 
Moat to find user problems and 

853
00:45:02,600 --> 00:45:05,520
to actually figure out if what 
you're building has value 

854
00:45:05,520 --> 00:45:07,640
because you can build and 
iterate so quickly. 

855
00:45:08,240 --> 00:45:12,400
So I don't know what it is in 
problems that are right now good

856
00:45:12,400 --> 00:45:14,840
to solve. 
I feel like education plays a 

857
00:45:14,840 --> 00:45:17,840
big part. 
I also feel like especially when

858
00:45:17,840 --> 00:45:22,560
it comes to kids and people 
going and teens with regards to 

859
00:45:22,560 --> 00:45:25,440
education, that is all going to 
evolve or I feel like it's quite

860
00:45:25,440 --> 00:45:28,200
behind. 
So there is an opportunity for 

861
00:45:28,200 --> 00:45:31,760
it to evolve. 
That might be the industries I 

862
00:45:31,760 --> 00:45:35,480
would look at specifically if I 
were to build a product. 

863
00:45:36,120 --> 00:45:38,920
In essence, if I am building a 
product, I would look at my own 

864
00:45:38,920 --> 00:45:41,840
interests. 
But yeah, it's very hard to find

865
00:45:41,840 --> 00:45:43,240
a problem that you then want to 
solve. 

866
00:45:43,800 --> 00:45:48,800
My interests, anime, fitness, 
nutrition, travel, a problem in 

867
00:45:48,800 --> 00:45:50,800
there. 
I don't know, to be honest. 

868
00:45:51,000 --> 00:45:54,920
I'm building up a little company
which I might share a lot more 

869
00:45:54,920 --> 00:45:57,160
about, but it has kind of 0 
tech. 

870
00:45:57,160 --> 00:46:00,080
Yes, we have a website, but a 
lot, a lot of it has to do with 

871
00:46:00,080 --> 00:46:02,600
community building. 
And those are very different 

872
00:46:02,600 --> 00:46:05,880
problems. 
So my biggest problem right now,

873
00:46:06,680 --> 00:46:09,880
the tech we have down my Co 
founder and I, it is getting 

874
00:46:09,880 --> 00:46:13,520
users, finding the right users. 
All right I have ideas but they 

875
00:46:13,520 --> 00:46:15,760
don't scale. 
I can go to meet ups but that's 

876
00:46:15,760 --> 00:46:19,560
just me physically. 
So how can I find users? 

877
00:46:21,720 --> 00:46:24,480
That's the hardest part. 
This is a meta question. 

878
00:46:24,480 --> 00:46:27,000
Do you like in the Q&A's? 
Do you like the Q's or the A's? 

879
00:46:27,680 --> 00:46:31,200
The funny thing is I like the 
questions that you ask to be 

880
00:46:31,200 --> 00:46:35,960
honest. 
And I then re listen to it and I

881
00:46:35,960 --> 00:46:38,400
figure out, do I like the answer
that I gave? 

882
00:46:38,480 --> 00:46:40,720
Am I just meandering? 
Am I just ranting? 

883
00:46:41,040 --> 00:46:42,920
Am I saying the same thing over 
and over again? 

884
00:46:43,080 --> 00:46:44,640
How's my delivery? 
All right? 

885
00:46:44,640 --> 00:46:46,640
Am I looking into the camera? 
Am I scratching my nose? 

886
00:46:46,640 --> 00:46:49,800
How's my posture? 
Oh, I should probably sit more 

887
00:46:49,800 --> 00:46:51,960
straight. 
Stuff like that I pay attention 

888
00:46:51,960 --> 00:46:54,400
to. 
And then I learn from how I am 

889
00:46:54,400 --> 00:46:58,600
perceived and that and doing 
that continuously has been a lot

890
00:46:58,600 --> 00:47:00,760
of growth for me personally and 
professionally. 

891
00:47:01,200 --> 00:47:03,640
So I like the cues. 
They make me think, they make me

892
00:47:03,640 --> 00:47:06,160
reflect, and then I like the end
result. 

893
00:47:06,480 --> 00:47:10,280
Maybe not even necessarily my 
answer, but going through that 

894
00:47:10,280 --> 00:47:11,760
process. 
I enjoy both. 

895
00:47:12,240 --> 00:47:16,240
So if you like you and A's, put 
your question in the comments so

896
00:47:16,240 --> 00:47:19,160
I can do more of them. 
What made you start this podcast

897
00:47:19,160 --> 00:47:22,040
while working? 
It was not my idea. 

898
00:47:22,600 --> 00:47:25,240
I will say that forever. 
I am quite transparent. 

899
00:47:25,240 --> 00:47:27,040
I'm quite honest. 
It was someone else's idea. 

900
00:47:27,520 --> 00:47:30,080
New person from marketing said a
podcast would be a great 

901
00:47:30,080 --> 00:47:31,760
platform to start sharing 
knowledge on. 

902
00:47:32,000 --> 00:47:34,040
And I'm looking for a host and 
I'll facilitate whatever you 

903
00:47:34,040 --> 00:47:38,080
need. 
And at that time, actually, my 

904
00:47:38,080 --> 00:47:42,560
grandparents had just passed 
away and I was focusing a lot on

905
00:47:42,560 --> 00:47:45,440
work and this seemed like a 
really cool opportunity. 

906
00:47:45,600 --> 00:47:47,960
I love listening to podcasts. 
I still do. 

907
00:47:48,400 --> 00:47:50,720
I listen a lot less. 
But back then I listened to so 

908
00:47:50,720 --> 00:47:53,400
many podcasts. 
It was always the thing that 

909
00:47:53,400 --> 00:47:57,080
while gaming would just be kind 
of educational content. 

910
00:47:57,480 --> 00:48:01,080
And even though I didn't listen 
to educational podcasts, I 

911
00:48:01,080 --> 00:48:04,280
genuinely listen to podcasts. 
PKA is one of them. 

912
00:48:04,280 --> 00:48:06,280
The old school gamers, they know
what I'm talking about. 

913
00:48:06,280 --> 00:48:10,080
Maybe, but it was just a group 
of three people, sometimes four 

914
00:48:10,080 --> 00:48:13,280
people with a guest talking to 
each other, talking shit, 

915
00:48:13,640 --> 00:48:16,600
talking about funny experiences 
was a lot of storytelling, was a

916
00:48:16,600 --> 00:48:20,840
lot about gaming. 
I learned a lot from that and 

917
00:48:20,840 --> 00:48:24,440
more than I realize because I 
learned a lot about engaging and

918
00:48:24,440 --> 00:48:27,720
communicating and storytelling 
and I learned a lot with regards

919
00:48:27,720 --> 00:48:31,320
to education, which is like 
little fun facts that are so 

920
00:48:31,320 --> 00:48:34,040
random, but they are somewhere 
anchored in my brain. 

921
00:48:34,680 --> 00:48:38,080
So the opportunity to do 
something that was similar, I 

922
00:48:38,080 --> 00:48:42,280
did not want to let that pass. 
I jumped on it immediately and 

923
00:48:42,280 --> 00:48:46,600
that's what started the podcast.
What were your strong opinions 

924
00:48:46,600 --> 00:48:49,040
about software development or 
tech in general? 

925
00:48:49,520 --> 00:48:54,720
Which changed Slash challenged 
after talking to guests on 

926
00:48:54,720 --> 00:48:58,240
podcasts. 
I'm going to take the most 

927
00:48:58,240 --> 00:49:00,920
recent example. 
And this is a conversation that 

928
00:49:00,920 --> 00:49:03,560
is not recorded yet. 
I hope it's going to get 

929
00:49:03,560 --> 00:49:04,880
recorded. 
The person has to get back to 

930
00:49:04,880 --> 00:49:07,520
me. 
But this is a person that has 

931
00:49:07,520 --> 00:49:11,440
worked in big tech and they are 
responsible as staff engineer 

932
00:49:11,920 --> 00:49:16,440
for topics like risk and safety.
As an engineer and to be honest,

933
00:49:16,440 --> 00:49:21,920
risk and safety, yeah, not 
really something I look forward 

934
00:49:21,920 --> 00:49:24,560
to. 
It's been in the way sometimes 

935
00:49:24,560 --> 00:49:27,040
when I'm trying to deliver, 
especially in bigger 

936
00:49:27,040 --> 00:49:29,560
organization like banks, for 
example. 

937
00:49:30,080 --> 00:49:33,040
So I was like, man, I don't know
if this is going to be an 

938
00:49:33,040 --> 00:49:36,640
interesting topic, but their 
perspective is with software, 

939
00:49:37,440 --> 00:49:38,920
things are not as black and 
white. 

940
00:49:39,280 --> 00:49:43,000
And that also means that you 
will not necessarily know if you

941
00:49:43,000 --> 00:49:46,080
are achieving an outcome. 
It is harder to measure right. 

942
00:49:46,520 --> 00:49:49,400
You're serving a certain user 
base and if they use it or not, 

943
00:49:49,680 --> 00:49:52,400
it's kind of up in the air. 
But if as an engineer, your 

944
00:49:52,400 --> 00:49:55,720
responsibility, your 
responsibility is safety and 

945
00:49:55,720 --> 00:49:59,280
risk, there's not a lot of grey 
area. 

946
00:49:59,400 --> 00:50:01,960
If there's something you cannot 
do, you need to make sure that 

947
00:50:01,960 --> 00:50:05,720
the software cannot do it. 
In essence, if you're then 

948
00:50:05,800 --> 00:50:08,360
bounded by that and the software
that you're creating or the 

949
00:50:08,360 --> 00:50:11,520
systems you're building, there 
is less room for error. 

950
00:50:11,800 --> 00:50:14,320
It is like doing software 
engineering with much higher 

951
00:50:14,320 --> 00:50:18,160
stakes, and I feel like it's 
like sports. 

952
00:50:18,920 --> 00:50:21,760
It could be software engineering
Olympics basically because you 

953
00:50:21,760 --> 00:50:25,480
have very different constraints.
And if you can still deliver in 

954
00:50:25,480 --> 00:50:30,280
such a way or still have output 
throughout many teams due to the

955
00:50:30,280 --> 00:50:34,840
system you have orchestrated 
that is safe and that mitigates 

956
00:50:34,840 --> 00:50:38,760
risk and people are not bothered
by it, then that's actually 

957
00:50:38,760 --> 00:50:41,040
quite cool. 
To be honest, that changed my 

958
00:50:41,040 --> 00:50:45,960
perspective because the best 
safety and risk in a software 

959
00:50:45,960 --> 00:50:49,360
delivery life cycle, if I'm an 
engineer, I don't want to 

960
00:50:49,360 --> 00:50:52,520
experience anything blocking 
what I'm trying to deliver, 

961
00:50:52,560 --> 00:50:53,760
right? 
Then it would be in the way. 

962
00:50:54,160 --> 00:50:57,320
But if the system is set up in 
such a way that I can deliver 

963
00:50:57,960 --> 00:51:02,200
and I don't even realize that 
everything is safe and the risk 

964
00:51:02,200 --> 00:51:05,000
has been mitigated, then that's 
actually quite cool. 

965
00:51:05,000 --> 00:51:09,040
I am fully enabled and I 
mentioned earlier I like helping

966
00:51:09,040 --> 00:51:11,280
people. 
Enabling people on that level is

967
00:51:11,280 --> 00:51:14,440
quite cool. 
So if you're responsible as 

968
00:51:14,440 --> 00:51:17,720
staff engineer, overseeing 
multiple systems, multiple teams

969
00:51:18,240 --> 00:51:21,880
and your mindset is I don't want
delivery to go down, I don't 

970
00:51:21,880 --> 00:51:24,160
want to throttle throughput, 
right? 

971
00:51:24,160 --> 00:51:26,720
I want people to excel and I 
want people to have the 

972
00:51:26,720 --> 00:51:29,280
fulfilment of delivery. 
However, these are the 

973
00:51:29,280 --> 00:51:31,720
constraints and that's what you 
accommodate for. 

974
00:51:32,280 --> 00:51:34,160
That's actually quite cool to be
honest. 

975
00:51:34,920 --> 00:51:37,520
What are your 3 to 5 
predictions? 

976
00:51:37,600 --> 00:51:41,920
Strong conviction about how AI 
will transform development slash

977
00:51:41,920 --> 00:51:44,960
employment. 
If writing code is outsourced to

978
00:51:44,960 --> 00:51:48,160
AI, what should be the new 
definition of 10X engineering? 

979
00:51:49,680 --> 00:51:52,440
Three to five? 
Man, you're asking asking me a 

980
00:51:52,440 --> 00:51:55,600
lot. 
I might give you 1 and this also

981
00:51:55,600 --> 00:51:58,800
comes from personal experience. 
I was responsible for product. 

982
00:51:59,120 --> 00:52:03,040
Then I went back to hands on for
close to half a year, mainly 

983
00:52:03,040 --> 00:52:05,960
because I was feeling FOMO, fear
of missing out. 

984
00:52:06,440 --> 00:52:08,840
Tooling had evolved. 
I was responsible for product 

985
00:52:08,840 --> 00:52:13,160
for a year and a half and I was 
talking to people that were 

986
00:52:13,160 --> 00:52:15,640
doing things and I was not doing
those same things. 

987
00:52:16,000 --> 00:52:19,040
I was not responsible building 
daily anymore because I was 

988
00:52:19,040 --> 00:52:21,920
responsible for product. 
So I wanted to go back to hands 

989
00:52:21,920 --> 00:52:25,520
on and the software development 
life cycle with AI tooling for 

990
00:52:25,520 --> 00:52:32,000
me changed because I was much 
less bothered by finding 

991
00:52:32,000 --> 00:52:34,320
information, by actually typing 
myself. 

992
00:52:34,800 --> 00:52:37,320
And I found this new way of 
working, which was me 

993
00:52:37,320 --> 00:52:41,440
orchestrating. 
Giving you an example, I would 

994
00:52:41,440 --> 00:52:43,640
be responsible for a certain 
ticket. 

995
00:52:44,040 --> 00:52:47,760
I would go to my CLII, would 
have my cloud code set up to go 

996
00:52:47,760 --> 00:52:50,360
to my ticketing system. 
Doesn't matter if it's JIRA. 

997
00:52:50,360 --> 00:52:52,720
In our case, it was linear. 
I would say we're going to pick 

998
00:52:52,720 --> 00:52:55,000
up this thing. 
We need to make a plan. 

999
00:52:55,400 --> 00:52:58,040
These are my ideas. 
These are the constraints. 

1000
00:52:58,600 --> 00:53:01,160
Let's create a plan together of 
what that would look like. 

1001
00:53:01,160 --> 00:53:04,120
I need you to think about these 
things, and that's what I would 

1002
00:53:04,120 --> 00:53:07,000
start with. 
Then I would have a plan and 

1003
00:53:07,000 --> 00:53:09,320
context. 
Specifically with AI tooling, it

1004
00:53:09,320 --> 00:53:12,080
spoils like milk, the fresher 
the better, basically. 

1005
00:53:12,480 --> 00:53:14,600
So with that context, I would 
have a plan. 

1006
00:53:14,600 --> 00:53:17,640
I would put that in Markdown. 
Nowadays there's more automated 

1007
00:53:17,640 --> 00:53:20,560
ways of doing so, but this is 
back in the day when I was doing

1008
00:53:20,560 --> 00:53:24,840
it, which is still a few months 
ago, but still plan and 

1009
00:53:24,840 --> 00:53:27,240
markdown. 
I would open up a new context. 

1010
00:53:27,240 --> 00:53:30,000
I would say senior software 
engineer characteristics. 

1011
00:53:30,520 --> 00:53:31,680
We're going to execute this 
plan. 

1012
00:53:31,920 --> 00:53:34,640
I would execute the plan. 
I would review it myself. 

1013
00:53:34,800 --> 00:53:36,560
The plan would be executed quite
quickly. 

1014
00:53:36,760 --> 00:53:39,000
Sometimes there was a little bit
of back and forth with regards 

1015
00:53:39,000 --> 00:53:41,280
to OK, we need to think about 
these things. 

1016
00:53:41,280 --> 00:53:43,320
Do you have a preference? 
Do you have a decision? 

1017
00:53:43,320 --> 00:53:45,520
We need to come to a decision on
this thing. 

1018
00:53:45,520 --> 00:53:49,080
We need to decide. 
It's like a buddy Claude code 

1019
00:53:49,080 --> 00:53:51,720
and I, it's a lot of fun. 
To be honest, I found a lot of 

1020
00:53:51,720 --> 00:53:53,840
joy in it. 
Once something was executed, I 

1021
00:53:53,840 --> 00:53:57,120
would review it myself. 
I would actually ask to make the

1022
00:53:57,120 --> 00:53:59,760
changes if I found some things, 
or sometimes I would manually 

1023
00:53:59,760 --> 00:54:01,440
change it if I thought that was 
faster. 

1024
00:54:02,040 --> 00:54:04,560
And then a pull request would go
and my colleagues would have 

1025
00:54:04,560 --> 00:54:07,480
feedback. 
And again, with cloud code, new 

1026
00:54:07,480 --> 00:54:10,080
context, we have built this 
thing. 

1027
00:54:10,120 --> 00:54:12,160
This is the feedback. 
Let's go through the feedback 1 

1028
00:54:12,160 --> 00:54:14,200
by 1 and see what we want to do 
with it. 

1029
00:54:15,320 --> 00:54:18,800
That would be my software 
development life cycle in the 

1030
00:54:18,800 --> 00:54:21,640
smaller sense from picking up a 
ticket, building testing, 

1031
00:54:22,080 --> 00:54:24,360
reviewing. 
There would always be unit tests

1032
00:54:24,360 --> 00:54:26,600
or integration tests in the 
build process as well. 

1033
00:54:28,040 --> 00:54:33,240
Then to make that a smoother 
process, I would take the review

1034
00:54:33,240 --> 00:54:36,720
remarks and I would say these 
are review remarks on the work 

1035
00:54:36,720 --> 00:54:39,720
that we have done. 
Can we build a skill so next 

1036
00:54:39,720 --> 00:54:42,880
time we can accommodate for the 
review remarks that are 

1037
00:54:42,880 --> 00:54:46,720
typically on pull requests that 
we've created specifically. 

1038
00:54:47,000 --> 00:54:50,200
So yeah, I don't want to do the 
same thing over and over again. 

1039
00:54:50,200 --> 00:54:53,440
If there's something that 
happens twice or three times, 

1040
00:54:53,440 --> 00:54:56,080
there might be a pattern. 
So I would take that and I would

1041
00:54:56,080 --> 00:54:59,400
build a skill specific to that. 
So my next cycle would be if 

1042
00:54:59,400 --> 00:55:02,320
we've built something Claude 
code and I I would execute the 

1043
00:55:02,320 --> 00:55:05,480
review skill. 
So with that skill and with some

1044
00:55:05,480 --> 00:55:09,120
of the remarks that we have 
distilled, we would see is the 

1045
00:55:09,120 --> 00:55:12,040
code actually fine? 
And then I would take the review

1046
00:55:12,040 --> 00:55:14,240
skill and I would take the code 
and I would make a code 

1047
00:55:14,240 --> 00:55:17,400
convention skill specifically. 
And I can use that when I'm 

1048
00:55:17,400 --> 00:55:20,040
creating a planning 
documentation on what we 

1049
00:55:20,040 --> 00:55:23,440
actually need to execute. 
So continuously I was in this 

1050
00:55:23,440 --> 00:55:26,960
life cycle of picking, picking 
up a ticket, executing, 

1051
00:55:26,960 --> 00:55:30,080
reviewing, figuring out what are
conventions or what are review 

1052
00:55:30,080 --> 00:55:33,760
remarks that are distillable and
can be conventions and then 

1053
00:55:33,760 --> 00:55:36,400
making skills for those or 
refining the existing skills 

1054
00:55:36,400 --> 00:55:40,000
that I had. 
And when that was smooth, I 

1055
00:55:40,000 --> 00:55:42,960
could do that in one terminal, I
could do some research, and in 

1056
00:55:42,960 --> 00:55:45,280
another terminal I could do 
execution. 

1057
00:55:45,440 --> 00:55:50,440
I could copy the code base that 
I was working on multiple times 

1058
00:55:50,440 --> 00:55:53,600
locally to have multiple 
terminals, both doing research 

1059
00:55:53,600 --> 00:55:56,400
and execution in parallel. 
I know you can do that with get 

1060
00:55:56,400 --> 00:55:58,120
work trees. 
I didn't really look at it. 

1061
00:55:58,120 --> 00:56:01,320
The fastest way for me to do it,
copy the repository. 

1062
00:56:01,640 --> 00:56:04,760
So yeah, probably at some point 
I need to figure out how get 

1063
00:56:04,760 --> 00:56:08,360
work trees work. 
But there's not much downside to

1064
00:56:08,360 --> 00:56:10,360
this, to be honest. 
And it worked quite well. 

1065
00:56:11,320 --> 00:56:15,040
That was my life cycle and in 
essence in explaining all of 

1066
00:56:15,040 --> 00:56:17,400
this I have forgotten the 
question. 

1067
00:56:19,520 --> 00:56:23,320
My prediction is that this life 
cycle will hold or this life 

1068
00:56:23,320 --> 00:56:27,240
cycle will more evolve. 
And I've already seen people 

1069
00:56:27,240 --> 00:56:32,120
labeling this as vibe coding. 
I've people go seen go beyond 

1070
00:56:32,520 --> 00:56:36,480
where they figure out to turn 
figure out a way to turn vibe 

1071
00:56:36,480 --> 00:56:40,040
coding into vibe engineering 
where the system that creates 

1072
00:56:40,040 --> 00:56:44,320
the software also self reflects 
with the same conventions and 

1073
00:56:44,320 --> 00:56:46,880
creates a whole system instead 
of just one feature 

1074
00:56:46,920 --> 00:56:48,760
specifically. 
Very cool. 

1075
00:56:49,080 --> 00:56:51,880
I feel like that is more of the 
future engineers will be 

1076
00:56:51,880 --> 00:56:55,240
responsible for engineering. 
Engineering has not become 

1077
00:56:55,440 --> 00:56:58,240
easier. 
Creating code has become easier.

1078
00:56:58,240 --> 00:57:01,920
So yes, we can engineer more, 
but engineering is still the 

1079
00:57:01,920 --> 00:57:04,760
same challenge. 
And you're an engineer, you're 

1080
00:57:04,760 --> 00:57:08,680
not a code monkey. 
So something else is now coding.

1081
00:57:09,160 --> 00:57:10,880
You're still engineering a 
system. 

1082
00:57:12,520 --> 00:57:13,880
That's my prediction. 
I'll give you 1. 

1083
00:57:14,480 --> 00:57:18,960
I typically don't do many 
predictions because there's the 

1084
00:57:18,960 --> 00:57:23,880
stubborn part of me not wanting 
to be wrong, but also I have to 

1085
00:57:24,280 --> 00:57:27,280
kind of feeling that it's going 
to be very hard for me to 

1086
00:57:27,280 --> 00:57:34,240
predict the right thing. 
So yeah, last question, are you 

1087
00:57:34,240 --> 00:57:37,520
satisfied with the growth on all
social media platforms? 

1088
00:57:38,320 --> 00:57:46,640
I'm assuming with regards to the
podcast Satisfied, I don't think

1089
00:57:46,680 --> 00:57:51,920
like I have a weird relationship
with Satisfied or like maybe 

1090
00:57:51,920 --> 00:57:55,840
content because I have ambition 
and I feel like I can go above 

1091
00:57:55,840 --> 00:57:58,560
and beyond, which means 
sometimes I'm never happy with 

1092
00:57:58,560 --> 00:58:02,520
growth and I think always I 
could have done better or we can

1093
00:58:02,520 --> 00:58:06,000
do better or yeah, that's just 
how I am. 

1094
00:58:06,000 --> 00:58:09,520
I raise the bar or I try to. 
It doesn't mean I'm not happy 

1095
00:58:09,520 --> 00:58:13,360
with where I am now, it means 
that I feel like I can do a lot 

1096
00:58:13,360 --> 00:58:14,960
more. 
Like that's just the drive that 

1097
00:58:14,960 --> 00:58:20,920
I have when it comes to numbers.
I was incredibly happy going on 

1098
00:58:20,920 --> 00:58:26,520
YouTube specifically to from 
zero to 1000 subscribers. 

1099
00:58:27,320 --> 00:58:31,720
And now the podcast has like 
50,000 subscribers and each 

1100
00:58:31,720 --> 00:58:33,920
video has like thousands of 
views. 

1101
00:58:33,920 --> 00:58:35,880
Like the number has just become 
a number for me. 

1102
00:58:36,440 --> 00:58:39,600
I'm happy with people commenting
saying I genuinely learned 

1103
00:58:39,600 --> 00:58:42,760
something from it or I 
absolutely disagree because of 

1104
00:58:42,760 --> 00:58:46,800
XY and Z because it gives me 
perspective, it shows me growth 

1105
00:58:47,520 --> 00:58:50,160
and I'm genuinely having fun 
talking to people. 

1106
00:58:50,680 --> 00:58:54,920
I feel like I could be way 
bigger of a podcast if I would 

1107
00:58:54,960 --> 00:58:57,480
have applied the learnings I 
know now very early at the 

1108
00:58:57,480 --> 00:58:59,000
beginning but that is 
impossible. 

1109
00:58:59,320 --> 00:59:02,280
I cannot go back in time. 
It is what it is right now and I

1110
00:59:02,280 --> 00:59:06,360
hate when people say it is what 
it is, but in essence, I know 

1111
00:59:06,360 --> 00:59:08,480
what I know and I'm very 
thankful for those learnings. 

1112
00:59:08,960 --> 00:59:12,080
And if I ever start something 
new, I can apply those learnings

1113
00:59:12,080 --> 00:59:14,280
from the start. 
And I'm happy that I'm still 

1114
00:59:14,280 --> 00:59:18,120
learning and I'm still 
experimenting specifically on 

1115
00:59:18,120 --> 00:59:21,120
things like Twitter or LinkedIn 
on my personal accounts. 

1116
00:59:21,480 --> 00:59:25,160
I feel like I could have grown 
to a much larger audience there,

1117
00:59:26,360 --> 00:59:28,080
but I'm just, it drains me 
sometimes. 

1118
00:59:28,680 --> 00:59:32,240
Like I, I had the idea of 
creating weekly LinkedIn posts 

1119
00:59:32,760 --> 00:59:35,960
and I, I followed through on 
that for a long time, but in the

1120
00:59:35,960 --> 00:59:38,720
end it was just draining. 
I was not doing it because I was

1121
00:59:38,720 --> 00:59:41,240
enjoying it. 
I was doing it for numbers. 

1122
00:59:41,920 --> 00:59:45,400
And once I realized I was doing 
that for numbers is also when I 

1123
00:59:45,400 --> 00:59:48,320
stopped doing that. 
In essence, I don't need to 

1124
00:59:48,320 --> 00:59:51,760
reach numbers on LinkedIn 
doesn't in it's not enjoyable. 

1125
00:59:52,360 --> 00:59:55,320
I don't, I see a lot of benefits
there, but it because it just 

1126
00:59:55,320 --> 00:59:59,600
doesn't give me energy with the 
podcast, I don't do a lot to 

1127
00:59:59,600 --> 01:00:03,520
contribute towards growth. 
In essence, probably because it 

1128
01:00:03,520 --> 01:00:06,040
doesn't give me joy, but also I 
don't have a team. 

1129
01:00:06,400 --> 01:00:09,960
So I have to make decisions. 
I have to do the things that 

1130
01:00:09,960 --> 01:00:12,840
give me the most energy, 
otherwise it is not going to be 

1131
01:00:12,840 --> 01:00:15,760
sustainable. 
And because I don't have a team 

1132
01:00:15,760 --> 01:00:19,640
or I don't have a big team, I 
should say, if I don't enjoy it 

1133
01:00:19,640 --> 01:00:22,240
anymore, the whole thing like a 
House of Cards, just it 

1134
01:00:22,240 --> 01:00:26,960
crumbles, which is a big risk. 
But in essence, my podcast, I do

1135
01:00:26,960 --> 01:00:28,920
have to enjoy it. 
So I do the things I enjoy. 

1136
01:00:29,520 --> 01:00:32,480
So yeah, am I happy? 
Yes, I'm very happy. 

1137
01:00:33,000 --> 01:00:36,040
To be honest. 
I'm very thankful because there 

1138
01:00:36,040 --> 01:00:38,080
will be no podcast without an 
audience. 

1139
01:00:38,080 --> 01:00:40,040
And the fact that the podcast 
now has an audience, a 

1140
01:00:40,080 --> 01:00:42,400
community, people that are 
watching, people that are 

1141
01:00:42,400 --> 01:00:45,200
listening, people that are 
sending in questions to gain my 

1142
01:00:45,200 --> 01:00:47,480
perspective, I'm very thankful 
for that. 

1143
01:00:48,040 --> 01:00:50,920
So yeah, if you're still here, 
thank you for listening. 

1144
01:00:51,360 --> 01:00:53,480
I love doing Q&A's. 
If you have more questions, put 

1145
01:00:53,480 --> 01:00:55,480
them in the comments. 
This has been it. 

1146
01:00:55,560 --> 01:00:58,560
I've done Q&A's now back-to-back
because of the amount of 

1147
01:00:58,560 --> 01:01:00,960
questions we had and I'm really 
thankful for that. 

1148
01:01:01,160 --> 01:01:02,880
So see you next time.