WEBVTT - What Happens Now to All the Laid Off Tech Workers?

0:00:10.119 --> 0:00:14.040
<v Speaker 1>Hello, and welcome to another episode of the Odd Lots Podcast.

0:00:14.080 --> 0:00:17.279
<v Speaker 1>I'm Joe Wisenthal and I'm Tracy Alloway. Tracy, have I

0:00:17.320 --> 0:00:20.680
<v Speaker 1>ever told you like my idea for like a two

0:00:20.720 --> 0:00:24.040
<v Speaker 1>part podcast or like a series of two part podcasts?

0:00:24.320 --> 0:00:27.520
<v Speaker 1>A series of two parts? Is it the debate one? No,

0:00:27.720 --> 0:00:31.600
<v Speaker 1>it's different. Okay, So I don't know about you, But

0:00:31.880 --> 0:00:35.599
<v Speaker 1>most of the time, after we do these interviews, I

0:00:35.720 --> 0:00:38.279
<v Speaker 1>usually have questions that I started kicked myself for not

0:00:38.440 --> 0:00:43.519
<v Speaker 1>having asked oh, yes, yes. So this often happens on

0:00:43.520 --> 0:00:46.920
<v Speaker 1>the podcast because we often touch on kind of wide

0:00:47.000 --> 0:00:50.839
<v Speaker 1>varying topics and we're not experts in a lot of

0:00:50.840 --> 0:00:53.120
<v Speaker 1>the things that we talked about, and often the first

0:00:53.159 --> 0:00:55.720
<v Speaker 1>episode is sort of you get to know your subject matter,

0:00:56.080 --> 0:00:59.200
<v Speaker 1>and then you leave it with even more questions. Yeah.

0:00:59.240 --> 0:01:01.560
<v Speaker 1>So I often kicked myself, like, oh, I should have

0:01:01.640 --> 0:01:04.080
<v Speaker 1>I should have obviously asked that obviously. And then the

0:01:04.080 --> 0:01:06.800
<v Speaker 1>other thing that happens is you post then the episode

0:01:06.840 --> 0:01:09.200
<v Speaker 1>comes out, and then like people on Twitter and elsewhere,

0:01:09.240 --> 0:01:10.880
<v Speaker 1>they'll talk about it. They talked about it, they're like,

0:01:10.920 --> 0:01:13.119
<v Speaker 1>what I'm curious about is actually like, oh, that's really

0:01:13.160 --> 0:01:15.400
<v Speaker 1>good question too. I should have thought of that. So,

0:01:15.480 --> 0:01:17.360
<v Speaker 1>like I thought, like a thing that we should do

0:01:17.440 --> 0:01:21.280
<v Speaker 1>maybe one day is schedule, like, have all episodes be

0:01:21.360 --> 0:01:24.000
<v Speaker 1>two parters where we do an interview with a guest,

0:01:24.600 --> 0:01:27.360
<v Speaker 1>take a week, sort of magrinate on it, think about it,

0:01:27.560 --> 0:01:29.319
<v Speaker 1>what are some questions we wish we would ask, and

0:01:29.319 --> 0:01:33.440
<v Speaker 1>then have the second episode schedule. I really like that idea.

0:01:33.640 --> 0:01:37.440
<v Speaker 1>It's sort of like it's almost the octopus model of

0:01:37.880 --> 0:01:42.920
<v Speaker 1>podcast episodes, where like one one episode just springs forth

0:01:42.959 --> 0:01:45.520
<v Speaker 1>a dozen you arms and legs that you can talk

0:01:45.520 --> 0:01:48.840
<v Speaker 1>about forever. So today we're kind of gonna we're kind

0:01:48.840 --> 0:01:50.960
<v Speaker 1>of gonna be doing that. We're this is I think

0:01:51.040 --> 0:01:53.440
<v Speaker 1>we might be This might be close. I'm not sure

0:01:53.480 --> 0:01:55.840
<v Speaker 1>what the record is, but this might be close to

0:01:55.880 --> 0:01:59.040
<v Speaker 1>the soonest we've ever had a guest on so soon

0:01:59.160 --> 0:02:01.600
<v Speaker 1>after they appeared the show. This is a pilot for

0:02:01.720 --> 0:02:04.400
<v Speaker 1>podcast two parters. The only other time I can think

0:02:04.440 --> 0:02:07.800
<v Speaker 1>of is we talked to Claudia Sam twice before the

0:02:07.840 --> 0:02:09.720
<v Speaker 1>pandemic and was because it was sort of like her

0:02:09.800 --> 0:02:13.560
<v Speaker 1>general views on how to like forecast recessions, and then

0:02:13.600 --> 0:02:15.760
<v Speaker 1>like two weeks later, like the pandemic was in view,

0:02:15.840 --> 0:02:18.080
<v Speaker 1>and it's like, oh, I shoot, this might be really bad,

0:02:18.360 --> 0:02:20.320
<v Speaker 1>so he had her on really fast. But this is

0:02:20.320 --> 0:02:22.600
<v Speaker 1>going to be close to that record. I think, yeah,

0:02:22.880 --> 0:02:25.000
<v Speaker 1>sounds good. All right, let's do it. So we recently

0:02:25.040 --> 0:02:30.600
<v Speaker 1>talked to Patrick McKenzie. He is a technology infrastructure financial

0:02:30.600 --> 0:02:34.720
<v Speaker 1>infrastructure specialist. He worked for Stripe for six years. He's

0:02:34.720 --> 0:02:37.200
<v Speaker 1>currently an advisor. He's the author of the Bits about

0:02:37.320 --> 0:02:40.400
<v Speaker 1>Money newsletter, and we talked to him about like corporate

0:02:40.440 --> 0:02:43.200
<v Speaker 1>I why it is the way it is? Why does

0:02:43.320 --> 0:02:46.200
<v Speaker 1>it seem to be like years and years behind what

0:02:46.280 --> 0:02:48.239
<v Speaker 1>we think of the cutting edge of software wise it

0:02:48.280 --> 0:02:51.079
<v Speaker 1>off and clunky wise it off and have these big

0:02:51.080 --> 0:02:54.080
<v Speaker 1>technical issues that can take a while to fix. That

0:02:54.160 --> 0:02:57.000
<v Speaker 1>was a great conversation. The public loved it. But there's

0:02:57.040 --> 0:03:00.080
<v Speaker 1>a lot going on in software these days. And the

0:03:00.120 --> 0:03:02.639
<v Speaker 1>other sort of big trend that we haven't really talked

0:03:02.680 --> 0:03:05.400
<v Speaker 1>about is that for the first time and I don't know,

0:03:05.480 --> 0:03:09.160
<v Speaker 1>maybe like fifteen years, we've been seeing all these tech layoffs, right,

0:03:09.200 --> 0:03:11.240
<v Speaker 1>And I think there was a little bit of tension

0:03:11.320 --> 0:03:13.399
<v Speaker 1>in that episode in that we were talking about why

0:03:13.440 --> 0:03:16.480
<v Speaker 1>corporate software is so bad. So it's almost like, well,

0:03:16.560 --> 0:03:19.280
<v Speaker 1>obviously there's a need for better software, and yet all

0:03:19.320 --> 0:03:23.000
<v Speaker 1>these big tech companies that ostensibly provide these services are

0:03:23.080 --> 0:03:27.680
<v Speaker 1>laying people off, but also in the broader macro picture.

0:03:28.080 --> 0:03:31.800
<v Speaker 1>Since we recorded that episode, we had a payrolls report

0:03:31.960 --> 0:03:36.800
<v Speaker 1>that came out much, much stronger than anyone expected. And

0:03:36.960 --> 0:03:39.480
<v Speaker 1>yet we've seen these big tech companies layoff people. And

0:03:39.520 --> 0:03:43.560
<v Speaker 1>so the question obviously becomes, is this something specifically about

0:03:43.680 --> 0:03:48.000
<v Speaker 1>tech or are these layoffs sort of the first sign

0:03:48.240 --> 0:03:51.120
<v Speaker 1>of something broader to come in the economy. And the

0:03:51.160 --> 0:03:54.000
<v Speaker 1>other thing that everyone points out to when when you

0:03:54.120 --> 0:03:58.600
<v Speaker 1>see these announcements from Meta and Alphabet, at various startups

0:03:58.600 --> 0:04:01.160
<v Speaker 1>and Microsoft and Amazon they all done it is like

0:04:01.320 --> 0:04:03.520
<v Speaker 1>they edited so many jobs over the last two years

0:04:03.560 --> 0:04:07.080
<v Speaker 1>that actually these layoffs are like fairly small in uh,

0:04:07.360 --> 0:04:09.800
<v Speaker 1>the grand scheme of things, even for these companies, based

0:04:09.800 --> 0:04:11.840
<v Speaker 1>on the amount of hiring that they've done. Yeah, but

0:04:11.880 --> 0:04:14.800
<v Speaker 1>I saw I saw a figure from Goldman Sex I

0:04:14.840 --> 0:04:16.880
<v Speaker 1>think it was Yannatsis, and he was talking about in

0:04:16.880 --> 0:04:19.279
<v Speaker 1>the tech sector, most of the companies that have been

0:04:19.400 --> 0:04:23.440
<v Speaker 1>laying people off grew their head count by over since

0:04:23.480 --> 0:04:26.240
<v Speaker 1>the pandemic basically because they thought all the pandemic trends

0:04:26.240 --> 0:04:28.440
<v Speaker 1>were going to keep going. Maybe there's a little bit

0:04:28.440 --> 0:04:31.839
<v Speaker 1>of labor hoarding. But it's a big figure. Absolutely. You know,

0:04:31.920 --> 0:04:35.800
<v Speaker 1>people in our industry, journalism, when journalists lose their jobs,

0:04:35.800 --> 0:04:39.160
<v Speaker 1>there's always trolls on Twitter saying, oh, learn to code.

0:04:39.440 --> 0:04:41.000
<v Speaker 1>You know, that's like a thing. I think at one

0:04:41.000 --> 0:04:43.120
<v Speaker 1>point even like Twitter start banning people for saying that.

0:04:43.360 --> 0:04:45.240
<v Speaker 1>But I guess the question is, right now, when you

0:04:45.279 --> 0:04:47.719
<v Speaker 1>see these layoffs, like should we learn to code or

0:04:47.800 --> 0:04:50.720
<v Speaker 1>is that not you know, is that not the career

0:04:50.760 --> 0:04:52.560
<v Speaker 1>safety that that it used to be? So all kinds

0:04:52.600 --> 0:04:55.560
<v Speaker 1>of questions about what is going on in the market

0:04:55.600 --> 0:04:57.960
<v Speaker 1>for tech talent. I'm sure someone's going to tell us

0:04:58.000 --> 0:05:00.400
<v Speaker 1>to learn to code. For the record, I can code

0:05:00.440 --> 0:05:04.000
<v Speaker 1>just in like very non useful languages. I have no well,

0:05:04.040 --> 0:05:07.039
<v Speaker 1>I coded in basic like yeah, yeah exactly, like C

0:05:07.160 --> 0:05:11.200
<v Speaker 1>plus plus and like some really basic HTML. But all right,

0:05:11.480 --> 0:05:13.839
<v Speaker 1>let's talk to someone who knows more about this question

0:05:13.880 --> 0:05:16.400
<v Speaker 1>than we do. We're bringing back Patrick. Thank you so

0:05:16.480 --> 0:05:19.000
<v Speaker 1>much for coming back on the podcast. Thanks very much

0:05:19.040 --> 0:05:22.560
<v Speaker 1>for having me. Absolutely so. I guess the question is,

0:05:22.720 --> 0:05:27.000
<v Speaker 1>before we even start talking about the recently off announcements,

0:05:27.480 --> 0:05:30.040
<v Speaker 1>why don't we start with like the hiring boom that

0:05:30.120 --> 0:05:32.479
<v Speaker 1>we really saw over the last two years, just massive

0:05:32.520 --> 0:05:35.039
<v Speaker 1>amount of headcount added and all these companies, we know

0:05:35.080 --> 0:05:39.040
<v Speaker 1>who they are, what drove that. So how about we

0:05:39.160 --> 0:05:41.960
<v Speaker 1>rule back history to two thousand nineteen and if you're

0:05:41.960 --> 0:05:45.039
<v Speaker 1>looking at recent history, as of two thousand nineteen, tech

0:05:45.120 --> 0:05:49.839
<v Speaker 1>has been on sort of an uninterrupted series of a

0:05:49.880 --> 0:05:53.039
<v Speaker 1>bunch of very good years, broad based expansion across the

0:05:53.160 --> 0:05:56.359
<v Speaker 1>entire industry, basically writing continuing to ride the wave that

0:05:56.400 --> 0:06:00.960
<v Speaker 1>had happened since the late pots. Is that how we

0:06:00.960 --> 0:06:05.760
<v Speaker 1>was it in English with the consolidation of mobile gains, etcetera, etcetera.

0:06:06.920 --> 0:06:11.120
<v Speaker 1>Then the pandemic happened and there was a brief pause

0:06:11.480 --> 0:06:15.640
<v Speaker 1>of okay, is this going to be an absolutely catastrophic

0:06:15.680 --> 0:06:19.599
<v Speaker 1>event for the entire world economy. Many bad things happened

0:06:19.640 --> 0:06:22.360
<v Speaker 1>during the pandemic, the way it played out for tech

