النص 🔗
WEBVTT
00:00:00.160 --> 00:00:03.359
Hey, it's Jason, host of the Code with Jason podcast.
00:00:03.520 --> 00:00:04.480
You're a developer.
00:00:04.639 --> 00:00:06.240
You like to listen to podcasts.
00:00:06.400 --> 00:00:07.679
You're listening to one right now.
00:00:07.919 --> 00:00:13.679
Maybe you like to read blogs and subscribe to email newsletters and stuff like that.
00:00:13.839 --> 00:00:14.960
Keep in touch.
00:00:16.079 --> 00:00:23.440
Email newsletters are a really nice way to keep on top of what's going on in the programming world.
00:00:24.239 --> 00:00:26.879
Except they're actually not.
00:00:27.199 --> 00:00:36.479
I don't know about you, but the last thing that I want to do after a long day of staring at the screen is sit there and stare at the screen some more.
00:00:36.640 --> 00:00:40.240
That's why I started a different kind of newsletter.
00:00:40.320 --> 00:00:43.679
It's a snail mail programming newsletter.
00:00:43.920 --> 00:00:44.479
That's right.
00:00:44.560 --> 00:00:51.679
I send an actual envelope in the mail containing a paper newsletter that you can hold in your hands.
00:00:51.840 --> 00:00:59.280
You can read it on your living room couch, at your kitchen table, in your bed, or in someone else's bed.
00:00:59.359 --> 00:01:02.159
And when they say, What are you doing in my bed?
00:01:02.399 --> 00:01:04.879
You can say, I'm reading Jason's newsletter.
00:01:04.959 --> 00:01:06.159
What does it look like?
00:01:06.640 --> 00:01:12.640
You might wonder what you might find in this snail mail programming newsletter.
00:01:12.879 --> 00:01:20.480
You can read about all kinds of programming topics like object-oriented programming, testing, DevOps, AI.
00:01:20.719 --> 00:01:23.760
Most of it's pretty technology agnostic.
00:01:24.239 --> 00:01:42.000
You can also read about other non-programming topics like philosophy, evolutionary theory, business, marketing, economics, psychology, music, cooking, history, geology, language, culture, robotics, and farming.
00:01:42.239 --> 00:01:46.239
The name of the newsletter is Nonsense Monthly.
00:01:46.560 --> 00:01:50.560
Here's what some of my readers are saying about it.
00:01:50.879 --> 00:01:57.120
Helmut Kobler from Los Angeles says, thanks much for sending the newsletter.
00:01:57.280 --> 00:02:00.879
I got it about a week ago and read it on my sofa.
00:02:01.120 --> 00:02:06.480
It was a totally different experience than reading it on my computer or iPad.
00:02:06.640 --> 00:02:12.319
It felt more relaxed, more meaningful, something special and out of the ordinary.
00:02:12.960 --> 00:02:18.879
I'm sure that's what you were going for, so just wanted to let you know that you succeeded.
00:02:19.199 --> 00:02:20.800
Looking forward to more.
00:02:22.000 --> 00:02:31.520
Drew Bragg from Philadelphia says, Nonsense Monthly is the only newsletter I deliberately set aside time to read.
00:02:31.759 --> 00:02:44.240
I read a lot of great newsletters, but there's just something about receiving a piece of mail, physically opening it, and sitting down to read it on paper that is just so awesome.
00:02:44.479 --> 00:02:46.319
Feels like a lost luxury.
00:02:47.360 --> 00:02:57.919
Chris Sonier from Dickinson, Texas says, just finished reading my first nonsense monthly snail mail newsletter and truly enjoyed it.
00:02:58.240 --> 00:03:03.199
Something about holding a physical piece of paper that just feels good.
00:03:03.439 --> 00:03:04.479
Thank you for this.
00:03:04.639 --> 00:03:06.240
Can't wait for the next one.
00:03:06.479 --> 00:03:16.319
Dear listener, if you would like to get letters in the mail from yours truly every month, you can go sign up at nonsense monthly dot com.
00:03:16.960 --> 00:03:19.919
That's nonsensemonthly dot com.
00:03:20.800 --> 00:03:22.159
I'll say it one more time.
00:03:22.400 --> 00:03:25.599
NonsenseMonthly dot com.
00:03:25.759 --> 00:03:29.360
And now without further ado, here is today's episode.
00:03:55.680 --> 00:03:56.400
Joel, welcome.
00:03:56.719 --> 00:03:58.240
Hey Jason, thanks for having me back.
00:03:58.400 --> 00:03:59.120
What is this?
00:03:59.360 --> 00:04:00.719
The fourth time?
00:04:01.199 --> 00:04:03.039
Something like that, yeah.
00:04:03.599 --> 00:04:11.599
And I think our podcast episode uh stuff spans years now.
00:04:11.919 --> 00:04:13.039
Yes, several years.
00:04:13.120 --> 00:04:16.639
I would guess this is the fourth appearance in five years.
00:04:16.879 --> 00:04:17.360
Oh wow.
00:04:17.600 --> 00:04:18.560
I've had some kids.
00:04:18.720 --> 00:04:20.639
I've had two kids since we started doing this.
00:04:20.720 --> 00:04:22.800
So yeah, my availability changes.
00:04:23.120 --> 00:04:24.480
How old are those kids now?
00:04:24.720 --> 00:04:28.160
My kids are a little over one and a little over three.
00:04:28.399 --> 00:04:29.040
Oh wow.
00:04:29.199 --> 00:04:31.759
My kids are 13 and 16.
00:04:32.160 --> 00:04:33.199
Oh wow.
00:04:33.519 --> 00:04:34.879
Okay, I have a question for you.
00:04:34.959 --> 00:04:35.199
Yeah.
00:04:35.439 --> 00:04:44.240
This is relevant to your audience, but like your kids, especially your 16-year-old, is probably starting to think about like what they're going to do with their lives once they leave the nest.
00:04:45.439 --> 00:04:51.759
How are you feeling about the world they're going into with all the upheaval in our industry?
00:04:52.560 --> 00:04:54.560
I'm not unconcerned.
00:04:55.279 --> 00:05:00.959
At the same time, they are very like well-adjusted, capable, confident people.
00:05:01.279 --> 00:05:02.079
Of course they are.
00:05:02.240 --> 00:05:08.240
Yeah, and so I don't have huge concerns for for them as people.
00:05:09.199 --> 00:05:13.360
Like if anybody can handle the world, they can, I feel like.
00:05:13.680 --> 00:05:14.160
Sure.
00:05:14.720 --> 00:05:15.360
Yeah.
00:05:15.759 --> 00:05:23.439
Um, but like, what is the world gonna look like economically and from a job market
Load full transcript
perspective and stuff like that?
00:05:23.680 --> 00:05:25.439
It's a weird world.
00:05:26.399 --> 00:05:27.040
It is.
00:05:27.439 --> 00:05:37.920
And you can imagine that my I'm asking the same questions about my kids in a much more vague uh manner because they're so much younger.
00:05:38.240 --> 00:05:50.879
I just can't even imagine if we even have half the pace of innovation we've had in our field in the past three years for the next 13, what it will look like when my oldest son is 16.
00:05:51.439 --> 00:05:51.759
Yeah.
00:05:52.079 --> 00:05:53.360
It's unreal to imagine that.
00:05:53.439 --> 00:06:02.959
Versus, like, for comparison, if you were to imagine the preceding 15 years before that, you know, a good chunk of my career, things were ultimately pretty stable.
00:06:03.040 --> 00:06:05.600
And I wonder how anomalous that was.
00:06:06.000 --> 00:06:06.639
Right.
00:06:07.759 --> 00:06:16.800
Yeah, like there's it's it's easy to think of the way the world currently is at any given point in time as the way the world turned out.
00:06:17.040 --> 00:06:22.879
You know, like the world went through all these shifts and changes and stuff, but like that's done now.
00:06:23.040 --> 00:06:26.399
This is just how things turned out, this is how things are.
00:06:26.560 --> 00:06:28.560
And obviously that's not the case.
00:06:28.800 --> 00:06:46.639
We're just seeing a snapshot of the way things happen to be at this moment, and it could be that um things are gonna get way different, and things that seem like a progression culminating in something um are actually just like a blip.
00:06:47.519 --> 00:07:00.959
Um like yeah, like the whole like uh, you know, a couple hundred years ago the whole like job thing was not it wasn't it it it didn't work the way it does now.
00:07:01.279 --> 00:07:08.399
And now it's like you go to college and get a job and stuff like that, but like that doesn't mean that in the future you go to college and get a job.
00:07:08.560 --> 00:07:10.800
It might be something we can't even imagine.
00:07:11.199 --> 00:07:11.600
Right.
00:07:11.759 --> 00:07:28.319
And I think that one of the things I've been thinking about lately with all the AI-related things going on in our industry is whether you know most technological progress is forward progress and that like it doesn't regress.
00:07:28.639 --> 00:07:38.160
But I have to wonder whether there will be certain things we're doing today that we weren't doing a year ago that we won't be doing two years from now.
00:07:38.800 --> 00:07:39.600
I'm sure.
00:07:40.639 --> 00:07:48.240
Like maybe we'll find that some of these things we're trying weren't the best for the companies we work at, for example, or for our profession.
00:07:48.399 --> 00:07:56.800
Like I think there's a lot of experimentation going on right now, and I think that we're more likely to be in that kind of environment where something we did just turns out to not be a great idea.
00:07:56.879 --> 00:07:59.600
I mean, I think you can see this in some larger technological trends.
00:07:59.759 --> 00:08:14.720
I pay attention to technology and education, for example, because we're about to have kids in schools, and I'm curious, and it's interesting to see the school districts in our area outside of Boulder, Colorado backtracking on their use of technology.
00:08:14.959 --> 00:08:31.759
And that to me just points to I think some really good intellectual flexibility on the part of the people running our school districts because it implies that they don't just view every single improvement or every single thing that they thought was an improvement to be durable in the long term.
00:08:32.320 --> 00:08:32.960
Mm-hmm.
00:08:34.799 --> 00:08:36.240
Yeah, I see what you mean.
00:08:36.399 --> 00:08:40.799
My mind went to a slightly different place uh a minute ago.
00:08:41.039 --> 00:08:57.360
I was thinking of like this is kind of a different thing, but like if you plop me in the woods or the middle of the ocean, like I'm probably not gonna be able to figure out how to get uh to get out of there.
00:08:57.519 --> 00:09:07.440
Um I can't navigate um or like hunt and forage to find food to survive for like a week or something like that.
00:09:07.840 --> 00:09:16.320
Um, because there's so much like knowledge that has been lost because we depend on technology now.
00:09:17.279 --> 00:09:20.720
Um, and like I've experienced that with programming.
00:09:20.879 --> 00:09:24.799
Like I feel like I've gotten at least a little dumber.
00:09:25.120 --> 00:09:28.799
Yes, deintellectualized is what I've been liking to say lately.
00:09:29.039 --> 00:09:29.200
Okay.
00:09:29.440 --> 00:09:31.840
I definitely feel like I'm a little dumber too in certain respects.
00:09:31.919 --> 00:09:41.600
I feel like I'm smarter in others, but I feel like there is like a very real finite limit to our human capability, and you kind of have to budget it.
00:09:42.879 --> 00:09:43.519
Yeah.
00:09:44.559 --> 00:09:52.879
Yeah, and okay, so like I've gotten dumber because I don't need to do as much intellectual grunt work.
00:09:53.039 --> 00:09:54.879
I've gotten like dumber and lazier.
00:09:55.200 --> 00:10:06.240
Because when there's I don't know, there's like a failing test or something, and rather than even look at it, I just copy the URL and I'm like, hey codex, why is this test failing?
00:10:06.480 --> 00:10:07.039
Right.
00:10:07.600 --> 00:10:09.360
Because why would I not do that?
00:10:10.320 --> 00:10:21.360
But now I'm not like using my brain very much, I'm just like copy-pasting something, and then I'll pass along that message to some other person, and that's it.
00:10:23.840 --> 00:10:32.879
And then if there's an instance where I need to use my brain, I'm like, ugh, I don't want to do this, and it's harder than it used to be.
00:10:33.519 --> 00:10:34.320
Absolutely.
00:10:34.480 --> 00:10:38.240
I think it's because more of our work is not thinking.
00:10:38.559 --> 00:10:44.720
So I I I've been thinking about the saying that you are like the five people you spend the most time with.
00:10:44.879 --> 00:10:56.000
Well, like, I spend a lot of time with AI, so I feel like I am becoming at least not necessarily becoming more like AI, but I'm becoming more of the person that I am when I use it.
00:10:57.519 --> 00:11:00.240
And that is not a totally positive thing.
00:11:00.320 --> 00:11:02.000
I think there are some positive aspects to it.
00:11:02.080 --> 00:11:14.879
For one, having to become a potentially more clear writer, or if you're dictating speaker, you know, like I feel like there is a shift towards natural language in our in our work.
00:11:15.039 --> 00:11:25.679
But yes, there is also a decomplecting force where like what we're needing to do is potentially less complex, it's requiring less deep of thought.
00:11:27.120 --> 00:11:27.600
Mm-hmm.
00:11:29.519 --> 00:11:32.000
Yeah, and that's that's a bit scary.
00:11:32.639 --> 00:11:42.960
It's I I I I'm sure that it's kind of analogous to like when calculators were first introduced, or even like when writing was first introduced.
00:11:43.120 --> 00:11:49.440
Like Socrates wasn't a big fan of writing because he thought it would make people like dumber and lazier.
00:11:49.759 --> 00:11:50.320
Right.
00:11:51.200 --> 00:11:59.120
And it's kind of funny because like maybe it did, but that doesn't mean that it's like a net loss.
00:11:59.919 --> 00:12:08.639
It's I certainly think writing is a net win, and I think AI is a net win, but it's not without casualties.
00:12:09.039 --> 00:12:09.360
Right.
00:12:09.519 --> 00:12:12.720
There's a a saying, uh automation is amputation.
00:12:12.960 --> 00:12:17.200
That anytime you automate something, you are taking away your ability to do something.
00:12:18.000 --> 00:12:20.399
And I think, especially in the long term, that is true.
00:12:20.559 --> 00:12:26.799
That like there are certain skills like deep debugging, for example, that are less exercised now.
00:12:27.120 --> 00:12:29.440
So when you go to do them, you are less good at them.
00:12:29.679 --> 00:12:31.600
They're also less necessary, though.
00:12:31.840 --> 00:12:39.919
So I think that that is like where AI is both the poison and the cure.
00:12:40.320 --> 00:12:44.080
And I think that is an uncomfortable place to be because it's a new technology.
00:12:44.159 --> 00:12:48.240
And I'm like, do I really want to be putting all of my faith in this thing?
00:12:48.799 --> 00:13:01.360
Especially given the fact that from like a very rationalist perspective, a lot of our practices were built on this tower of like first principles knowledge, where like you would start a software project.
00:13:01.440 --> 00:13:06.159
I'm thinking about View Component, just for example, that like day one, 100% test coverage.
00:13:06.320 --> 00:13:08.720
Day one, I knew every line.
00:13:08.960 --> 00:13:16.559
Like, literally, in the last major release we did, I forget how long ago it was, I read every single line of code.
00:13:16.720 --> 00:13:18.240
I like reread the whole library.
00:13:18.320 --> 00:13:23.120
I reread every line of documentation, I wrote, re-wrote everything that was under version control.
00:13:23.519 --> 00:13:26.080
I didn't read the image binaries, but you get the idea.
00:13:26.320 --> 00:13:34.559
Like, and I was able to understand all of what it did and remove as much as possible.
00:13:34.720 --> 00:13:43.360
Like, I in that release, my goal was to have as few lines in that repository as possible, just as a mental exercise, if nothing else.
00:13:43.519 --> 00:13:47.360
And I don't know how good I would be at doing that exercise at this point.
00:13:48.000 --> 00:13:52.799
I also don't know if that's a great point of optimization anymore.
00:13:52.879 --> 00:14:01.759
I just had a really interesting experience this week using Astra for what, like five or six sessions in a row.
00:14:01.919 --> 00:14:06.320
I basically just gave it a simple prompt, which was like, here's view component, find bugs.
00:14:07.279 --> 00:14:11.519
And it found 12 bugs each time.
00:14:12.480 --> 00:14:13.120
Oh wow.
00:14:13.440 --> 00:14:18.080
So it found like I might be exaggerating a little bit, but I think it might have found 50 bugs this week.
00:14:18.320 --> 00:14:26.000
And they were all some of them were more likely to be hit than others, but they were all the kinds of things that I think we would have hit eventually.
00:14:26.240 --> 00:14:42.879
There's a lot of people using the project in a lot of different ways, and you know, eventually the the holes in the cheese, Swiss cheese line up, but it really just made me think about how you know I was reviewing changes to all these bugs, looking at all the test cases.
00:14:43.200 --> 00:14:47.039
My foundation of trust in that code was lower.
00:14:47.200 --> 00:14:50.240
My reasoning towards the truth in that code was lower.
00:14:50.799 --> 00:14:54.720
And it's just a different place to be in.
00:14:56.000 --> 00:15:01.600
And I don't know how comfortable I'd be taking that approach without excellent test coverage.
00:15:01.840 --> 00:15:03.840
Like excellent, excellent test coverage.
00:15:04.399 --> 00:15:10.000
Um but it's fascinating to see that it found that many bugs with that much test coverage.
00:15:12.159 --> 00:15:23.279
And making me wonder about like what does that say about where we were, where we had like all this like pretty good metrics for this application, you know, for this library or framework, I should say.
00:15:23.600 --> 00:15:26.320
And uh it still had all these problems.
00:15:30.399 --> 00:15:31.039
Hmm.
00:15:32.320 --> 00:15:38.080
Yeah, um, you know, it's not limited in the way that we are.
00:15:39.039 --> 00:15:47.120
Um like it can just go into every nook and cranny and very easily find all these problems.
00:15:48.559 --> 00:15:54.879
Um I've I think I've had similar experiences with
some of my projects.
00:15:55.120 --> 00:15:56.960
Um, and that's a great benefit.
00:15:57.679 --> 00:16:03.679
It's a great benefit for it to be able to find those problems and bring them to your attention.
00:16:05.679 --> 00:16:08.799
Um a little bit different of a thing.
00:16:09.039 --> 00:16:17.440
Um I've been thinking the last few days, like I don't know, just kind of really big picture, like what is going on?
00:16:18.159 --> 00:16:20.000
What are we all doing?
00:16:20.240 --> 00:16:22.320
What are people interested in these days?
00:16:22.480 --> 00:16:31.039
Like, because okay, I myself am a content creator for lack of a term that I like more.
00:16:31.360 --> 00:16:44.480
Um and it used to be that I would write blog posts about like uh I don't know, software design, abstraction, coupling, cohesion, stuff like that.
00:16:45.360 --> 00:16:54.879
Um but I I haven't written anything in a while, partly because I had like a weird stretch in my personal life for the last few months.
00:16:55.120 --> 00:17:01.039
But now I'm kind of coming back and being like, all right, let's let's resume this work.
00:17:01.440 --> 00:17:04.720
And I sit down in front of the keyboard and I'm like, I don't know.
00:17:04.880 --> 00:17:08.640
Like, what do people want to read about these days?
00:17:08.720 --> 00:17:16.880
And I like look at Reddit, I'm like, okay, what is like upvoted on the Ruby and Rails subreddits?
00:17:17.599 --> 00:17:21.839
And like it's all almost all stuff about AI.
00:17:23.200 --> 00:17:27.759
Um, and it's like, what are people wanting?
00:17:28.400 --> 00:17:29.200
I don't know.
00:17:29.599 --> 00:17:30.799
Like, what are people thinking about?
00:17:30.960 --> 00:17:32.240
What are they wanting to talk about?
00:17:32.319 --> 00:17:33.200
I'm not sure.
00:17:34.000 --> 00:17:40.720
I mean, it's introduced a certain amount of uncertainty across the entire discipline.
00:17:41.039 --> 00:17:51.440
Like I think we're finding kind of across the board and all the things we've done in our all the professional activities we've done habitually have been affected by this change.
00:17:52.480 --> 00:17:56.720
And I view both that as both exciting and terrifying.
00:17:57.680 --> 00:17:59.039
I view it as exciting.
00:17:59.200 --> 00:18:05.519
I'll say this, and I and I have to wonder if this is true for you, but for me, I was in a little bit too much of a groove.
00:18:06.880 --> 00:18:10.000
Like I had kind of set myself on a pretty steady path.
00:18:10.079 --> 00:18:13.119
Like I'm not trying to get promoted or anything at work.
00:18:13.440 --> 00:18:20.160
And you know, having all these kids, like I wasn't trying to like push myself as much professionally as I might have in the in the previous years.
00:18:20.480 --> 00:18:30.319
But really, right around when these, you know, the more revolutionary agentic kind of models landed was right about when I was kind of coming out of the woods a little bit.
00:18:31.200 --> 00:18:45.039
And I was like kind of dreading going back to just doing more of the same of and I say this like really politely, like I still really like like I still really liked what I was doing, still like what I'm doing.
00:18:45.279 --> 00:18:58.160
Um but AI has been such a disruptive force in the positive for me, and that it's just m forced me to reassess a lot of things, like you're saying.
00:18:58.319 --> 00:19:01.839
Like I and I think that it's a healthy exercise in general.
00:19:01.920 --> 00:19:04.000
Like I'm a very habit-driven person.
00:19:04.160 --> 00:19:20.559
I like put so much on the calendar, like I put all my workouts on the calendar, I put like I have a really good to-do list ritual, like I'm really regimented, but that can limit me cognitively into certain modes of thinking.
00:19:20.799 --> 00:19:31.119
And I think that what is the healthiest part of this revolution is the way that it it has made us question old practices.
00:19:32.400 --> 00:19:36.000
So I'll pick one off the shelf for you that is a great one to talk about.
00:19:36.160 --> 00:19:37.119
Code review.
00:19:38.400 --> 00:19:46.079
Like hindsight is 2020, but man, we do some weird stuff with code review.
00:19:46.880 --> 00:19:49.039
Like, code review is really weird.
00:19:49.440 --> 00:19:50.559
Like, think about it.
00:19:50.720 --> 00:19:52.000
Like, really strange.
00:19:52.160 --> 00:20:01.200
You write this thing, and at one point in time, you get one other human who they look at your tests and they're like, okay, the tests exercise us a certain way.
00:20:01.359 --> 00:20:04.480
They read the code and like, okay, I learned something from what you did.
00:20:04.720 --> 00:20:08.000
They also run the code in their heads, was a thing a lot of us did.
00:20:08.079 --> 00:20:11.759
We'd like read it and be like, oh, what about this edge case?
00:20:12.160 --> 00:20:15.920
That is like an interesting task to put on humans.
00:20:16.240 --> 00:20:18.319
And it already did not scale well.
00:20:18.400 --> 00:20:25.839
Like, we would have to limit our PRs to like what 100-line diff was like roughly the comprehension level for like functional changes.
00:20:26.240 --> 00:20:36.559
Um there are a lot of these things that like are now falling over, falling on their face as we have a 10x increase in in code volume, right?
00:20:36.720 --> 00:20:39.680
And that and this is and this is trickling down to other parts of the system too.
00:20:40.960 --> 00:20:56.799
Yeah, all this a lot of the effects of or a lot of the things that this AI revolution has revealed, um I found extremely depressing.
00:20:57.279 --> 00:21:12.160
Um like it has revealed to me like how many things um how many things, how many people just deeply don't understand or misunderstand.
00:21:12.799 --> 00:21:19.039
Like the code review thing, ask ten people, like why do we do code review?
00:21:19.599 --> 00:21:28.480
And you'll probably get different answers, and sadly, probably not very good ones.
00:21:30.160 --> 00:21:35.200
Um, and it's kind of like um theater.
00:21:36.160 --> 00:21:51.279
Like a lot of times you you put up a PR and somebody looks at it and they rubber stamp it, and a second person looks at it, and they just like find some trivial thing to comment on.
00:21:52.400 --> 00:21:59.200
Meanwhile, the code is garbage, and it's like, what is this really accomplishing?
00:21:59.279 --> 00:22:13.119
It's it's Nah, and and then uh for code reviews that are blocking, like it has to get reviewed and approved before it can be merged, that introduces such an enormous um time bottleneck.
00:22:13.279 --> 00:22:45.359
Like I was trying to um I I added a new Grafana graph to a service the other day, um and it took me like 30 seconds to have Codex write the code for it, and then a number of days to get the approvals that I needed, and then I noticed that I like named a file, something I didn't want, and so I renamed the file, and then I had to go ask the same person for a review again.
00:22:46.240 --> 00:22:58.640
Um, and it's I've thought to myself, like, if I had a competitor and I could wish any curse upon them that I could, I would wish for them to have blocking code reviews.
00:22:58.799 --> 00:23:03.680
Although I probably wouldn't need to add that because almost everybody already does it.
00:23:03.839 --> 00:23:15.599
But it's one of those things that's just like frankly, really dumb, and like uh um it's just dumb, yet everybody does it.
00:23:16.079 --> 00:23:23.519
Well, and it wasn't a bottleneck as much before, it still was to a certain extent, so I think we didn't notice it.
00:23:23.680 --> 00:23:33.200
Now that we have this like way, like it's like a tsunami of code because it's not a wave, because a wave comes and goes, but a tsunami just keeps coming, right?
00:23:34.079 --> 00:23:41.680
And I think that it's forcing us to consider what those truths are and like what the goal was.
00:23:41.759 --> 00:23:47.920
Like we have we have the same required reviews things, and there's a there are some legal reasons we do it, like as they're common at most companies.
00:23:48.000 --> 00:23:50.400
Like you have to say that someone signed off on it.
00:23:51.200 --> 00:23:58.400
The thing that's made me think about is like what does it mean to really attest to a PR?
00:23:58.480 --> 00:24:08.079
Because that's what you're doing, is you're saying I approve this thing, and it's there's some you're you're committing some act of testimony about a diff.
00:24:09.200 --> 00:24:20.319
And what's been interesting to me is to study and start to look at what comments are being left.
00:24:22.559 --> 00:24:27.119
Starting to study like what changes lead to production issues.
00:24:27.599 --> 00:24:29.920
And these are great things to put AI on.
00:24:30.240 --> 00:24:49.119
So like I know I've worked with Copilot, we use Copilot on top of you know any number of models, and had it summarize code review comments for a few peers for the past
like six months, just to like specifically the comments that led to changes in the code, just as like a study of what is the function of code review for these people.
00:24:49.680 --> 00:24:57.759
And what it was finding for me is that we had really poor test coverage in some really key areas.
00:24:57.920 --> 00:25:06.480
And like, I don't say poor because like there was still coverage, but like the systems we had in place were not adequate defenses.
00:25:06.640 --> 00:25:08.880
We needed people as a defense.
00:25:09.279 --> 00:25:16.960
And that premise is a very tricky one to maintain in this era of higher code throughput.
00:25:17.200 --> 00:25:18.960
Because what what premise is?
00:25:19.200 --> 00:25:22.079
That pe people as a defense, people as a safety mechanism.
00:25:22.240 --> 00:25:25.839
Like if you're truly expecting, you know, we had this comp just this week.
00:25:25.920 --> 00:25:38.079
I was working on I I uh my my job at GitHub right now is to keep Ruby and Rails up to date, which means keeping really just keeping our gem file up to date, which is a massive undertaking.
00:25:38.240 --> 00:25:49.279
Uh and we had an upgrade that like two of us agreed on, but one person very rightfully disagreed and caught an issue that was like somewhere in between us and Rails.
00:25:49.359 --> 00:25:52.480
It really wasn't us, but it really wasn't Rails, it was like the combination.
00:25:52.720 --> 00:26:01.519
It's kind of like I forget, there's like a complicated like Git puzzle you can have where like tests pass on branch A and branch B, but the combination of them creates a failure.
00:26:01.680 --> 00:26:04.240
It's with that kind of like logic puzzle.
00:26:04.640 --> 00:26:08.160
Um so it just so happened that like this person saved us from like a production issue.
00:26:08.319 --> 00:26:11.839
Now it would have been the kind of thing that we would have like caught mid-deploy and just rolled back.
00:26:11.920 --> 00:26:14.079
Like it's not like a huge risk kind of thing.
00:26:14.400 --> 00:26:23.920
But it really highlighted for me that the safety factor in our systems is under a lot more stress in this environment.
00:26:24.079 --> 00:26:31.119
And I I don't know if we can like code review our way out of it at this volume with the same number of people.
00:26:31.200 --> 00:26:40.480
You'd almost need to like change the ratio of staffing on your team to be like one author, five or you can't have like every author can't be reviewing.
00:26:40.720 --> 00:26:41.519
You get what I'm saying?
00:26:41.599 --> 00:26:45.599
Like you almost need like to dedicate more of your time to review.
00:26:47.519 --> 00:26:51.839
Yeah, I I'm familiar with this challenge.
00:26:52.559 --> 00:26:59.039
Um, and I I've seen people say things like, I'm just drowning in reviews now.
00:26:59.279 --> 00:27:15.599
It's it's so cheap to comp it's so cheap to generate code and so expensive to review it, and now there's like way more code than there was before, and so there's just this extraordinary burden of reviews.
00:27:16.880 --> 00:27:23.680
Um, but to me, that is a sign um it's a sign of something.
00:27:24.000 --> 00:27:30.079
Um, it's it's kind of like a bit of a um okay.
00:27:31.119 --> 00:27:43.119
I've made this analogy before where like in the universe nothing can move faster than the speed of light, and there's so many like downstream consequences because of that fact.
00:27:43.759 --> 00:28:02.799
Um and in the systems, um you can't make changes to the system faster than the people responsible for the system can understand those changes, or else you're gonna have some trouble.
00:28:03.440 --> 00:28:10.960
Um, you know, maybe not immediately, but you're like you're accumulating potential trouble.
00:28:11.200 --> 00:28:19.680
And you can only accumulate potential trouble for so long before some of that potential trouble turns into actual trouble.
00:28:19.920 --> 00:28:20.559
Right.
00:28:21.759 --> 00:28:46.000
And so I think what is happening when people are are buried under this flood of code review is that the people in the organization are not understanding um that even though we have the ability to generate great amounts of code very quickly, the like fundamental laws of the universe still apply.
00:28:47.519 --> 00:29:03.599
Um and you're not you're not like gaining anything by writing more code that you're not gaining anything by writing code at a higher rate of speed than it can be understood.
00:29:04.559 --> 00:29:08.400
It's like going to a restaurant and ordering 10 entrees.
00:29:08.720 --> 00:29:20.559
It's like it's good to eat food, but it's not good to have ten times as much food as you can eat, because like you're gonna eat one of those entrees and then the other nine, you can't do anything with them.
00:29:20.640 --> 00:29:22.000
They're just waste.
00:29:22.319 --> 00:29:22.799
Right.
00:29:23.119 --> 00:29:26.160
So that's that's the same with all this extra code.
00:29:26.400 --> 00:29:31.279
I I don't know why that's not more like widely understood, but that's that's my take on it.
00:29:31.599 --> 00:29:36.480
I mean, you do see though, more code is landing.
00:29:36.799 --> 00:29:51.279
And I and I think that just like the I think the non-controversial thing you can say is that there are more lines of code going to production, more diff lines going to production per capita than there were a year ago.
00:29:52.000 --> 00:30:03.359
Which means that factually, I believe, the confidence in those lines is lower because I view confidence as like a one-to-one relationship with number of lines of code per capita.
00:30:03.519 --> 00:30:10.480
Like the more you have to read, the less confident you're going to be in it.
00:30:11.440 --> 00:30:17.599
Unless we are changing the equation, like or shouldn't say changing the equation.
00:30:17.680 --> 00:30:19.039
I think we can change that equation.
00:30:19.279 --> 00:30:22.640
And that I think we can change the
factors in that equation.
00:30:22.799 --> 00:30:28.720
One is you can change the automated levels of confidence you have in the system.
00:30:29.200 --> 00:30:35.119
You can also change your ability to respond to bad changes in the system.
00:30:35.440 --> 00:30:38.880
So, like, we're getting really good at rolling back changes.
00:30:39.200 --> 00:30:46.000
We're getting really good or have gotten really good at deploying smaller changes or feature flagging, for example.
00:30:46.160 --> 00:30:53.359
Like all these things can make your mean time to recovery, MTTR, is what a lot of people call it, faster.
00:30:53.680 --> 00:31:02.319
And that can permit certain lower levels of verification, of like manual verification.
00:31:02.640 --> 00:31:05.359
I think those things kind of have to be true.
00:31:05.599 --> 00:31:08.640
The nice thing is that AI is great at building those things.
00:31:08.799 --> 00:31:13.920
Like, so for example, we had a we had a PR, I had a PR the other day.
00:31:14.079 --> 00:31:20.960
I was upgrading our a library we use to generate PDFs, just a standard, like kind of dependabot kind of thing.
00:31:21.119 --> 00:31:24.000
And the reviewing team said, Great, this this looks good.
00:31:24.160 --> 00:31:28.559
I need to go run a script to generate these PDFs and just make sure that nothing is wrong.
00:31:28.799 --> 00:31:32.000
And I was like, Oh, well, I didn't know to do that.
00:31:32.240 --> 00:31:33.359
CI didn't tell me to do that.
00:31:33.440 --> 00:31:34.640
CI was green.
00:31:35.200 --> 00:31:36.559
You know where this is going.
00:31:36.799 --> 00:31:40.240
Like, surely we can write a test for that.
00:31:40.480 --> 00:31:41.440
So I did.
00:31:41.759 --> 00:31:44.720
And it caught bugs that were already there.
00:31:44.880 --> 00:31:53.440
Because when you ran the test a couple times, like some things there was an unordered select, classic, like easy thing to miss, where you don't have an order by ID.
00:31:53.599 --> 00:31:57.440
And then the database doesn't guarantee that it returns things by ID.
00:31:57.519 --> 00:31:59.279
It returns them by page in the database.
00:31:59.359 --> 00:32:03.839
So if you have like deletions or additions, things that can come in quote unquote out of order.
00:32:04.079 --> 00:32:09.200
Like they're not coming unless you like order by the ID or ideally by like a created ad or something.
00:32:09.440 --> 00:32:19.279
Um so that test uncovered that bug, and that now means that we can move faster when we change that code because we don't need to run that manual validation step.
00:32:19.519 --> 00:32:24.559
And I think that that is like where AI is the poison and the cure.
00:32:24.799 --> 00:32:30.400
Yes, it is poisoning us with this huge with tenantres on the table.
00:32:30.559 --> 00:32:35.599
I don't know if I have the right metaphor here, but because you're still not going to eat the tenantres.
00:32:36.480 --> 00:32:45.839
But it's I think it can, in certain circumstances, allow us to test our way out of these things by making it cheaper to write the tests that we might not have previously.
00:32:46.000 --> 00:32:47.200
Maybe even the more useful tests.
00:32:47.279 --> 00:32:55.599
Like I think it would have been easier to write like a unit test for some of those PDFs, for example, but actually running the code that generates the PDFs, doing an image diff, that was more complicated.
00:32:55.680 --> 00:32:59.759
Like standing that all up took, you know, changing like our base image for things.
00:32:59.920 --> 00:33:11.119
And that was something that would have been maybe too expensive to justify, but now is something that can be done as like a very, very, very side hustle kind of side thread of my main work.
00:33:11.839 --> 00:33:16.559
I want to put a nuance on or point out a nuance in what I'm saying.
00:33:16.799 --> 00:33:24.640
Um, I'm not saying that I don't think we can ship changes to production faster.
00:33:24.880 --> 00:33:26.799
I think we can and we have.
00:33:27.119 --> 00:33:39.920
Um it's that I think before we were making changes to systems at a rate that was slower than the maximum rate we could understand.
00:33:41.039 --> 00:33:47.680
And now some people are releasing changes at a rate that's faster than what they can understand.
00:33:48.640 --> 00:34:15.039
At the same time, I agree with what you're saying, which is like if in the I mean, I'm not saying that you're saying this, but if in the past we were releasing changes at 20% of the rate of the maximum rate that we could understand the changes going out the door, then we have room to do 5x that much, and we're still okay.
00:34:15.519 --> 00:34:23.760
We just can't do anything more than that without accumulating some potential trouble.
00:34:25.119 --> 00:34:25.760
I think.
00:34:26.159 --> 00:34:32.079
I just I want to asterisk all that with I'm not a hundred percent sure that I agree with myself.
00:34:32.559 --> 00:34:49.679
Well, I think that what I would say is that this is another thing that I think has been very enlightening for me is realizing that what I think you're saying was true, but perhaps only at the point of authorship.
00:34:50.639 --> 00:34:52.000
Only at the point of authorship.
00:34:52.400 --> 00:34:56.960
Because these systems change outside of your purview.
00:34:57.119 --> 00:35:03.280
Like you land your code, someone else changes it a year later.
00:35:03.519 --> 00:35:06.079
Or you land your code, you leave.
00:35:07.039 --> 00:35:13.039
Like the ability to do things with confidence was always based on the test suite.
00:35:14.400 --> 00:35:16.800
Because at least in the long term.
00:35:16.960 --> 00:35:22.320
In the short term, yes, code review is like a kind of a friction point for this where it's like, okay, we're gonna review this change.
00:35:22.480 --> 00:35:33.119
But your confidence in not making that same mistake that was caught in the code review was entirely almost entirely
predicated on the test suite and you know, tribal knowledge, right?
00:35:33.199 --> 00:35:38.880
Which, like, you know, we have a multi-thousand engineer company.
00:35:38.960 --> 00:35:44.480
You know, we have a what I want to say, I think it's safe to say that we have maybe around a thousand people contributing to our monolith.
00:35:44.719 --> 00:35:50.079
But how many people have contributed, how many individuals have contributed to that monolith in the history of the company?
00:35:50.239 --> 00:35:52.000
It's probably several times that.
00:35:52.400 --> 00:35:55.199
So, like, those people don't work at GitHub anymore.
00:35:55.280 --> 00:36:00.719
They can't be coming back to review their code and telling you why they did that thing.
00:36:01.119 --> 00:36:10.159
And when you build on top of what they've done, you are hoping that you are kind of guessing on top of that foundation.
00:36:10.800 --> 00:36:24.480
And that's why, to me, I'm starting to feel even stronger feelings against things like code comments, for example, and documentation, because these things are not durable truth.
00:36:24.719 --> 00:36:32.960
Like we had a situation the other day where we had a code comment that was incorrect, and I went down a thread on that code comment for half a day.
00:36:33.280 --> 00:36:39.119
And luckily the author of the comment came in and corrected me, but it was a fairly time-sensitive thing.
00:36:39.440 --> 00:36:46.159
And I think that that's why what this moment has really led me to is studies of automated verification.
00:36:46.320 --> 00:36:52.000
Like I think that if there's anything where we need to expand our perspective creatively, it's in that realm.
00:36:52.320 --> 00:37:03.519
Because there are so many things we did implicitly, organizationally, that are just falling over, or really we're kind of already falling over, but we were like staying ahead of them enough, like we were picking up the pieces fast enough.
00:37:03.679 --> 00:37:15.840
And I think that that is where we're most likely to fall behind as we ship more code, is that is you're kind of saying we're like we're accumulating these potential issues at a higher rate.
00:37:16.079 --> 00:37:34.079
And I think that to keep the same safety factor, which I think is a totally reasonable goal, that we should say that we have the same number of customer-facing defects in 2027 as we did in 2024, that means that our defect rate might need to be 50% of what it was in 2024 because we're shipping so many more changes.
00:37:34.320 --> 00:37:43.599
And that shifting that uh equation uh I think is basically a requirement unless our customers are going to accept lower quality software.
00:37:47.440 --> 00:37:48.800
Yeah, okay.
00:37:49.039 --> 00:37:53.519
Yeah, you're bringing a perspective that I hadn't really thought about.
00:37:54.239 --> 00:38:03.039
And you're making me rethink some of my prior positions, uh, which is good.
00:38:04.239 --> 00:38:13.519
Um, and I'm I'm curious Okay, switching topics yet again, if I may.
00:38:13.760 --> 00:38:20.960
Um what are you personally like paying attention to these days?
00:38:21.440 --> 00:38:25.599
Is it different from that's not how I meant to put it?
00:38:25.760 --> 00:38:32.239
It's like how are you like how are you doing professional development?
00:38:32.400 --> 00:38:35.760
Um, is maybe the question that I'm that I want to ask.
00:38:35.920 --> 00:38:42.000
And how has that changed, if it has changed, since all this stuff has happened?
00:38:42.400 --> 00:38:55.360
Okay, so I have actually had something I wanted to talk to you about in this specific space that I would actually like to ask you, which is what is a tech conference in 2027?
00:38:55.679 --> 00:38:56.559
Oh man.
00:38:56.880 --> 00:38:57.920
Like, what is the point?
00:38:58.719 --> 00:39:02.239
And I say this because I'm on the program committee for RubyConf next year.
00:39:02.480 --> 00:39:09.360
Oh and we're starting to think about you know, how do we position, like what are the topics we want to do, like what do we want this conference to look like?
00:39:09.519 --> 00:39:12.800
And I I know you are planning, you've planned conferences in the past.
00:39:13.039 --> 00:39:16.639
Um Yeah, I and that is professional development, right?
00:39:16.719 --> 00:39:19.679
Like, how do you think about that in this current age?
00:39:20.159 --> 00:39:23.679
And did you know that I was involved with RubyConf 2026?
00:39:23.920 --> 00:39:24.960
Yeah, yeah, yeah.
00:39:25.119 --> 00:39:25.519
Yeah.
00:39:25.760 --> 00:39:32.800
Uh in case in case you didn't know, dear listener, I I co-chaired RubyConf 2026.
00:39:32.880 --> 00:39:35.679
And so, yeah, I faced some of these same questions.
00:39:35.840 --> 00:39:47.519
Um, for a long time I've thought that conferences are like ostensibly something that exists for professional development.
00:39:47.920 --> 00:40:03.519
Um, and it's kind of a polite fiction, but really, you know, it's it's like employers often have viewed and still view conferences as like an investment.
00:40:04.159 --> 00:40:10.960
But I don't think it's exactly it's not mostly investment, it's part investment, but I th I don't think it's mostly investment.
00:40:11.119 --> 00:40:13.039
I think it's mostly perk.
00:40:13.920 --> 00:40:28.480
Um like getting to go to conferences is a perk of working here rather than sending your employees to a conference is a way to invest in their professional development.
00:40:29.280 --> 00:40:39.679
Um and this question, like I think this question only makes sense through the lens of the people who are attending the conferences.
00:40:40.400 --> 00:40:46.880
Because, like, what is a conference for depends highly on who you ask.
00:40:47.039 --> 00:40:58.079
Like, for maybe, I don't know, 80% of developers, the answer to what are conferences for is nothing because they don't go to conferences and they never will.
00:40:59.119 --> 00:41:03.119
People who do go
to conferences, why do they go to conferences?
00:41:03.760 --> 00:41:12.159
Um, I think a lot of them go to like um to like put gas in their tank.
00:41:13.280 --> 00:41:26.000
You by going to conferences over a period of years, you tend to see the same people over and over, and you develop a social circle that's made up of people who live all over the country and world.
00:41:27.039 --> 00:41:35.679
Um, and it's funny, some people like end up seeing that group of people more often than they see their like local friends.
00:41:35.920 --> 00:41:40.239
That certainly has been the case with me, and so that's a big part of it.
00:41:40.320 --> 00:41:45.920
But I don't want to I don't know if like just calling it socialization is the right label to put on that.
00:41:46.159 --> 00:41:51.039
It's more like some kind of um fulfillment or something like that.
00:41:51.280 --> 00:42:18.159
Like we have a deep psychological need to be like part of a tribe, um and so we go to conferences for that, but then as far as like the content of the conference, um like I like I like to be made aware of new things, maybe especially things that I didn't know I didn't know.
00:42:18.880 --> 00:42:36.800
I'm not a big talk attender myself, and when I do the the talks that I like, it's usually like I see the talk, and there's a little tidbit in a talk that inspires me to go like dig deeper into something once I get home.
00:42:36.960 --> 00:42:45.760
It's not necessarily that the c the talk itself is a a piece of education that is like complete and usable.
00:42:45.920 --> 00:42:50.719
It's more like a hint that that I'm and I'm gonna go use that hint later on.
00:42:50.960 --> 00:42:53.039
Anyway, that's those are some thoughts.
00:42:53.360 --> 00:42:56.639
No, no, I uh I resonate with a lot of what you said.
00:42:56.800 --> 00:43:05.840
I think that there is for one, so for example, like I as one of the keepers of GitHub's gem file, I have to do a lot of open source stuff.
00:43:06.159 --> 00:43:11.360
So the more people that I know in the community, just the more enjoyable that is.
00:43:11.440 --> 00:43:25.360
Like it's nice to that you know, I've had to do some actually over the past year I've done quite a few like uh open source contributions, and they've a chunk of them have been to projects owned by people that I've met at conferences.
00:43:25.440 --> 00:43:29.199
And it's just been really fun to have that connection and like they know who I'm I am.
00:43:29.280 --> 00:43:32.079
I'm not just like a stranger coming in to make a contribution.
00:43:32.159 --> 00:43:40.400
And I think that there's like something magical about that in our industry specifically, because I think Ruby has always had such an open source bent to it.
00:43:41.199 --> 00:43:47.360
I'd also say that your comment about like filling up your tank really resonates with me.
00:43:47.519 --> 00:43:53.519
I find that conferences to me, first and foremost, are like a source of creative energy.
00:43:54.480 --> 00:44:04.000
And I think it's the spaces they create being around a lot of people who are also who also care and are the Type of people who would go to a conference just fills up fills me up.
00:44:04.079 --> 00:44:06.000
It also drains me in other ways.
00:44:06.400 --> 00:44:13.119
But um it's a lot of the same reasons I go to our meetup really regularly.
00:44:13.199 --> 00:44:17.119
Like we have a Ruby meetup in Boulder that's excellent, that's been going on for like 20 years now.
00:44:17.199 --> 00:44:18.320
It's incredible.
00:44:18.559 --> 00:44:22.639
Um and it's yeah that I need that like almost every month.
00:44:22.719 --> 00:44:25.280
And I think this is especially true in the era of remote work.
00:44:25.599 --> 00:44:26.400
Oh yeah.
00:44:27.199 --> 00:44:32.880
Yeah, I think having a remote job, frankly, is like pretty psychologically unhealthy.
00:44:33.119 --> 00:44:50.159
Like our whole modern way of living is you know, it it's it's not like a novel insight or something, it's like a widely held view that like modern life is not psychologically healthy healthy, even going back, you know, a few decades.
00:44:50.639 --> 00:44:53.280
Um but uh especially now.
00:44:53.760 --> 00:45:02.639
Um but something something you said made me think about another reason for going to conferences, which is like intellectual stimulation.
00:45:02.800 --> 00:45:09.519
I think something you said was like you didn't use those words, but like that's what came to mind.
00:45:09.679 --> 00:45:24.079
It's like not exactly necessarily learning something new, but being able to have interesting conversations about the things that you're interested in with other people who like are in that world.
00:45:24.880 --> 00:45:27.519
I don't have personally, I don't have that locally.
00:45:28.480 --> 00:45:35.119
Um I have to go to a conference to have that, and it's a really nice it's a really nice treat.
00:45:35.599 --> 00:45:38.719
Yeah, and certain professional situations can provide that.
00:45:38.880 --> 00:45:46.639
Like I'd say I'm really fortunate to have some great colleagues that the pair programming we do feels like that quite often.
00:45:46.800 --> 00:45:59.360
You know, like I work with uh my colleague Daniel uh Colson and we like sometimes we'll be looking at like Ruby heap dumps, and I'm just like, whoa, this guy, this guy knows some stuff I don't know.
00:45:59.440 --> 00:46:11.760
But it's just it's like one of those things where it's like I can just the act of trying to understand what someone else is doing or like learning something interesting someone else did, even if it's not completely relevant, does something for me cognitively.
00:46:11.920 --> 00:46:23.360
And I think that like in this age of AI, maybe that is like something that is more interesting as like as a counterforce to that kind of deintellectualizing feeling we were both lamenting at the beginning of our conversations today.
00:46:23.679 --> 00:46:26.159
But
you so you asked about like professional development.
00:46:26.239 --> 00:46:28.400
Like, like what do I actually do?
00:46:28.639 --> 00:46:35.920
Well, these days I'm reading every PR that lands to Rails, every PR that lands to Ruby, because that's just like part of my work.
00:46:36.320 --> 00:46:47.840
But I find that to be interesting in and of itself because I'm seeing what types of things are changing in these projects, because those changes are in response to larger forces in the industry.
00:46:47.920 --> 00:46:52.719
Like I see all these Ractor-related changes going into Rails, and it's just interesting to see.
00:46:52.960 --> 00:46:58.880
Like we don't have any explicit plans for using that code, but it does affect our contributions, say, to Rails.
00:46:59.199 --> 00:47:12.000
The other thing is that I'm starting to look more towards maybe some maybe a little more non-technical sources of learning inspiration.
00:47:12.159 --> 00:47:16.159
So like I'm reading a book now called Refactoring English by Michael Lynch.
00:47:16.239 --> 00:47:19.039
It's excellent and just talks about writing techniques.
00:47:19.280 --> 00:47:25.360
I think they matter more and more, especially in an age where like basically all we're doing is writing.
00:47:25.440 --> 00:47:36.719
I think being a really good writer almost matters more because there's just like so much text to be consumed that like making sure your writing respects the readers in your life, I think is super important.
00:47:37.199 --> 00:47:42.079
So making that more a part of my practice has been beneficial.
00:47:42.239 --> 00:47:50.480
The other thing that I'm kind of curious from you that I've been trying to learn about is like, what the heck does like a flow state look like in this day and age?
00:47:50.880 --> 00:47:56.000
Because it used to be that you could be like single tasking, deep into something, headphones on.
00:47:56.480 --> 00:48:02.719
And now it's like conversely, because agents are oddly slow, they're both fast and slow.
00:48:02.960 --> 00:48:05.760
Like the feedback loop is longer, even though they're getting more done.
00:48:05.840 --> 00:48:10.880
So you're ending up with these different size gaps that I usually fill with working with another agent.
00:48:10.960 --> 00:48:14.159
Like I'll sometimes have like five or six agents going at a time.
00:48:14.639 --> 00:48:36.079
Um, but I'm trying to, that's where a lot of ultimately my inquisition is professionally, is trying to find maybe not a new routine, but like uh something that is now sustainable in this new world because I knew what it was to be a sustainable professional programmer, you know, working normal hours two years ago.
00:48:36.320 --> 00:48:48.320
Answering that question now, I don't have such a solid found, like solid idea of what that should look like in a way that's gonna like make me feel like I'm not burning out slowly or quickly.
00:48:48.880 --> 00:48:49.519
Yeah.
00:48:50.960 --> 00:48:51.599
Yeah.
00:48:52.000 --> 00:49:07.519
Um, so at my day job, I don't do a huge amount of coding anyway, and so that's been like the timing kind of coincided with like when I got a different job and when AI hit an inflection point.
00:49:07.760 --> 00:49:21.519
Like there's kind of consensus among people I know that like the early part of 2026 was a big inflection point for AI, and that is when did I start my job?
00:49:21.679 --> 00:49:24.960
I started my job like nine months before that, huh?
00:49:25.039 --> 00:49:26.960
So I guess that comment doesn't really hold up.
00:49:27.039 --> 00:49:30.239
But anyway, I don't write a huge amount of of code at work.
00:49:30.559 --> 00:49:40.000
Um but on Saturn CI, I write a lot of code, my um continuous integration platform that I've been building for the last few years.
00:49:40.239 --> 00:49:53.199
And I used to uh fill the waiting time with working with other agents, but then I went back to single tasking because I have found that I would get confused.
00:49:54.800 --> 00:50:04.719
And I've even before AI, I've like tried to switch between two tasks when like, I don't know, you're waiting for tests to run or something like that.
00:50:05.039 --> 00:50:47.199
And I find that I forget which task is like the primary task and which one is the secondary task, because there's almost always one that's more important, and the other one is just kind of filler, something that is not unimportant, but you picked it just to pick something rather than because it's the thing you need to do today or whatever, and I forget which is which, and then I get like I get my priorities screwed up, and I discover that I've been working on the secondary task for 45 minutes and neglecting the primary task, and I'm the bottleneck, it's just waiting on me.
00:50:48.079 --> 00:50:52.880
So I'm not being more efficient, I'm just being busier.
00:50:53.920 --> 00:51:01.599
And so I've gone back to monotasking, and it you know, this is this is a statement that is generally true.
00:51:02.159 --> 00:51:13.440
Um oftentimes being efficient feels inefficient, and doing things that feel inefficient are actually very inefficient.
00:51:15.519 --> 00:51:16.480
I agree.
00:51:17.920 --> 00:51:21.360
I wish that I could have A-B tested myself for the past like year.
00:51:21.679 --> 00:51:24.800
I feel like this is like a this is something I've been meaning to do.
00:51:24.880 --> 00:51:31.760
I have a I have a friend, Brooke, he might have met Brooke Coolman, brilliant engineer.
00:51:32.480 --> 00:51:39.599
I have met a man named Brooke, which is probably not a huge pool of people, so it might be the same person.
00:51:40.079 --> 00:51:43.360
And uh he doesn't use AI much at all.
00:51:43.920 --> 00:51:46.960
And what I've been meaning to do is to do a bake off with him.
00:51:47.039 --> 00:51:59.280
Like I'd love to just like sit on a Zoom call with him for half a day and work on the same like open source project problem, but like see who actually is faster or better.
00:52:00.559 --> 00:52:07.360
And just kind of really take a step back and evaluate like what the real trade-offs are.
00:52:08.559 --> 00:52:19.360
I suspect that multitasking can be more effective, but I don't think it is out of the box.
00:52:19.920 --> 00:52:37.360
Like, I think this is kind of what I've been getting at in our conversation that I feel like there are ways of working that we have yet to totally discover, or maybe we've discovered them, but we we haven't fully isolated them that will allow us to better thrive in this new environment.
00:52:37.679 --> 00:52:46.079
So, like, for one, figuring out how to manage the code review workflows is a is a new challenge.
00:52:46.159 --> 00:52:52.239
And I think that if we we might find a more clever solution, for example, that like makes that feel different.
00:52:53.599 --> 00:53:07.360
Or we make our like so, for example, one thing I've been doing now is I have when an agent generates a PR, I have it do a self-review explaining all of the code with comments, like what change what necess necessitated each change.
00:53:08.079 --> 00:53:12.320
Uh like examples of like why each test case was written a certain way.
00:53:12.480 --> 00:53:15.199
And that makes the act of code reviewing easier.
00:53:16.000 --> 00:53:26.320
And I have to wonder whether for a lot of these things, whether we're thinking about that them in the old way, which is why they feel and probably are to a certain extent less efficient than we think.
00:53:26.719 --> 00:53:30.400
Um I view that as a temporary phenomenon.
00:53:30.639 --> 00:53:36.719
I think that we will learn new ways of working within these systems, and we will come out the other side more productive.
00:53:37.440 --> 00:53:42.480
Something else that I expect to happen is I expect LLMs to get faster.
00:53:42.800 --> 00:53:43.280
Right.
00:53:43.519 --> 00:53:46.639
And so you'll give it a prompt and it'll say done.
00:53:47.599 --> 00:54:06.239
And then the the ball is back in your court and it it spends basically all its time in your court because every time you pass it over to the LLM side, it just hits it back immediately instead of taking a minute or whatever it might take now.
00:54:06.480 --> 00:54:41.519
So that's something that I'm always thinking about because I don't want to, you know, remember when there was that whole prompt engineering thing and people were constructing these big like JSON prompts and stuff like that, and it's like I've seen those kinds of things as they have come and gone, and I'm just like, guys, like the AI is just gonna get better and make what you're doing irrelevant sufficiently soon that everything you did was pretty much a waste of time, and that's that's what's been happening.
00:54:41.920 --> 00:54:51.920
Um, and so I'm consciously trying not to get too comfortable with the way things are because they're probably gonna get different soon.
00:54:52.400 --> 00:54:56.400
Okay, having said
all that, uh I do a similar thing to you.
00:54:56.559 --> 00:55:10.000
Like I'll ask for a change, um, I'll look at what the change is, which may or may not mean looking at every single line, but I at least want to get the essence of the change.
00:55:10.880 --> 00:55:17.360
Um, and I will often have sometimes I just look at it and it looks fine and good.
00:55:17.760 --> 00:55:31.360
Um, sometimes I'll say, give this a review, and I have a specific like test design review skill that I wrote, and a software design reviews skill that I wrote.
00:55:31.840 --> 00:55:53.119
Um, and part of the reason I I put it through those is because like sometimes I see code that I know is problematic and I want to experiment and see like, okay, this thing that I have in my head of what I don't like about this test, for example, will you find it if I tell you just to review it?
00:55:53.360 --> 00:56:00.960
And if not, can I like change the review criteria so that from now on you will find such things?
00:56:01.280 --> 00:56:04.639
I find that to be a very interesting exercise.
00:56:04.880 --> 00:56:11.760
And so I've been accumulating these things, and I found that it gets pretty good.
00:56:13.440 --> 00:56:16.079
So that's that's how I do that part.
00:56:16.719 --> 00:56:22.800
So when you're working this way, when you have little gaps, when you're waiting for the LLM, what do you do?
00:56:23.519 --> 00:56:24.719
What do I do?
00:56:25.280 --> 00:56:26.480
Do you look at the wall?
00:56:27.440 --> 00:56:29.039
I don't look at the wall.
00:56:30.320 --> 00:56:31.599
I don't know what I do.
00:56:34.639 --> 00:56:36.480
Maybe I watch a YouTube video?
00:56:36.880 --> 00:56:37.679
That's what I do.
00:56:37.840 --> 00:56:38.800
Or I have been doing.
00:56:38.880 --> 00:56:46.639
I'm I'm trying not to now because this is the thing I'm I'm fascinated with is like these kind of cognitive timelines we put ourselves on.
00:56:46.719 --> 00:56:48.480
Like what is your brain doing?
00:56:48.960 --> 00:56:56.480
Like what is your time budgeting for your like during your pro like a pr an hour, like the best hour of your day?
00:56:56.559 --> 00:56:59.280
What does like the 10 second blocks look like?
00:56:59.519 --> 00:57:03.280
Almost like a you know, a uh flame graph.
00:57:04.559 --> 00:57:07.039
Yeah, I don't know anymore.
00:57:08.239 --> 00:57:23.760
Um but going back to what you asked a second ago, a habit going back many years is that sometimes instead of task instead of context switching on the screen, I will have a book in front of me.
00:57:24.000 --> 00:57:24.320
Yeah.
00:57:24.559 --> 00:57:35.119
And I'll leave the screen where it is and just move my eyes down to the book, and that makes and there's two reasons why that why I find that to be better.
00:57:35.440 --> 00:57:49.840
One is because I can still monitor the screen continuously, and the other is because the secondary task is so different from the primary one, it doesn't like compete for headspace.
00:57:51.039 --> 00:57:51.760
Agreed.
00:57:52.000 --> 00:57:58.079
Like the it's almost like the more different, like the like the most distracting thing is gonna be another programming task.
00:57:58.239 --> 00:58:01.599
The least distracting thing might be folding laundry.
00:58:02.480 --> 00:58:12.639
So my answer, I I wrote a blog post about this recently, is like how I find that finding non-work distractions makes my work productivity much higher.
00:58:13.599 --> 00:58:14.239
Yeah.
00:58:15.039 --> 00:58:15.519
Mm-hmm.
00:58:15.840 --> 00:58:29.039
So, like for example, uh I clean my garage once a week because the kids, and I have headphones on, and I can hear the pings from co-pilot.
00:58:29.280 --> 00:58:33.199
So I'll like break down a box, I hear a ping, go over, type the input.
00:58:34.320 --> 00:58:34.719
Enter.
00:58:34.880 --> 00:58:36.719
Yes, go do another like little thing.
00:58:36.800 --> 00:58:43.199
Or like I I ride my bike a lot, so I go, I have to do a ton of maintenance on it because I'm riding like a hundred miles a week right now.
00:58:43.360 --> 00:58:47.679
Um, so I'll like put the air in a tire, hear a ding, go over and do it.
00:58:47.760 --> 00:58:51.039
Like it's a really easy, interruptible, non-technical task.
00:58:51.360 --> 00:59:01.360
And I find myself having a way higher level of mental clarity in that mode than when I'm filling it with anything that involves technology.
00:59:01.599 --> 00:59:02.079
Yeah.
00:59:02.320 --> 00:59:06.559
And that my like my my reasoning level is so much higher.
00:59:07.760 --> 00:59:13.039
Yeah, I wasn't thinking about that for some reason, but I definitely do that.
00:59:13.119 --> 00:59:31.280
Like I'll have my computer on the kitchen table while I'm making dinner, and it's debatable whether this is like a healthy way to live, but it's like put some onions in the pan, that's gonna take a minute, go over, type a prompt, go stir the onions, go back to the computer, type another prompt.
00:59:32.559 --> 00:59:39.519
I have a feeling like a Buddhist would not approve of that way of living.
00:59:39.840 --> 00:59:45.360
Okay, so you're reminding me there is, I mean, this is the note we can end on, is that there's a book called The Zen.
00:59:45.519 --> 00:59:47.760
Is it the Zen of Software Engineering?
00:59:48.639 --> 00:59:50.480
The Zen of Computer Programming, something like that.
00:59:50.559 --> 01:00:00.079
And it's a short book, but it talks about so the author talks about some sort of regimen that involves meditation and exercise as part of the programming habit.
01:00:00.159 --> 01:00:12.079
And this is old-ish, so it definitely predates the AI world, but it would like encourage you to do like sit-ups after like complete writing a commit or something like that.
01:00:12.559 --> 01:00:23.599
Or like go for a walk, or like it like it created, it was like some sort of like practice around doing physical things as part of your active computer programming.
01:00:23.760 --> 01:00:25.519
And I find that to be way more useful now.
01:00:25.599 --> 01:00:39.440
Like I have a I have a thing my eye doctor makes me use, which it blanks my screen every 20 minutes, and it because I'm supposed to look at least 20 feet away every 20 minutes for 20 seconds because it reduces like the headaches I get.
01:00:39.679 --> 01:00:50.880
But what I've been doing now is I'll just do like literally go walk down the hallway or back, or I'll do some sit-ups or some push-ups or something that uh helps my body move a little bit.
01:00:51.119 --> 01:00:55.280
And I find that is cognitively beneficial.
01:00:56.000 --> 01:01:08.079
Yeah, everything is connected, like getting enough sleep is it has a huge bearing on how you put how you will perform at work the next day.
01:01:08.320 --> 01:01:12.480
Um we should probably start heading toward a conclusion soon.
01:01:12.719 --> 01:01:15.840
Um I I want to ask you about one more thing.
01:01:15.920 --> 01:01:29.119
We could probably do a whole nother episode at least on this, but um we've been exchanging emails for the last I don't know how long, couple months, because I keep not responding to your emails for a long time, which I apologize for.
01:01:29.280 --> 01:01:29.760
It's all good.
01:01:29.840 --> 01:01:30.320
It's all good.
01:01:30.559 --> 01:01:32.880
But you're working on a device, right?
01:01:33.360 --> 01:01:39.519
Yeah, so I have uh a project I did what started what 10 years ago.
01:01:40.159 --> 01:01:50.480
The premise is that having the physical totem of your cell phone near you has a psychological effect on you.
01:01:50.960 --> 01:01:52.480
And this has been proven in studies.
01:01:52.639 --> 01:01:58.000
It's been proven that people are less attentive, literally having their phone within reaching distance in social situations.
01:01:58.079 --> 01:02:05.840
Like if you're having dinner with your wife, for example, like phones on the table, your brain is in a is functions differently than if that phone is in the car.
01:02:07.360 --> 01:02:14.559
So when my wife and I got married, we decided that we were not going to have any electronics in like our bedroom area.
01:02:16.719 --> 01:02:35.679
But that quickly fell over because we realized that we still needed, or at least wanted some information from the internet, like our calendar, like what the weather was like, basically stuff that helps you like pick out your clothes, talk about like these days, like who's gonna have which kid when, that kind of thing.
01:02:36.079 --> 01:02:44.159
So I started with some prototypes using old jailbroken Kindles, which are really nice because they don't have a light.
01:02:44.320 --> 01:02:47.679
Like you, they just get lit by whatever lights you have in the room.
01:02:48.239 --> 01:02:52.159
And that has evolved over time to some more finished devices.
01:02:52.239 --> 01:02:55.199
I now sell using some open source hardware.
01:02:55.920 --> 01:03:00.320
Uh the project is called Timeframe, and it's this kind of e-paper-based solution.
01:03:00.400 --> 01:03:06.320
We have a couple of the screens in our house of various sizes and fed fidelities, and it's a really interesting system.
01:03:06.400 --> 01:03:10.000
And I'm starting to like play with having it be a product.
01:03:10.079 --> 01:03:12.079
It's kind of in a very prototype phase.
01:03:13.280 --> 01:03:13.599
Yeah.
01:03:13.760 --> 01:03:17.360
Well, I look forward to um getting my hands on one of those.
01:03:17.519 --> 01:03:23.119
The only the only thing stopping that from happening is me responding to your email you sent me about it.
01:03:23.599 --> 01:03:27.360
Um do you do you have something online that people can go look at?
01:03:27.679 --> 01:03:29.280
Yeah, it's at timeframe.app.
01:03:29.679 --> 01:03:35.199
And especially for your audience, they should know that it's open source, or at least the core of it is open source.
01:03:35.280 --> 01:03:42.559
So you can run it inside Home Assistant and it will use like all the weather and calendar data, et cetera, from Home Assistant.
01:03:42.639 --> 01:03:44.800
It will also display Home Assistant status things.
01:03:44.880 --> 01:03:54.880
Like, for example, we have it set up so it tells us whether all our exterior doors are locked, which when you have kids is really important because our kid, our especially our toddler likes to open doors.
01:03:55.199 --> 01:03:59.360
So it's really nice looking when you go to bed at night that like it shows that all our doors are locked.
01:03:59.519 --> 01:04:04.960
Um, so yeah, you can run the core software for free inside Home Assistant.
01:04:05.119 --> 01:04:06.960
I also have a cloud version, that's what I charge for.
01:04:07.039 --> 01:04:20.239
And then you can run it on hardware that I sell, or you can run it on it's there, uh there's some firmware you can run on your own devices, or you can run it inside a web browser and you can run it on basically anything then at that point, a TV, uh, you know, computer monitor, etc.
01:04:20.719 --> 01:04:23.039
Any other links you want to share before we go?
01:04:23.280 --> 01:04:25.280
Just my website is hoxa.org.
01:04:25.360 --> 01:04:26.960
I blog there occasionally.
01:04:27.039 --> 01:04:27.360
Yeah.
01:04:27.679 --> 01:04:28.079
All right.
01:04:28.239 --> 01:04:30.320
We will put those things in the show notes.
01:04:30.400 --> 01:04:32.559
And Joel, thanks so much for coming on the show.
01:04:32.719 --> 01:04:33.840
Hey, thanks for having me.
01:04:34.000 --> 01:04:34.960
Look forward to the next time.