अनुलिपि 🔗
WEBVTT
NOTE
Transcription provided by Podhome.fm
Created: 06/19/2026 13:44:39
Duration: 2106.749
Channels: 1
1
00:00:08.720 --> 00:00:09.360
Okay.
2
00:00:10.639 --> 00:00:11.679
Looks like it's going.
3
00:00:12.559 --> 00:00:14.400
It is. So hi. Welcome.
4
00:00:14.955 --> 00:00:17.115
Thank you. Yeah. Thank you so much. This
5
00:00:18.875 --> 00:00:20.395
is the first time that we meet.
6
00:00:20.635 --> 00:00:24.395
So maybe I'll introduce myself a little bit so that you know who I am.
7
00:00:25.355 --> 00:00:29.755
I'm Barry. I'm a cloud solution architect working for Microsoft, The Netherlands.
8
00:00:30.560 --> 00:00:32.960
I just started there in March.
9
00:00:33.120 --> 00:00:37.760
It's now April, but it feels like a year ago because it's
10
00:00:38.239 --> 00:00:41.280
well, you you work for a big company. You know how it goes.
11
00:00:41.840 --> 00:00:43.199
Yeah. Everything changes fast.
12
00:00:44.055 --> 00:00:50.935
Yeah. It's crazy. Learn so much, do so much stuff, see so many customers. It's it's lots of fun.
13
00:00:51.575 --> 00:00:55.335
So maybe you can take it from there and tell us who you are.
14
00:00:55.895 --> 00:00:56.935
Yeah. Absolutely.
15
00:00:57.490 --> 00:01:02.850
My name is Brittany Ellich. Thank you so much for chatting with me. This is exciting.
16
00:01:03.490 --> 00:01:06.610
I am a staff engineer at GitHub.
17
00:01:06.770 --> 00:01:09.410
I am currently working in the enterprise space,
18
00:01:09.490 --> 00:01:16.065
and I'm very just passionate about using AI to make things work better.
19
00:01:16.145 --> 00:01:24.065
I think that, you know, if you're an engineer right now, this is a really this is, like, the exciting space to be in. So yeah. Isn't it cool? Yeah.
20
00:01:25.130 --> 00:01:34.250
It's it's so cool. It's just such an exciting time. That's also why I kinda joined Microsoft now because this is the most exciting time I've seen
21
00:01:34.570 --> 00:01:36.490
since I've been working in software.
22
00:01:36.970 --> 00:01:38.330
It's just so much fun.
23
00:01:38.810 --> 00:01:40.810
So how did you end up at GitHub?
24
00:01:41.945 --> 00:01:47.465
Yeah. I've been at GitHub for almost four years now. And I
25
00:01:47.865 --> 00:01:57.520
was previously working for a as a software engineer at a medical education company. It was pretty small. And I've done I've done a couple of other gigs too.
26
00:01:58.320 --> 00:02:00.880
And, yeah, I was very excited about GitHub
27
00:02:00.880 --> 00:02:03.280
to get into developer tools.
28
00:02:03.520 --> 00:02:09.280
And that was my first foray into it, and I realized that I actually really enjoy working on developer tools. And
29
00:02:09.974 --> 00:02:27.290
I like GitHub specifically because the product is very engineering driven, and so I feel like I get to sort of flex my, like, product skills in addition to my engineering skills, which is really fun. So I worked on GitHub actions for the first two years, and now I am in the enterprise space.
30
00:02:28.330 --> 00:02:31.290
Ah, what does that mean in the enterprise space?
31
00:02:31.610 --> 00:02:33.450
I work in billing,
32
00:02:33.530 --> 00:02:38.115
which is, like, it's just every it's one of the things that falls under under enterprise.
33
00:02:38.595 --> 00:02:40.755
And so, like, looking at things like enterprise
34
00:02:41.475 --> 00:02:42.275
licensing
35
00:02:42.275 --> 00:02:47.475
and subscriptions and things like that. I specifically do most of my work on metered billing, which means,
36
00:02:48.275 --> 00:02:50.355
like, the usage based billing, like,
37
00:02:51.155 --> 00:02:51.715
Copilot
38
00:02:52.290 --> 00:02:59.170
requests and actions things and stuff. So, like, each one of those needs a line item to bill for it, and that's that's what I work on.
39
00:02:59.890 --> 00:03:00.930
Ah, okay.
40
00:03:01.250 --> 00:03:04.050
And and how do you do that? Do you use AI?
41
00:03:05.095 --> 00:03:06.135
Oh,
42
00:03:06.135 --> 00:03:08.535
I mean, we use AI quite a bit for
43
00:03:09.255 --> 00:03:10.135
development,
44
00:03:10.295 --> 00:03:11.015
definitely.
45
00:03:11.495 --> 00:03:20.490
But one of the things that's kind of interesting about working in billing, like, in a lot of other roles that I've had, you really worry about things like speed or,
46
00:03:22.170 --> 00:03:31.770
you know, some other engineering metric. Like, it's the most important thing, and you're always driving towards that. Whereas in billing, the the speed at which people get billed is a little bit less important, and it's more about accuracy.
47
00:03:32.815 --> 00:03:37.135
So that's sort of the thing that you're always optimizing for is trying to make sure that the
48
00:03:37.535 --> 00:03:41.055
amount that people are billed for is as accurate as possible.
49
00:03:41.695 --> 00:03:44.575
And that gets really complicated when you have, you know,
50
00:03:45.470 --> 00:03:47.710
many, many, many millions of event
51
00:03:48.030 --> 00:03:50.430
all the time. Yeah.
52
00:03:50.590 --> 00:03:52.350
It's hard to do, but it's fun.
53
00:03:53.310 --> 00:03:56.590
Yeah. I can imagine. That is such an interesting space, though.
54
00:03:57.150 --> 00:04:03.345
Because, yeah, it doesn't really matter if it's a minute later that you show it. It just needs to be super duper accurate.
55
00:04:03.505 --> 00:04:11.425
Yep. Yeah. Yep. Which is really hard in a distributed system, actually, to optimize for accuracy because there are so many things that can go wrong
56
00:04:11.825 --> 00:04:22.450
and so many ways that you can miss. Usually, if something goes wrong, then you on the side of underbilling. But, like, you also don't wanna do that because that means that your company's making less money. So
57
00:04:23.490 --> 00:04:28.050
avoiding overbilling is a lot a much easier problem than avoiding underbilling.
58
00:04:28.850 --> 00:04:32.665
Uh-huh. Yeah. So if you make a mistake and you underbill,
59
00:04:32.825
Load full transcript
--> 00:04:33.465
then
60
00:04:33.785 --> 00:04:38.905
GitHub can lose millions. Yeah. It's true. Yeah. We try not Yeah. To do
61
00:04:39.625 --> 00:04:40.505
No pressure.
62
00:04:40.905 --> 00:04:46.290
Yeah. It's it's pretty interesting too. I like the fact that there's a lot of different customers for it.
63
00:04:46.690 --> 00:04:50.530
Like, it's not just like the customer, which is like the GitHub user, but it's also
64
00:04:51.090 --> 00:05:00.175
you have like the product customer where like the actions team or the copilot team or whatever, we're always trying to optimize for their experience so that they don't have to think about billing.
65
00:05:00.815 --> 00:05:04.175
Ideally, as like a platform, that's something you wanna optimize for,
66
00:05:04.415 --> 00:05:15.850
as well as, you know, the support team. And then we have, like, the business side of things where we have to make sure that we have accurate data for the business to be able to make decisions. So it's a pretty interesting role, I think, from that perspective.
67
00:05:16.889 --> 00:05:19.530
And then how does that work? Because GitHub
68
00:05:19.530 --> 00:05:27.690
is a is a SaaS platform. Right? It runs in the cloud, GitHub Cloud, GitHub Enterprise Cloud, and there's different clouds as well. Right? Like data residency,
69
00:05:27.945 --> 00:05:37.145
as in GitHub in Europe or in different places. And you can also host it yourself. Right? Yes. Yeah. Yeah. There's a lot of different customization options,
70
00:05:37.625 --> 00:05:43.070
which is the other fun side of the billing coin. I feel like it's like all of it is edge cases.
71
00:05:43.710 --> 00:05:45.150
Everything is an edge Yeah.
72
00:05:46.830 --> 00:05:50.590
So lots of different ways that people can have their
73
00:05:51.870 --> 00:05:56.430
their enterprise set up because lots of different enterprises are different, and business needs are different. So
74
00:05:57.574 --> 00:06:04.615
So is your billing engine then all the same for all these products, or do you use different, let's say, versions?
75
00:06:05.495 --> 00:06:22.670
They're more or less the same. I think that billing works a little bit differently depending on what people are using. Like, I think server works differently, and we don't necessarily connect the billing side to enterprise server. So I think that's part of, like, the the benefit is that people run it on their own equipment.
76
00:06:22.990 --> 00:06:32.435
And then we have different versions of our billing system for different data residencies. That way, like, the data that is generated in Europe stays in Europe.
77
00:06:33.395 --> 00:06:35.715
Same with everywhere that there's data residency.
78
00:06:35.715 --> 00:06:39.155
That way that way, it all is where it needs to be.
79
00:06:40.260 --> 00:06:41.860
Yeah. Complicated.
80
00:06:41.940 --> 00:06:44.660
Yeah. But fun. Yeah. That's you fun.
81
00:06:45.700 --> 00:06:49.220
Still write code, or do you just talk to an
agent all day?
82
00:06:49.700 --> 00:06:51.060
That's a good question.
83
00:06:51.460 --> 00:06:53.780
And I feel like that's something that's changing,
84
00:06:54.100 --> 00:06:54.420
gosh,
85
00:06:55.074 --> 00:06:55.794
so
86
00:06:56.194 --> 00:06:57.155
rapidly.
87
00:06:57.634 --> 00:07:00.915
I think most of what I do
88
00:07:00.995 --> 00:07:27.055
now the way that I kind of divided in my head is like there's asynchronous development work that I'm doing, and then there's synchronous development work that I'm doing. And so I typically have quite a few things going on async where I'm like, just just saying like, hey, like, Cloud Agent, do this for me. And then I'm like delegating tasks out to a Cloud Agent. And I try to not take on more than like three or four of those at once because then it just ends up being really hard to keep up with all of the code that gets generated.
89
00:07:27.775 --> 00:07:33.535
And then locally, then I work in Versus Code or with Copilot CLI to
90
00:07:33.615 --> 00:07:49.430
do that synchronous work. And that's usually like more difficult things or things that I haven't quite figured out yet. So I don't have all of the knowledge that I need yet to go and delegate that task. So those are the synchronous things that I typically work on. And usually, those I try to do, like, one thing at a time when
91
00:07:49.430 --> 00:07:50.229
possible.
92
00:07:51.110 --> 00:08:01.115
Yeah. Because now you you get all these little tasks that you delegate everywhere, and then it kind of fills your whole memory space, your your own memory space. It's difficult to keep track of everything.
93
00:08:01.435 --> 00:08:17.470
Yeah. That's a really hard problem right now, I think, is just, like, dealing with the the human brain part of, like, what am I working working on? On? And how do I get all of these things done instead of just started? It's very easy to start things with AI. It can be very difficult to make sure that they all get finished.
94
00:08:18.510 --> 00:08:20.990
And then when you just said asynchronous
95
00:08:20.990 --> 00:08:27.985
stuff, do you mean you ask GitHub Copilot agents to think that it is in the cloud on github.com
96
00:08:27.985 --> 00:08:33.425
to do something to create a PR for you? Is that what you mean? Yeah. Yeah. So I
97
00:08:33.905 --> 00:08:45.480
I'm typically doing something like that for, like, small bug fixes or things like my general rule of thumb when I'm like, is this a thing that I'm going to do? Or is this a thing that Coding Legion is gonna do?
98
00:08:45.720 --> 00:08:46.280
Is
99
00:08:47.560 --> 00:08:58.295
like, can do I know exactly how to do this thing? And if I do, then I just make sure that I write everything up. I use Whisper right now. That's my, like, tool of choice for transcribing
100
00:08:58.295 --> 00:09:00.055
everything very quickly.
101
00:09:00.375 --> 00:09:14.520
And then use Copilot to, like, make sure everything is there in the task and then assign it to assign it to Copilot to actually go and do the work. Whereas if it's a thing that I still feel like I need to explore or I'm not quite sure what the approach is, then I'll do it myself.
102
00:09:15.880 --> 00:09:16.920
In in,
103
00:09:16.920 --> 00:09:20.120
like, in an IDE working with coding the
104
00:09:21.115 --> 00:09:23.755
other agent. There's so many agents now.
105
00:09:23.995 --> 00:09:25.915
It is such an overloaded term.
106
00:09:26.875 --> 00:09:28.075
It is a very yeah.
107
00:09:29.035 --> 00:09:36.420
In in agent mode. Yeah. Yeah. Yeah. It is very confusing because in Versus Code, you have your little chat window
108
00:09:36.420 --> 00:09:38.580
and there is agent mode.
109
00:09:38.820 --> 00:09:41.220
But really it's just it's different modes
110
00:09:41.300 --> 00:09:44.020
that have different tools and different permissions,
111
00:09:44.260 --> 00:09:58.715
and then they call those participants as well. And you can have all sorts of specific ones. It's very confusing. Basically, it's just a text box that you just talk to. Yeah. And it just does stuff for you. Yeah. And I would say, I think, like, a 100% of my work now is with
112
00:09:59.035 --> 00:09:59.835
AI
113
00:10:00.075 --> 00:10:01.035
doing it
114
00:10:01.355 --> 00:10:03.675
either synchronously or asynchronously.
115
00:10:04.050 --> 00:10:13.650
There's occasionally a time where, like, if it's like, oh, like, there's a CSS problem. I'm gonna run-in and, like, fix that really quick because it'll probably be done faster by me than with an agent or,
116
00:10:13.890 --> 00:10:21.144
you know, some, like, manual text changes or something. But everything else is pretty much all done now with AI, which is weird.
117
00:10:22.105 --> 00:10:36.390
It's very strange. Yeah. And and so when you work on, let's say, a new feature or something, do you plan it out yourself and you go, oh, I need this file and this change here and this thing here? Or do you just say, hey, agent. I just I need this feature.
118
00:10:36.550 --> 00:10:37.510
Go plan it.
119
00:10:38.710 --> 00:10:42.950
Depends on the feature. If it's something that's, like, very large,
120
00:10:43.715 --> 00:10:48.275
then I will typically plan that out like in advance.
121
00:10:48.755 --> 00:11:03.670
And then figure out how to break it into smaller pieces so that it's not all just like one shot at and done at once. Because I feel like that's sort of where AI still sort of breaks down is like, yeah. If not the AI breaking down, but in like the review process,
122
00:11:04.710 --> 00:11:05.510
then,
123
00:11:06.550 --> 00:11:12.485
then I'll break it into smaller pieces. Whereas if it's, you know, just a small discrete chunk of work that needs to be done,
124
00:11:12.885 --> 00:11:19.525
then I'll typically use, like, the plan mode first to figure out exactly how I want it done and then run agent mode to do the actual work.
125
00:11:20.485 --> 00:11:22.245
Ah, okay. And and not
126
00:11:22.485 --> 00:11:32.930
spec driven development or something like that? Yes. Yeah. I think that's what it's called. I have a a on my very long list of things that I need to look into, spec kit is on there.
127
00:11:33.330 --> 00:11:37.490
And I I Yeah. Yeah. Would like to. I did play with squad over the weekend
128
00:11:37.985 --> 00:11:41.265
recently, and that was really, really cool
129
00:11:41.985 --> 00:11:44.785
and very interesting. Explain what that is to the listeners?
130
00:11:45.105 --> 00:11:47.585
Yeah. So it is a
131
00:11:47.745 --> 00:11:48.785
group of
132
00:11:49.670 --> 00:11:54.470
it's like a group of agents that you can set up and work all together. So you'll it'll
133
00:11:54.790 --> 00:12:10.774
it's really easy to install. I think you just, like, NPM install it everywhere and then do squad and knit within Copilot CLI. And then it'll go through and, staff your group of folks. So I think I had, like, a front end developer, a back end developer, like, a tech lead that was overseeing everything,
134
00:12:11.894 --> 00:12:13.415
and, like, a test
135
00:12:14.134 --> 00:12:15.095
engineer.
136
00:12:15.574 --> 00:12:28.000
Yeah. I think it was, like, five or six different roles. But then they all work together and make decisions and sort of like play back and forth with each other to, you know, write something very quickly. And so I was doing, like, just like a a fun
137
00:12:28.480 --> 00:12:33.120
project on my own just to, like, try this out and, like, solve a small problem for myself.
138
00:12:34.655 --> 00:12:47.135
And I used Squad for the first time to do that. And I realized, like, that was a really great way to, like, get a lot of stuff going at once and sort of, you know, like, scaffold something into existence that then I could take and, like, shape into what I wanted it to be.
139
00:12:48.010 --> 00:12:50.330
And it's like a more less
140
00:12:50.970 --> 00:12:58.650
less crazy, I guess, the way where there weren't as many things happening at once because it was hard to also keep track of all the changes happening at once.
141
00:12:59.050 --> 00:13:04.065
But I didn't really need to keep track of them until I was ready to, like, actually shape it into what I wanted it to be.
142
00:13:04.705 --> 00:13:09.105
Yeah. And and do those agents then work truly autonomously,
143
00:13:09.105 --> 00:13:11.185
or do you still need to ask them things?
144
00:13:11.585 --> 00:13:35.214
Yeah. So it seemed like the way that it worked is, like, copilot the Copilot CLI would come back and they went and, like, created I I created a spec markdown file and then a design markdown file, and they pretty much just worked off of that and came back and divided that into a couple of different chunks of what to do. And then Copilot would come back to me and be like, alright. They're done. Should we move on to the next one, or do you wanna smoke test the the changes?
145
00:13:35.375 --> 00:13:42.095
And so I would, like, go
test the changes and come up with, you know, feedback for them on how what I wanted to change from there.
146
00:13:42.975 --> 00:13:43.295
Yeah.
147
00:13:44.160 --> 00:13:53.360
Yeah. So it's it's kinda local offshoring. You have a little team. Yep. They just say, go do this, and then they just go do that. Yeah. They just go do it. It was crazy.
148
00:13:54.079 --> 00:14:15.555
And it was yeah. It's very cool, and it makes me realize, like, just how many things can be done now because I've been a software engineer for long enough that I have like a very long list had a very long list of side projects or ideas on what I wanted to do. And that would usually die at the point where I, you know, start thinking about breaking down the tasks or go buy a domain.
149
00:14:16.970 --> 00:14:17.450
Got a
150
00:14:18.089 --> 00:14:20.890
massive collection of domains that haven't done anything.
151
00:14:21.610 --> 00:14:33.065
And now that's not the you know, doing the work isn't really the bottleneck. Like, you can go from idea to a working prototype in, you know, a couple hours, which is really cool.
152
00:14:33.785 --> 00:14:40.745
Yeah. That's the thing now, isn't it? It's the hardest thing is now you need to figure out what you wanna make. Yes. What is worth making?
153
00:14:41.090 --> 00:14:49.810
Yeah. Yeah. And yeah. I mean, all of those things are not free necessarily to, like, deploy. So now you have to make the decision of, like, what what deserves to exist
154
00:14:50.050 --> 00:14:50.930
in my,
155
00:14:51.810 --> 00:14:55.170
you know, in my droplet somewhere or for me to actually pay for.
156
00:14:55.935 --> 00:14:57.775
And that's kind of an interesting
157
00:14:58.175 --> 00:15:05.535
change where I feel like a lot of engineers are having to sort of step into this, like, product management role in a way that they haven't had to in the past.
158
00:15:06.255 --> 00:15:09.135
I think now you need to think about value
159
00:15:09.215 --> 00:15:10.095
way earlier.
160
00:15:10.589 --> 00:15:23.310
Because previously, when you had a cool idea, you buy a domain name and you go build a thing because that's the fun. You build a thing. It might not be super valuable, but you keep building it and building it. Maybe you push it and then you think, meh. It's a bit meh.
161
00:15:24.110 --> 00:15:30.255
Yep. But now you just don't bother. Yep. Yep. It's true. Yeah. I feel like it's sort of changed the way that I think about
162
00:15:30.575 --> 00:15:32.095
about building things
163
00:15:32.735 --> 00:15:33.535
for sure.
164
00:15:34.495 --> 00:15:36.654
Yeah. So so squad,
165
00:15:36.654 --> 00:15:38.975
would you trust it for your daily work?
166
00:15:41.380 --> 00:15:43.700
Don't know. I don't think that I would run it on,
167
00:15:45.060 --> 00:15:46.260
like, on my
168
00:15:46.820 --> 00:15:53.700
work that I'm working on in production. But that's also in part because I don't think that I think it's good for large changes that need
to be made.
169
00:15:54.260 --> 00:15:56.365
Not so much for, like,
170
00:15:56.445 --> 00:16:06.445
you know, a lot of the work that I do is like, oh, there's a small bug fix or a small part of this feature that I'm going to add or something like that that typically it just doesn't really require, like, that much
171
00:16:07.180 --> 00:16:08.700
effort going into it.
172
00:16:09.180 --> 00:16:16.300
I should try it. I think it would be fun. I mean, that's the beauty of git repository. Right? It's like, you could just run it and see how it does.
173
00:16:17.580 --> 00:16:19.660
And see if it just one shots that feature.
174
00:16:20.975 --> 00:16:27.135
You know? Yeah. You don't have to push it to production. Yeah. It's true. You don't have to push it. You can just experiment and see what it's like.
175
00:16:27.935 --> 00:16:30.975
I feel like that's sort of been like my lesson with doing
176
00:16:31.295 --> 00:16:34.240
AI things is like a lot of my discomfort
177
00:16:34.240 --> 00:16:41.839
with like what I would actually do with it is like very much on me. And it's not necessarily on what they can do. It's like, oh, have I tried
178
00:16:42.079 --> 00:16:45.040
running squad on, you know, in
179
00:16:46.025 --> 00:16:55.945
on my, like, normal day to day code base. Like, I'm sure once I did it, I would be actually very comfortable with it and realize like, oh, there's so much more. But then that comes with, like, the existential crisis of
180
00:16:56.825 --> 00:17:01.920
who am I? What am I doing? Like, all of those things that come up with AI
181
00:17:02.480 --> 00:17:04.320
as well. So yeah.
182
00:17:05.040 --> 00:17:14.159
Yeah. I found in the beginning when this started to work, and I'm talking like six months back or something because before that, it wasn't that great at coding. Was good. But,
183
00:17:14.880 --> 00:17:15.120
you know,
184
00:17:16.205 --> 00:17:22.125
I had a little bit of shame when I pushed something into production that I didn't write myself. It's like, come on. I'm cheating.
185
00:17:22.285 --> 00:17:27.005
It's like copy pasting from Stack Overflow or something. It's not not right.
186
00:17:27.245 --> 00:17:32.159
Just it doesn't feel right. Mhmm. But now I'm very comfortable with it. It takes a while.
187
00:17:32.480 --> 00:17:33.999
Yeah. So Yeah.
188
00:17:34.880 --> 00:17:43.200
Yeah. I think it takes a while to build that muscle and, like I think and there was a really good talk last year at Cascadia JS that I really liked from Craig Dennis too that he did about,
189
00:17:43.865 --> 00:17:50.105
I feel like I recommended a lot. That's about, can you be proud of the things that AI builds for you?
190
00:17:50.985 --> 00:17:53.225
Yeah. And it was a really interesting
191
00:17:54.105 --> 00:17:57.705
viewpoint, I think, where it's like, can you? I mean,
192
00:17:58.429 --> 00:18:00.029
it's still your ideas
193
00:18:00.270 --> 00:18:01.230
that made Yeah.
194
00:18:02.110 --> 00:18:02.590
Still
195
00:18:02.990 --> 00:18:16.045
requires typically, anyway, it requires a lot of shaping. Maybe it didn't. Maybe it didn't require a lot of, like, expertise or interest. But I still think it's really cool when something like that happens. So I land more on the side of, yes. Yes. You can be proud of it. But
196
00:18:16.765 --> 00:18:17.325
Yeah.
197
00:18:17.645 --> 00:18:24.605
And you need to learn to trust it a little bit as well. Mhmm. Like, you know, if you would run Squad in production or for production code.
198
00:18:25.480 --> 00:18:27.960
And so for for instance, do you still check
199
00:18:28.200 --> 00:18:29.720
everything that it does?
200
00:18:29.960 --> 00:18:30.919
All the code?
201
00:18:31.720 --> 00:18:35.159
Yeah. I would say the vast majority of things, but I feel like I'm pretty
202
00:18:35.880 --> 00:18:47.485
comfortable now just being an engineer in general of knowing, like, what parts are the important parts that need to absolutely work and need unit tests and what parts are a little bit less, you know, like, it can it could do
203
00:18:48.365 --> 00:18:52.605
what it needs to do, and it'll be fine if, like, they use a, you know,
204
00:18:53.290 --> 00:18:58.809
a slightly different front end component or it's not built exactly how I would imagine it being built.
205
00:18:59.770 --> 00:19:02.330
So Yeah. I would say that I still check most of it.
206
00:19:04.410 --> 00:19:08.810
Yeah. Exactly. Your CSS won't cost GitHub millions.
207
00:19:09.405 --> 00:19:10.765
Exactly. Yeah.
208
00:19:10.925 --> 00:19:12.125
Yeah. Yeah.
209
00:19:12.845 --> 00:19:13.565
So
210
00:19:13.965 --> 00:19:17.325
where do you hope this is going for yourself or productivity?
211
00:19:18.765 --> 00:19:19.565
Oh,
212
00:19:19.885 --> 00:19:21.565
good question. I think
213
00:19:22.285 --> 00:19:22.925
I
214
00:19:23.509 --> 00:19:26.789
this is April, mid April, and the
215
00:19:27.429 --> 00:19:28.229
recent
216
00:19:28.549 --> 00:19:31.109
mention of mythos is something I've been
217
00:19:31.990 --> 00:19:39.634
keeping an eye on because I'm like, oh, it looks like we hit yet another, you know, step change in how how good AI is.
218
00:19:40.035 --> 00:19:42.754
So I'm curious to see how that changes things.
219
00:19:44.595 --> 00:19:45.315
I
220
00:19:45.715 --> 00:19:56.729
lean on the side of, like, leaning in to all of it. Like, there's nothing that I can individually to say like, hey, maybe maybe we should pump the brakes on this AI thing. Like, it's gonna happen regardless.
221
00:19:56.970 --> 00:20:03.850
So I would rather learn how to use it and do well with it. Because I think that, like, if you're going to be an engineer,
222
00:20:04.605 --> 00:20:14.764
like, five or even a year from now, like, has to be you have to you have to use it, and you have to use it well because the folks that are doing it are going to be so much faster
223
00:20:14.845 --> 00:20:15.565
and,
224
00:20:16.205 --> 00:20:22.250
than the
ones that aren't. So I try to keep up with it as much as possible and continue using it.
225
00:20:22.730 --> 00:20:28.090
But I also I don't know. I think I also appreciate the viewpoints of folks that are like, but I liked writing the code.
226
00:20:29.975 --> 00:20:31.815
For me, it was never really like
227
00:20:32.135 --> 00:20:35.975
part of my identity be identity to be like a good coder
228
00:20:36.135 --> 00:20:42.455
or really good like, LeetCode. Like, gosh, I cannot I can think of a million other things I'd rather do than do LeetCode problems.
229
00:20:43.390 --> 00:20:52.669
I really like building things, and now I can build things so much faster and better and easier than I was able to before. And I think that part's exciting. But I think a lot of folks probably struggle with the fact that, like,
230
00:20:53.150 --> 00:20:54.270
things are different now.
231
00:20:55.505 --> 00:21:00.625
Yeah. Things are different. But like you say, you can add value way more quickly now. Yeah.
232
00:21:00.945 --> 00:21:02.145
Yeah. That's true.
233
00:21:03.665 --> 00:21:09.760
Yeah, you just need to, I think, develop different muscles. Mhmm. Like, you become more of a product owner. Mhmm.
234
00:21:10.080 --> 00:21:17.200
And architect and, you know, notch the AI into, no. No. You should look into this or it needs to be scalable.
235
00:21:17.680 --> 00:21:20.880
It shouldn't cost 10,000 to to run or something.
236
00:21:21.280 --> 00:21:21.840
Yeah. So
237
00:21:23.075 --> 00:22:00.125
Yeah. I think I've seen some recent discourse about how, like, the role of engineer and product manager are sort of merging together to just be, like, a builder of things. And I feel like I have a product manager that I work with regularly at GitHub, and I think that we are both, like, converging on this same similar role where I'm, like, helping her become an engineer, and she's helping me become a product manager. And I feel like we're sort of converging on this one thing that we both end up doing. So yeah. Yeah. That's pretty cool. Yeah. Because, obviously, non tech people can now do tech stuff as well. They just talk into the box and stuff happens. Yeah. Why not? Yeah. And and do you think that
238
00:22:01.320 --> 00:22:06.839
well, you kinda alluded to it already, but do you think everybody will still be able to be an engineer?
239
00:22:07.080 --> 00:22:11.639
Or will it just be a couple of folks because, you know, people can do so much more now?
240
00:22:12.120 --> 00:22:12.759
Yeah.
241
00:22:13.000 --> 00:22:23.304
Yeah. I kinda lean on the side where I think that there's so much demand for software that I don't think it's going away. Even in a role right now where I am
242
00:22:24.265 --> 00:22:30.905
building with AI very regularly and building faster than I ever have before, our backlog has not gotten any smaller.
243
00:22:33.490 --> 00:22:39.250
Because the more things you build, the more things you have to maintain. And the more things change, and the more things people want.
244
00:22:40.050 --> 00:22:52.535
And there's also, I think, a story to be told about, like, there are the right features. And you have to figure out what those are and not necessarily build everything. So I think there's enough work to be done in the world of software that I'm not personally worried about that.
245
00:22:53.415 --> 00:22:55.175
But I could see that it would be
246
00:22:55.575 --> 00:23:01.510
potentially difficult to get a job anywhere as an engineer if you're not leaning into,
247
00:23:01.910 --> 00:23:04.470
learning those AI skills. Because
248
00:23:04.790 --> 00:23:10.835
the folks that are doing it are gonna be, you know, five or six times more productive than you would be without it. So
249
00:23:11.635 --> 00:23:12.114
yeah.
250
00:23:13.475 --> 00:23:15.154
Yeah. And I
251
00:23:15.395 --> 00:23:20.835
yeah. It's it's such a strange world now. Like, have two kids. One is 10 years old already.
252
00:23:21.315 --> 00:23:24.755
And I don't know. A year ago, if you would ask me what
253
00:23:25.090 --> 00:23:34.369
should she go and do and learn, I would say, you know, software development or something like that. It's good for problem solving and, you know, you'll probably find a job.
254
00:23:34.690 --> 00:23:38.929
But now, I'm not so sure if you could do that as like an entry level person.
255
00:23:39.935 --> 00:23:40.894
I don't know.
256
00:23:41.295 --> 00:23:43.774
Yeah. What would what would you advise?
257
00:23:44.815 --> 00:23:49.375
Yeah. I think that the story for junior engineers is probably really difficult right now.
258
00:23:50.575 --> 00:23:58.299
I mean, I know it is. Everybody that I talked to that's like early on in their career is like, what is happening? Why why is this Yeah. Is this normal? No.
259
00:23:58.300 --> 00:24:01.259
It's different. It's completely different than it ever has been before.
260
00:24:02.220 --> 00:24:05.740
But I like I said, I do think that there's still gonna be a demand for software
261
00:24:06.445 --> 00:24:16.605
going forward. And even if it's not necessarily like your full time role, I could see that having those skills to build software, I think, is gonna be important for a lot of roles in the future even if it's not like
262
00:24:16.845 --> 00:24:18.685
being a software engineer.
263
00:24:18.685 --> 00:24:19.965
So I still think it's worth doing.
264
00:24:20.610 --> 00:24:24.370
I think that we're going to come up with, like, a potential,
265
00:24:24.930 --> 00:24:29.730
crisis here in, like, five years if we don't still have junior engineers,
266
00:24:30.370 --> 00:24:31.650
because you can't just, like,
267
00:24:32.785 --> 00:24:52.780
come out of the gate as a senior engineer. Like, a lot of it is a lot of your job early on is knowing how learning how to build software because, you know, the boot camps and the even the degree programs don't really teach that. They teach, like, this is how computers work. I'm
like, this is how you write React code or something like that. But Yeah. Yeah. The actual, like, act of engineering
268
00:24:52.780 --> 00:24:59.659
software is something that you really only learn on the job. And so if we're not investing in those skills for folks early in career, then I think we're gonna have some problems
269
00:24:59.900 --> 00:25:03.955
a few years from now. The whole world runs on software. So like,
270
00:25:04.115 --> 00:25:06.274
I don't feel like that's gonna go away and
271
00:25:06.995 --> 00:25:08.195
anytime soon,
272
00:25:08.595 --> 00:25:11.235
barring any sort of like major disaster.
273
00:25:12.595 --> 00:25:23.090
And so, yeah, I I think it'll still be a good career to go into. But I'm also wondering the same thing. My oldest is five, and she's like, when I grow up, I'm gonna be a software worker like my mom. I'm like,
274
00:25:23.490 --> 00:25:24.530
maybe. I
275
00:25:25.410 --> 00:25:26.290
guess we'll see.
276
00:25:27.250 --> 00:25:28.770
Yeah. Yeah. Nobody knows.
277
00:25:29.415 --> 00:25:36.775
Yeah. I I think we're moving up the stack way more and more and more. And and that was already the case. Like,
278
00:25:37.335 --> 00:25:38.535
juniors now,
279
00:25:39.255 --> 00:25:40.375
you know, they use
280
00:25:41.255 --> 00:25:45.015
front end frameworks and they think that's like the the bottom of the stack.
281
00:25:45.680 --> 00:25:54.879
They have no idea. And that's fine too. That's fine. That's just how you're raised and how your career progresses. But now,
282
00:25:55.440 --> 00:26:02.725
the stack is very different. You just talk into a box, you type something in there, and then something happens. You don't need to really even see the code.
283
00:26:02.965 --> 00:26:05.365
And this is the worst it's gonna be.
284
00:26:05.765 --> 00:26:09.205
Like, a year from now, can you imagine? Mythos like
285
00:26:09.365 --> 00:26:10.085
something?
286
00:26:10.805 --> 00:26:14.169
Do we even need to have c sharp anymore?
287
00:26:14.250 --> 00:26:17.769
I don't know. Maybe the thing just makes something that just compiles and runs.
288
00:26:18.570 --> 00:26:19.929
Yeah. That's true.
289
00:26:20.330 --> 00:26:31.455
Yeah. And I think there's a lot of talk to you about, like, languages that are, you know, optimized in one way or another. And I think people might lean more towards those, and towards rewrites in,
290
00:26:31.775 --> 00:26:40.895
you know, maybe it does make sense of what the Rust stations have been saying for a while to just rewrite everything in Rust because that's that's the language that's apparently
291
00:26:41.490 --> 00:26:43.169
the in the meta right now.
292
00:26:44.770 --> 00:26:46.130
Yeah. I
293
00:26:46.770 --> 00:26:51.010
I'm curious to see how it goes. I think it's really uncomfortable
294
00:26:51.570 --> 00:26:54.975
not knowing what the future looks like. And
295
00:26:55.535 --> 00:27:00.174
I think it's like a good reminder that, like, nobody does, even the folks predicting
296
00:27:00.815 --> 00:27:02.815
everything. Like, nobody really knows.
297
00:27:03.295 --> 00:27:08.735
And we're all uncomfortable at the same time. So, like, we're all in this boat together, I guess.
298
00:27:09.615 --> 00:27:12.710
But But let's let's let's just choose to be optimistic.
299
00:27:12.710 --> 00:27:14.470
Yeah. Because why not?
300
00:27:14.790 --> 00:27:15.990
I think also
301
00:27:16.150 --> 00:27:27.385
a part of the optimism may maybe is all this stuff is currently is written by humans still, kinda. There's so much code written by humans, and that means that we have loads of technical debt.
302
00:27:28.025 --> 00:27:30.105
And that can't be solved just
303
00:27:30.745 --> 00:27:32.825
in a couple of seconds by AI.
304
00:27:33.065 --> 00:27:39.385
That doesn't work like that. Mhmm. So I think there's still lots lots of work to do for us as humans.
305
00:27:39.545 --> 00:27:54.985
Yeah. Yeah. I mean, even now with, like, static site generators existing and stuff, there's still, like, demand for so many, you know, small businesses that aren't online yet. And so, like, I think there's gonna be plenty of stuff to do just to
306
00:27:55.625 --> 00:28:01.465
get software enablement out there for everybody and to maintain it and to keep it going for a long time. So,
307
00:28:02.105 --> 00:28:05.625
yeah. I think it's still gonna be around for a while. I'm optimistic. Yeah.
308
00:28:06.105 --> 00:28:06.825
Good.
309
00:28:07.225 --> 00:28:07.705
Me too.
310
00:28:08.520 --> 00:28:14.600
So as you work with with billing and metering and also with the GitHub Copilot
311
00:28:14.600 --> 00:28:15.400
premium
312
00:28:15.400 --> 00:28:20.600
request units, you probably work on those or see those or something. I do. Yes.
313
00:28:21.424 --> 00:28:25.744
Do you see those being used a lot or overused a lot or that people run into limits?
314
00:28:27.265 --> 00:28:32.225
I think it kinda depends. It seems like in a lot of places, there's, like, a lot of power users
315
00:28:32.385 --> 00:28:38.330
and then, like, a trail like, a big long trail of, like, folks that don't use it as much within,
316
00:28:38.490 --> 00:28:38.969
like,
317
00:28:39.370 --> 00:28:45.529
places. And I feel like that's the only trend I've really noticed is like, there's some people using a ton of AI and then
318
00:28:46.409 --> 00:28:48.089
less as you get on the stack,
319
00:28:48.555 --> 00:28:58.315
which which I think is interesting. I actually I look at my own usage quite a bit just because this is a space that I'm in and I'm very interested in And I feel like I use a lot of AI, but I really don't.
320
00:28:59.835 --> 00:29:00.955
You know, I
321
00:29:01.195 --> 00:29:02.235
compared to
322
00:29:03.130 --> 00:29:09.049
a lot of the folks, maybe that's just the way that GitHub is run where there's just a ton of folks using a ton of AI. But
323
00:29:09.370 --> 00:29:14.330
I personally don't use a ton, so I don't really
know how to, like,
324
00:29:14.650 --> 00:29:15.290
how to gauge.
325
00:29:16.405 --> 00:29:27.365
Is there somebody that uses a lot and that's the way to do it? I think there's been, like, some talk online about how, like, oh, like, if you aren't using your salary and tokens every month, like, are you even an engineer?
326
00:29:29.200 --> 00:29:34.320
Don't think I use, like, an extra $100 or something like that in usage beyond my normal
327
00:29:34.880 --> 00:29:43.200
amount. Oh, great. Yeah. That seems like a very reasonable trade off for the amount of productivity I feel like I gain out of it.
328
00:29:43.600 --> 00:29:54.855
So I don't think that that discourse is gonna be around forever where everybody's like, oh, you gotta use as much as you can, and you're gonna be the most productive engineer. I don't think that there's, like, a linear relationship between token usage and productivity
329
00:29:55.335 --> 00:29:58.935
from what I can see. But No. No. Tokens
330
00:29:58.935 --> 00:30:01.830
are expensive. They are. Yeah. Yeah.
331
00:30:02.150 --> 00:30:07.110
I'm curious to see when Mythos comes out. I feel like it's probably maybe it's gonna be more expensive. I don't know. I don't know.
332
00:30:07.590 --> 00:30:10.070
That's what I'm most excited to see soon.
333
00:30:11.030 --> 00:30:25.705
Yeah. I think it's an OpenAI. They also have something similar. Right? That's coming up. Don't remember the the code name. It it was an interesting code name. I don't know. Mhmm. I'm sure they have it already, all all this stuff, because once one company drops one,
334
00:30:26.025 --> 00:30:38.320
day after the other one does it. Yeah. So it's gonna be wild. Yeah. What else I think is interesting is it seems like recently there's been a lot of talk about local models actually, like, getting good. It seems like they're maybe, like, six months to a year behind,
335
00:30:38.960 --> 00:30:40.559
like, the frontier models,
336
00:30:40.640 --> 00:30:42.559
which is actually great because six months ago,
337
00:30:43.415 --> 00:30:54.535
development got a lot better. And so if local models are hitting that inflection point as well, then maybe we can you know, maybe the conversation about the cost and everything like that is changing soon. We'll see
338
00:30:55.050 --> 00:31:17.585
how that changes. Yeah. That'll be interesting for GitHub Copilot as well because now with Copilot CLI, it can run local models since a couple days. And there's now Gemma four, for instance, Google Gemma four, which runs locally. Haven't tried it yet if it's fast enough or capable enough, but that'll be interesting. Yeah. Like, how will billing go? What what's the value of Copilot? Just a harness? Or
339
00:31:18.865 --> 00:31:23.665
Yeah. Yeah. I think that the there's going to be more changes than we anticipate
340
00:31:24.670 --> 00:31:28.350
as things actually settle out. Like I said, nobody knows what the future is going to be.
341
00:31:28.990 --> 00:31:30.510
No. No.
342
00:31:31.310 --> 00:31:32.270
Exciting.
343
00:31:32.510 --> 00:31:33.150
Okay.
344
00:31:34.190 --> 00:31:37.470
So what are you excited about working on next?
345
00:31:39.015 --> 00:31:40.294
Yeah. I think
346
00:31:41.175 --> 00:31:41.975
I've
347
00:31:42.375 --> 00:31:46.054
recently so I think up until now, I've really been using
348
00:31:46.615 --> 00:31:54.859
AI tools more as like, I need to create this feature or fix this bug or something like that. And I really wanna spend more time using them,
349
00:31:55.419 --> 00:31:56.940
for refactoring.
350
00:31:57.019 --> 00:32:00.059
I think that that's like one of the bigger opportunities
351
00:32:00.059 --> 00:32:08.379
is like how do we now refactor a lot of this existing code to like optimize for how, you know, the agent would build this thing.
352
00:32:08.940 --> 00:32:14.515
So that it theoretically works better when, you know, Copilot or something like that is working on it.
353
00:32:14.915 --> 00:32:22.515
Yeah. I think that's gonna be an interesting space both with, like, these more advanced models coming out that are, you know, able to find all of those security exploits.
354
00:32:23.310 --> 00:32:29.150
You know, it sounds like we're supposed to be rewriting all software in the next few months to avoid that.
355
00:32:30.270 --> 00:32:32.350
But also to see, you know, I think that
356
00:32:32.750 --> 00:32:35.550
a lot of these models are good enough now to
357
00:32:36.495 --> 00:32:52.975
to take the wheel for the most part on building software. And so what does that mean for all of the existing code and all of the tech debt that's out there already that we need to go handle and deal with? So I'm interested to do more refactoring with Copilot and see how that changes things
358
00:32:54.070 --> 00:32:55.350
with my own workflow.
359
00:32:56.230 --> 00:33:12.534
Yeah. And get rid of some technical debt and stuff. Yeah. Mhmm. I would love to see the end of a backlog one day. That sounds nice. I don't think that it could happen. Like I said, I think that, you know, you never get to the end of the to do list, but I would love to see the end of a to do list and be like, we did it. We build it all the software.
360
00:33:13.335 --> 00:33:15.654
Well, you're friends with the product manager, so
361
00:33:16.135 --> 00:33:20.615
maybe maybe you can make something happen. That's true. That's true. We can
362
00:33:21.190 --> 00:33:23.510
also get there by just removing everything.
363
00:33:24.070 --> 00:33:24.630
And
364
00:33:25.510 --> 00:33:26.070
yeah.
365
00:33:26.950 --> 00:33:28.710
Yeah. But I think that's gonna be interesting.
366
00:33:29.670 --> 00:33:31.350
Okay. Very cool.
367
00:33:31.830 --> 00:33:34.870
And then maybe finally, is there anything
368
00:33:34.835 --> 00:33:37.475
exciting coming up in the GitHub world?
369
00:33:37.635 --> 00:33:40.115
Like features or capabilities
370
00:33:40.355 --> 00:33:41.394
that we should
371
00:33:41.715 --> 00:33:43.315
keep our eye on out for?
372
00:33:44.755 --> 00:33:51.260
That's a good question. I don't feel like I'm plugged in enough because a lot of the things that I'm working on right now are not
373
00:33:51.820 --> 00:33:53.260
shared publicly.
374
00:33:53.740 --> 00:33:54.460
So probably.
375
00:33:55.900 --> 00:33:59.740
And you'll have to stay tuned to see how those actually work out.
376
00:34:00.715 --> 00:34:02.794
Cliffhanger. Yeah. Cliffhanger.
377
00:34:02.875 --> 00:34:04.315
Great things are coming.
378
00:34:05.355 --> 00:34:09.435
Okay. Exciting. Yeah. We'll keep an eye out for that. Yep. Excellent.
379
00:34:09.595 --> 00:34:16.510
Well, thank you very much for talking with me today. This was fun. Yeah. Thanks for go and and find out more about you?
380
00:34:17.230 --> 00:34:24.910
Yeah. So I have a website that sort of aggregates all of the things on my socials and all that, and it is britneyelick.com.
381
00:34:26.735 --> 00:34:30.495
Excellent. Cool. And from there, they can also find your podcast.
382
00:34:30.735 --> 00:34:33.855
Yes. Yeah. I've got a podcast where I chat with some of my
383
00:34:34.575 --> 00:34:36.175
some of my engineering
384
00:34:36.175 --> 00:34:41.230
friends about folks that are very dedicated and excited about the world of software engineering.
385
00:34:41.390 --> 00:34:48.670
I write online too, write some blogs. I just got on the front page of Hacker News the other day for the first time, which was like a career milestone.
386
00:34:48.990 --> 00:34:52.785
So I'm online a lot. Probably more than I should be. Yeah. Thank you.
387
00:34:54.625 --> 00:34:55.425
Okay.
388
00:34:55.425 --> 00:34:57.905
Thank you very much. Yeah. Thank you for having me.