文字稿 🔗
WEBVTT
NOTE
Transcription provided by Podhome.fm
Created: 06/24/2026 19:35:47
Duration: 2218.632
Channels: 1
1
00:00:06.240 --> 00:00:08.160
And I've been following
2
00:00:08.480 --> 00:00:12.320
your career for a while. Heard you're also on dot net rocks and stuff
3
00:00:12.480 --> 00:00:17.305
back in the day. I've been also doing software development for a couple decades.
4
00:00:18.824 --> 00:00:23.625
As you've also been in the industry for a long time now as well.
5
00:00:23.865 --> 00:00:24.425
Yeah.
6
00:00:25.305 --> 00:00:27.384
What have you been up to lately?
7
00:00:27.785 --> 00:00:32.400
Yeah. So it's interesting. Our team, so I work on James Montemagno's
8
00:00:32.400 --> 00:00:44.720
team at Microsoft. We've moved around a bit, but we do the same thing. So a few years ago, I was mostly focused on dot net community, and then over time, that expanded to dev dev community.
9
00:00:46.114 --> 00:00:49.234
And dev dev was kinda all across developer division.
10
00:00:49.394 --> 00:00:50.995
And then as of this year,
11
00:00:51.635 --> 00:00:52.675
unsurprisingly,
12
00:00:52.675 --> 00:00:53.795
we're focused on
13
00:00:54.274 --> 00:00:55.714
agentic development.
14
00:00:56.515 --> 00:00:57.074
So,
15
00:00:57.954 --> 00:00:58.355
honestly,
16
00:00:58.910 --> 00:01:05.630
agentic development is kind of part of everything developers do anyways nowadays. It impacts just about everything.
17
00:01:05.950 --> 00:01:09.790
So so, really, it's a community team,
18
00:01:10.110 --> 00:01:10.670
and
19
00:01:11.085 --> 00:01:13.965
community is a lot of different things. So
20
00:01:14.525 --> 00:01:15.405
sometimes
21
00:01:15.325 --> 00:01:20.525
like this morning, I've been helping with I help run a few of the blogs at Microsoft.
22
00:01:20.525 --> 00:01:21.805
I coordinate,
23
00:01:21.805 --> 00:01:23.165
do editorial review,
24
00:01:24.490 --> 00:01:26.490
basically manage the blogs.
25
00:01:28.330 --> 00:01:34.010
And then, also, I help run external events. I help run internal events. I write content.
26
00:01:34.330 --> 00:01:34.970
This
27
00:01:35.530 --> 00:01:36.970
year, I've been focused
28
00:01:37.295 --> 00:01:40.734
a lot more than in the past on internal
29
00:01:40.734 --> 00:01:42.255
kind of evangelism.
30
00:01:42.814 --> 00:01:45.374
Okay. And Yeah. Basically helping
31
00:01:45.935 --> 00:01:53.370
you know, it's a big shift, this kinda agentic development world. It's a big shift for everybody, including people inside Microsoft.
32
00:01:53.450 --> 00:01:54.810
And that includes,
33
00:01:55.290 --> 00:01:58.890
you know, traditional software developers, but then it also includes
34
00:01:59.130 --> 00:02:00.090
PMs,
35
00:02:00.090 --> 00:02:00.890
marketing,
36
00:02:01.050 --> 00:02:02.330
legal, like,
37
00:02:03.050 --> 00:02:05.610
And I'm working with a lot of people that are,
38
00:02:06.090 --> 00:02:07.210
say, in marketing,
39
00:02:07.975 --> 00:02:09.655
have never written code before,
40
00:02:09.895 --> 00:02:19.254
and they're writing a lot of code or they're using a lot of code. You know? Yeah. Yeah. You know? And, you know, maybe they're using, Scout or maybe they're using Gab Copilot.
41
00:02:20.019 --> 00:02:21.380
Semisurprisingly,
42
00:02:21.540 --> 00:02:24.740
a lot of people are using Copilot CLI
43
00:02:25.299 --> 00:02:27.940
for, like, PM or,
44
00:02:28.580 --> 00:02:31.140
marketing roles, things like that. And
45
00:02:31.379 --> 00:02:34.580
they're they're getting a lot done, and they also wanna be more,
46
00:02:36.745 --> 00:02:38.185
let me see,
47
00:02:38.425 --> 00:02:44.665
intentional about what they're doing. You know? They wanna they're kinda like, okay. Things are kinda working, but what can I do a little better?
48
00:02:45.305 --> 00:02:49.800
So we we, like, last week, we ran this internal conference. We had,
49
00:02:50.120 --> 00:02:52.440
look the numbers, I think, about, like, 3,000
50
00:02:52.840 --> 00:03:05.055
views on this internally, and I think we can do more in the future. But it it was pretty cool to see people all across the company coming together and just learning. We had, like, a who's who of all the top people.
51
00:03:05.855 --> 00:03:16.255
You know? We had keynote with Scott Hansen, and then, you know, just all kind of Of course. Yeah. Real session. I learned a ton, honestly. And, I mean, this is my job, but I still learned a ton. So
52
00:03:17.450 --> 00:03:30.170
Yeah. But that's kinda what this is. Right? When you teach, you learn, and you keep learning. And, also, this stuff is so new, and it keeps evolving so quickly. Right? It does. It really does, and it it kinda helps to have a,
53
00:03:30.810 --> 00:03:32.730
a perspective that learns from
54
00:03:33.495 --> 00:03:35.415
history. And, you know, like,
55
00:03:35.895 --> 00:03:40.215
we take our existing experience in with good software development practices
56
00:03:40.215 --> 00:03:55.480
and good, you know, like, this is what a good program should look like, and this is this is the kind of code that's okay to just do a quick one off, and I don't care what the code looks like. And for this other project, I really do care what the code looks like. And I want tests, and I want quality and a software, like,
57
00:03:55.959 --> 00:03:57.720
lifecycle and things like that.
58
00:03:58.280 --> 00:03:58.920
So
59
00:03:59.365 --> 00:04:07.045
you know, we take all that, but we also have to take a lot of humility in now because things are changing. And a lot of things that I think
60
00:04:07.525 --> 00:04:08.645
were accurate
61
00:04:08.725 --> 00:04:13.365
a month ago are not anymore. You know? And so I always have to kind of
62
00:04:13.810 --> 00:04:15.890
take a lot of that into,
63
00:04:16.610 --> 00:04:24.130
both my intuition and then when I'm talking to people, hey. Here's what I think is the right way to do this, or here's what I think this feature
64
00:04:24.450 --> 00:04:26.210
set is. It may be
Load full transcript
different.
65
00:04:27.405 --> 00:04:33.005
So Yeah. It's a that's a very strange thing. So I do a lot of GitHub Copilot
66
00:04:33.405 --> 00:04:35.965
workshops for developers now for customers.
67
00:04:36.365 --> 00:04:44.740
And every time I do one, I the day before, I just open everything up again and then I take a look at where the buttons are now or which new buttons are there.
68
00:04:45.220 --> 00:04:50.740
And almost always, there's one clever guy or gal there and she says,
69
00:04:50.979 --> 00:05:05.605
well, you know what? No. It's probably more like this. And I'm like, yeah. You're you're probably right. Yeah. Yeah. New insight. Because also the question is, you know, we're just talking into a text box basically. Right? So, it's not rocket science. It is natural language.
70
00:05:05.765 --> 00:05:14.210
They made it super easy for us to use this stuff. But then everybody's asking themselves like, how can I use this better? What's the magic sauce?
71
00:05:14.290 --> 00:05:25.570
And then there's all these things like skills and custom instructions and custom agents and MCP servers. Mhmm. But also, those are not rocket science. It's all markdown stuff.
72
00:05:26.050 --> 00:05:31.665
But what do you think? Are they still very important or or not so much anymore?
73
00:05:31.905 --> 00:05:42.690
I think they're a lot more important than we've given them credit for. And I think that's becoming more obvious now when people are caring about and being charged at the token level.
74
00:05:43.090 --> 00:05:43.810
And
75
00:05:44.289 --> 00:05:54.210
in the past, you know, we were all operating in startup mode, it's like, who cares about tokens? Just have a loop run all weekend and just burn a million tokens. You know? And
76
00:05:54.974 --> 00:06:02.655
I think now we're starting to think more about, like, how can we be more efficient? I've really been I've written a lot of MCPs.
77
00:06:02.974 --> 00:06:05.615
I've been writing a lot of skills.
78
00:06:06.495 --> 00:06:07.935
I'm also,
79
00:06:08.335 --> 00:06:10.094
like, doing a lot of things with,
80
00:06:10.789 --> 00:06:11.350
oh,
81
00:06:11.590 --> 00:06:12.310
like,
82
00:06:13.830 --> 00:06:16.630
workflows and, you know, GitHub actions
83
00:06:16.789 --> 00:06:19.110
and Yeah. You know, really trying to
84
00:06:19.590 --> 00:06:22.710
think about anything that I can do deterministically,
85
00:06:23.110 --> 00:06:23.990
do with
86
00:06:24.295 --> 00:06:28.775
an EXE or a script or something. So, like, just this past,
87
00:06:29.895 --> 00:06:38.390
this past few days, I was writing up a report on this conference, and I was like, hey. I want a bunch of screenshots from all these
88
00:06:38.710 --> 00:06:44.070
all these videos. And the videos are all in SharePoint and you know? So but I was like, hey.
89
00:06:44.470 --> 00:06:55.885
I could use AI and just say, please go get a bunch of screenshots. But then I thought about it. I'm like, wait. This is super inefficient, and I don't know what I'm gonna get. And it may run for a half hour and then give me trash.
90
00:06:56.285 --> 00:06:58.525
So instead, I had it write a script,
91
00:06:59.005 --> 00:07:02.685
get screenshots from five and fifteen minutes into one video.
92
00:07:03.349 --> 00:07:08.069
Okay. That looks good. Now do it for all the videos. You know? And and,
93
00:07:08.470 --> 00:07:12.229
so I'm I'm just really focusing a lot more. That's something I,
94
00:07:12.470 --> 00:07:14.949
like, as a, you know, tech evangelist, really
95
00:07:15.270 --> 00:07:19.585
think is something I want to be, you know, speaking about and and communicating
96
00:07:19.745 --> 00:07:21.105
better is like, hey.
97
00:07:23.025 --> 00:07:31.025
Things that you the the getting the right balance between what an LLM is good at and what deterministic code is good at is really important.
98
00:07:31.710 --> 00:07:35.470
It's gonna be it's gonna save you money, but it's also going to give you more
99
00:07:35.790 --> 00:07:39.070
predictable results. Higher quality results too.
100
00:07:39.550 --> 00:07:43.310
Yeah. And and, yeah, higher quality equals less tokens.
101
00:07:43.645 --> 00:07:44.525
Exactly.
102
00:07:44.525 --> 00:07:49.805
Exactly. Because you're not repeating work. You know, we we've all kind of we're going through this,
103
00:07:51.085 --> 00:08:09.200
this growing up phase of working with LON. And the first kind of hello world is like you talk into a chat box, and it actually gives you back useful results. And you're like, woah, this is crazy. Like, I remember I remember closing every chatbot for years because they were stupid. And then all of a sudden, one time on ChatGPT,
104
00:08:09.440 --> 00:08:33.870
people are like, hey, try this ChatGPT, and I did something, and it worked. I'm like, this is crazy. But then after a bit, we we think, hey. This is not super productive typing. Like, for instance, I would, way back in the day, like, type chat, write this function. No. That's not right. Do it again. No. Do it again. And and so that's that's a really, like, naive way of doing it. Right? And then we're kinda growing up over time to
105
00:08:34.430 --> 00:08:36.190
I started working more with, like,
106
00:08:37.105 --> 00:08:48.225
do some things and do pull requests and have the pull request do a co code review. You know? And then and then over time, it's like, hey. What can we automate in terms of those GitHub actions? And,
107
00:08:48.865 --> 00:08:51.985
you know, just working with this whole kind of
108
00:08:52.940 --> 00:08:58.780
you know, really kinda seeing it as more of, like, an outsource or, like, you're working with another
109
00:08:59.100 --> 00:09:01.580
you know, someone else is writing code. That's fine.
110
00:09:02.060 --> 00:09:13.725
We've done this and other you know, this isn't completely new to collaborate with another developer. No. Now let's put quality into the process. Like, I want unit tests. I want,
you know, like, I want,
111
00:09:14.445 --> 00:09:19.325
like, rubber duck style reviews. Different people review each other's code, etcetera. So
112
00:09:20.180 --> 00:09:22.420
Yeah. So it's it's basically like you're
113
00:09:22.579 --> 00:09:24.420
outsourcing it to some
114
00:09:25.620 --> 00:09:35.779
some country, your software development. Right? Exactly. You're not sure what you're gonna get back, and you don't know about the quality. Not really. Right. And I've done this at a lot of other jobs in the past, and sometimes
115
00:09:36.075 --> 00:09:40.955
the problem is my fault because I didn't give clear clear specs. Right? You know? And
116
00:09:41.435 --> 00:09:50.955
so, like, it really comes down to instead of saying build me a website, it's, hey. I want you know, I'll actually start now with a
117
00:09:50.490 --> 00:09:55.210
PRD, a product requirements document. And I'll I'll say, here's
118
00:09:55.850 --> 00:10:00.090
you know, I'll work with AI to write a a document in markdown
119
00:10:00.410 --> 00:10:05.370
with very clear, like, here's what I want. Here are some references. Here's some similar
120
00:10:05.875 --> 00:10:09.235
existing projects, websites, open source software, or whatever.
121
00:10:09.715 --> 00:10:11.715
Here are the acceptance criteria.
122
00:10:11.715 --> 00:10:12.755
Here's the,
123
00:10:13.715 --> 00:10:14.995
you know, initial,
124
00:10:15.635 --> 00:10:28.510
phase delivery and then future possible things. And and so really hammer that out and then say, okay. Iterate on phase one. Right? And and the quality is so much better because
125
00:10:28.990 --> 00:10:43.055
it doesn't go off and build me something in PHP because I never told it. Right? So Okay. You know, if I say actually say, no. You know, I want it in this language. I want with this testing format. I want this, you know, color scheme, whatever. Right? So
126
00:10:43.774 --> 00:10:58.140
Yeah. Exact and and that is already spec driven development kind of. Right? Because you make a spec, and then you you do the thing. And we've we should have always been doing this. Exactly. And that's part of the thing is that, you know, AI is good at
127
00:10:58.620 --> 00:10:59.740
predictable
128
00:11:00.395 --> 00:11:04.715
grunt work. So things that are frustrating and boring, and that's things like,
129
00:11:04.875 --> 00:11:05.595
you know,
130
00:11:06.475 --> 00:11:12.075
writing up specs and writing unit tests and, you know, writing documentation
131
00:11:12.155 --> 00:11:13.195
and doing
132
00:11:13.550 --> 00:11:14.510
architectural
133
00:11:14.510 --> 00:11:27.949
reviews for duplicate code. And, you know, all these things that are Yeah. Not hard work. They're just boring, and we all hated it. So we didn't do it enough. You know? And so now it's a time where we can just put that in the process and start integrating that.
134
00:11:28.935 --> 00:11:35.175
Yeah. Yeah. So I see that a lot in companies as well, where they have to
basically go back into their processes
135
00:11:35.335 --> 00:11:39.095
and mature themselves with more specifications,
136
00:11:39.175 --> 00:11:45.900
more unit tests, more quality controls around what they're doing. Because now they hire these outsourced developers
137
00:11:45.980 --> 00:11:54.380
who work somewhere in a data center in The US somewhere, and you don't know what you're going to get back. Usually it's amazing, but you need some more control.
138
00:11:54.700 --> 00:11:55.580
We all need
139
00:11:55.855 --> 00:11:59.775
you know, learn to grow up. So and we're all learning because it's super early.
140
00:12:00.175 --> 00:12:11.375
You know? And on on the one hand, like, part part of that sounds really boring. Right? But then the the nice thing is that allows me to focus on the fun part, which is the creative part.
141
00:12:11.960 --> 00:12:18.280
So, like, on, you know, weekends and evenings, I've been building I've I've built a game for my,
142
00:12:18.840 --> 00:12:22.920
my Quest three VR headset. I've built a iPad,
143
00:12:23.240 --> 00:12:25.240
stationary bike app. I've built,
144
00:12:26.285 --> 00:12:32.524
you know, games with Godot. I've been building, you know, just, like, websites, all kinds of fun stuff.
145
00:12:32.925 --> 00:12:48.330
And I get to focus on, like, what is the game script? Is this game fun? How can I, you know, add a zombie mode to my biking app? Like, whatever. You know? And and that's the fun part. And I have tons of unit tests, and I have tons of specs, and I have tons of quality steps
146
00:12:48.970 --> 00:12:58.925
so that I don't have to think about that stuff. You know? Yeah. And what's your favorite, let's say, modality to use, GitHub Copilot in this case? I
147
00:12:59.085 --> 00:13:04.205
bounce around a lot, and partly because that's my job. I need to be able to Mhmm. Keep up with everything.
148
00:13:05.380 --> 00:13:10.180
Lately, I have been using a lot of Copilot CLI and Versus Code,
149
00:13:10.740 --> 00:13:14.260
and partly that's because of just, like, the different
150
00:13:14.500 --> 00:13:16.980
projects I'm working in. But
151
00:13:17.060 --> 00:13:25.205
I do, of course, use I use the the new GitHub app. I've been really liking the canvases in there, which are pretty fun. I made a canvas for Squad.
152
00:13:25.365 --> 00:13:30.805
I don't I don't know if you've looked at Squad, but I made, like, a dashboard for Squad, and it keeps track of all the different things.
153
00:13:31.845 --> 00:13:37.180
And then, of course, Visual Studio. I use Visual Studio a lot for things like modernization.
154
00:13:37.660 --> 00:13:44.300
Yeah. I was really good at that stuff. But, I'd have to say a lot of the time, I'm just using Copilot CLI
155
00:13:44.300 --> 00:13:52.405
with Squad. I for my personal projects, I've been really liking using Squad and, like, dialing in the,
156
00:13:53.845 --> 00:13:54.885
the different
157
00:13:55.125 --> 00:14:02.085
Squad members and, you know, having, like, ones that are very focused with all the skills. You know, the front end designer has,
158
00:14:02.405 --> 00:14:09.730
say, like, specific skills, and the and the tester has and so then they can be very efficient, use just the right model.
159
00:14:10.850 --> 00:14:13.090
And and it's really fun to just kinda
160
00:14:13.570 --> 00:14:19.855
set it all up and then say, like, implement phase three, and then go have a copy and come back. Yeah.
161
00:14:21.615 --> 00:14:26.415
Yeah. For for listeners to who don't know what SQUAD is, it is
162
00:14:26.894 --> 00:14:30.175
kind of this open source framework by Brady Gaster.
163
00:14:30.254 --> 00:14:39.560
Mhmm. He still owns it, I think. He does. He co run runs it. There's, I think, Tamir, and there's several other people that contribute to it. Mhmm. And
164
00:14:40.360 --> 00:14:50.565
it's based on I think there's some other kind of similar things and other AI kind of there's, I think, Gastown and some things like that. The general idea is you have
165
00:14:51.925 --> 00:14:53.685
you have agents
166
00:14:54.404 --> 00:14:57.845
in it working together in a team, like collaborative team,
167
00:14:58.165 --> 00:14:59.605
and you have a coordinator,
168
00:15:00.200 --> 00:15:07.320
and then you have specific roles. So you'll have, like, a front end dev and a back end dev and a and an architect and a tester.
169
00:15:08.760 --> 00:15:09.400
And,
170
00:15:10.440 --> 00:15:18.085
you know, I've seen some kinda people say, oh, that sounds silly. And, you know, I I kinda get it, and I kinda like, once I work with it enough
171
00:15:18.485 --> 00:15:21.365
and got it tuned in just right for my projects,
172
00:15:21.605 --> 00:15:25.285
I get it. You know? Like, it really and the the important thing is
173
00:15:26.020 --> 00:15:26.740
that
174
00:15:27.300 --> 00:15:28.420
LLMs
175
00:15:28.580 --> 00:15:38.420
are constrained by context. Right? There's only and so over time, as you keep chatting back and forth, you're building up all this context. And then in order to like,
176
00:15:38.985 --> 00:15:47.545
when that context gets full, then we have to compact it. And so then we lose some of the information because we've compressed down that that chat.
177
00:15:47.945 --> 00:15:53.385
And so over time, we're kind of always battling this problem of, like, so much context
178
00:15:54.190 --> 00:15:56.430
going back and forth in the conversation.
179
00:15:56.750 --> 00:15:58.670
And what's really cool with these
180
00:15:59.230 --> 00:16:07.390
sub agents is that we can really focus the context. So I can have issues assigned to a sub agent, and the sub agent is is
181
00:16:08.225 --> 00:16:18.385
not concerned with any of the other thing. You know? Like, if the front end agent doesn't worry about other things, they can ask the other agent or it can get a summary from something. But it
182
00:16:18.704 --> 00:16:25.860
and and also, it can be very tuned as far as
what the skills are, what MCPs it works with, what language
183
00:16:25.860 --> 00:16:32.100
model it's using. And so because of that, like, for instance, if I have a scribe role or a Git,
184
00:16:32.660 --> 00:16:45.935
you know, a role that's just focused on my Git history and things like that, it can be a very fast model. It doesn't need to be super smart. I don't need to waste tokens, and I can also use a very tuned model, you know, that's very quick. So
185
00:16:46.735 --> 00:16:57.120
so that's one of those things, again, where just like in the real world, you wouldn't just hire one super genius to build your project for. You you'd probably hire a team, and the team would have,
186
00:16:57.519 --> 00:16:59.519
you know, peep and and also,
187
00:17:00.240 --> 00:17:11.505
you can tell I'm getting all excited about this. But it is fun. You can have, like, the the agents can learn over time, and you can say, like, hey. I didn't like what you did with all the purple gradients there.
188
00:17:11.825 --> 00:17:17.665
This is the style I'm going for. I want you to remember this. And that specific agent will make that note.
189
00:17:18.385 --> 00:17:21.410
So, you know, it sounds like I'm selling Brady's
190
00:17:22.050 --> 00:17:27.410
project, and I do like it. But it's really more of a pattern. And, you know, it's just built using
191
00:17:27.490 --> 00:17:29.010
markdown and skills
192
00:17:29.090 --> 00:17:29.650
and,
193
00:17:30.930 --> 00:17:31.730
you know, like,
194
00:17:32.765 --> 00:17:35.645
it's it's just a pattern that you can use anywhere.
195
00:17:36.125 --> 00:17:39.165
GitHub actions and things like that. But the idea is like,
196
00:17:39.325 --> 00:17:42.365
hey. If we orchestrate things so that we've got
197
00:17:43.165 --> 00:17:53.090
you know, these are front end skills. These are back end skills. These are architectural skills, testing skills, etcetera. Then you can split that off, and you can you can be more hyper focused with that. Yeah.
198
00:17:53.649 --> 00:17:59.009
Yeah. Yeah. It's very cool, and, it it's been out for quite a while. So I really am wondering
199
00:17:59.169 --> 00:18:01.409
if this will ever get absorbed
200
00:18:01.409 --> 00:18:12.905
into the product as a feature or or some sort of template or something like that or a spin off product. I don't know. Yeah. I know that the teams talk together a lot, and there are some specific
201
00:18:13.705 --> 00:18:18.585
features in in Copilot for, like, fleet mode and some of these other specific
202
00:18:19.100 --> 00:18:22.140
they're they enable the general ideas,
203
00:18:22.940 --> 00:18:25.660
but they're not and so I know that they're kinda
204
00:18:25.900 --> 00:18:27.340
figuring out because they also
205
00:18:28.460 --> 00:18:30.299
squad is kinda prescriptive
206
00:18:30.620 --> 00:18:44.134
and may not fit in specifically with some people. So so at a product level, I think they're trying to get that sort of balance right. But
I think generally across, you know, not just the copilot world, but the AI development world, that's a
207
00:18:44.535 --> 00:18:45.894
a thing that
208
00:18:46.500 --> 00:18:51.139
it's it's not the right thing for every project, but it's the right thing for a lot of projects.
209
00:18:51.300 --> 00:18:51.779
Yeah.
210
00:18:52.180 --> 00:18:53.220
Yeah. Definitely.
211
00:18:53.380 --> 00:18:54.500
Yeah. It's interesting.
212
00:18:54.820 --> 00:18:59.140
So we're evolving so incredibly fast. Like yeah.
213
00:18:59.715 --> 00:19:06.274
If we zoom out now, right? So we have this whole thing that now developers have a new tool basically to be more productive.
214
00:19:06.515 --> 00:19:09.634
Companies as well where they can stick AI into
215
00:19:10.755 --> 00:19:18.729
applications with, I don't know, with Foundry, Microsoft Agent Framework, things like that to create a chatbot or something more interesting perhaps.
216
00:19:18.970 --> 00:19:19.769
We
217
00:19:20.330 --> 00:19:21.690
see all this happening
218
00:19:21.929 --> 00:19:23.690
also with customers that we
219
00:19:24.490 --> 00:19:31.129
talk to from our side. It's very interesting. But if we zoom back out, right, this is one major technology
220
00:19:31.985 --> 00:19:32.785
evolution,
221
00:19:32.785 --> 00:19:33.585
revolution.
222
00:19:33.905 --> 00:19:35.105
We've seen more.
223
00:19:35.345 --> 00:19:39.665
Like, back in the day, we had cloud, for instance, was kind of a new I
224
00:19:40.065 --> 00:19:46.240
love that you brought that up. I'm sorry to jump in, but this is something I've been thinking too lately is people act like this is
225
00:19:47.280 --> 00:19:54.240
out of like, we've never had this happen before. We've never gone through this. And the cloud revolution was huge. You know? And there were a lot of different
226
00:19:54.480 --> 00:20:04.565
ones over time, you know, even going 16 to 32 to 64 bit and, like Yeah. You know, open source. And, I mean, we've gone through a lot of big software revolutions.
227
00:20:04.565 --> 00:20:09.605
Outsourcing was a big thing for a while where it was like, oh, no. This is gonna change everything.
228
00:20:09.765 --> 00:20:10.565
Yeah. And,
229
00:20:11.285 --> 00:20:11.605
you know,
230
00:20:13.100 --> 00:20:19.580
even the Internet, it kinda the cloud wave went in some big phases and, you know, like things like,
231
00:20:21.100 --> 00:20:29.215
oh, I don't know, the the JavaScript revolution, you know, where JavaScript all of a sudden was running everything. We're like, how did that happen? So
232
00:20:29.455 --> 00:20:48.460
it it is it is important to, like, take it seriously and to really kind of, like, not ignore it and just say, like, I I don't do AI. Like, it's that would be the same as saying, like, I don't believe the Internet exists or, you know, like Yeah. I I think you have to recognize that it's there, but also,
233
00:20:50.460 --> 00:20:55.325
I don't know. Put it in context and think about,
like, hey. We've gone through
234
00:20:55.565 --> 00:21:02.605
change. The whole software development industry has been a period of rapid change, you know, over the past couple decades.
235
00:21:03.005 --> 00:21:07.885
So so we we had big ones. Right? Like clouds. Big one. Mhmm. We still have,
236
00:21:08.580 --> 00:21:13.940
know, you still companies that are still hybrid or moving to the cloud, for instance, for all sorts of reasons.
237
00:21:14.260 --> 00:21:15.940
We had smaller ones like
238
00:21:16.659 --> 00:21:18.580
big data, smaller ones. Oh, yeah.
239
00:21:19.059 --> 00:21:26.325
Remember? The big data. Mobile first was also one of the things. That's right. That's right. Yeah. The metaverse
240
00:21:26.325 --> 00:21:28.245
kind of thing that never really,
241
00:21:28.485 --> 00:21:29.685
really did anything.
242
00:21:29.845 --> 00:21:30.565
Yeah. And
243
00:21:31.205 --> 00:21:33.605
now there's this thing. So do
244
00:21:33.765 --> 00:21:35.205
you think this is different
245
00:21:35.950 --> 00:21:39.470
profoundly, than, let's say, cloud? Because that's kind of a big one.
246
00:21:39.950 --> 00:21:41.790
That is a tough question.
247
00:21:41.950 --> 00:21:44.030
I do think it is profoundly different,
248
00:21:44.190 --> 00:21:44.750
but
249
00:21:47.070 --> 00:21:49.230
I think some of it is that this is
250
00:21:51.235 --> 00:21:54.115
this has more of an opportunity to accelerate.
251
00:21:55.795 --> 00:21:57.315
Cloud can so
252
00:21:57.875 --> 00:22:01.154
for instance, a cloud was an architectural change,
253
00:22:01.315 --> 00:22:05.730
and while speed kinda continued to go up and we have more computers network together,
254
00:22:07.890 --> 00:22:09.090
the cloud
255
00:22:09.410 --> 00:22:13.169
you know, well, some of the patterns and things have changed over the past
256
00:22:13.410 --> 00:22:15.409
decade or so, but it's not like
257
00:22:15.890 --> 00:22:20.095
a fundamentally different cloud now than it was ten years ago, say.
258
00:22:20.655 --> 00:22:21.375
Whereas,
259
00:22:22.895 --> 00:22:26.174
large language models, I do feel like we're still
260
00:22:27.934 --> 00:22:35.240
we've been growing in terms of what the models do. I I kinda feel like we're on this edge of, like, some sort of architectural
261
00:22:35.240 --> 00:22:35.880
shift
262
00:22:36.280 --> 00:22:37.080
and,
263
00:22:37.960 --> 00:22:41.240
where it's it's likely to keep accelerating more.
264
00:22:41.480 --> 00:22:43.560
And then I I do wonder about things like,
265
00:22:44.205 --> 00:22:49.164
you know, quantum as quantum gets thrown into the mix with with AI. Right? And
266
00:22:49.885 --> 00:22:51.804
I think there are some huge
267
00:22:52.684 --> 00:22:53.804
opportunities
268
00:22:53.804 --> 00:22:54.364
for
269
00:22:55.965 --> 00:22:56.524
for
270
00:22:56.765 --> 00:23:04.769
you you know, like, when the math nerds all of a sudden are like, hey. We found a way to make things twice as fast or twice as whatever. So I I feel like we're,
271
00:23:05.330 --> 00:23:09.809
in a way, kinda scratching the surface of what large language model technology is.
272
00:23:10.610 --> 00:23:10.850
Yeah.
273
00:23:11.815 --> 00:23:19.895
So I don't I mean, that that's kind of gut driven. That's kind of a hunch sort of feel. But I do feel like this is a bigger change partly because
274
00:23:20.775 --> 00:23:23.895
software development is all about code.
275
00:23:24.055 --> 00:23:26.615
It's implemented in code and everything, and
276
00:23:27.809 --> 00:23:32.769
large language models are extremely good at writing code. So it's
277
00:23:33.409 --> 00:23:34.849
the whole loop of
278
00:23:35.409 --> 00:23:45.155
I'm stuck. Go look it up on Google and Stack Overflow. Find some code. Paste it in. It didn't quite work. Okay. Do this. It's instant now. Right? And
279
00:23:45.955 --> 00:23:52.355
I was thinking about the this past you know, like, a week ago, I ran into something that was frustrating me in PowerToys,
280
00:23:52.355 --> 00:23:54.355
which is in c plus plus
281
00:23:54.929 --> 00:24:05.729
and or the the thing was and I'm like, I'll just fix it. Right? And I, like, iterated. And, of course, I was very careful. I haven't written production c plus plus in a long, long time.
282
00:24:06.049 --> 00:24:07.969
But I feel like I actually,
283
00:24:08.210 --> 00:24:12.524
like, got this thing done in a short amount of time relatively.
284
00:24:12.684 --> 00:24:13.244
And,
285
00:24:14.924 --> 00:24:23.164
I I guess where I'm going with this is that that I feel like we're going to be changing the building blocks of software development
286
00:24:23.245 --> 00:24:25.165
using large language models
287
00:24:25.380 --> 00:24:26.580
in a way that
288
00:24:27.940 --> 00:24:38.260
that accelerates more, if that makes sense. Yeah. Yeah. I'm still figuring this out. I don't know the answer, but it just feels a little bit of a bigger shift than some of those other ones were.
289
00:24:38.420 --> 00:24:44.684
Some of those two were a a little bit style driven. Like, hey. It's mobile first. Okay. That's a consumer
290
00:24:45.085 --> 00:24:45.885
preference.
291
00:24:45.885 --> 00:24:49.565
Right? You know? And it's like, hey. I would like things to work better on my phone.
292
00:24:50.205 --> 00:24:52.925
Whereas large language models open up
293
00:24:53.570 --> 00:24:54.610
whole new
294
00:24:55.250 --> 00:25:10.825
things where, like, people are who aren't even develop my younger brother is not a trained software developer, and he's building something with Python run running on a Raspberry Pi that it's like, this could be a product you could sell. You know? I mean, it's it so it's kind of really
295
00:25:11.225 --> 00:25:12.424
a big shift.
296
00:25:13.465 --> 00:25:17.144
Yeah. Yeah. I I think so too. That it's very different.
297
00:25:17.305 --> 00:25:18.265
Because if you look like,
298
00:25:18.745 --> 00:25:20.184
at cloud, for instance,
299
00:25:20.425 --> 00:25:22.184
that is very deterministic.
300
00:25:22.260 --> 00:25:34.820
These are products that we now sell. You just move your stuff. Your your computer is just now over there instead of over there. Yeah. And we package it nicely so that you can use it easily. And that kept evolving, of course, but still it's deterministic.
301
00:25:34.820 --> 00:25:43.725
You just do it or you don't. Yeah. And now we're in this strange world where we talk to things that predict predict the next words, and it's nondeterministic.
302
00:25:43.965 --> 00:25:46.285
And I think as humans, we have a bit of
303
00:25:47.405 --> 00:25:48.684
trouble adjusting
304
00:25:49.165 --> 00:25:51.870
to this this world of nondeterministic
305
00:25:51.870 --> 00:25:59.630
technology that kinda does stuff, and it can do a lot. It's yeah. It is wild. And and I think intuitively,
306
00:25:59.630 --> 00:26:01.470
I kept thinking of it.
307
00:26:03.015 --> 00:26:06.774
It took me a while to realize it's just text in and text out.
308
00:26:07.095 --> 00:26:09.414
There's no, like, okay. It
309
00:26:09.655 --> 00:26:23.899
acts like it's text in and text out, but it's really doing some other things. It's like, no. It's really just predicting the next token. You know? And Yeah. We keep we keep adding layers on top of it with better harnesses and better system prompts and better,
310
00:26:24.139 --> 00:26:24.779
you know,
311
00:26:25.500 --> 00:26:32.220
corrections and tuning. But at the end of the day, it's just a big predictive model of what's the next token.
312
00:26:33.035 --> 00:26:33.754
Yeah.
313
00:26:34.635 --> 00:26:38.875
So you mentioned that you're you're teaching this also to non techies
314
00:26:38.955 --> 00:26:52.960
Mhmm. Within the company as well as perhaps also outside of the company. Yeah. Yeah. So where's kind of the the line of, you know, when do they use, let's say, Office three Copilot three sixty five, which is the business version,
315
00:26:53.280 --> 00:26:53.919
versus,
316
00:26:54.720 --> 00:26:59.120
GitHub Copilot? Because you can kinda use both, right, for almost anything.
317
00:26:59.600 --> 00:27:06.114
Yeah. That's also a slightly tricky question because, like you said, we have multiple GitHub Copilot,
318
00:27:06.595 --> 00:27:10.114
some things to go. Right? And I feel like
319
00:27:11.475 --> 00:27:13.475
what what I try and
320
00:27:14.370 --> 00:27:26.370
I try and look at what is the most comfortable, easy fit for the thing you're doing right now. Right? So, like That's good. My family, you know, I'll show them Copilot on the desktop or the web Copilot app. You know?
321
00:27:27.490 --> 00:27:27.970
And then,
322
00:27:29.005 --> 00:27:38.124
you know, that's a quick, like, I can get started, and I can use this basically like a better Google, you know, kind of Yeah. Okay. So I feel like that's a nice kind of
323
00:27:38.765 --> 00:27:43.180
if you're doing office work, I look at m three sixty five Copilot.
324
00:27:43.180 --> 00:27:47.419
You know? And then with more sophisticated users like Scout.
325
00:27:48.140 --> 00:27:50.220
And that's because it's connecting to,
326
00:27:50.700 --> 00:27:52.460
you know, company resources
327
00:27:52.460 --> 00:27:53.980
and and that sort of stuff.
328
00:27:54.795 --> 00:27:58.554
And then I do feel like if you're doing anything code related,
329
00:27:58.715 --> 00:28:00.635
it really helps to be in
330
00:28:01.195 --> 00:28:03.035
an environment that understands
331
00:28:03.035 --> 00:28:09.799
code base. So, like, that's where, you know, GitHub Copilot is really productive because it
332
00:28:10.200 --> 00:28:14.039
can figure out the Git history. It has my entire context
333
00:28:14.279 --> 00:28:16.919
of files in the solution or project
334
00:28:17.000 --> 00:28:20.600
or folder. Right? And, like so that was something where
335
00:28:21.095 --> 00:28:24.054
I mentioned my younger brother was building something with Python,
336
00:28:24.215 --> 00:28:28.534
and he was doing everything in a really long chat GPT conversation.
337
00:28:28.775 --> 00:28:36.790
And that kinda works, but it kinda doesn't after a while because it loses the context, and it's, you know, it's doesn't really
338
00:28:37.910 --> 00:28:42.789
so I I kinda steered him over to working in Versus Code. And and,
339
00:28:43.030 --> 00:28:52.164
you know, it's like, look. Here now you have all your files in one folder, and now I've got a cleaner context. Right? So I feel like that's
340
00:28:52.645 --> 00:28:56.085
but it really is kind of a where do you feel most comfortable? And,
341
00:28:56.325 --> 00:28:59.044
you know, we we got that question internally
342
00:28:59.125 --> 00:29:07.870
at that conference. It was like, hey. You have all these different you know, do I use Copilot CLI or the GitHub app, or do I use Versus Code? And it's like, well,
343
00:29:10.030 --> 00:29:18.225
get get familiar with the different ones, and then use the one that feels best at the time. And I very often will start a project.
344
00:29:19.025 --> 00:29:25.905
A lot of the time my flow is, I'll just pop into the Copilot, the web app, and I'll say, hey. I'm thinking about this sort of project.
345
00:29:26.065 --> 00:29:27.585
Is there something similar already?
346
00:29:28.690 --> 00:29:36.770
You know, how would it work? What would and I'll iterate for a bit, and then I'll think, I think I actually wanna build this. I'll say, write me a markdown block
347
00:29:36.850 --> 00:29:38.930
that I can paste in as a PRD.
348
00:29:39.170 --> 00:29:41.490
And then I'll pop into, like, Copilot CLI.
349
00:29:42.165 --> 00:29:42.805
And
350
00:29:43.445 --> 00:29:44.245
depending
351
00:29:44.245 --> 00:29:49.685
if I'm feeling like I'm ready to you know, where I'm at, I'll I'll initialize a squad, and I'll say,
352
00:29:50.245 --> 00:29:51.605
here's a PRD.
353
00:29:52.565 --> 00:30:00.419
Start this project. And then, you know, let get things going. And then after a bit, I'll say, I really wanna dig into this code more. And then I'll pop into,
354
00:30:00.820 --> 00:30:08.005
you know, Versus Code or Visual Studio and, like, get the whole view of it. So and then, you know, so I really feel like it's
355
00:30:08.005 --> 00:30:09.524
nice to like,
356
00:30:10.005 --> 00:30:15.284
you're not stuck in any of them, especially when you're developing code. Right? You can bounce around. You can
357
00:30:16.005 --> 00:30:24.090
and so a lot of time, I'll have, say, Versus Code and Copilot CLI open, and I'll work with both of them. Because it's all the code's,
358
00:30:24.409 --> 00:30:32.890
you know, in the same directory. It's I've got a git, you know, keeping me safe as long as I'm committing regularly and you know? So
359
00:30:33.625 --> 00:31:00.659
yeah. Yeah. Yeah. Don't have I don't have a super clear like, I can talk about, well, if you if you wanna look if you wanna work at the chat level and you wanna manage multiple sessions and and things like that, you might work with GitHub app more. And if you wanna, you know, work more if you're in a space where command line is kinda feeling simpler, you know, then Copilot's got and if you have an existing code pace, you might wanna pop open Versus Code or Visual Studio and kinda,
360
00:31:01.225 --> 00:31:08.664
you know, make it easier to see your kinda code context. And so but, really, I feel like it's just like whenever I feel
361
00:31:09.625 --> 00:31:12.664
yeah. I'm a little constrained here. I'm a little claustrophobic.
362
00:31:12.664 --> 00:31:29.280
Right? I wanna break out. I wanna move to the world that you know? So so and and GitHub Copilot's with you in any of those places is, you know, like, marketing thing, I think. So it's like the same models, the same context. As long as you're preserving things in markdown docs or issues or whatever,
363
00:31:29.600 --> 00:31:31.360
it just goes with you anyways.
364
00:31:31.520 --> 00:31:35.825
So Yeah. Yeah. And and even sessions sync now to GitHub.
365
00:31:35.825 --> 00:31:39.745
So per perhaps they can also sync to different clients in a bit.
366
00:31:40.145 --> 00:31:44.225
And, you know, another thing too there is, well, it feels like
367
00:31:45.750 --> 00:31:47.909
this large language model is
368
00:31:48.310 --> 00:32:02.455
conscious, and it's sitting there in this chat with you. It really is kinda like a stateless web where every single chat question that goes in, it's a brand new thing. Right? And so it, in a way, it doesn't really matter. As long as I'm preserving
369
00:32:02.695 --> 00:32:03.815
my context,
370
00:32:04.135 --> 00:32:07.575
my issues, my session state like you're talking about, then
371
00:32:08.295 --> 00:32:15.830
my next chat, even if I switch harnesses and go from CLI to Versus Code, it's the same thing. Know? Hey.
372
00:32:16.309 --> 00:32:23.269
Now I wanna fix this issue. Okay. Go ahead. You know? And Yeah. Yeah. I I think
that's where it's going. Definitely. Mhmm. Yeah. Mhmm.
373
00:32:23.909 --> 00:32:24.470
Okay.
374
00:32:25.110 --> 00:32:27.270
As we we're nearing the end here,
375
00:32:27.904 --> 00:32:36.065
you've already given lots of advice and talking about also non techies and stuff. So what would you advise somebody
376
00:32:36.225 --> 00:32:46.020
that's kinda in tech or maybe not, and and has heard of AI but is kinda still on the fence like, nah. You know what? I'll sit this one out. Let's see what the next thing is. What would you say to them?
377
00:32:47.620 --> 00:32:48.260
Well,
378
00:32:48.820 --> 00:32:49.860
I would
379
00:32:52.180 --> 00:32:59.924
I guess, like, I've I've recommended in a lot of things over time is, like, give it a try in something small. Give it a try in something fun.
380
00:33:01.845 --> 00:33:03.605
For instance, my younger daughter,
381
00:33:03.765 --> 00:33:05.924
you know, has written a a
382
00:33:06.405 --> 00:33:15.190
game for her college project. I said, hey. Let's sit at the kitchen counter, and let's work on building a game, or let's build a website together.
383
00:33:15.590 --> 00:33:21.350
It is really helpful if you do have a nerdy friend who's already using stuff effectively.
384
00:33:21.429 --> 00:33:22.950
Just sit down together
385
00:33:23.270 --> 00:33:25.590
and solve a problem together. You know?
386
00:33:26.275 --> 00:33:42.749
I think it is don't don't focus on the like, it's very easy to get caught up in the who's winning now in this race, who's who's the biggest player, who's the you know? Like, none of that matters. What what works for you when you're solving a project?
387
00:33:43.549 --> 00:33:45.389
I do recommend using
388
00:33:46.590 --> 00:33:49.070
AI modes if it's, you know, if it's,
389
00:33:49.549 --> 00:33:50.350
Copilot
390
00:33:50.350 --> 00:33:56.985
consumer or if it's Google Gemini or whatever. Try using that instead of Google searches
391
00:33:57.225 --> 00:34:02.345
and use it for all kinds of things. I use it for cooking recipes. I use it for
392
00:34:02.585 --> 00:34:10.600
figuring out, you know, home repair problems. Like, just all sorts of things like that. Right? Yeah. And so so I I feel like that is a good
393
00:34:11.880 --> 00:34:17.160
a good first step for consumers. It's just instead of Google searches and kinda
394
00:34:17.400 --> 00:34:18.520
trial and error,
395
00:34:19.000 --> 00:34:23.224
use those those sorts of things. And then for developers,
396
00:34:23.224 --> 00:34:24.185
I recommend
397
00:34:25.065 --> 00:34:25.705
trying
398
00:34:26.345 --> 00:34:40.340
trying a project but thinking about it like you would in real professional software development. Meaning, don't say build me a website, and then it builds a bad website, and then you say AI is terrible. Think about like you communicate with a junior developer.
399
00:34:40.420 --> 00:34:42.340
Right? And write up a
400
00:34:42.580 --> 00:34:44.020
a detailed plan
401
00:34:44.420 --> 00:34:49.865
and then iterate through it. And the same way that you would kind of build trust with a a
402
00:34:50.105 --> 00:34:51.145
new developer
403
00:34:51.305 --> 00:35:06.240
where you wouldn't say, go build an entire project. I'll check when you're done. Say, like, implement the first thing. Implement this. And, you know, like, and then over time, as you build up that velocity, then you say, okay. Now spec out phase two.
404
00:35:06.640 --> 00:35:10.880
Implement phase two, you know, and kind of step back as as you go.
405
00:35:11.280 --> 00:35:13.520
And I do one final thing is
406
00:35:14.424 --> 00:35:16.025
for enterprises,
407
00:35:16.025 --> 00:35:17.865
for people wanting to use this in
408
00:35:18.585 --> 00:35:19.944
production environments,
409
00:35:19.944 --> 00:35:21.145
focus on
410
00:35:21.704 --> 00:35:22.585
quality
411
00:35:22.984 --> 00:35:24.905
things that you haven't been doing,
412
00:35:25.625 --> 00:35:28.200
like unit tests, like documentation,
413
00:35:28.840 --> 00:35:30.120
like architectural
414
00:35:30.120 --> 00:35:30.920
reviews,
415
00:35:31.160 --> 00:35:31.960
like, you
416
00:35:32.360 --> 00:35:33.880
know, performance analysis,
417
00:35:33.880 --> 00:35:37.240
benchmarks, things like that that are not gonna break your application,
418
00:35:37.880 --> 00:35:40.600
but are likely to actually improve
419
00:35:40.600 --> 00:35:41.240
your quality.
420
00:35:41.934 --> 00:35:42.575
And
421
00:35:42.815 --> 00:35:54.734
once you get familiar with those and comfortable with those, that also makes it easier to implement AI because you've got all those safety nets of, you know, your unit tests and, you know, all those even documentation.
422
00:35:54.734 --> 00:35:56.734
AI can read your documentation
423
00:35:56.734 --> 00:36:02.760
to build better code. Right? So if you have good quality docs, that improves your velocity there too.
424
00:36:03.480 --> 00:36:07.800
Okay. That that's great. Yeah. That's great stuff. Okay.
425
00:36:07.800 --> 00:36:10.280
Thank you very much. So where can people
426
00:36:10.520 --> 00:36:11.960
go and connect with you?
427
00:36:13.145 --> 00:36:15.545
That's a trickier thing.
428
00:36:18.025 --> 00:36:26.665
Social media has got a little crazy. I'm on Blue Sky mostly. I've been thinking about getting more involved in LinkedIn
429
00:36:26.660 --> 00:36:27.860
kinda in the future.
430
00:36:29.460 --> 00:36:32.660
But and then, you know, also at conferences.
431
00:36:32.660 --> 00:36:33.140
Whenever
432
00:36:33.460 --> 00:36:37.380
I'm at conferences, love to chat with people, come up, and say hi.
433
00:36:37.780 --> 00:36:38.340
So
434
00:36:38.740 --> 00:36:46.355
Okay. Real real world preference. Yeah? Yep. That's good. Just just go and say hi. That's we will do that. There you go. Excellent.
435
00:36:46.595 --> 00:36:49.075
Alright. And thank you very much for this conversation.
436
00:36:49.817 --> 00:36:51.256
This was great. Thanks, Barry.