0:06:22.680 --> 0:06:26.240
<v Speaker 1>was probably not how anyone would have expected one. There

0:06:26.279 --> 0:06:29.080
<v Speaker 1>was sort of a one two punch of a combined

0:06:29.080 --> 0:06:32.360
<v Speaker 1>fiscal response from governments built in the United States and

0:06:32.720 --> 0:06:36.520
<v Speaker 1>worldwide to stave off a huge economic disaster, which had

0:06:36.560 --> 0:06:40.520
<v Speaker 1>the effect of both putting money into consumers pockets and

0:06:40.600 --> 0:06:44.880
<v Speaker 1>also using the markets for assets, for example tech stocks,

0:06:45.279 --> 0:06:47.000
<v Speaker 1>which will come back to the importance so that in

0:06:47.000 --> 0:06:50.000
<v Speaker 1>a moment to a lot of the customers were, due

0:06:50.080 --> 0:06:53.920
<v Speaker 1>to various non pharmaceutical inventions, sitting at home with very

0:06:53.920 --> 0:06:56.800
<v Speaker 1>little to do other than use the internet. And so

0:06:57.120 --> 0:07:00.040
<v Speaker 1>a lot of commerce that had been possible on the

0:07:00.080 --> 0:07:02.680
<v Speaker 1>internet before the share of it that was soaked up

0:07:02.680 --> 0:07:06.159
<v Speaker 1>by the Internet in uh both sort of like semi

0:07:06.200 --> 0:07:10.280
<v Speaker 1>discretionary places like food delivery, but also much less discretionary

0:07:10.280 --> 0:07:14.560
<v Speaker 1>places like you know, core supermarkets suddenly shifted online in

0:07:14.600 --> 0:07:18.600
<v Speaker 1>a very very fast way. And so this combination of

0:07:18.720 --> 0:07:20.960
<v Speaker 1>there's more money slashing around and more of it is

0:07:21.000 --> 0:07:25.400
<v Speaker 1>falling into the online bucket led to absolutely blockbuster years

0:07:25.440 --> 0:07:29.400
<v Speaker 1>for tech companies, and it was a real like trying

0:07:29.480 --> 0:07:32.880
<v Speaker 1>to keep your fingers onto the rocket internally at the companies,

0:07:33.000 --> 0:07:35.960
<v Speaker 1>like the amount of new users that was on boarding,

0:07:36.560 --> 0:07:38.560
<v Speaker 1>at the rate of growth of the business, the raw

0:07:38.720 --> 0:07:41.200
<v Speaker 1>volumes of stuff that was going through the pipes made

0:07:41.240 --> 0:07:44.400
<v Speaker 1>it like difficult to keep everything up and running. And

0:07:44.560 --> 0:07:47.840
<v Speaker 1>a good news front, the business is largely successfully did

0:07:47.920 --> 0:07:50.120
<v Speaker 1>keep up and running during a time where society very

0:07:50.160 --> 0:07:53.800
<v Speaker 1>much needed them to. They also started to like readjust

0:07:53.880 --> 0:07:57.280
<v Speaker 1>their projections of what the future would look like, and

0:07:57.800 --> 0:08:01.680
<v Speaker 1>for a while it was looking like. Yeah. The phrase

0:08:01.680 --> 0:08:04.480
<v Speaker 1>that was going around was decades of growth were happening

0:08:04.520 --> 0:08:06.600
<v Speaker 1>every couple of weeks in terms of, you know, our

0:08:06.680 --> 0:08:10.200
<v Speaker 1>anticipated long term shift of the offline economy into the

0:08:10.240 --> 0:08:14.840
<v Speaker 1>online economy. And there was a big question of how

0:08:14.880 --> 0:08:17.440
<v Speaker 1>long does that continue for and is that pulling forth

0:08:17.480 --> 0:08:20.080
<v Speaker 1>growth growth that is happening in the future, is it

0:08:20.240 --> 0:08:24.320
<v Speaker 1>a one time spike, etcetera, etcetera. To to various structural

0:08:24.360 --> 0:08:28.240
<v Speaker 1>and competitive dynamics, a lot of firms spit simultaneously. This

0:08:28.320 --> 0:08:33.080
<v Speaker 1>is a pretty durable change. We find ourselves crushed by

0:08:33.120 --> 0:08:35.400
<v Speaker 1>the amount of demand we're seeing right now. We're going

0:08:35.440 --> 0:08:37.880
<v Speaker 1>to need to hire and hire aggressively to deal with

0:08:37.920 --> 0:08:40.480
<v Speaker 1>this and to position ourselves for what we see as

0:08:40.559 --> 0:08:43.040
<v Speaker 1>the you know, eventual coming out of the pandemic future.

0:08:43.679 --> 0:08:46.880
<v Speaker 1>And as a result of this, companies were mature companies

0:08:47.040 --> 0:08:50.680
<v Speaker 1>the Google's Amazons Facebooks of the world. We're hiring on

0:08:50.760 --> 0:08:54.079
<v Speaker 1>the order of like year over year growth across large

0:08:54.120 --> 0:08:58.439
<v Speaker 1>portions of their business. Somewhat earlier stage companies, companies that

0:08:58.520 --> 0:09:01.439
<v Speaker 1>might look like a stripe even though stripe as uh

0:09:01.480 --> 0:09:06.160
<v Speaker 1>somewhat larger these days, or early stage startups were on

0:09:06.280 --> 0:09:10.679
<v Speaker 1>boarding multiples of their pre pandemic had count as we

0:09:11.000 --> 0:09:14.320
<v Speaker 1>used over the course of the pandemic, so huge expansion

0:09:14.400 --> 0:09:17.640
<v Speaker 1>during the during the interval, and then as we came

0:09:17.640 --> 0:09:20.240
<v Speaker 1>out of the pandemic, companies assessed a number of things.

0:09:20.360 --> 0:09:23.400
<v Speaker 1>One the growth rates tended to go back to his

0:09:23.400 --> 0:09:26.360
<v Speaker 1>historical norms rather than this shot in the arm that

0:09:26.679 --> 0:09:31.520
<v Speaker 1>the pandemic was offering. Importantly, and you know, tech is

0:09:31.520 --> 0:09:34.240
<v Speaker 1>a wide sector. It touches every part of the economy

0:09:34.280 --> 0:09:37.200
<v Speaker 1>these days, so it's difficult to say with huge generalizations,

0:09:37.240 --> 0:09:40.440
<v Speaker 1>but as top line level things did not decline back

0:09:40.480 --> 0:09:43.120
<v Speaker 1>to two thousand nineteen. And again, two thousand nineteen was

0:09:43.160 --> 0:09:46.080
<v Speaker 1>not a bad year for tech. It was a, you know,

0:09:46.120 --> 0:09:48.280
<v Speaker 1>a pretty good year after a number of pretty good years.

0:09:48.679 --> 0:09:51.439
<v Speaker 1>So we haven't gone back to the pre pandemic baseline.

0:09:52.120 --> 0:09:54.200
<v Speaker 1>We haven't even stopped growing. In a number of cases,

0:09:54.480 --> 0:09:58.240
<v Speaker 1>the growth curve has just spent downwards, and so the

0:09:58.600 --> 0:10:03.120
<v Speaker 1>sustained like plus plus headcount growth over time didn't look

0:10:03.120 --> 0:10:05.040
<v Speaker 1>like it could be that could be sustained. And then

0:10:05.120 --> 0:10:08.720
<v Speaker 1>companies started to look at things that they had allowed

0:10:08.760 --> 0:10:12.199
<v Speaker 1>to happen for the course of the pandemic to characterize

0:10:12.240 --> 0:10:15.480
<v Speaker 1>these broadly. One of the things that happened during the

0:10:15.480 --> 0:10:19.800
<v Speaker 1>pandemic was due to the lockdowns and advisability of having

0:10:19.880 --> 0:10:22.199
<v Speaker 1>large numbers of people congregate in small pockets of air,

0:10:22.720 --> 0:10:25.840
<v Speaker 1>a bunch of companies went to both remote work and

0:10:25.920 --> 0:10:29.160
<v Speaker 1>remote hiring where they might not have had a huge

0:10:29.200 --> 0:10:33.200
<v Speaker 1>amount of institutional experience with that model of working before,

0:10:34.040 --> 0:10:36.839
<v Speaker 1>and after two to three years of working with these

0:10:37.040 --> 0:10:41.240
<v Speaker 1>newer cohorts of people, they've found that there are some

0:10:41.920 --> 0:10:44.280
<v Speaker 1>practices that they want to continue from this room at

0:10:44.280 --> 0:10:47.120
<v Speaker 1>work world into the future, and that there's some amount

0:10:47.160 --> 0:10:51.040
<v Speaker 1>of internal impetus to return to office and have sort

0:10:51.080 --> 0:10:54.920
<v Speaker 1>of a cultural reset around the office or headquarters, etcetera

0:10:55.000 --> 0:10:58.080
<v Speaker 1>as the sort of beating center of these firms. I've

0:10:58.080 --> 0:11:00.480
<v Speaker 1>worked remote for most of my career, myself of a

0:11:00.480 --> 0:11:03.920
<v Speaker 1>broad fan of the model. Let's say that there was

0:11:04.000 --> 0:11:07.040
<v Speaker 1>some cultural tension and companies on where the locus of

0:11:07.080 --> 0:11:08.880
<v Speaker 1>activity is going to be, whether it's going to be

0:11:09.160 --> 0:11:12.000
<v Speaker 1>in this online in zoom meetings and slack all the time,

0:11:12.520 --> 0:11:16.000
<v Speaker 1>or in the office high band with communication directly with

0:11:16.040 --> 0:11:18.720
<v Speaker 1>trusted peers, and a lot of companies wanted to have

0:11:18.760 --> 0:11:21.640
<v Speaker 1>a bit of a pullback towards the office, and then

0:11:21.800 --> 0:11:26.880
<v Speaker 1>they're looking more granularly at the classes of people to

0:11:26.920 --> 0:11:29.400
<v Speaker 1>the heart over the last couple of years, and found

0:11:29.480 --> 0:11:33.120
<v Speaker 1>that in comparison to prior classes, there was a bit

0:11:33.120 --> 0:11:35.720
<v Speaker 1>of cultural drift relative to where the companies want their

0:11:35.760 --> 0:11:38.880
<v Speaker 1>baselines to be, and also in some cases a bit

0:11:38.920 --> 0:11:41.840
<v Speaker 1>of a measured productivity difference versus where they wanted their

0:11:41.840 --> 0:11:45.400
<v Speaker 1>baselines to be. That's sort of expected because when you're

0:11:45.440 --> 0:11:49.280
<v Speaker 1>pulling out all the steps to hire, you like necessarily

0:11:49.280 --> 0:11:50.800
<v Speaker 1>you have to be a little less choosy than you

0:11:50.880 --> 0:11:53.480
<v Speaker 1>normally are. You have, you know, to the extent that

0:11:53.480 --> 0:11:55.880
<v Speaker 1>you describe any value at all to the in person

0:11:56.040 --> 0:11:59.400
<v Speaker 1>interview loop, which I describe relatively little value too, but

0:11:59.480 --> 0:12:03.560
<v Speaker 1>hopefully like slightly greater than zero. You you lose that

0:12:03.600 --> 0:12:06.439
<v Speaker 1>amount of signal and they're sort of hiring in a

0:12:06.480 --> 0:12:09.520
<v Speaker 1>slightly more challenge fashion than usual. And so I think

0:12:09.600 --> 0:12:12.840
<v Speaker 1>that companies will be pretty quiet about saying, but we'll

0:12:13.000 --> 0:12:17.000
<v Speaker 1>we'll say to themselves is we probably have a few

0:12:17.080 --> 0:12:21.560
<v Speaker 1>more regrets in like hiring classes than we did in

0:12:21.679 --> 0:12:26.520
<v Speaker 1>the hiring classes as a percentage, Patrick, this actually leads

0:12:26.559 --> 0:12:28.680
<v Speaker 1>to something that I want to ask you, but what

0:12:28.760 --> 0:12:33.320
<v Speaker 1>does blow actually look like in the tech sector, and

0:12:33.520 --> 0:12:37.480
<v Speaker 1>you know, is it something that only emerges as business

0:12:37.520 --> 0:12:41.840
<v Speaker 1>activity actually slows down, or even in one would you

0:12:41.840 --> 0:12:47.640
<v Speaker 1>have characterized tech as bloated. So it's difficult. This tech

0:12:48.840 --> 0:12:51.080
<v Speaker 1>sort of subsumes more and more of the economy into

0:12:51.160 --> 0:12:55.760
<v Speaker 1>its every increasing embrace to make like huge paint with

0:12:55.960 --> 0:12:59.720
<v Speaker 1>raw brush assertions across all of it. But let's see

0:12:59.720 --> 0:13:04.760
<v Speaker 1>where to start here. So one, the number of things

0:13:04.760 --> 0:13:08.559
<v Speaker 1>that are done in these large companies are extremely varied.

0:13:08.640 --> 0:13:11.120
<v Speaker 1>People might have a image that like most people who

0:13:11.320 --> 0:13:14.600
<v Speaker 1>could google our engineers, that's actually not the case. Depending

0:13:14.600 --> 0:13:17.360
<v Speaker 1>on the company we're talking about between twenty and the

0:13:17.360 --> 0:13:20.679
<v Speaker 1>people who work at the company are technologists broadly written,

0:13:21.040 --> 0:13:25.560
<v Speaker 1>they are software engineers, their system administrators, their designers at

0:13:25.600 --> 0:13:28.680
<v Speaker 1>some companies reporting to the same division. And then the

0:13:28.720 --> 0:13:31.000
<v Speaker 1>rest are every sort of worker that you would have

0:13:31.080 --> 0:13:35.080
<v Speaker 1>in any company in the economy. Lawyers, regulatory people, customer

0:13:35.120 --> 0:13:39.320
<v Speaker 1>sport agents, etcetera, etcetera, etcetera. Management layers upon layers of management.

0:13:40.320 --> 0:13:44.200
<v Speaker 1>So what does what does company growth look like? In

0:13:44.679 --> 0:13:47.680
<v Speaker 1>one case, it is staffing up more teams to work

0:13:47.760 --> 0:13:51.960
<v Speaker 1>on products that already exist. Sometimes staffing teams that sort

0:13:52.000 --> 0:13:54.880
<v Speaker 1>of like grow with the the rate of usage of

0:13:54.920 --> 0:13:58.679
<v Speaker 1>your products. So like customer service teams typically grow relatively

0:13:58.760 --> 0:14:03.280
<v Speaker 1>linearly with the usage of your service. Sometimes it's teams

0:14:03.320 --> 0:14:06.040
<v Speaker 1>that grow relatively nearly with the size of your organizations.

0:14:06.120 --> 0:14:09.880
<v Speaker 1>So as companies were having these sort of like unprecedented

0:14:09.920 --> 0:14:13.079
<v Speaker 1>amounts of employees getting on boarded every year, they needed

0:14:13.200 --> 0:14:16.880
<v Speaker 1>larger recruiting divisions to staff up there are other employees,

0:14:16.920 --> 0:14:20.120
<v Speaker 1>and it's just based on like the productivity math of

0:14:20.160 --> 0:14:22.800
<v Speaker 1>a recruiter. And you can, like finger to the wind

0:14:22.920 --> 0:14:25.480
<v Speaker 1>that if you hire a recruiter, that recruiter will be

0:14:25.520 --> 0:14:27.320
<v Speaker 1>able to hire twenty five people in the year. And

0:14:27.360 --> 0:14:29.880
<v Speaker 1>so if you need to hire four thousand people, then

0:14:30.080 --> 0:14:33.520
<v Speaker 1>you know, work math backwards, you require a hundred sixty

0:14:33.520 --> 0:14:36.440
<v Speaker 1>recruiters that you didn't have previously. That will tend to

0:14:36.520 --> 0:14:40.320
<v Speaker 1>cause your recruiting division to get larger as you are

0:14:40.360 --> 0:14:43.000
<v Speaker 1>doing a rapid expansion, and then it will contract faster

0:14:43.120 --> 0:14:45.680
<v Speaker 1>than the rest of your company will when you decide

0:14:45.720 --> 0:14:48.160
<v Speaker 1>to take your foot off the gas bottle. So those

0:14:48.200 --> 0:14:51.600
<v Speaker 1>are the the things that are sort of less inside

0:14:51.600 --> 0:14:54.120
<v Speaker 1>of your control. You you just need to keep doing

0:14:54.120 --> 0:14:57.560
<v Speaker 1>them to run the business, and then you're making some

0:14:58.520 --> 0:15:01.360
<v Speaker 1>more speculative investments on like what are what is our

0:15:01.400 --> 0:15:03.480
<v Speaker 1>new product line up going to look? Like? What features

0:15:03.520 --> 0:15:07.240
<v Speaker 1>are we going to add? And so the basic unit

0:15:07.280 --> 0:15:10.160
<v Speaker 1>of organization within an engineering organization these days is a

0:15:10.240 --> 0:15:13.680
<v Speaker 1>single engineering team will typically be like five to eight people,

0:15:14.160 --> 0:15:17.080
<v Speaker 1>and that team has a mental bandwidth to deal with

0:15:17.360 --> 0:15:21.120
<v Speaker 1>three relatively narrowly scoped problems. And so the more that

0:15:21.160 --> 0:15:25.320
<v Speaker 1>you want your software services suite, etcetera. To do, the

0:15:25.360 --> 0:15:28.200
<v Speaker 1>more like narrowly scoped problems that come into its domain,

0:15:28.400 --> 0:15:30.680
<v Speaker 1>more like five to eight people engineering teams you need,

0:15:31.400 --> 0:15:34.520
<v Speaker 1>and so you might find yourself in a position where

0:15:34.960 --> 0:15:37.160
<v Speaker 1>you've hired like five to eight people to work on

0:15:37.280 --> 0:15:44.320
<v Speaker 1>three relatively narrowly scoped problems somewhat opportunistically, and then when

0:15:44.320 --> 0:15:48.560
<v Speaker 1>you you know, come to three and are thinking very

0:15:48.640 --> 0:15:52.440
<v Speaker 1>rigorously around like, Okay, we think we're a little bigger

0:15:52.440 --> 0:15:54.640
<v Speaker 1>than we were when we were efficient back a couple

0:15:54.640 --> 0:15:57.320
<v Speaker 1>of years ago. We think the economic environment not be

0:15:57.680 --> 0:16:00.280
<v Speaker 1>might not be as strong and as we were model link,

0:16:00.800 --> 0:16:03.160
<v Speaker 1>Which of all the problems in our company are the

0:16:03.160 --> 0:16:05.440
<v Speaker 1>ones that we definitely need to keep focusing on, and

0:16:05.480 --> 0:16:08.360
<v Speaker 1>which can we refer into later or just our corridor

0:16:08.440 --> 0:16:11.440
<v Speaker 1>business right now, then perhaps like some of these nearroly

0:16:11.480 --> 0:16:13.920
<v Speaker 1>scoped problems are not at the top of our list.

0:16:14.320 --> 0:16:17.400
<v Speaker 1>And then if you consider, you know, like this product

0:16:17.400 --> 0:16:19.880
<v Speaker 1>that we thought we would bring to market in three

0:16:19.880 --> 0:16:22.840
<v Speaker 1>maybe it will not be brought to mark till then

0:16:22.920 --> 0:16:25.480
<v Speaker 1>there might be like ten teams implicated by that that

0:16:25.520 --> 0:16:28.320
<v Speaker 1>you do not have propletied for I have a lot

0:16:28.360 --> 0:16:31.000
<v Speaker 1>of questions. You know, when Ellen bought Twitter, and he,

0:16:31.160 --> 0:16:33.680
<v Speaker 1>like what you know, much more aggressive with the layoffs

0:16:33.720 --> 0:16:36.280
<v Speaker 1>than anything else that we've seen. There were all these

0:16:36.400 --> 0:16:40.520
<v Speaker 1>like vcs and stuff. A common to the Dirty Secret

0:16:40.520 --> 0:16:42.680
<v Speaker 1>and Silicon Valley is that all these companies could do

0:16:42.720 --> 0:16:46.000
<v Speaker 1>that they have fifty of their employees not really working

0:16:46.000 --> 0:16:49.040
<v Speaker 1>on anything and not really contributing anything. And like, thank

0:16:49.080 --> 0:16:51.520
<v Speaker 1>you Ellen for showing that this could be done. And

0:16:51.600 --> 0:16:53.680
<v Speaker 1>Twitter still is operating. Although I don't know how the

0:16:53.680 --> 0:16:56.120
<v Speaker 1>businesses or whether he cut too deep to the bone

0:16:56.200 --> 0:16:58.920
<v Speaker 1>or whatever, but like, would you hear that, like is

0:16:58.960 --> 0:17:01.600
<v Speaker 1>that the case that just like over the years, setting

0:17:01.640 --> 0:17:07.399
<v Speaker 1>aside the unrealistic expectations of one and maybe two, was

0:17:07.480 --> 0:17:11.320
<v Speaker 1>there just a wide scale over hiring relative to the

0:17:11.359 --> 0:17:16.000
<v Speaker 1>needs of the business. So tech has been in sort

0:17:16.040 --> 0:17:18.480
<v Speaker 1>of a land grab mode for essentially all of my

0:17:18.520 --> 0:17:21.080
<v Speaker 1>adult life. We certainly haven't hit the asom to oute

0:17:21.119 --> 0:17:23.200
<v Speaker 1>of how many things in the economy can be orchestrated

0:17:23.200 --> 0:17:25.879
<v Speaker 1>by software. We certainly haven't hit the assom tote of

0:17:26.000 --> 0:17:28.920
<v Speaker 1>how many human and human interactions will be intermediated by

0:17:29.040 --> 0:17:33.119
<v Speaker 1>a technical system happening over a smartphone, etcetera, etcetera. In

0:17:33.160 --> 0:17:37.040
<v Speaker 1>that sort of land grab mode, you aren't simply like

0:17:37.119 --> 0:17:39.480
<v Speaker 1>trying to answer what is the minimal set of things

0:17:39.480 --> 0:17:41.280
<v Speaker 1>we can do with the minimal number of people, but

0:17:41.359 --> 0:17:44.440
<v Speaker 1>are sort of opportunistically looking at what are the next

0:17:44.600 --> 0:17:46.919
<v Speaker 1>ten things that we can try such that one of

0:17:46.960 --> 0:17:51.680
<v Speaker 1>them becomes a company defining product feature, etcetera, etcetera. I

0:17:51.760 --> 0:17:55.639
<v Speaker 1>have a little bit of risk reflective contrarianism when people

0:17:55.640 --> 0:18:00.280
<v Speaker 1>say all tech companies are overstaffed by Could you cut

0:18:00.359 --> 0:18:03.280
<v Speaker 1>eighty percent of people who work at tech companies and

0:18:03.600 --> 0:18:06.600
<v Speaker 1>still have something functional at the end of the day.

0:18:07.160 --> 0:18:11.199
<v Speaker 1>Probably true, that would be extremely painful. But if you

0:18:11.240 --> 0:18:14.800
<v Speaker 1>went into a very different mode of operation and just

0:18:14.920 --> 0:18:17.720
<v Speaker 1>wanted them to continue the products and services they had

0:18:17.760 --> 0:18:21.959
<v Speaker 1>three years ago, possibly that could be done. Probably wouldn't

0:18:21.960 --> 0:18:24.720
<v Speaker 1>be optimal for any of them. That's one major reason

0:18:24.760 --> 0:18:28.840
<v Speaker 1>why nobody does it. There's also some not gone like cultural, etcetera.

0:18:28.840 --> 0:18:31.239
<v Speaker 1>Effects that make it virtually unthinkable. If you were an

0:18:31.240 --> 0:18:34.560
<v Speaker 1>executive at at a tech company and you were sufficiently

0:18:34.560 --> 0:18:37.080
<v Speaker 1>in your cups and had a had a heart to

0:18:37.080 --> 0:18:39.399
<v Speaker 1>heart with someone and said, what's the true number of

0:18:39.480 --> 0:18:43.640
<v Speaker 1>Like if I could wave a magic wand and no consequences,

0:18:44.000 --> 0:18:47.000
<v Speaker 1>where would our staffing be? Would probably be like eighty

0:18:47.160 --> 0:18:49.880
<v Speaker 1>five to ninetent of what it is currently. I think

0:18:49.920 --> 0:18:51.679
<v Speaker 1>I think most people would say, like, oh, there's a

0:18:51.680 --> 0:18:54.760
<v Speaker 1>bit of there's a bit of like I hate the

0:18:54.760 --> 0:18:58.120
<v Speaker 1>word fat in this context about you know, a little

0:18:58.119 --> 0:19:00.480
<v Speaker 1>bit of fluff around the edges, but we're not in

0:19:00.600 --> 0:19:04.879
<v Speaker 1>systemically a terrible place. And I think you know you

0:19:04.880 --> 0:19:07.560
<v Speaker 1>you would get different numbers from different people in different

0:19:07.560 --> 0:19:10.040
<v Speaker 1>parts of the organization, but that feels like plus or

0:19:10.080 --> 0:19:12.439
<v Speaker 1>minus right to me. Should be noted that I was

0:19:12.480 --> 0:19:15.240
<v Speaker 1>a beer worker b rather than the sort of executive

0:19:15.280 --> 0:19:34.440
<v Speaker 1>that would be tesked with making that kind of decision. Patrick,

0:19:34.640 --> 0:19:39.600
<v Speaker 1>you mentioned the sort of impetus towards creating company defining features,

0:19:39.640 --> 0:19:42.160
<v Speaker 1>and this is also something I've always wondered, is there

0:19:42.200 --> 0:19:47.320
<v Speaker 1>a bias in tech towards creating new products and our

0:19:47.440 --> 0:19:52.240
<v Speaker 1>employees and engineers you know, rewarded for doing new things

0:19:52.440 --> 0:19:57.560
<v Speaker 1>rather than maybe maintaining the old ones and perfecting those. Oh,

0:19:57.720 --> 0:20:00.199
<v Speaker 1>this is an extremely important thing to understand and the

0:20:00.200 --> 0:20:03.000
<v Speaker 1>behavior of the large tech companies from outside of them

0:20:03.040 --> 0:20:06.000
<v Speaker 1>that they all have what's called a PERF process in

0:20:06.040 --> 0:20:09.119
<v Speaker 1>the industry, it's called PURF outside is a performance review,

0:20:09.680 --> 0:20:14.159
<v Speaker 1>and the performance reviews are largely how a company takes

0:20:14.840 --> 0:20:17.439
<v Speaker 1>creative work that is done over this time scale of

0:20:17.520 --> 0:20:20.680
<v Speaker 1>like quarters and years, and it is often sort of

0:20:21.200 --> 0:20:24.320
<v Speaker 1>indevigable and very area and reduces it to a number

0:20:24.440 --> 0:20:27.080
<v Speaker 1>such that the company can dole out things of value

0:20:27.160 --> 0:20:32.119
<v Speaker 1>like promotions and bonuses and career paths, etcetera, etcetera. And

0:20:32.320 --> 0:20:36.400
<v Speaker 1>PERF happens on a semi annual or annual basis, and

0:20:37.280 --> 0:20:39.440
<v Speaker 1>the way it PERF works that most large tech companies

0:20:39.480 --> 0:20:42.480
<v Speaker 1>is heavily biases in the direction of getting your name

0:20:42.600 --> 0:20:46.040
<v Speaker 1>attached to new things that shipped in the world versus

0:20:46.440 --> 0:20:48.720
<v Speaker 1>you know, I was assigned to this legacy product, the

0:20:48.720 --> 0:20:51.080
<v Speaker 1>product did not go down for six months, you should

0:20:51.080 --> 0:20:53.800
<v Speaker 1>definitely give me a bonus on that basis. Oddly enough,

0:20:54.400 --> 0:20:57.440
<v Speaker 1>this is not straightforwardly the things that is in the

0:20:57.480 --> 0:21:01.600
<v Speaker 1>company's interests because all of the money is made by existing, well,

0:21:01.640 --> 0:21:03.840
<v Speaker 1>not all the money. The supermajority of money in the

0:21:03.840 --> 0:21:07.359
<v Speaker 1>tech companies is made by satisfying customers you already have

0:21:07.520 --> 0:21:11.200
<v Speaker 1>rather than getting new customers, and the supermajority of money

0:21:11.240 --> 0:21:13.679
<v Speaker 1>is made on your oldest and tourist products rather than

0:21:13.720 --> 0:21:18.000
<v Speaker 1>the new stuff. But institutionally, tech companies biased towards we

0:21:18.080 --> 0:21:20.480
<v Speaker 1>want our best people to be on the new things

0:21:20.560 --> 0:21:24.600
<v Speaker 1>all of the time. And if your individual best people

0:21:25.000 --> 0:21:28.120
<v Speaker 1>want to be, you know, doing the hard yards that

0:21:28.280 --> 0:21:31.200
<v Speaker 1>keeps the old stuff running, they will quickly be dissuaded

0:21:31.240 --> 0:21:33.920
<v Speaker 1>by their mentors and managers, etcetera, and say don't, no, no,

0:21:34.400 --> 0:21:37.560
<v Speaker 1>that is not the way to exceed expectations. You will like,

0:21:37.920 --> 0:21:41.000
<v Speaker 1>if you only do great maintenance work for the for

0:21:41.040 --> 0:21:44.639
<v Speaker 1>the next couple of years, you will be, you know,

0:21:45.119 --> 0:21:48.600
<v Speaker 1>severely career limited here. So figure out something new to

0:21:48.640 --> 0:21:50.439
<v Speaker 1>do and make sure your name is attached to it

0:21:50.520 --> 0:21:53.439
<v Speaker 1>in a way that is legible to your manager and

0:21:53.520 --> 0:21:57.240
<v Speaker 1>your manager's manager and this performance roview process. So let's

0:21:57.280 --> 0:22:00.400
<v Speaker 1>talk about the layoffs that we've seen. Because you said

0:22:00.440 --> 0:22:02.840
<v Speaker 1>something interesting in your first answer, which is that's sort

0:22:02.880 --> 0:22:08.800
<v Speaker 1>of like hiring discipline, hiring quality. During those crazy years

0:22:07.720 --> 0:22:12.720
<v Speaker 1>of one part of may have been loose, maybe not

0:22:12.920 --> 0:22:15.520
<v Speaker 1>as the standards were a little lower, or maybe people

0:22:15.600 --> 0:22:19.200
<v Speaker 1>just didn't fit or something like that. When companies these

0:22:19.280 --> 0:22:23.000
<v Speaker 1>days are now or recently making the decisions about who

0:22:23.040 --> 0:22:26.320
<v Speaker 1>they're going to let go, how skewed is it towards

0:22:26.560 --> 0:22:28.960
<v Speaker 1>that sort of recent cohort. Because the other thing I

0:22:29.000 --> 0:22:31.840
<v Speaker 1>could see is that look at many companies, you probably

0:22:31.880 --> 0:22:35.119
<v Speaker 1>have people who have been there forever who are getting

0:22:35.119 --> 0:22:39.359
<v Speaker 1>paid extremely high salaries or very good salaries just based

0:22:39.400 --> 0:22:42.280
<v Speaker 1>on the fact that they got some bump every single year.

0:22:42.960 --> 0:22:45.560
<v Speaker 1>Maybe they're not pulling their weight to some perceived degree

0:22:45.600 --> 0:22:47.960
<v Speaker 1>as much as they used to be. So how much

0:22:48.000 --> 0:22:49.600
<v Speaker 1>of the you know, when when are they when the

0:22:50.000 --> 0:22:52.560
<v Speaker 1>executive look and say, okay, we're gonna make cuts. How

0:22:52.640 --> 0:22:55.639
<v Speaker 1>much was it skewed towards the new cohort versus seeing

0:22:55.640 --> 0:22:58.560
<v Speaker 1>as like this is an opportunity to get rid of

0:22:58.600 --> 0:23:01.560
<v Speaker 1>some highly paid employees maybe don't add as much value

0:23:01.560 --> 0:23:05.040
<v Speaker 1>as they want. So a disclaimer off the top, layoffs

0:23:05.040 --> 0:23:08.360
<v Speaker 1>are like understandably traumatic for the people who go through them.

0:23:09.200 --> 0:23:11.280
<v Speaker 1>I don't want to minimize that. At the same time,

0:23:11.320 --> 0:23:14.320
<v Speaker 1>I think we often, particularly as as workers in this industry,

0:23:14.720 --> 0:23:18.400
<v Speaker 1>sort of like advocate responsibility for understanding the like structures

0:23:18.440 --> 0:23:20.520
<v Speaker 1>that cause these things to happen in ways that are

0:23:20.560 --> 0:23:23.080
<v Speaker 1>not in our interests. So broadly it's it's good to

0:23:23.119 --> 0:23:26.240
<v Speaker 1>have like open conversations about how these sort of decisions

0:23:26.240 --> 0:23:29.160
<v Speaker 1>are made. I think it is different on a firm

0:23:29.160 --> 0:23:32.840
<v Speaker 1>differing basis, but broadly speaking, you would not want your

0:23:33.440 --> 0:23:36.200
<v Speaker 1>simply to like roll back for the last six months

0:23:36.240 --> 0:23:38.879
<v Speaker 1>of your hiring. There's a couple of different reasons for that.

0:23:39.320 --> 0:23:43.280
<v Speaker 1>One is that when you're dealing with these complex ecosystems

0:23:43.280 --> 0:23:48.119
<v Speaker 1>that sufficiently large companies ecosystem to itself, there's all sorts

0:23:48.119 --> 0:23:50.959
<v Speaker 1>of levers that you are like managing a parallel and

0:23:51.000 --> 0:23:54.280
<v Speaker 1>one of those levers is that you are attempting to

0:23:54.359 --> 0:23:57.800
<v Speaker 1>balance the seniority ranges in various parts of your organization

0:23:58.160 --> 0:24:00.720
<v Speaker 1>such that you always have a mixed within some error

0:24:00.760 --> 0:24:04.520
<v Speaker 1>bars of how many people that you have they're acclimating

0:24:04.600 --> 0:24:07.359
<v Speaker 1>to the company versus how many who have acclimated and

0:24:07.359 --> 0:24:10.040
<v Speaker 1>could do productive work, versus how many are in that

0:24:10.240 --> 0:24:13.439
<v Speaker 1>senior mode where they can lately parachuting to consult on

0:24:13.560 --> 0:24:17.800
<v Speaker 1>things and do the architecture stuff that you're more intermediate

0:24:17.800 --> 0:24:21.200
<v Speaker 1>employees might not be able to do. Yet, if you

0:24:21.840 --> 0:24:25.719
<v Speaker 1>sort of create a bubble in the pipeline by concentrating

0:24:25.720 --> 0:24:27.760
<v Speaker 1>your cuts in the people that were only hired in

0:24:27.760 --> 0:24:31.160
<v Speaker 1>the last six months to two years, then you are

0:24:31.560 --> 0:24:33.600
<v Speaker 1>setting yourself up for a bubble a couple of years

0:24:33.600 --> 0:24:36.879
<v Speaker 1>from now where you have far too few people at

0:24:36.920 --> 0:24:39.520
<v Speaker 1>a portion of the experience curve to do work that

0:24:39.600 --> 0:24:42.200
<v Speaker 1>you urgently need to do work on a week by week,

0:24:42.240 --> 0:24:45.639
<v Speaker 1>quarter by quarter basis. And so if you come to

0:24:45.680 --> 0:24:48.840
<v Speaker 1>the conclusion that we've hired a few too many people

0:24:48.880 --> 0:24:51.359
<v Speaker 1>over the last couple of the last couple of months,

0:24:51.400 --> 0:24:53.359
<v Speaker 1>what are we going to do about that? You have

0:24:53.480 --> 0:24:57.600
<v Speaker 1>to distribute your cuts over a larger number of cohorts

0:24:57.600 --> 0:24:59.960
<v Speaker 1>than the most recent cohorts, or you will set yourself

0:25:00.000 --> 0:25:03.040
<v Speaker 1>fun for some pain. There's also some compliance and legal

0:25:03.080 --> 0:25:05.320
<v Speaker 1>issues that come up with is employees and you already

0:25:05.359 --> 0:25:09.240
<v Speaker 1>a protected class in particular jurisdictions, which also plays into

0:25:09.280 --> 0:25:11.760
<v Speaker 1>it into a little bit. But the biggest reason is

0:25:11.800 --> 0:25:15.400
<v Speaker 1>to avoid causing the operational issues for your company layoffs.

0:25:15.480 --> 0:25:19.600
<v Speaker 1>Is performance management that is a thing that exists in

0:25:19.640 --> 0:25:22.520
<v Speaker 1>the world. And so you know, if you were hearing

0:25:22.640 --> 0:25:25.080
<v Speaker 1>skeptical FECs on Twitter, that they would say about large

0:25:25.080 --> 0:25:27.640
<v Speaker 1>software companies is not merely that they were a little

0:25:27.640 --> 0:25:31.000
<v Speaker 1>bit flabby, but that they were a little bit uh

0:25:31.240 --> 0:25:33.280
<v Speaker 1>self assured of their position in the world, and it

0:25:33.359 --> 0:25:35.680
<v Speaker 1>had too many good years in a row. And if

0:25:35.720 --> 0:25:38.119
<v Speaker 1>you got attached to them, you could you get a

0:25:38.200 --> 0:25:40.639
<v Speaker 1>job in a corner office and not do all that

0:25:40.720 --> 0:25:44.280
<v Speaker 1>much and still be fine. I think that is a

0:25:44.359 --> 0:25:47.199
<v Speaker 1>little exaggerated, but let's say there's certainly cases of it,

0:25:47.280 --> 0:25:51.080
<v Speaker 1>and there's certainly some people like mature into a career

0:25:51.080 --> 0:25:54.320
<v Speaker 1>where they continue being impactful over years and decades, and

0:25:54.359 --> 0:25:56.840
<v Speaker 1>some people end up in sort of a tenured professor

0:25:56.920 --> 0:26:00.280
<v Speaker 1>mode where they've become critical to the organization because they

0:26:00.440 --> 0:26:02.600
<v Speaker 1>know a couple of things that the organization needs to know,

0:26:03.000 --> 0:26:06.120
<v Speaker 1>but they don't bring the same intensity that they used

0:26:06.119 --> 0:26:08.240
<v Speaker 1>to in their career. And then there are some people

0:26:08.280 --> 0:26:13.720
<v Speaker 1>who have like successfully created a niche for themselves inside

0:26:13.720 --> 0:26:16.920
<v Speaker 1>the company, but the company might not desire to exist,

0:26:17.400 --> 0:26:20.400
<v Speaker 1>and nobody wakes up in the morning and says today,

0:26:20.400 --> 0:26:24.000
<v Speaker 1>I want to do layoffs. But given a circumstance where

0:26:24.119 --> 0:26:28.400
<v Speaker 1>everyone in the industry is doing layoffs, some executives might say, okay,

0:26:28.760 --> 0:26:31.400
<v Speaker 1>it is a good time to reevaluate and like turn

0:26:31.480 --> 0:26:34.120
<v Speaker 1>up the heat a little bit on our performance management

0:26:34.160 --> 0:26:36.639
<v Speaker 1>and say, okay, is there anyone who has been coasting

0:26:36.680 --> 0:26:39.280
<v Speaker 1>a little too long? Is there anyone who has uh,

0:26:39.400 --> 0:26:43.000
<v Speaker 1>you know, created a secure little nest for themselves in

0:26:43.000 --> 0:26:44.920
<v Speaker 1>a way that that nest does not add a lot

0:26:44.920 --> 0:26:47.240
<v Speaker 1>of value to the company. Given that we we need

0:26:47.280 --> 0:26:50.920
<v Speaker 1>to usher some people on two new positions, let's start

0:26:50.960 --> 0:26:53.399
<v Speaker 1>with that first and then move to the cuts that

0:26:53.440 --> 0:26:56.040
<v Speaker 1>are going to take more mental energy to do. You know,

0:26:56.160 --> 0:27:00.479
<v Speaker 1>we're talking broadly about hiring discipline and the idea of bloat.

0:27:00.760 --> 0:27:04.879
<v Speaker 1>And this is a slightly loaded question, but to what degree,

0:27:05.200 --> 0:27:09.800
<v Speaker 1>if any, do you think the sort of maybe monopolistic

0:27:09.960 --> 0:27:13.159
<v Speaker 1>mode that some big tech companies have built around their

0:27:13.200 --> 0:27:18.960
<v Speaker 1>businesses has contributed to some complacency on the hiring front.

0:27:20.600 --> 0:27:23.760
<v Speaker 1>And a little adverse to the word monopolistic, but I

0:27:23.800 --> 0:27:26.080
<v Speaker 1>think I get what you're getting at, and that there

0:27:26.160 --> 0:27:28.639
<v Speaker 1>is certainly a lot of rent created in the technology

0:27:28.640 --> 0:27:33.400
<v Speaker 1>industry where these are some of the most effective businesses

0:27:33.480 --> 0:27:37.600
<v Speaker 1>ever created in any industry. Google AdWords will print a

0:27:37.720 --> 0:27:42.200
<v Speaker 1>ginormous amount of money next year, and almost no amount

0:27:42.320 --> 0:27:45.920
<v Speaker 1>of action taken by any set of first actors internal

0:27:46.000 --> 0:27:49.080
<v Speaker 1>or external ad to Google will cause Google AdWords to

0:27:49.119 --> 0:27:52.840
<v Speaker 1>not be worth many, many, many billions of dollars, and

0:27:52.920 --> 0:27:57.520
<v Speaker 1>so the margins on it are very high as well

0:27:57.560 --> 0:28:01.320
<v Speaker 1>in comparison to you know, we we're talking last time

0:28:01.320 --> 0:28:04.480
<v Speaker 1>about the airline industry, where the airline industry has struggled

0:28:04.560 --> 0:28:08.960
<v Speaker 1>mightily to maintain like single digit percentage positive margins over

0:28:09.000 --> 0:28:12.439
<v Speaker 1>a multi decade timeframe. Tech doesn't have that problem. The

0:28:12.520 --> 0:28:16.200
<v Speaker 1>nature of these very sticky products that shearsket size of them,

0:28:16.440 --> 0:28:19.240
<v Speaker 1>and the margins do tend to create a little more

0:28:19.400 --> 0:28:25.640
<v Speaker 1>room for that flabbiness than in exists in many industries

0:28:25.640 --> 0:28:29.160
<v Speaker 1>that have more of a cutthroat reputation. This is sort

0:28:29.160 --> 0:28:32.320
<v Speaker 1>of the polar opposite question. But nowadays we hear a

0:28:32.320 --> 0:28:37.000
<v Speaker 1>lot about the possibility of companies hoarding labor when it

0:28:37.040 --> 0:28:40.000
<v Speaker 1>comes to tech. How much of that do you think

0:28:40.040 --> 0:28:42.280
<v Speaker 1>has actually gone on in the sense that do you

0:28:42.320 --> 0:28:47.840
<v Speaker 1>see tech companies opportunistically hiring people just so their competitors

0:28:47.920 --> 0:28:51.120
<v Speaker 1>can't get their hands on them. I've heard this theory

0:28:51.160 --> 0:28:54.440
<v Speaker 1>advanced many times, and honestly, I don't think it is

0:28:54.560 --> 0:28:59.360
<v Speaker 1>very explanatory, and sometimes it's phrased Google would rather hire

0:28:59.640 --> 0:29:02.800
<v Speaker 1>a particular talented engineers so that they don't create a

0:29:02.800 --> 0:29:06.680
<v Speaker 1>startup and then eventually become competition to one of Google's products.

0:29:07.280 --> 0:29:12.040
<v Speaker 1>If hypothetically that were something that actually motivated executives at

0:29:12.040 --> 0:29:14.880
<v Speaker 1>tech companies, there would be a number of things that

0:29:14.880 --> 0:29:17.920
<v Speaker 1>would be easier to do than quote unquote labor hoarding

0:29:18.200 --> 0:29:21.600
<v Speaker 1>that we don't do institutionally. So in finance, there's this

0:29:21.640 --> 0:29:25.600
<v Speaker 1>institution of gardening leave. Tech doesn't institutionalize gardening leave at

0:29:25.640 --> 0:29:28.880
<v Speaker 1>any level almost anywhere in the industry. And if you

0:29:28.960 --> 0:29:32.240
<v Speaker 1>were thinking about let's prevent highly talented people from doing

0:29:32.280 --> 0:29:35.880
<v Speaker 1>interesting things for our competitors or for new startups that

0:29:35.920 --> 0:29:38.360
<v Speaker 1>they could create. The people in the industry that you

0:29:38.440 --> 0:29:41.440
<v Speaker 1>have the like tightest speed on their productivity level are

0:29:41.480 --> 0:29:44.720
<v Speaker 1>your existing employees, and so you would be you would think, oh, well,

0:29:44.840 --> 0:29:47.280
<v Speaker 1>like the natural place to start is like start with

0:29:47.320 --> 0:29:49.720
<v Speaker 1>people who are already work here and say, if you leave,

0:29:50.000 --> 0:29:51.720
<v Speaker 1>we would like to buy twelve months of your time

0:29:51.760 --> 0:29:54.400
<v Speaker 1>sight unseen, and no one does that. And there's other

0:29:54.440 --> 0:29:58.120
<v Speaker 1>things that you can do Broadly tech is there's always

0:29:58.160 --> 0:29:59.560
<v Speaker 1>a bit of push and pull between the needs of

0:29:59.560 --> 0:30:01.560
<v Speaker 1>a company and the needs of employees, but broadly tech

0:30:01.560 --> 0:30:06.000
<v Speaker 1>who is strikingly pro worker relative to many industries in

0:30:06.000 --> 0:30:08.360
<v Speaker 1>the United States. These things that are done that would

0:30:08.400 --> 0:30:11.840
<v Speaker 1>be consistent with the labor hoarding hypothesis just are not done.

0:30:12.360 --> 0:30:14.440
<v Speaker 1>You know, you can talk to the people that are

0:30:14.440 --> 0:30:16.640
<v Speaker 1>involved in the decisions that that are read on the

0:30:16.640 --> 0:30:21.680
<v Speaker 1>outside as labor hoarding, and they never advanced that as

0:30:21.760 --> 0:30:24.240
<v Speaker 1>a reason to you know, buy up. A new company

0:30:24.280 --> 0:30:26.959
<v Speaker 1>that has four engineers attached to it is typically phrased

0:30:27.280 --> 0:30:29.720
<v Speaker 1>something more similar to, well, this is a team that

0:30:29.760 --> 0:30:33.920
<v Speaker 1>seems already jelled. They're clearly highly highly productive individual contributors,

0:30:34.200 --> 0:30:36.840
<v Speaker 1>and we could have a bunch of engineering recruiters work

0:30:36.880 --> 0:30:40.040
<v Speaker 1>for months to find for similarly talented individuals or the

0:30:40.440 --> 0:30:42.680
<v Speaker 1>m and a team can like tick one box off

0:30:42.680 --> 0:30:44.640
<v Speaker 1>in Q one and get them all in the door

0:30:44.640 --> 0:30:46.560
<v Speaker 1>for the price of one low check. Let's do it.

0:30:47.000 --> 0:30:49.400
<v Speaker 1>The notion of like and let's take this team off

0:30:49.400 --> 0:30:51.800
<v Speaker 1>the table, so they don't, you know, have a market

0:30:51.840 --> 0:30:54.560
<v Speaker 1>success in three years and create something competitive with us

0:30:54.760 --> 0:31:14.400
<v Speaker 1>never comes up. Okay, we started talking about why the

0:31:14.480 --> 0:31:17.680
<v Speaker 1>hiring boom happened. In the first place, we've talked about

0:31:17.720 --> 0:31:20.480
<v Speaker 1>maybe some of the decisions on who is getting cut.

0:31:21.200 --> 0:31:23.720
<v Speaker 1>Let's talk about the sort of prospects for the people

0:31:23.760 --> 0:31:26.280
<v Speaker 1>that have lost their jobs and or the people that

0:31:26.320 --> 0:31:28.200
<v Speaker 1>are thinking about going into a career in tech. So

0:31:28.320 --> 0:31:31.240
<v Speaker 1>how quickly do you perceive that the people losing their

0:31:31.360 --> 0:31:35.280
<v Speaker 1>jobs over the last several months are finding new offers? Like,

0:31:35.320 --> 0:31:37.880
<v Speaker 1>let's start really simple. Can I tack something onto that,

0:31:37.960 --> 0:31:42.560
<v Speaker 1>which is how how fungible are these types of jobs

0:31:42.600 --> 0:31:45.840
<v Speaker 1>in reality? Yeah, A long time ago, in a place

0:31:45.880 --> 0:31:48.680
<v Speaker 1>far far away, during the dot com crash, I was

0:31:48.960 --> 0:31:52.840
<v Speaker 1>graduating from university and the Wall Street Journal was which

0:31:53.320 --> 0:31:55.520
<v Speaker 1>read the Wall Street Journal every day with my father

0:31:55.560 --> 0:31:57.280
<v Speaker 1>growing up. It was how I learned to read the

0:31:57.320 --> 0:31:59.840
<v Speaker 1>Wall Street Journal. Could do no no wrong in my

0:32:00.040 --> 0:32:04.080
<v Speaker 1>as as a an undergraded engineer, and the Wall Street

0:32:04.160 --> 0:32:07.640
<v Speaker 1>Journal was pretty decided that yep, engineering as a field

0:32:07.720 --> 0:32:10.680
<v Speaker 1>is done in the United States of America. Henceforth, all

0:32:10.720 --> 0:32:14.320
<v Speaker 1>engineering will happen in Asia. And I said, oh, chucks,

0:32:14.480 --> 0:32:16.760
<v Speaker 1>I really wanted to get an engineering job. I guess

0:32:16.800 --> 0:32:18.920
<v Speaker 1>I have to move to Asia, and so I did.

0:32:19.200 --> 0:32:23.400
<v Speaker 1>Oh back, now we know the origin story. This is

0:32:23.440 --> 0:32:25.520
<v Speaker 1>the backstory of how I ended up spending my entire

0:32:25.520 --> 0:32:28.440
<v Speaker 1>adult life in Japan. Now that ended up being a

0:32:28.440 --> 0:32:31.120
<v Speaker 1>good read like a good life decision for me for

0:32:31.480 --> 0:32:34.560
<v Speaker 1>entirely unrelated reasons. But it turns out there were, in

0:32:34.640 --> 0:32:37.520
<v Speaker 1>fact engineers hired between two thousand and four and two

0:32:37.560 --> 0:32:40.000
<v Speaker 1>thousand and twenty three in the United States, and so

0:32:40.400 --> 0:32:44.560
<v Speaker 1>reports of the field's demise were heavily exaggerated. If you

0:32:44.600 --> 0:32:48.280
<v Speaker 1>are considering a career in engineering, every reason you had

0:32:48.320 --> 0:32:52.440
<v Speaker 1>to consider a career in engineering in is like still

0:32:52.520 --> 0:32:55.680
<v Speaker 1>a reason to do it. So this like minor wobble

0:32:55.800 --> 0:32:59.320
<v Speaker 1>that will be forgotten in a matter of months. Please

0:32:59.320 --> 0:33:01.560
<v Speaker 1>don't allow it to like cause you to make major

0:33:01.640 --> 0:33:05.960
<v Speaker 1>drastic life decisions. Although life is what happens when when

0:33:06.000 --> 0:33:09.200
<v Speaker 1>you're busy dealing with these little wabbles. Okay, so that

0:33:09.280 --> 0:33:13.800
<v Speaker 1>out of the way. How fungible are people? Broadly speaking?

0:33:14.240 --> 0:33:17.480
<v Speaker 1>In the early levels of career, tech tends to cast

0:33:17.560 --> 0:33:20.920
<v Speaker 1>a very wide net and hire people for what's often

0:33:20.920 --> 0:33:24.320
<v Speaker 1>called horsepower, with the expectation that they will be able

0:33:24.360 --> 0:33:28.120
<v Speaker 1>to specialize over time. There is some degree of worry

0:33:28.200 --> 0:33:31.479
<v Speaker 1>that if you spend ten years or fifteen years in

0:33:31.480 --> 0:33:35.760
<v Speaker 1>a particular industry doing. The quote often used is have

0:33:35.880 --> 0:33:37.960
<v Speaker 1>the same year ten years in a row, then you

0:33:37.960 --> 0:33:40.600
<v Speaker 1>will end up over specialized and only be available for

0:33:40.720 --> 0:33:42.560
<v Speaker 1>doing that sort of thing in the future. Depending on

0:33:42.640 --> 0:33:45.600
<v Speaker 1>the thing you are doing, there might be a sharply

0:33:45.640 --> 0:33:49.080
<v Speaker 1>limited set firms for which that is relevant. But broadly speaking,

0:33:49.320 --> 0:33:52.200
<v Speaker 1>the engineers that were hired to do anything in the

0:33:52.240 --> 0:33:56.720
<v Speaker 1>first five seven is years of their career are broadly

0:33:56.760 --> 0:34:00.920
<v Speaker 1>expected to be able to do not quite anything, but

0:34:01.040 --> 0:34:03.400
<v Speaker 1>like a large subset of all the things that a

0:34:03.600 --> 0:34:06.440
<v Speaker 1>tech employer could want an engineer to do. And so

0:34:06.920 --> 0:34:10.800
<v Speaker 1>the liquidity in the tech market within like a broad

0:34:10.800 --> 0:34:16.520
<v Speaker 1>class like recruiters or engineers, etcetera liquidity between job titles,

0:34:16.560 --> 0:34:19.759
<v Speaker 1>exact roles, exact companies business model of the company is

0:34:19.840 --> 0:34:23.480
<v Speaker 1>very high. And I'm forgetting what Joe's original question was, Well,

0:34:23.560 --> 0:34:26.080
<v Speaker 1>so are they finding just a short term like you

0:34:26.160 --> 0:34:29.560
<v Speaker 1>must hear from people, you must talk to people like, uh,

0:34:30.239 --> 0:34:33.520
<v Speaker 1>people just got cut off? Are they recruiters already reaching

0:34:33.560 --> 0:34:38.080
<v Speaker 1>out to them from different companies? Structurally tech company this

0:34:38.080 --> 0:34:40.480
<v Speaker 1>would be a bad pool quote. Structurally tech companies are

0:34:40.520 --> 0:34:43.040
<v Speaker 1>like sharks. Okay, we're gonna we're gonna pull their quote.

0:34:45.320 --> 0:34:48.080
<v Speaker 1>Just just like sharks, like the way that their gills work.

0:34:48.120 --> 0:34:51.240
<v Speaker 1>They have to keep swimming or they stop getting oxygen.

0:34:51.280 --> 0:34:53.759
<v Speaker 1>And that's an unfortunate thing for most creatures. The tech

0:34:53.760 --> 0:34:57.799
<v Speaker 1>companies because of their staffing models, they and that thing

0:34:57.800 --> 0:35:00.239
<v Speaker 1>we talked about earlier, where they are constantly mixing the

0:35:00.920 --> 0:35:03.480
<v Speaker 1>number of people at each level of seniority within the company.

0:35:03.560 --> 0:35:06.080
<v Speaker 1>They have to keep hiring. And so even if an

0:35:06.120 --> 0:35:09.879
<v Speaker 1>individual company decides like, Okay, we're going to like push

0:35:09.920 --> 0:35:13.280
<v Speaker 1>pause for six weeks and do quote unquote hiring freeze

0:35:13.560 --> 0:35:15.799
<v Speaker 1>one the amount of time and they can actually do

0:35:15.960 --> 0:35:18.680
<v Speaker 1>that and not severely damage the business is limited. So

0:35:19.040 --> 0:35:22.319
<v Speaker 1>it pauses always temporary unless the company is going down

0:35:22.360 --> 0:35:25.359
<v Speaker 1>the tubes. And like the large tech companies certainly are

0:35:25.360 --> 0:35:27.920
<v Speaker 1>not going down the tubes. Some startups might get shaken

0:35:27.960 --> 0:35:30.560
<v Speaker 1>out at the march and tow to UH funding constraints,

0:35:30.600 --> 0:35:34.160
<v Speaker 1>et cetera, But the like the overall business of the Internet,

0:35:34.400 --> 0:35:38.799
<v Speaker 1>continues to grow apace. So pauses are temporary nature. And

0:35:39.280 --> 0:35:43.200
<v Speaker 1>there exists, you know, like many different companies inside that

0:35:43.640 --> 0:35:46.440
<v Speaker 1>the broader ambit of tech. Some of them might be

0:35:46.440 --> 0:35:49.319
<v Speaker 1>positive any given moment, Some of them are you know,

0:35:49.680 --> 0:35:52.960
<v Speaker 1>still attempting to make new investments for three and some

0:35:53.080 --> 0:35:55.640
<v Speaker 1>of them while they're not in uh sort of rapid

0:35:55.640 --> 0:35:59.600
<v Speaker 1>growth mode, growth mode for doing things like you know,

0:35:59.719 --> 0:36:01.399
<v Speaker 1>we have to back fill for people who are leaving

0:36:01.440 --> 0:36:04.360
<v Speaker 1>the company, and in a typical year at a typical

0:36:04.360 --> 0:36:06.319
<v Speaker 1>tech company, that may be like ten percent of our

0:36:06.360 --> 0:36:09.239
<v Speaker 1>engineering staff. So if we've got two thousand engineers, we

0:36:09.239 --> 0:36:11.319
<v Speaker 1>have two hundred engineers that we are slate to hire

0:36:11.360 --> 0:36:15.279
<v Speaker 1>in Interestingly, one of the things that cost a bit

0:36:15.280 --> 0:36:17.960
<v Speaker 1>of the over hiring was companies have this model for

0:36:18.400 --> 0:36:20.640
<v Speaker 1>what percentage of people will leave in a year and

0:36:20.680 --> 0:36:22.839
<v Speaker 1>therefore how many you need to hire just to stay

0:36:22.840 --> 0:36:25.439
<v Speaker 1>at the current level of employment that you have. And

0:36:25.480 --> 0:36:29.320
<v Speaker 1>when the economy started wobbling in, what happened was the

0:36:30.200 --> 0:36:33.560
<v Speaker 1>rates of voluntary attrition that companies, meaning that people who

0:36:33.680 --> 0:36:36.520
<v Speaker 1>resigned out of their own volution, went lower than the

0:36:36.560 --> 0:36:40.880
<v Speaker 1>model predicted. And because you need to like set in

0:36:40.920 --> 0:36:43.680
<v Speaker 1>place a process that takes months to hire people, but

0:36:43.920 --> 0:36:47.880
<v Speaker 1>the process of deciding not to quit is not visible

0:36:47.920 --> 0:36:50.160
<v Speaker 1>for those months, that resulted in sort of like a

0:36:50.239 --> 0:36:53.440
<v Speaker 1>hiring overhang, and so companies overshot their targets for how

0:36:53.440 --> 0:36:57.040
<v Speaker 1>many people would be in the company, which doesn't sound

0:36:57.080 --> 0:36:58.319
<v Speaker 1>like an easy thing to do, but it is a

0:36:58.400 --> 0:37:01.080
<v Speaker 1>very easy thing to do if there is a sort

0:37:01.120 --> 0:37:03.799
<v Speaker 1>of like sharp change and employee behavior with regards to

0:37:03.840 --> 0:37:06.160
<v Speaker 1>things that they have total control over and don't have

0:37:06.200 --> 0:37:08.160
<v Speaker 1>to announce to you, like deciding to leave or not

0:37:08.320 --> 0:37:12.879
<v Speaker 1>leave in a statistical fashion. Are there signs that tech

0:37:12.960 --> 0:37:16.160
<v Speaker 1>workers should look out for that they're about to be

0:37:16.239 --> 0:37:19.680
<v Speaker 1>laid off? Like do you stop being a signed new projects?

0:37:19.719 --> 0:37:22.440
<v Speaker 1>Do your access codes get cut off? Does someone come

0:37:22.480 --> 0:37:25.520
<v Speaker 1>take your stapler off your desk? Like? What exactly are

0:37:25.520 --> 0:37:30.319
<v Speaker 1>the warning signs that you might be in the danger zone? Many,

0:37:30.400 --> 0:37:34.080
<v Speaker 1>many tech people have a large degree of stress with

0:37:34.120 --> 0:37:38.640
<v Speaker 1>regards to whether I'm doing well, am I on the list, etcetera, etcetera,

0:37:38.800 --> 0:37:41.440
<v Speaker 1>And I don't want to add to that stress. Broadly.

0:37:41.560 --> 0:37:44.920
<v Speaker 1>You should. You should have an understanding of how performance

0:37:44.960 --> 0:37:48.399
<v Speaker 1>is calculated at your company, and consider that official view

0:37:48.400 --> 0:37:51.880
<v Speaker 1>of your performance to be perhaps more important than you

0:37:51.920 --> 0:37:54.919
<v Speaker 1>would naively believe it too, because the official view where

0:37:54.960 --> 0:37:57.880
<v Speaker 1>you're the entirety of your performance is reduced down to

0:37:57.960 --> 0:38:01.320
<v Speaker 1>like one number, I'm a full or for this six months.

0:38:01.719 --> 0:38:03.799
<v Speaker 1>That is the only view that is going to be

0:38:03.840 --> 0:38:07.800
<v Speaker 1>available to someone who might be two, three, four steps

0:38:07.800 --> 0:38:10.520
<v Speaker 1>above you on the ladder when they're going to make

0:38:10.800 --> 0:38:14.200
<v Speaker 1>hard decisions in a hypothetical future where they're making hard decisions.

0:38:14.680 --> 0:38:18.480
<v Speaker 1>So the things that cause formal visibility to accompany are

0:38:18.680 --> 0:38:22.399
<v Speaker 1>anomalously important, and the career oriented people around you, who

0:38:22.520 --> 0:38:26.400
<v Speaker 1>are very good at work in those systems their advantages

0:38:26.400 --> 0:38:29.680
<v Speaker 1>will find advantages based on that. But I wouldn't, you know,

0:38:30.040 --> 0:38:32.880
<v Speaker 1>over rotate on perfect The only thing we're thinking about

0:38:33.040 --> 0:38:37.000
<v Speaker 1>seems simple, But just do great work and then make

0:38:37.040 --> 0:38:38.759
<v Speaker 1>sure people are aware of the fact that you did

0:38:38.760 --> 0:38:40.680
<v Speaker 1>the great work, and then things will tend to work

0:38:40.680 --> 0:38:43.160
<v Speaker 1>out in a career fashion over only a long period

0:38:43.160 --> 0:38:46.880
<v Speaker 1>of time, not gun. So I have a question that

0:38:47.040 --> 0:38:50.759
<v Speaker 1>bridges this conversation with the conversation we had last week

0:38:50.800 --> 0:38:53.279
<v Speaker 1>about I T. And I realized I should have asked

0:38:53.320 --> 0:38:56.600
<v Speaker 1>it last time. This whole episode has been because it's

0:38:56.640 --> 0:38:59.920
<v Speaker 1>actually I actually only just had one question from last time.

0:39:00.000 --> 0:39:02.000
<v Speaker 1>I had to come up with a whole excuse for

0:39:02.080 --> 0:39:03.840
<v Speaker 1>why we needed to have you back out just so

0:39:03.880 --> 0:39:06.160
<v Speaker 1>I could ask this. But occurred to me, you know,

0:39:06.280 --> 0:39:09.600
<v Speaker 1>like in the in the business press, we're always reporting

0:39:09.600 --> 0:39:12.200
<v Speaker 1>on c E O s getting fired or let go

0:39:12.320 --> 0:39:16.960
<v Speaker 1>and hired. Sometimes CFOs I don't see much coverage of,

0:39:17.000 --> 0:39:18.719
<v Speaker 1>like c t O S or c I O is

0:39:18.760 --> 0:39:20.799
<v Speaker 1>like the people who run the internal tech systems being

0:39:20.880 --> 0:39:23.759
<v Speaker 1>let go for poor performance. I actually think the only

0:39:23.800 --> 0:39:26.680
<v Speaker 1>time I can ever remember hearing any sort of CTO

0:39:26.840 --> 0:39:29.760
<v Speaker 1>or something losing their job for poor performance is probably

0:39:29.760 --> 0:39:32.960
<v Speaker 1>like fifteen years ago when Twitter was always having the

0:39:33.000 --> 0:39:35.880
<v Speaker 1>fail wills and like they weren't scaling very well during

0:39:36.040 --> 0:39:38.480
<v Speaker 1>the boom years. And other than that, I can't actually

0:39:38.680 --> 0:39:42.400
<v Speaker 1>recall a time in which I like read a story

0:39:42.440 --> 0:39:44.560
<v Speaker 1>about it, you know, a CTO being laid off for

0:39:44.600 --> 0:39:47.560
<v Speaker 1>bad performance. How often does that happen? And you know,

0:39:47.600 --> 0:39:50.160
<v Speaker 1>in the context of whether we're talking about tech companies

0:39:50.600 --> 0:39:52.560
<v Speaker 1>or all. You know, I think we were talking about

0:39:52.680 --> 0:39:55.920
<v Speaker 1>Southwest and others last time, Like how often do the

0:39:55.960 --> 0:39:58.600
<v Speaker 1>head of do those positions lose their job because they say, like,

0:39:59.080 --> 0:40:03.240
<v Speaker 1>our I is not good. So it's a complicated subject

0:40:03.280 --> 0:40:05.400
<v Speaker 1>for a number of reasons. One is that the degree

0:40:05.400 --> 0:40:08.920
<v Speaker 1>of saliency of CTO most companies to the media is

0:40:08.960 --> 0:40:12.160
<v Speaker 1>relatively low. The degree of saliency of many things that

0:40:12.200 --> 0:40:14.200
<v Speaker 1>are very important in the tech industry to the media

0:40:14.360 --> 0:40:16.040
<v Speaker 1>is lower than many people in the tech industry, but

0:40:16.239 --> 0:40:18.880
<v Speaker 1>like and that is one cause of the frequent conflict

0:40:18.880 --> 0:40:21.680
<v Speaker 1>between the media and tech. But be that doesn't two

0:40:21.719 --> 0:40:26.239
<v Speaker 1>people get laid off for for performance. Yes, one relatively

0:40:26.280 --> 0:40:29.200
<v Speaker 1>frequent thing that happens relative to the incidents of senior

0:40:29.880 --> 0:40:34.279
<v Speaker 1>senior executives departing is the uh sort of like fall

0:40:34.320 --> 0:40:37.440
<v Speaker 1>on your sword motion if there is a significant outage.

0:40:37.800 --> 0:40:40.799
<v Speaker 1>Is a thing that frequently happens, are frequently relative to

0:40:40.960 --> 0:40:44.960
<v Speaker 1>all causes for a departure and hesitant to give you

0:40:45.040 --> 0:40:47.919
<v Speaker 1>the example because Tokyo is a small town, but there

0:40:47.960 --> 0:40:50.920
<v Speaker 1>are a number of banks, both in Japan and outside

0:40:50.960 --> 0:40:54.120
<v Speaker 1>of Japan that have had disabling computer outages for like

0:40:54.239 --> 0:40:55.879
<v Speaker 1>days to weeks at a time, where that is an

0:40:55.920 --> 0:40:59.799
<v Speaker 1>extremely extremely thing to be avoided for a bank and

0:41:00.040 --> 0:41:02.800
<v Speaker 1>rules up fairly directly to the head of I T

0:41:03.200 --> 0:41:06.200
<v Speaker 1>or the CEO. And there are cases where either the

0:41:06.239 --> 0:41:08.080
<v Speaker 1>head of I T or the CEO of have left

0:41:08.120 --> 0:41:10.520
<v Speaker 1>us a result of doing that. There is one thing

0:41:10.560 --> 0:41:13.200
<v Speaker 1>that I do like about the culture that is Japanese management,

0:41:13.280 --> 0:41:16.719
<v Speaker 1>where in the sort of like ritualized speech that an

0:41:16.719 --> 0:41:20.239
<v Speaker 1>executive gives it that they will often say police don't

0:41:20.239 --> 0:41:22.120
<v Speaker 1>blame the people that had their hands on the keyboards

0:41:22.160 --> 0:41:24.480
<v Speaker 1>during this. The fact that this was allowed to happen

0:41:24.560 --> 0:41:28.040
<v Speaker 1>was a result of managements miss decisions or taken over

0:41:28.040 --> 0:41:31.759
<v Speaker 1>the course of years. I presided over them, and as

0:41:31.760 --> 0:41:34.600
<v Speaker 1>a result this uh, this allage. Even if you know

0:41:34.640 --> 0:41:37.920
<v Speaker 1>it was one person individually fat fingering something that took

0:41:37.960 --> 0:41:39.960
<v Speaker 1>us down for a week, this belongs at my door,

0:41:40.000 --> 0:41:42.880
<v Speaker 1>and I'm resigning to take responsibility for it. There are

0:41:42.920 --> 0:41:45.319
<v Speaker 1>many things I don't love about Japanese management culture, but

0:41:45.400 --> 0:41:50.319
<v Speaker 1>that bit I do like. Another thing is there are

0:41:50.360 --> 0:41:55.120
<v Speaker 1>reasons for companies to be other than other than maximally

0:41:55.120 --> 0:41:57.760
<v Speaker 1>public about the fact that we are removing a senior

0:41:57.800 --> 0:42:00.480
<v Speaker 1>executive for cost. If you remember the over the course

0:42:00.480 --> 0:42:02.800
<v Speaker 1>of the last couple of years, the I T sector

0:42:02.800 --> 0:42:05.840
<v Speaker 1>has been in sort of like massive boom mode. Companies

0:42:05.880 --> 0:42:09.239
<v Speaker 1>are extremely protective of their brand with respect to engineering candidates.

0:42:09.640 --> 0:42:13.640
<v Speaker 1>Nobody wants to join a organization that exists under a

0:42:13.680 --> 0:42:17.240
<v Speaker 1>cloud who's CTO just got fired for being an idiot.

0:42:17.680 --> 0:42:21.040
<v Speaker 1>So the thing that might happen is like, oh, well,

0:42:21.600 --> 0:42:25.919
<v Speaker 1>the previous VP of engineering wasn't quite up to enough.

0:42:26.239 --> 0:42:29.040
<v Speaker 1>Maybe they can be shuffled onto a different project, and

0:42:29.080 --> 0:42:31.719
<v Speaker 1>we're going to hire a CTO above them. If you've

0:42:31.719 --> 0:42:34.160
<v Speaker 1>already hired a CTO, that's a bit of a bit

0:42:34.160 --> 0:42:37.440
<v Speaker 1>of a more difficult thing. But like shuffles with regards

0:42:37.480 --> 0:42:39.880
<v Speaker 1>to who are the most important people in the engineering

0:42:39.960 --> 0:42:42.920
<v Speaker 1>organization and is there a separate product organization? Do they

0:42:42.920 --> 0:42:45.800
<v Speaker 1>report to the same people, etcetera, etcetera, are sometimes caused

0:42:45.840 --> 0:42:49.239
<v Speaker 1>by like X isn't getting it done. We want to

0:42:49.640 --> 0:42:51.880
<v Speaker 1>like shuffle in why, But we don't want that to

0:42:51.920 --> 0:42:55.160
<v Speaker 1>be seen as a repudiation of X. Not because we

0:42:55.200 --> 0:42:57.239
<v Speaker 1>care about X's opinions so much, but we care about

0:42:57.280 --> 0:42:59.719
<v Speaker 1>how this will be read by internal engineers who we

0:42:59.800 --> 0:43:03.680
<v Speaker 1>want to keep attaptioned to the company and external candidas. Alright,

0:43:03.800 --> 0:43:07.400
<v Speaker 1>one last small question they'll probably eject, a question that

0:43:07.440 --> 0:43:08.880
<v Speaker 1>we can talk about for a long time, but just

0:43:08.880 --> 0:43:11.440
<v Speaker 1>real quickly. So the one one area within tech that

0:43:11.480 --> 0:43:15.000
<v Speaker 1>seems like almost certainly going to be hiring like crazy

0:43:15.080 --> 0:43:18.480
<v Speaker 1>for years at this point is anything to do with AI.

0:43:18.520 --> 0:43:20.799
<v Speaker 1>And you know we all know what's going on there.

0:43:21.520 --> 0:43:23.799
<v Speaker 1>How much are the skills that some of these like

0:43:23.800 --> 0:43:28.520
<v Speaker 1>sort of cutting edge AI companies in need of. How

0:43:28.600 --> 0:43:31.280
<v Speaker 1>much are these skills that sort of legacy or existing

0:43:31.320 --> 0:43:34.600
<v Speaker 1>tech workers might have, or how much are the skills

0:43:34.600 --> 0:43:36.880
<v Speaker 1>that they need something that like you really need years

0:43:36.920 --> 0:43:40.480
<v Speaker 1>of like focus training in the specific area to satisfy

0:43:40.520 --> 0:43:43.360
<v Speaker 1>what these companies need. Can I can I add another

0:43:43.400 --> 0:43:46.440
<v Speaker 1>thing onto the back of that place? How many coding

0:43:46.520 --> 0:43:50.479
<v Speaker 1>jobs will something like chat GPT destroy? Ye? Should people

0:43:50.480 --> 0:43:54.160
<v Speaker 1>stop learning to code? Yeah? Yeah, talk about talk about

0:43:55.120 --> 0:43:58.520
<v Speaker 1>So I have a glib but true answer with respect

0:43:58.560 --> 0:44:02.000
<v Speaker 1>to our advanced AI techniques going to destroy programming jobs.

0:44:02.360 --> 0:44:05.080
<v Speaker 1>The first program or class of programs that we had

0:44:05.120 --> 0:44:08.560
<v Speaker 1>where an advanced computer was obviating the need for human

0:44:08.560 --> 0:44:12.520
<v Speaker 1>programmers was called the compiler, where instead of doing you know,

0:44:12.960 --> 0:44:16.480
<v Speaker 1>complex low level and instructions directly and assembly and speaking

0:44:16.520 --> 0:44:19.160
<v Speaker 1>sort of natively the language of the computer, you use

0:44:19.200 --> 0:44:21.800
<v Speaker 1>what we're called high level programming language is like C

0:44:22.080 --> 0:44:24.520
<v Speaker 1>back in the day. And then the compiler would you know,

0:44:24.920 --> 0:44:27.560
<v Speaker 1>use its magic AI powers to turn that C into

0:44:27.719 --> 0:44:30.040
<v Speaker 1>assembly language so that you didn't have to laboriously do

0:44:30.080 --> 0:44:34.480
<v Speaker 1>the assembly language itself. So every technology that gives programmers

0:44:34.560 --> 0:44:38.240
<v Speaker 1>more power, more capability to do things that are valuable

0:44:38.280 --> 0:44:42.239
<v Speaker 1>for human society probably increases the aggregate demand for programmers

0:44:42.320 --> 0:44:44.200
<v Speaker 1>is sort of like my high level view on the

0:44:44.200 --> 0:44:47.840
<v Speaker 1>world and if yet to see a contrary example to that.

0:44:48.920 --> 0:44:53.040
<v Speaker 1>So an interesting question with regards to AI is what

0:44:53.239 --> 0:44:56.880
<v Speaker 1>are the like, what series of steps is going to

0:44:56.880 --> 0:44:59.919
<v Speaker 1>be necessary to take it to market in a way

0:45:00.200 --> 0:45:03.920
<v Speaker 1>that it actually creates the value for individual people land

0:45:03.960 --> 0:45:07.000
<v Speaker 1>for society, and that it seems to have Latin within it.

0:45:07.360 --> 0:45:10.279
<v Speaker 1>And if you look at like chat GPT, if you

0:45:10.520 --> 0:45:13.080
<v Speaker 1>like I view it as an iceberg, there's the above

0:45:13.160 --> 0:45:15.960
<v Speaker 1>the waterline part and below the waterline part, and below

0:45:16.000 --> 0:45:20.320
<v Speaker 1>the waterline part has some let's say deep deep magic

0:45:20.440 --> 0:45:24.200
<v Speaker 1>there bracketting out that magic for the moment, it seems

0:45:24.239 --> 0:45:27.239
<v Speaker 1>like the above the waterline part was very important in

0:45:27.719 --> 0:45:31.239
<v Speaker 1>why everyone has heard chat GPT and probably used it

0:45:31.280 --> 0:45:34.160
<v Speaker 1>if you're listening to this podcast, but it hasn't heard

0:45:34.200 --> 0:45:37.279
<v Speaker 1>of like similar efforts at Google, etcetera. The reason is

0:45:37.360 --> 0:45:39.759
<v Speaker 1>that there was a you know, a product focused team

0:45:39.840 --> 0:45:43.160
<v Speaker 1>that made a relatively pedestrian piece of software like a

0:45:43.280 --> 0:45:47.719
<v Speaker 1>chat interface, but made it really, really good and like

0:45:47.880 --> 0:45:50.719
<v Speaker 1>work on that to the point where people's interactions with

0:45:50.760 --> 0:45:55.799
<v Speaker 1>the underlying large language model would be like sufficiently effervescent

0:45:55.840 --> 0:45:58.160
<v Speaker 1>that it would screenshot that interaction has shared it over

0:45:58.160 --> 0:46:02.319
<v Speaker 1>to Twitter, and so everything that above the water line

0:46:02.400 --> 0:46:07.280
<v Speaker 1>part is amenable to the to the technologies and tactics

0:46:07.280 --> 0:46:11.480
<v Speaker 1>that existing engineers have with no modification whatsoever. There you're

0:46:11.520 --> 0:46:13.720
<v Speaker 1>talking to the back end. The back end is implemented

0:46:13.719 --> 0:46:15.279
<v Speaker 1>in a different kind of magic than your back ends

0:46:15.360 --> 0:46:18.000
<v Speaker 1>usually are. But the back end has always been magic too.

0:46:18.520 --> 0:46:22.600
<v Speaker 1>That is like part of the answer. There's an interesting question,

0:46:22.840 --> 0:46:25.040
<v Speaker 1>like how much of the work is going to be

0:46:25.120 --> 0:46:28.520
<v Speaker 1>that above the waterline part. The productization of these you know,

0:46:29.040 --> 0:46:32.520
<v Speaker 1>creating like new forms of user interfaces, new models for

0:46:32.560 --> 0:46:35.680
<v Speaker 1>interactions with users, new metaphors that we have to teach

0:46:35.719 --> 0:46:39.759
<v Speaker 1>to people, like new you know there there might be

0:46:39.800 --> 0:46:42.040
<v Speaker 1>an entire field and like education and how to do

0:46:42.239 --> 0:46:45.080
<v Speaker 1>I don't know, prompt engineering, well, prompt engineering being how

0:46:45.120 --> 0:46:47.800
<v Speaker 1>do you type in the right series of incantations to

0:46:47.880 --> 0:46:51.120
<v Speaker 1>the machine so that the the spirited some and stuff

0:46:51.160 --> 0:46:54.360
<v Speaker 1>out of the ether does the right thing for you? So, like,

0:46:54.880 --> 0:46:57.200
<v Speaker 1>what percentage of the work will happen there? First? What

0:46:57.239 --> 0:47:00.319
<v Speaker 1>percentage of the work will happen on these like core

0:47:00.480 --> 0:47:03.319
<v Speaker 1>under the hood model things. A sub sub question to

0:47:03.360 --> 0:47:06.360
<v Speaker 1>that too is like okay, so for the work happening

0:47:07.440 --> 0:47:10.400
<v Speaker 1>at that model layer. Is that work going to happen

0:47:10.520 --> 0:47:13.560
<v Speaker 1>at every company that consumes models, or is it going

0:47:13.600 --> 0:47:17.640
<v Speaker 1>to happen primarily at open AI and Google and Microsoft.

0:47:18.080 --> 0:47:20.000
<v Speaker 1>And we can count the number of firms that like

0:47:20.080 --> 0:47:23.120
<v Speaker 1>need this these engineers on a single hand. In a

0:47:23.200 --> 0:47:26.239
<v Speaker 1>world where we count the number of firms that need

0:47:26.360 --> 0:47:30.040
<v Speaker 1>like dedicated hard AI researchers on a single hand, that

0:47:30.080 --> 0:47:33.279
<v Speaker 1>probably implies like lower total employment of them than in

0:47:33.320 --> 0:47:36.399
<v Speaker 1>the world where every firm that touches AI has its

0:47:36.400 --> 0:47:40.040
<v Speaker 1>own AI practice on staff. But it's at least as

0:47:40.040 --> 0:47:43.319
<v Speaker 1>of like the current state play deeply uncertain where that

0:47:43.360 --> 0:47:45.080
<v Speaker 1>will shake out. And so these are some of the

0:47:45.160 --> 0:47:47.720
<v Speaker 1>questions that get debated upon people at both the AI

0:47:47.760 --> 0:47:50.319
<v Speaker 1>firms and also like you know, if if you are

0:47:50.560 --> 0:47:53.839
<v Speaker 1>a VC that's adventure that's investing in the space, you

0:47:53.880 --> 0:47:56.759
<v Speaker 1>are probably having like a number of interesting dinner conversations

0:47:56.760 --> 0:47:59.879
<v Speaker 1>on okay, where does the value accrue in this chain?

0:48:00.320 --> 0:48:02.560
<v Speaker 1>Where does most of the work get done? What do

0:48:02.640 --> 0:48:05.279
<v Speaker 1>these products like expose themselves to in the life of

0:48:05.280 --> 0:48:07.840
<v Speaker 1>the user. Is it's something deeply under the hood or

0:48:07.880 --> 0:48:10.600
<v Speaker 1>is it integrated into their daily operations? Do they know

0:48:10.760 --> 0:48:13.560
<v Speaker 1>they're using an AI do they know they're using software?

0:48:14.080 --> 0:48:16.440
<v Speaker 1>Is it something that they're like directly typing in or

0:48:16.480 --> 0:48:19.239
<v Speaker 1>is it something that they're interfacing with someone who's doing

0:48:19.239 --> 0:48:22.480
<v Speaker 1>the typing on their path, etcetera, etcetera. Well, Patrick, this

0:48:22.680 --> 0:48:25.040
<v Speaker 1>was absolutely great talking to you. We could talk for

0:48:25.080 --> 0:48:27.319
<v Speaker 1>a long time, but instead we'll just talk to you

0:48:27.320 --> 0:48:29.200
<v Speaker 1>in a few weeks again when we have a million

0:48:29.280 --> 0:48:31.759
<v Speaker 1>more questions. Now, I'm big patigias, but I learned a

0:48:31.760 --> 0:48:35.000
<v Speaker 1>lot and really appreciate you coming back on the show.

0:48:35.360 --> 0:48:36.959
<v Speaker 1>Thanks very much for having me, and I always happy

0:48:36.960 --> 0:48:52.560
<v Speaker 1>to be come back. Thanks Patrick. That was fun, so Tracy,

0:48:52.600 --> 0:48:55.160
<v Speaker 1>there were so many interesting elements of that conversation. I'm

0:48:55.160 --> 0:48:58.239
<v Speaker 1>really glad we had Patrick back. I'm not even sure

0:48:58.239 --> 0:49:00.680
<v Speaker 1>where to begin, but to start, you know, his point

0:49:00.680 --> 0:49:03.600
<v Speaker 1>about the hiring boom during the pandemic, I thought was interesting,

0:49:03.640 --> 0:49:06.080
<v Speaker 1>not just that maybe these companies had a sort of

0:49:06.200 --> 0:49:09.479
<v Speaker 1>unrealistic expectations about how long does growth boo would last,

0:49:09.880 --> 0:49:12.799
<v Speaker 1>but that when you're hiring that fast and under sort

0:49:12.840 --> 0:49:16.719
<v Speaker 1>of extremely unusual situations, like you have that drift where

0:49:16.800 --> 0:49:18.799
<v Speaker 1>maybe you're like there's a little bit of a we're

0:49:18.800 --> 0:49:21.560
<v Speaker 1>not that happy with the class. And then also that point,

0:49:21.640 --> 0:49:24.400
<v Speaker 1>but you also can't just hire everyone who came in

0:49:24.480 --> 0:49:29.240
<v Speaker 1>recently for reasons of like seasoning and like skill level growth. Well,

0:49:29.400 --> 0:49:32.719
<v Speaker 1>to me, it kind of I guess hammers home the

0:49:32.760 --> 0:49:36.120
<v Speaker 1>point that three years on from the start of the

0:49:36.160 --> 0:49:41.759
<v Speaker 1>COVID pandemic, we are still experiencing these normal developments. And

0:49:41.840 --> 0:49:44.680
<v Speaker 1>it kind of gets to the macro versus micro point

0:49:44.800 --> 0:49:48.040
<v Speaker 1>about some of the recent payrolls figures. You know, all

0:49:48.120 --> 0:49:50.880
<v Speaker 1>the tech layoffs that have been announced. Are they saying

0:49:51.120 --> 0:49:54.440
<v Speaker 1>something about the wider economy or is this really a

0:49:54.480 --> 0:49:58.920
<v Speaker 1>tech specific problem? And I think, I mean, I can

0:49:58.960 --> 0:50:00.640
<v Speaker 1>kind of argue it either way. I think I come

0:50:00.680 --> 0:50:04.960
<v Speaker 1>away from that conversation thinking, well, you know, one were

0:50:05.080 --> 0:50:08.480
<v Speaker 1>really unusual periods in terms of hiring for the big

0:50:08.480 --> 0:50:12.040
<v Speaker 1>tech companies, and to some extent it seems reasonable that

0:50:12.040 --> 0:50:14.719
<v Speaker 1>that starts to get rolled back a little bit. But uh,

0:50:14.920 --> 0:50:17.319
<v Speaker 1>you know, it's also I take his point, is he

0:50:17.520 --> 0:50:21.120
<v Speaker 1>and I suspect it's probably true, which is that if

0:50:21.160 --> 0:50:22.960
<v Speaker 1>a year ago you were thinking you wanted to go

0:50:23.000 --> 0:50:27.400
<v Speaker 1>into engineering or coding or something like that, very little

0:50:27.480 --> 0:50:30.640
<v Speaker 1>about what we've seen so far in three should make

0:50:30.680 --> 0:50:32.720
<v Speaker 1>you change your mind. I thought that was really interesting

0:50:32.719 --> 0:50:35.919
<v Speaker 1>too about like sort of the questions about AI and

0:50:36.200 --> 0:50:38.719
<v Speaker 1>how so it's like, as he pointed out, like there

0:50:38.719 --> 0:50:42.200
<v Speaker 1>are other you know, places working on very similar, if

0:50:42.239 --> 0:50:45.760
<v Speaker 1>not equal technology. What sort of made things breakthrough recently

0:50:46.480 --> 0:50:49.440
<v Speaker 1>was the consumerization of some of the chat interface or

0:50:49.480 --> 0:50:52.680
<v Speaker 1>some of these AI images imaging things. So like how

0:50:52.800 --> 0:50:54.680
<v Speaker 1>much of like to go to market for this stuff?

0:50:54.760 --> 0:50:59.400
<v Speaker 1>Ultimately isn't sort of like familiar experiences that people already have.

0:50:59.800 --> 0:51:02.840
<v Speaker 1>It reminds me a lot and I don't mean this

0:51:03.120 --> 0:51:05.719
<v Speaker 1>necessarily in a negative way, but it reminds me a

0:51:05.760 --> 0:51:08.680
<v Speaker 1>lot of crypto in the sense that, like, yes, there

0:51:08.719 --> 0:51:11.799
<v Speaker 1>is a lot of hype around AI, but also in

0:51:11.840 --> 0:51:14.200
<v Speaker 1>the sense that this is a new technology that people

0:51:14.239 --> 0:51:17.680
<v Speaker 1>can actually participate in. And so the use of the

0:51:18.320 --> 0:51:22.480
<v Speaker 1>AI image generators, chat GPT, it kind of brings it

0:51:22.520 --> 0:51:24.479
<v Speaker 1>to people in the same way that they are able

0:51:24.520 --> 0:51:27.680
<v Speaker 1>to experiment with, you know, blockchain and different types of

0:51:27.719 --> 0:51:31.359
<v Speaker 1>money using crypto, and so it suddenly becomes a lot

0:51:31.400 --> 0:51:33.920
<v Speaker 1>more salient for people in that way. Yeah, you know,

0:51:33.960 --> 0:51:36.440
<v Speaker 1>like there's a good example because like with crypto, like

0:51:36.440 --> 0:51:39.319
<v Speaker 1>if you're like interacting with like core protocols are like

0:51:39.360 --> 0:51:42.120
<v Speaker 1>developing on ethereum like that's going to be a limited

0:51:42.200 --> 0:51:44.239
<v Speaker 1>a limited number of people know how to do that.

0:51:44.760 --> 0:51:47.680
<v Speaker 1>But if you're building like an exchange, there are a

0:51:47.680 --> 0:51:49.640
<v Speaker 1>lot of I mean, everyone can have a wallet, right

0:51:49.800 --> 0:51:52.319
<v Speaker 1>you're marketing or stuff like that. There are still all

0:51:52.360 --> 0:51:55.120
<v Speaker 1>of these roles within crypto that have like sort of

0:51:55.120 --> 0:51:58.880
<v Speaker 1>like consumer facing analogs to any other industry. Yeah, I

0:51:58.920 --> 0:52:02.040
<v Speaker 1>need to look up the compile tiler. That sounds interesting. Yeah,

0:52:02.120 --> 0:52:05.320
<v Speaker 1>I'm gonna go off in Google um deep learning compiler.

0:52:05.520 --> 0:52:07.600
<v Speaker 1>I guess for so far a job security, we still

0:52:07.600 --> 0:52:09.879
<v Speaker 1>need to learn to code. Huh. I think we need

0:52:09.960 --> 0:52:14.719
<v Speaker 1>to learn AI. I don't know. Probably I don't know,

0:52:14.960 --> 0:52:18.359
<v Speaker 1>but you know C plus plus, which is what I

0:52:18.440 --> 0:52:22.000
<v Speaker 1>learned in a little bit of no because it's obsolete.

0:52:22.239 --> 0:52:24.720
<v Speaker 1>Like no, I don't think anyone uses c post plus

0:52:24.760 --> 0:52:27.040
<v Speaker 1>and they certainly don't use it for for AI and

0:52:27.560 --> 0:52:30.440
<v Speaker 1>machine learning stuff. I should have asked Patrick what language?

0:52:30.640 --> 0:52:33.320
<v Speaker 1>What coding language Python? When we have them back in

0:52:33.400 --> 0:52:36.480
<v Speaker 1>the Yeah, okay, yeah, our next episode with Patrick will

0:52:36.520 --> 0:52:39.080
<v Speaker 1>be about which coding language we should all be learning

0:52:39.120 --> 0:52:41.279
<v Speaker 1>in the future. Shall we leave it there? Let's leave

0:52:41.320 --> 0:52:43.920
<v Speaker 1>it there. This has been another episode of the All

0:52:43.960 --> 0:52:46.640
<v Speaker 1>Thoughts podcast. I'm Tracy Alloway. You can follow me on

0:52:46.680 --> 0:52:49.480
<v Speaker 1>Twitter at Tracy Alloway. And I'm Joe wisn't Thal. You

0:52:49.520 --> 0:52:52.919
<v Speaker 1>can follow me on Twitter at the Stalwart. Follow our

0:52:52.960 --> 0:52:57.080
<v Speaker 1>guest Patrick McKenzie. He's at Patio eleven and check out

0:52:57.160 --> 0:53:01.520
<v Speaker 1>his Bits about Money newsletter. Follow our producers Carmen Rodriguez

0:53:01.560 --> 0:53:05.160
<v Speaker 1>at Carmen Armand and Dash Bennett at Dashbot. And check

0:53:05.160 --> 0:53:09.000
<v Speaker 1>out all of our podcasts Bloomberg under the handle at podcasts,

0:53:09.200 --> 0:53:12.640
<v Speaker 1>and for more odd Lots content, go to Bloomberg dot

0:53:12.640 --> 0:53:16.560
<v Speaker 1>com slash odd Lots when we push the transcripts Tracy

0:53:16.600 --> 0:53:18.520
<v Speaker 1>and I blog. If we have a weekly newsletter that

0:53:18.600 --> 0:53:21.520
<v Speaker 1>comes out every Friday, go there and sign up. Thanks

0:53:21.600 --> 0:53:22.040
<v Speaker 1>for listening