In short
The Peterman Pod - Episode Summary
Episode Title
Distinguished Eng On Stack Ranking, Competing with Bezos, Regrets | Bryan Cantrill
Description In this episode, Bryan Cantrill, a distinguished engineer formerly at Sun Microsystems and now founder of Oxide Computer Company, shares insights from his extensive 30-year career in software engineering. The discussion covers his experiences navigating the tech boom and bust cycles, competition with Jeff Bezos, and reflections on career regrets.
Links
- [YouTube Episode](https://youtu.be/qhSL-5GtmQM)
- [Apple Podcasts](https://podcasts.apple.com/us/podcast/the-peterman-pod/id1777363835)
- [Episode Transcript](https://www.developing.dev/p/distinguished-eng-on-stack-ranking)
Timimestamps
- 00:00:00 - Intro
- 00:00:42 - Working at Sun Microsystems
- 00:10:17 - His growth to distinguished engineer
- 00:19:14 - Why goaling on promotion is bad
- 00:29:34 - Stack ranking and layoffs
- 00:36:00 - Why he hated the Oracle acquisition
- 00:44:19 - Why Bezos is the apex predator of capitalism
- 00:48:04 - Differences between CTO and VP
- 00:49:58 - Starting his own company
- 01:02:37 - Grilling him on his past
- 01:11:57 - AI boom and bust advice
- 01:14:41 - When he was happiest in his career
- 01:17:22 - Top career regret
- 01:19:21 - Advice for younger self
- 01:20:57 - Outro
---
Key Concepts and Discussions
Background and Career Path
- Sun Microsystems Experience: Cantrill shares how he began his career at Sun, a pioneer in operating systems, and what made it a unique environment for innovation.
- Promotion Philosophy: Discusses the flawed nature of "stack ranking" and artificial promotion goals, arguing that they can hinder motivation and performance, leading to a toxic workplace culture.
Reflections on Leadership and Company Culture
- Stack Ranking: Cantrill describes stack ranking as "organizational cancer," emphasizing that it fosters competition rather than collaboration among team members.
- Oracle Acquisition: Expresses disdain for Oracle's acquisition of Sun, stating it fundamentally changed the company culture and operations, leading to a lack of trust and alignment with customer needs.
Competition with Industry Giants
- Bezos as the Apex Predator: Cantrill refers to Jeff Bezos as an apex predator in capitalism, noting Amazon's relentless execution and innovation, particularly in cloud computing.
- Comparison of Roles: Discusses differences between the roles of CTO and VP, indicating that VPs may focus more on internal management while CTOs often engage externally.
Personal Reflections and Career Regrets
- Happiest Career Moments: Cantrill reflects on his happiest moments being tied to collaborative efforts with strong teams tackling challenging problems, rather than focusing on titles or promotions.
- Top Regret: He admits to a significant hiring mistake early in his career, which ultimately helped him refine Oxide's hiring processes to ensure alignment with company values.
Advice for Future Generations
- Listening to Market Trends: Advises young engineers to remain independent thinkers, cautioning against blindly following market trends or advice from others.
- Importance of Meaningful Work: Stresses the importance of intrinsic motivation in choosing career paths, encouraging others to pursue what resonates with them rather than what is trendy or financially driven.
---
Key Takeaways
- Team Collaboration: The most fulfilling work comes from being part of a passionate team that collectively overcomes challenges.
- Critique of Corporate Practices: Cantrill’s critique of performance reviews, stack ranking, and acquisitions reflects broader issues within corporate culture that can stifle innovation.
- Navigating Career Path: Emphasizes the importance of intrinsic motivation and personal fulfillment over traditional metrics of success in a tech career.
Conclusion Bryan Cantrill’s experiences provide valuable insights into the dynamics of engineering careers, the impact of leadership on company culture, and the importance of pursuing meaningful work. His reflections serve as a guide for those navigating the complexities of the tech industry.
Written by AI. May contain mistakes. Listen to the episode to check what was said.
Chapters
Tap a time to open that second in VOThe Impact of Static Ranking
0:45 to 2:45
Discussion on the negative effects of static ranking in organizations.
“You know, your career started at Sun Microsystems, and that's kind of a legendary company.”
Competing with Jeff Bezos
2:45 to 4:49
Insights into the competitive landscape and lessons learned from Bezos.
“This is where I sound like a true, like, living fossil.”
Early Career at Sun Microsystems
4:49 to 6:47
Bryan shares stories from his early career and the tech industry landscape.
“case you know years later would be just very underhanded very wanting to like to it was not a company that had the best technology.”
Challenges with Microsoft
6:47 to 9:33
Exploration of Microsoft's operating systems and their impact on the industry.
“That you, one, you wanted to work on an operating system, kernel development.”
Career Growth at Sun
9:33 to 12:38
Bryan discusses his career advancement and the promotion process at Sun.
“And really, and I had decided that I didn't want to go back to CUNIX professionally, that I did want.”
Reflections on Performance Reviews
12:38 to 14:06
Critique of the performance review process and its effectiveness.
“The one exception though I would say to that is that the promotion to distinguished engineers was very regrettable and stupid.”
The Promotion Dilemma
14:06 to 15:11
Learn about the complexities and frustrations of the promotion process.
“And they had this thing where if you were superlative, they had to promote you.”
Incentive Programs at Sun
15:12 to 16:12
Explore the Key Employee Incentive Program and its implications.
“Actually, it was funny because all the staff engineers, so Sun had this thing called Keep, the Key Employee Incentive Program.”
Paths to Distinguished Engineer
16:13 to 18:07
Understand the two paths to become a distinguished engineer.
“that I wasn't doing it for the keep bonus because the keep bonus was zero.”
The Role of a CTO in Promotions
18:08 to 19:29
Learn how a CTO's support can shape career advancements.
“first submission called Fishworks, where we had developed a new storage product.”
Show all 39 chapters
Finding Meaning Beyond Titles
19:30 to 21:07
Discuss the importance of seeking meaning beyond career goals.
“Or I'm going to do the other thing where, you know, I talk to my manager.”
Financial Independence and Its Challenges
21:08 to 23:00
Examine the quest for financial independence and its implications.
“Like, let me introduce you to some miserable DEs.”
Lessons from the Dot-Com Bust
23:01 to 24:40
Learn how the dot-com bust influenced career motivations and values.
“Most people kind of like lost it all, but also were fine.”
Postpartum in Engineering
24:41 to 25:25
Explore the concept of postpartum feelings after major achievements.
“And going through periods of like, oh, like I'll buy six houses.”
The Search for Meaning in Wealth
25:26 to 28:00
Discuss the importance of finding meaning beyond financial success.
“Quit your job at Meta and become a podcaster, you know?”
Early Yahoo Experience
28:00 to 29:24
Learn about a Yahoo employee's unconventional job and early success.
“so he gets a job as like a web surfer one at Yahoo, but as like employee number, like single digit.”
The Flaws of Stack Ranking
29:24 to 30:14
Exploration of stack ranking and its negative impact on team dynamics.
“And so that is the kind of person who was.”
Layoffs at Sun Microsystems
30:14 to 33:44
Discussion on the frequency and consequences of layoffs at Sun Microsystems.
“It was like 35 layoffs, 35 rounds of layoffs over like eight years.”
Impact of the Dot-Com Bust
33:44 to 35:08
Understanding how the dot-com bust affected tech companies, including Sun.
“I mean, it is hard to express the period from the dot-com bust when, you know, kind of pets.com creators in the spring of 2000, they kind of ran on momentum until the end of 2000.”
Contrasting Oracle and Sun
35:08 to 37:58
A comparison of the corporate cultures of Oracle and Sun Microsystems.
“That was for, I think that Paul Graham was defending some of the worst behavior of Richard Stallman.”
The Existence of Trust with Customers
37:58 to 41:56
How customer trust affected Sun's reputation and operations.
“There were so many of these like seminal technologies that came out of Sun because of that kind of that passion and independence.”
Leaving Oracle: A Trust Crisis
42:00 to 43:34
Explore Bryan's reasons for leaving Oracle due to a lack of trust and personal integrity.
“what I perceived to be the best of both companies.”
Competing Against AWS: The Apex Predator
43:34 to 44:48
Bryan discusses Joyant's competition with AWS and describes Bezos as a formidable force in the industry.
“You mentioned people were eager to get themselves laid off.”
The Relentless Execution of Amazon
44:48 to 47:52
Learn about Amazon's strategic moves and relentless execution during its peak years.
“And what made Bezos really, really good is that, and I would say, and when I say its height, I mean Amazon hits the mother load.”
The Roles of VP and CTO Explained
47:52 to 49:40
Understand the distinctions between the roles of VP of Engineering and CTO in tech organizations.
“we found lanes where we can go compete with Amazon, but it was, it was, it was brutal.”
The Journey to Starting Oxide
49:40 to 51:16
Hear about Bryan's desire to start a company with his colleague Steve and the initial challenges they faced.
“And what's the story behind you starting your own company?”
Finding the Right Idea for Oxide
51:16 to 53:12
Bryan and Steve navigate the difficult journey of finding a viable startup idea that resonates with them.
“But we're trying to like come up with things that people would fund.”
Pitching VCs and Facing Rejection
53:12 to 55:10
Listen to Bryan's experience pitching to VCs and dealing with rejection from a previous contact.
“He had lived at, Steve had been at Dell prior to Joyant.”
Navigating VC Relationships for Success
55:10 to 56:01
Discover strategies for engaging with VCs and leveraging their networks even when they don't invest.
“What do you want me to do with that one?”
Understanding VC Dynamics
56:01 to 56:41
Explore how VCs' optimism and naivety can shape startup trajectories.
“it's often because like, actually I understand this problem a lot better.”
Lessons from a Startup Failure
56:41 to 58:46
Learn about a startup's pitfalls and the consequences of capital mismanagement.
“He made the intro and it was really, really interesting.”
Building for General Purpose Compute
58:46 to 1:02:24
Discover the focus on general-purpose compute over GPUs in Oxide's strategy.
“And our belief had always been like, that's what we actually want.”
Reflections on Past Regrets
1:02:24 to 1:04:35
Examine the evolution of perspectives on past comments and their impact.
“But, you know, I've been kind of saying it's like 18 months away for a while or 18 months that we would really start thinking about it.”
Leadership and Company Success
1:04:35 to 1:09:50
Analyze the importance of leadership in the success or failure of companies.
“I just want to be sure that I want to be clear that like, it was a mistake.”
Critique of Twitter's Management
1:09:50 to 1:12:08
Discuss the ongoing critique of Twitter's management and its performance.
“So like we're now, I guess Gwen Shotwell now runs, runs Twitter.”
Navigating Booms and Busts in Tech
1:12:09 to 1:14:37
Advice on surviving market fluctuations based on personal experience.
“But what advice would you give, given your experience through the booms and busts, for people who are in today's market?”
Finding Fulfillment in Work
1:14:38 to 1:17:18
Reflections on the happiest times in one's career and the importance of team dynamics.
“I notice your career, almost everything's driven from fulfillment and intrinsic motivation.”
Lessons from Hiring Mistakes
1:17:19 to 1:19:14
Exploration of a significant hiring error and its impact on future hiring practices.
“You know, when you look back on your whole career, is there a particular top regret that you have?”
Reflections on Career Advice
1:19:15 to 1:20:28
Thoughts on giving oneself advice based on past experiences and career luck.
“maybe I would take away the Usenet post and maybe that wouldn't have any long-lasting consequences, but boy, that's about it.”
Transcript
Automatic transcript. May contain errors.0:00Static ranking is organizational cancer.
0:02Bryan Cantrill:This is Bryan Cantrill. He was a distinguished engineer at the original Sun Microsystems, and I asked him about everything he learned over his 30-year career. Performance review is not about you performing better. It's about us measuring your performance. He had interesting stories from competing with Jeff Bezos. He is not merely a predator. He is an apex predator in capitalism. This is what makes him so good. To stories from when he started his own company, Oxide. You go to hang up on a VC, they'll be like, Wait, wait, wait, wait, wait, wait, wait, wait, wait. It's like, oh, okay. And he even let me grill him about his past.
0:34Bryan Cantrill:You raise this long thing and you reply with just a few words. You say, have you ever kissed a girl? We actually, I mean, this is dark, but we... Here's the full episode.
0:48Bryan Cantrill:You know, your career started at Sun Microsystems, and that's kind of a legendary company. It was before my time. What was the industry like when you first entered it? Was there FANG equivalence at the time? What was Sun Microsystems like? What were the other companies like? Yeah, you know, it's kind of funny because there's always been like a FANG kind of equivalent. You know, in the 60s, it was called the bunch. Burroughs, Univac, NCR, Control Data, and Honeywell were the bunch. It was IBM and the bunch. So for kind of every era, there's always some hot group, some growing sector. And in my day, though, so things were, I mean, I think in a bit of a divot.
1:33So I graduated in 96, so I was really interviewing in 95. And there was for sure on-campus interviews happening, but Microsoft was very dominant in that era. And I definitely knew I was not going to go to Microsoft as a kind of a point of principle. What was that? Oh, Bill Gates robbed me of my childhood. Microsoft had such garbage. I mean, they really did. In what sense? Their operating system was, you know, I came up in the personal computer era. So I came up in the 80s. And it wasn't until, you know, I went to university in 1992. and it wasn't, you know, I had just been accustomed to kind of like garbage on the computer.
2:21And it's like, it's garbage in a way that is kind of unfathomable now. DOS itself, the disk operating system from Microsoft, had no memory protection whatsoever. So if an application misbehaved, the machine would just reboot. And this just became like part of life. It's like the machines reboot. Boy, you got to save your work because you'd be in WordPerfect or WordStar or whatever. This is where I sound like a true, like, living fossil. I feel like I'm relaying, like, coming across the Oregon Trail or something. But you'd be in your word processor, you know, working on your English paper, and all of a sudden the machine would reboot.
2:58And actually, that was just – that was life. And I hope you saved it. I hope you had a hard copy. And it was only when I got to college that I realized, like, wait a minute. Hold on. There's actually something called – there's memory protection in the microprocessor. and for much of my adolescence, there had been memory protection present and DOS didn't use it at all. And Windows used it, I mean, with Windows, it gets complicated, but the short answer is Windows didn't use it either. And so it wasn't until I got to like Unix on a workstation and I just remember being like, you know, 18 years old and having like having a command line shell up in one window, having an FTP to Woo Archive, downloading some like EGA game that I would want to go play back in my dorm in another window, having something else going on in a third window, having a compile in a fourth window.
3:49And having this happen magically, concurrently, was just mind bending. It's like, how is this even possible? I mean, again, it sounds, and I appreciate how old this sounds, but this is what it was. And then looking back, I'm like, why do I have garbage from Microsoft? And it's, Microsoft was just not an operating system company. They were the dominant operating system provider, but, but in their DNA, the most fundamental, like the nucleotide base pairs of Microsoft are compilers. They were a compiler company, not an operating systems company. And Apple was, you know, Apple, what was Apple at that time?
4:28I mean, Apple had, this is long fired Steve Jobs. This is the, the, the, the Apple was kind of the Mac was really honestly not that much better it was like cleaner but also didn't make use of memory protection so this was just like unconscionable to me and there was just and this is like aside from all the bad behavior from Microsoft and there was plenty of bad behavior from Microsoft Microsoft was very anti-competitive and you know the findings of fact in the Netscape case you know years later would be just very underhanded very wanting to like to it was not a company that had the best technology.
5:03It was a company that jockeyed for position and then would kind of abuse its position.
5:08Bryan Cantrill:What's the TLDR of that abuse? So what Microsoft would do, and this is a pattern you would see repeated since, but what Microsoft would do is they would announce, you know, you're a promising company that has something that's an application that people might use. They would announce that it's going to become a forthcoming feature of the operating system. And then, but as it turns out, then it wouldn't show up. It was vaporware, that the term vaporware, I think if it didn't originate with Microsoft, Microsoft definitely perfected the art of vaporware of announcing something that didn't exist. And they were kind of dominant with this mediocrity.
5:46Now to their credit, they also, when they went in for, so for example, Microsoft Word, which I mean, still exists, but WordPerfect was the really the dominant word processor, WordPerfect and WordStar. But Microsoft Word was very bad. And to their credit, it would get better over time and ultimately supplanted WordPerfect in part because they started bundling it with the operating system. So they were very deeply anti-competitive. And that's not like an opinion. That's like a judicial finding of fact. That's a Judge Alsup finding of fact. And that changed a lot when Gates, I mean, Gates, when he hit middle age, that company changed a bunch.
6:29And after the antitrust case in the late 90s. But I was not going to work for Microsoft.
6:32Bryan Cantrill:I saw in your goodbye post from Sun Microsystems, when you were leaving the company, you wrote a public post. And you said that when you joined the company and you interviewed, you only knew two things. That you, one, you wanted to work on an operating system, kernel development. And two is that you didn't particularly want to work for Sun. But it looks like you had an amazing time. So what flipped the switch from going from I don't want to work here to I love working here? So when I had kind of talked with other groups at Sun, And I just like the people I dealt with at Sun were fine, but just not where it didn't feel energizing.
7:17And and certainly PBN did not feel energizing. And, you know, I was kind of accustomed to being the youngest person in a group. But, you know, you don't want to be completely by your lonesome. You want to feel like there are other people that have that kind of that same shared passion. And when I met Kevin Clark and Jeff Bonwick, it was like a bolt of lightning. Those two were energized, passionate, really. They saw all of the same things that I saw in terms of the potential for operating systems to be innovative and wanted to go rip out broken code and replace it with beautiful code and all that same verve that I felt.
8:01and yeah, it was absolutely meeting those two. You're just like, okay, I am going to work for Sun. I remember actually very vividly coming back from that trip being like, oh my God, I'm going to go work for Sun. They're going to make me an offer and I'm absolutely going to go work there.
8:15Bryan Cantrill:I saw that eventually you grew to a distinguished engineer there. What was the career ladder like? It would be interesting to know where the kind of member of technical staff, staff engineer, senior staff engineer, distinguished engineer comes from. um i think it might come from sun i think it's possible that sun is the originating company it's also possible from xerox park you have to kind of take it apart where and i actually remember when uh you know i had interacted with some folks at sun and they'd give me a business card and i remember like coming out to sun being like and not really knowing what my rank was and i'm like because i was gonna make business cards i'm like why i'm an engineer and i'm on staff so i like i think i'm a staff engineer so and you know i kind of go to make business cards And then I kind of like didn't complete submission on the form or whatever.
9:00And then, of course, it wasn't that long afterwards. Everybody was like, oh, wait a minute. That was like – that would have been like saying I've got tenure. Like I definitely am not a staff engineer. I'm a member of technical staff. I was an MTS3. So there was the – you would kind of climb up through those ranks and then to staff engineer, senior staff engineer, distinguished engineer.
9:17Bryan Cantrill:And 3 was the start of the – No. I mean I suppose – I think it did start at MTS1. No, most college hires would start at MTS2. but they um but i was an unusual college hire in a lot of ways interesting so they brought you on two levels deep as a new grad yeah yeah that's right um i mean i'd had a lot i um so sun was actually not the first company i worked for i worked for a company called cunex in canada um and i'd done kernel development there so i'd done um os development at at cunex for for two summers um and i'd done some actually some work that i was that i still think is actually i love that.
9:52I love working for CUNIX. I love being in Canada. And really, and I had decided that I didn't want to go back to CUNIX professionally, that I did want. The other thing I would say is I decided that I wanted to come out to Silicon Valley. I did not want to be, I'd gone to school in the Northeast, had worked in Canada, but I really wanted to come out to Silicon Valley. I see.
10:11Bryan Cantrill:So then when you look at your journey growing from, I guess, this MTS3 to up to where you grew like if you were to break down that i guess the story behind that growth and kind of what are the highlights that that stuck out to you that made you grow yeah so i i mean i was not i was very much not focused on my my my grade my rank or promotion that was not on i was not interested in that my view was always like i would much rather be under promoted than over promoted I'd much rather be doing work where people are like, wait a minute, why is, why, why, why are you back here? Like, what happened to you?
10:52You know, I, I, I, that's just, I am not interested in being kind of doing work performatively. I was always going to do what, like, what I felt was the most important thing to go do. And, you know, Sun was a company that was very accommodating of headstrong engineers. And so that's what I wanted to do was solve the problems that our customers had, make the operating system what I believed it could be, kind of realize that vision for what the OS could be. Sun was the only company, honestly, in 1996 that was really invested in the operating system. Every other company was mortgaging its future to Microsoft and Windows.
11:32And all these computer companies were giving up on their own operating system, giving up on Unix. It was really Unix's darkest hour. and the being in that group in Solaris kernel development during those years was enormously energizing and allowed us to do all sorts of things and then along the way you get promoted right along the way like promotions were just the kind of thing that that happened as you as you went along the way um the I mean sons became I learned I would say I took away a lot of life lessons in terms of what works and doesn't work. I found that the, because of course we had formalized performance review and I found this is like not a deep thought, but that formalized performance review never resulted in me having higher performance.
12:18And this is like, this is one of these things that you kind of like feels very naive to say. Cause it's like, you know, dummy, like performance review is not about you performing better. It's about us measuring your performance. it's like well that's not what it should be about it what it should be about is like what feedback is great like we should be making everyone be the best that they can possibly be and the the the formalized the annual cadence of it i felt was very broken you know we would have you submit a self-review of course and then your review is like oh wow my review looks stunningly like my self-review albeit with like grammatical errors introduced uh and you know that in every review um even the reviews in which i was promoted they were just not uplifting like that was not when i look back at the moments of like what were the the highlights for me during that progression it was never being promoted it was always doing a significant body of work or nailing a hard bug or working with someone on something that we thought was impossible like that was the stuff that that that was really catalytic for me um and then this like son just kind of had to promote me along the way.
13:28The one exception though I would say to that is that the promotion to distinguished engineers was very regrettable and stupid. I mean, not my promotion, but just in general, like the process. The process for being promoted at Sun was, I would say, very traditional in that, you know, you're taking your folks that are performing very well and you're promoting them up to the next grade. The Sun did have a very silly process thing that, you know, they had three grades they would give you superlative, excellent, and good. And then I think there was like a, you know, like 70 % good, maybe 20 % excellent and 10 % superlative, something like that.
14:06And they had this thing where if you were superlative, they had to promote you. Like that was like the index for promoting you. Like if you got that superlative grade, they promote you, but also they had to promote you if you, they gave you that superlative grade. So you would, I had these, I had these reviews that were like apologetic being like, look, I have to give you an excellent grade even though like the work that you've done over this past period has been extraordinary and innovative and actually better than the work that you did two years ago or a year ago but I I can't actually give you the superlative grade because if I give you the superlative grade I would have to promote you and we just promoted you a year ago and it's really like we don't want to promote people any faster than every 18 months and you're like okay this doesn't make sense to you I mean this doesn't like I was like okay if like if if you're satisfied with this?
14:52Like, fortunately, like, I just don't care one way or the other. So like, sounds good. Okay. Can I get back to work now? Are we, are we done here? It's like, are we, and then again, trying not to be trolled by the grammatical reviews in my, in, in, in the review that's being handed to me. So now the difference for that was the, and the, you know, the promotion of staff engineers, it was a big deal and like, great, fine. Actually, it was funny because all the staff engineers, so Sun had this thing called Keep, the Key Employee Incentive Program. and keep was effectively like an annual dividend.
15:23It was like a bonus. So, you know, and there was like a keep pool that was set across the company and, you know, kind of a traditional thing, right? And the metric was based on like company performance. That's what they, and so I did hear when I was, you know, an MTS3, MTS4, the staff engineers, like, you know, they would get their keep bonus. And if the keep bonus is really good, they take everyone out to dinner. And it was kind of like, you know, it was like being at the mining town, right? When there's a big ore strike or what have you, Gold Strike. So I was like, okay, wow, this is like, this will be great.
15:52So of course, I mean, just like, of course, like when do I get promoted to staff engineer? It must've been in like 2000, 2001. I get promoted to staff engineer as like the dot-com nuclear bomb goes off. And the keep bonus was, I never got like, keep bonus was zero from then on out. Sun lost 98 % of its value in the public markets. And like, I never, so it's a good thing that I wasn't doing it for the keep bonus because the keep bonus was zero. But then getting – so that was staff engineer, senior staff engineer, and then distinguished engineer was really unfortunate in that there were kind of two paths in to distinguished engineer.
16:29And this may be true of a lot of companies. I don't know. I mean, I don't have ranks at Oxide for this reason. Like I think ranks are corrosive. I don't think they get people to do their best work. I'm not interested in them. But the – at Sun, there were two ways to be a distinguished engineer. One was, of course, to be like promoted from a senior staff engineer to a distinguished engineer. and uh that was a very very i mean i would say rigorous but it's giving it far too much credit it was a very political process the de's would vote on whether you should be admitted to this country club of distinguished engineers which is a terrible idea putting like this is like the wrong place for democracy in a society right the for so many different reasons and the but so that's how you would get promoted distinguished engineer very hard to get promoted the other way to become a distinguished engineer is Sun is buying your little company is aqua hiring your company and your the company's got just enough leverage during that process to be like oh by the way our CTO needs to be a DE so you would have these like DE's just kind of like pop in the side you're like who is this like oh yeah we yeah then we acquired their company so and and there was definitely a difference in like you you knew the the homegrown DE's versus the ones that had been had been aqua hired in But when I actually like, and this is like, I just do not want to even think about this process.
17:47Like, you know, I'm not really a political person. Like the last thing I want to do. Fortunately, we had, I'd done work that was kind of so indisputable at that point that it was going to be, it was pretty clear that if Sun is going to have such a rank, I was probably worthy of it. But again, I didn't want to deal with it. Sun's CTO at the time, Greg Papadopoulos, very grateful to Greg. Greg had chartered this group that we'd developed in San Francisco, first submission called Fishworks, where we had developed a new storage product. Storage product was going gangbusters. It was a great product.
18:21Although a great product, if it had asterisks on it, wasn't as great as we thought it was when we shipped it. We learned a lot about it. But the product was doing really well. Greg, again, I was not in the meeting, so this was told to me secondhand. but your DE case needs to be presented by someone, another DE. Well, Greg presented my case. And so you had the CTO of the company and someone was not a very hierarchical company and Greg was not a very hierarchical person, but Greg put apparently my materials up and it's like, I don't expect anyone to vote against this. Take your vote.
18:52Bryan Cantrill:He said that. Yeah, and apparently it was unanimous. So it's like, thank you, Greg. Deeply appreciative of Greg. I didn't have to deal with that bullshit because Greg was dealing with it for me. and it was kind of like you know honestly it was kind of a validation of my hypothesis like greg honestly viewed it more of a reflection on the company than a reflection on me it's like great i had done work that was at some level kind of indisputable and that's kind of the way i had wanted to chart my career i think there's two schools of thoughts on on you know how people structure their careers within these i guess ladders if a really ambitious new graduate engineer comes to you and they say hey i want to be a distinguished engineer one day I have two ideas.
19:29Bryan Cantrill:One idea is I'm going to just focus on the work and just, you know, promotions will be a byproduct. Or I'm going to do the other thing where, you know, I talk to my manager. I'm like, hey, how do I get to that next level? And hey, what are those things that the next level needs to do? And then I will do work that molds to that mold. Yeah, I would try to to steer someone to a third path what's the third path like what why why do you want to be what what does it why do you want to be distinguished engineer because if that's the goal if the goal is to be a distinguished engineer you get there be distinguished engineer now what i mean do you like do you you know you you can be so fixated on that it's like it doesn't at some level it doesn't that doesn't actually that's not the thing that matters that's that doesn't give you meaning and to me if I had a young engineer who's like I'm I want to be a distinguished engineer I'm like that's a recipe for a midlife crisis so let's try to dial you differently and I think that what I think what you what I would steer someone to is what what's get you on a path that has meaning where you're going to be developing and what drives meaning for you what's important to you and it's like well what's what's important to me is to be a distinguished engineer I'll be like Like, okay, I mean, you'd want to tease it apart.
20:51Get them on the couch a little bit. Like, I mean, are you not loved enough as a child? Like, what's going on? Like, you know, and you kind of work through some of these issues because you don't want to be dependent on that kind of external validation. I would want to be like, let me introduce you to people who've achieved what you are putatively setting out as your goal and are miserable. Like, let me introduce you to some miserable DEs. You want to be wealthy? Let me introduce you to some miserable, wealthy people. so you know that it's like that's that can't be it it's there's got to be something else that that is that the fuel in that furnace and like let's go find that thing and and then we then like the promotions will happen and the work will happen okay but let's say okay mentee comes
21:38Bryan Cantrill:to you and says you have a good point i want financial independence a lot of people i think want that is they they want to yeah what's financial independence though i mean because like we are in such a well compensated domain it's like you and i right now could go out and get a cup of coffee that is the best cup of coffee in the war in san francisco we're in the mission we can get some coffee that is like some ethiopian coffee some amazing coffee that is like the and that is attainable to you and me and and to basically everyone else it's like a six dollar a cup of coffee right yeah yeah well okay well let's say you define it as you don't need to work for money ever again but then what i mean this is like okay you don't need to work for money ever again like okay i get that but but so you can go off and do the thing that actually motivates you then go off and do the thing that actually motivates you but what if it doesn't make money well i think and i well this is where i you want to take it apart and so you want to find a way i I mean, certainly you're going to have things like the difference that you want to make, the meaning that you're going to find is going to be something that's like, yeah, this is just not a career path at all.
22:47Like I can't actually sustain myself at all. So then you need to find a way to balance that, I would say, with your career. And you want to keep that balance. I also think it's a mistake to be like, I'm going to achieve financial independence and then I'm going to do the thing that is meaningful to me. it's like and again you just and i i definitely had the blessing of no most people were like me made a lot of money on paper in the dot-com boom and just lost every penny of it i mean i had a i had a lost carry forward for so many years that i actually like one year i lost track of my lost carry forward i'm like and i just did so but i had a lost carry forward i that and i was like you i had like fond memories of the dot-com bubble when i would take my whatever it was three thousand a year against my, from a lost carry forward.
23:31The, that was most people around here. Most people kind of like lost it all, but also were fine. I think this is the other thing. Like the dot-com bust was super helpful because if you had geared yourself to be really economically motivated in 99, 2000, 98, 99, 2000, which would have been easy. 2001, 2002, 2003, like you, that was not why you were here because this place was nuclear winter. And you had to find something else. And I knew, so the funny thing, I knew lots of people that had to remind themselves why they got in this and it wasn't money. I also knew people, I did know people that made a bunch of money in the dot-com boom.
24:14The people that made a bunch of money in the dot-com boom weren't that interested in tech to begin with. So when it went up in late 99, 2000, they were like, I'm selling it all. I actually don't want to do this. and those people, and there are a couple of them that I knew, and some of them really, really struggled in the next decade because they didn't have to work for the rest of their lives. But now what? Like, you don't have to work. So like now what do you do? And they were on their own search for meaning and like not easy. And going through periods of like, oh, like I'll buy six houses. Then you realize like six houses are kind of like a pain in the ass.
24:49It's like you and I could go drink six cups of coffee concurrently, but you're just like, what am I doing here? Am I just like proving that I can buy six houses? So why do I want six houses? Then you scale that way back. I mean, it gives you like, it really opens your eyes about what matters and what doesn't matter. What doesn't matter as much. Certainly you need to be able to provide for yourself and provide for a family. You wanna be able to raise a family and so on. So you wanna be able to have that, but you wanna do that in a way that's honestly sustainable. I think that too many folks are focused on like, I'm gonna do this so I can leave.
Read the full transcript
25:22It's like, then maybe you shouldn't be in this industry at all. Like go do the thing you would do when you left and find a way to do that in a way. And go pursue that dream. And because you'll be happier. You'll have meaning doing that. Quit your job at Meta and become a podcaster, you know? Oh, well, I did. Yeah, yeah, yeah.
25:44Bryan Cantrill:Well, it's interesting you say that because there's this subreddit, subreddit this community that's all about uh financial independence earning enough and i'll see a very regular post that says guys i did it and i don't know what to do now yeah yeah i did it i did and also like i gear i mean i think this is like this is a problem by the way in engineering not even in the even when the goal is has meaning this is a problem this is right this is what i call postpartum in engineering when you are really focused on shipping something and you're just like shipping this thing is just the lens through which you're doing everything and when we shipped our first rack of oxide i was very concerned about like we are going to have postpartum and there are going to be people who are like i was working so hard and pulling so hard for so long and now we shipped it and like now what and i'm i so even when the thing you've done is obviously meaningful and you've achieved something extraordinary you're going to have that when the thing you've also achieved is like, well, I can like buy any cup of coffee.
26:47It's like the thing I want, like now I'm not even like, I got like, what am I supposed to do? It's just easy to see how you people wonder what the meaning of it really is. And then there are some people that just like snip all the wires and they're like, well, the meaning of it is to get even more. And then just like, you know, then you get like Larry Ellison or whatever, but like, that's also not something that people should
27:08Bryan Cantrill:aspire to right i i well what would you say because i i do know someone who is genuinely happy just doing nothing and by doing nothing i just mean like uh relaxing in bed you know watching their shows you know going to hanging out with friends and stuff i think they had a billion dollars they just do that every day yeah but what you said doesn't work in that case because that doesn't earn anything. You know, I actually did know a guy. I knew a guy who, I actually did know a guy who did this, who, as I'm thinking about people who made money, I knew one of, I believe one of Yahoo's like first employees, but not because he was like crazy sharp or anything, because he like, they wanted to hire a web surfer.
27:54And he was like a pothead. He was like, this sounds like the level of work that I'm, so he gets a job as like a web surfer one at Yahoo, but as like employee number, like single digit. He gets the equity grant as part of like joining the company, never gets another equity grant, but makes a king's ransom because he's very early at Yahoo, never promoted above like web server rank one or whatever, and was complaining to everybody about how much his job sucked. And it was like, you surf the web for a living. Like you've somehow managed to like win this insane lottery where you're getting paid to do like very close to nothing.
28:32And he like, at the start, he owned like all of Yahoo in terms of like surfing. Because the way Yahoo worked, you may be wondering what the hell I'm talking about. Yahoo was a curated directory of links. This is again where I sound like it. Oh, pre-Google. Very much pre-Google. This is like pre-Google. This is not just pre-Google. This is like pre-Lycos, pre-Hotbot, pre-AltaVista. This is like basically pre the ability to search the internet. You would have these curated directory of links. And someone needs to go like find this content. And it was like this guy, Yahoo employee number six or whatever he was.
29:05And so he originally like owned the entire directory, but he's like not very good and not very energetic. It was like, you know, stoned all the time. So they kind of like carved. And finally, I believe at the end, before he finally quit, he owned only like snowboarding in Northern California. That's what it was his like responsibility to. It's like, this is a job. And so that is the kind of person who was. And you would like to think that he found something that was actually meaningful to him, but clearly it was not the work or work for that matter.
29:34Bryan Cantrill:Right. You said earlier there were these ratings, superlative, excellent, good. Excellent, good, something like that. Yeah, yeah, yeah. I noticed you didn't mention there's a bad rating. There was a, yeah, no, there was not, basically not. not sun did not um the the idea of like a pip or the the whole like rank and yank which is what intel famously did um the um rank and yank is that was was that just stack ranking and it was it was their name for stack ranking yeah it was rank and yank um yeah stack stack ranking is organizational cancer it is it is very very very bad news when you especially if you are going to terminate a bottom end percent that is um that's death i i really think that is just a wall-to-wall terrible idea because you've incentivized people to have dead weight on their teams um that they can that oh is that oh so they have fodder they got someone to throw into the wood chipper uh wait so you think that a manager is strategically keeping around oh i know so i mean that definitely happened at sun for sure oh yeah for sure i mean there were people that were like why are they still here like they don't they don't seem to be doing anything and someone kind of took me aside like yeah that person is in your best interest because like do you know what that person's rating is it is always like good like they they get a good so you can be an excellent or a superlative and i'm again i'm like does this make sense to you like why are we okay so you know all sorts of perverse incentives all sorts of perverse incentives with stack ranking was that stack ranking fundamentally you that stack ranking teaches you that your team are adversaries and that's a bad idea that is and it's just not the way i want to operate like the the my big belief is that that teams do extraordinary things and that everybody should want to be serving the team it is it is the team that wins or loses the team that succeeds and i think that stack ranking really operates very much contrary to that you mentioned that sun i mean the stock price went down by 98 percent yeah trading below our cash at one point i mean was there not some management at some point saying hey we gotta it's time to oh i mean mass layoff oh no no sun did i mean sun resisted layoffs for a little while scott was kind of famously did not mcnealy famously did not want to lay people off but that which was a mistake he waited too long for that um but no once the layoff started i mean i I think at one point I counted the number of layoffs that had the rounds of layoffs.
32:10It was like 35 layoffs, 35 rounds of layoffs over like eight years.
32:14Bryan Cantrill:I mean, it's more than for a year. Yeah, absolutely. Yeah, no, it was brutal. That's insane. Well, you get these like small layoffs, big layoffs. I mean, this is actually before the Warn Act, I think. But you would get – we actually – I mean, this is dark. but we, you could, you could, uh, uh, there was an API effectively to the, although this is like before the era of rest APIs, but there was a way to get the employee directory programmatically. And so we would run what we called the obits and the obits would run every day and would tell you who is no longer at the company. And so you would see these small layoffs that were not actually like you, you would see, you know, a group that was like, Oh, or you would see, and then you would see like, oh my God, like that's 1500 people or that's 3000 in today's OVITs.
33:01Bryan Cantrill:Was the company aware that you had that access to that data? Uh, it's Sun. Sun's strength and weakness was that no one was truly in charge. So, um, I mean, I think it would not have been, I would not have been surprising. Um, but, um, I mean, Sun to its credit, um, was a pretty transparent company. So I don't think that we would have, I think that we weren't violating any kind of policy. We were accessing the org tool, which was the tool they had to show you kind of organizational layouts. And we weren't doing anything untoward. But it was a way for us to know, like, what's happening in the company.
33:37So, no, it was layoff after layoff after layoff after layoff after layoff.
33:40Bryan Cantrill:I mean, 35 layoffs. It's crazy. But that was everybody, too. Again, that was not like – Oh, okay. I mean, it is hard to express the period from the dot-com bust when, you know, kind of pets.com creators in the spring of 2000, they kind of ran on momentum until the end of 2000. And at the end of 2000, the dot-com bubble truly, truly burst for everybody, for Sun included. And then 9-11 did not help, right? So what was – and the economy was – tech was basically dead for five years. And Y Combinator is formed kind of at that – Y Combinator is I think 2006. I see. And starts to form, I think in part because I think – to get Graham's perspective on this.
34:36But the – I mean there was a – there was a capital deficit at that point. There were like people that could solve interesting things and there was like no way to start a company to go do it. So it was really, really bleak here for many, many years. I see.
34:50Bryan Cantrill:Slightly off topic, but I was stalking your Twitter and I saw that Paul Graham had blocked you. Do you know? Paul Graham blocked me. He did block me. I think he, yeah, that was a point of pride. I did feel like I really arrived when Paul Graham blocked me. Yeah, Paul Graham blocked me. Yeah, I definitely feel like I'm on the right side of history on that one. Well, what do you think that was for? No, I know what that was for. That was for, I think that Paul Graham was defending some of the worst behavior of Richard Stallman. And the worst behavior of Richard Stallman does not age very well. It's truly, truly some pretty gross kind of behavior.
35:25And he was defending that and I was attacking him for it and he was blocking me for that. So like, all right, I'll take that. But yeah, I mean, Paul Graham is complicated for me. He, and there are a couple of people like this in Silicon Valley that are complicated in that there are, says some things that I really strongly agree with and some things that I really strongly disagree with. Often in the same sentence. So often you're just like, well, I feel like my brain's getting zapped. Like, okay, this is like wrong, but also not wrong. And so, yeah, you see he's a complicated one. There are a couple of people like that.
36:00Bryan Cantrill:I understand that Sun Microsystems was eventually acquired by Oracle. Yes, invaded, yeah. And I just want to know, why was it so controversial at the time? There's even a Wikipedia page that says the acquisition of Sun Microsystems, and it's almost like an obituary, and there's a lot of top-level engineers. Well, it was dramatic. There's actually a really interesting SEC filing, because it's a public company, that IBM and HP were both jockeying to try to buy Sun. And each was trying to sabotage the other. And each was trying to get the kind of their – because they almost wanted to buy Sun punitively.
36:40They were both competitors with Sun. And while they were kind of screwing with one another, Oracle swept in and bought the company. So Oracle – that happened really quickly. The actual acquisition itself was necessarily controversial. It took a while to close. Um, what, I mean, to, to the contrary, I mean, there's nothing like really controversial about Oracle because Oracle is what it is. Um, Oracle is just, there's not a lot of depth to Oracle. Um, Oracle is just an octopus that knows how to feed itself. And the, um, the sun was very much not that way. Sun was, there was, there was a level, I wouldn't call it purism, but there was, sun was always endeavoring to do the right thing by its customers.
37:27Sun was endeavoring to solve hard, interesting technical problems that had commercial relevance. And it gave its engineers, us, tremendous freedom to go do so. And it tended to attract people that wanted to do that, that wanted to do – that wanted to be bold. And it was a great place for that reason because it rewarded that kind of technical boldness. So that's why, you know, NFS and Spark and Java and Solaris and then all the technologies that I worked on, you know, all these things came out of Sun. There were so many of these like seminal technologies that came out of Sun because of that kind of that passion and independence.
38:06Oracle doesn't have any of that. Oracle is just like – Oracle truly is focused on really on one thing, namely its own profitability, which is like I thought when the acquisition happened, I'm like, well, this will be interesting because we'll get someone with like great business savvy maybe. One of the things that was frustrating me about Sun is that Sun, in terms of business execution, Sun fell down a bunch of times. And I thought we would have someone in Oracle that would be just better at the execution of a commercial enterprise. As it turns out, I was really overestimating Oracle. Oracle really is about being able to get effectively a monopoly, a natural monopoly over its own customers, asphyxiating competition, and then raising the rent on its customers.
38:50Like that is really what Oracle wanted to go do. And it's not a company I wanted to work for.
38:56Bryan Cantrill:I see. Because there's a talk that you gave that where you really, I mean. You know, I didn't even, yeah, I know you're talking. The talk is crazy. The Lisa talk from 2011. Yeah, before you even got to talking about it, you said, I'm going to try and make it through this slide without crying. Oh, that was on the same slide. Yeah, yeah. Yeah, and then I think when you were talking about Oracle and you said that they screw customers and lie, I guess you explained the screw customers part, but what's the lie part of? Of Oracle. Yeah. Oracle has made many promises to its own customers that it does not keep.
39:36Oracle has not earned the trust of its customers. If you ask customers, do you trust Oracle, the answer to that would be no. And I would kind of let that speak for itself. Yeah, the making that slide without crying bit was not about Oracle. That was very much about Sun. And that was Scott McNeely's epitaph for Sun. Kicked butt, had fun, didn't cheat, loved our customers, changed computing forever.
40:00Bryan Cantrill:Yeah, you said that. Yeah, that was the bit that – like it still chokes me up a little bit just because it's true. It was true. and we um when we started oxide it's like adopted that as our own mission because that that's exactly what we wanted to go do with oxide um and i thought was a very uh concise distillation of that and that was just not oracle oracle was not interesting when when a lot of the top engineers it seems like there was a an exodus a big exodus where people confiding with each other like were you talking to other high-level engineers say hey we gotta get out of here oh yeah oh yeah i mean it's not even like, I mean, you're just like, you're in a burning building.
40:38Are people confiding with one another that they should leave the burning building? It's like, no, actually people are just like running for their lives. I mean, you're just not like, Oh, what do you think of the burning building? Like, do you think the building is burning? What do you, uh, and no, I mean, it was pretty clear. And there were actually the real true jockeying came from those engineers before it actually closed. There were going to be some engineers that would be laid off before it closed. but as the acquisition closed in other words there were some people that were son employees that were not going to be oracle employees uh aqua laid off like they wouldn't there wouldn't be a
41:14Bryan Cantrill:existing company they're just right that's right so they would they would lose their job okay but they would get like a pretty rich severance package so you had like an absolute line at the trough for how can i get laid off you like i lay me off first um this was not me this was not us. We were, I, I, I was, I mean, in many, I mean, at least to the credit of the, like the people lining up at the trough, at least they knew what was going to happen. Uh, and there's still people to this day that are a little resentful of people who are like that guy, Oh, that guy got laid off. And I, I mean, I quit because I could not work there in good conscience after 45 days, that guy got laid off and got a year of salary or whatever it was.
41:51Um, but we, no, I, um, I was not that I was, we were at this fishworks group in San Francisco and I was really optimistic that I'm really optimistic, somewhat optimistic, um, that we could combine the best of both companies or what I perceived to be the best of both companies. And as it turns out, that's not the case. So
42:07Bryan Cantrill:what'd you see? Cause you left really quick. So, Oh yeah. Oh, it was really clear to me that, but this was a very, very different company. I mean, Oracle gave me like, I decided like, I can't work here anymore. And the time between I decided that and I actually left, which was only like 30 days, a little longer than that, maybe 45 days. Oracle gave me like four other reasons to be like, oh my God, I just can't, I can't stomach working here. I mean, I, and I mean, it was a bunch of things. One, it was Sun for all of its faults. And there were many, many faults of Sun. Sun had the trust of its customers.
42:45Our customers actually were rooting for us at Sun. Our customers wanted us to prevail. Why? Because they actually, they trusted us. And they, even when it wasn't in our own best interests. Like we would be straight with our customers. And I think that that was, we did not lie to our customers, right? And that was something that our customers found very, very appealing. That was not Oracle. Oracle does not have the trust of its customers. And I realized something very important about myself. I can't work for a company that has that kind of profound distrust. I mean, in terms of what we're talking about meaning, that so eroded my own sense of meaning.
43:21I felt ashamed. I felt ashamed to work there. And I had never felt that. I've never, you know, for Sun, I was embarrassed from time to time, but never ashamed. And with Oracle, I was ashamed.
43:35Bryan Cantrill:You mentioned people were eager to get themselves laid off. How do you even do that? Oh, you tell your manager, look, there's a list. Put me on it. Yeah. Oh, there is a list. Okay. Who else is on it? Like, I want to be on it. I mean, it's like all the ways that you, I mean, it's not like you don't fill out a web form. I mean, you're obviously like, you know, you're, you're a courtier kind of whispering about trying to figure out like, what's the scuttlebutt? Who's going to get laid off? I thought you'd have to like really, you know, underperform and like. No, no, no, no, no, no, no, no, no. I think that they were, no, it was all about like, hey, I'm, I have no value to Oracle.
44:10Could you, I mean, it was much more like Oracle's not interested in what I'm doing, right? And then you get like, Oracle is interested. You're like, oh, God damn it.
44:18Bryan Cantrill:um uh so okay so i i get why you left oracle and and obviously sun was acquired yeah and so i the next place you worked at was uh joyant yeah and i understand that this company competed with aws that's right yeah and uh i listened to some of the conversation you already had and yeah interesting quote you said bezos is the apex predator of capitalism yeah what makes you say that Amazon at its height was so relentless on execution. And what made Bezos really, really good is that, and I would say, and when I say its height, I mean Amazon hits the mother load. And they hit the mother load not because they're lucky.
45:05There's luck involved. You know, they allow S3 to be developed, right? They develop EC2. Then they realize what they're on to. and they're on cloud computing before anyone has figured it out. And those reinvents in like from 2010 to say 2015 were relentless. Every reinvent was a price cut. It was price cut and it was a bunch of new services. And if you're a customer, you're like, this is awesome. I love this. This is great. Like, why would I not? I mean, so it was so, and that's what I mean by the Apex operator, because he was on something that was wildly profitable. He pulled off a, just an absolute move of moves in that Amazon did not break out their revenue.
45:54So it was just like Amazon. It's like, you got the dot-com side, you have AWS. They're not breaking out any of that. They're just like literally like, this is how much Amazon's making. Analysts would ask in the call. They're just like, yeah, we're not talking about that. It was apparently you can get away with as a public company. And so they actually created this idea, especially with the relentless price cuts, people are like, oh, the cloud's a terrible business. Like no one should get into the cloud because it's a terrible business. And so people didn't. And meanwhile, like what we knew because we did compete with Amazon, we did have a public cloud and we knew it's like, no, the actual, the margins on this thing are great.
46:26Like this is actually a great business. And Amazon was executing very, very, very, very well. And they did extraordinarily well in those years. And I mean, they are still, obviously, it's a very profitable company, but they have, Amazon has, is not what it was in those years. I'm not sure when the last price cut was announced at reInvent, but it's been a while. It is not, that's not what you get at reInvent. You don't get the kind of the new services that you can't live without. So it's a different company.
47:00Bryan Cantrill:AWS was early and they already had, I guess, a dominant market share. Yeah. Why would Jeff Bezos continue to just like ruthlessly keep going and keep going instead of milking it? Because he is not merely a predator. He is an apex predator in capitalism. This is what makes him so good. He's like, I'm not going to know. Like I'm going to press my advantage. Like I'm going to make it so no one can compete with me. And I'm going to make it so no one wants to get into this business. And I'm going to do it honestly like the right way. I'm going to do it by like giving a great product at a reasonable price.
47:37It's like, damn, yeah, that's, that's good. That's like, that's how, that's a win-win that's a win-win. And it was like essential for innovation during that era of companies that were cloud born. And it, I mean, it was really, and it was very, very hard to compete with Amazon. I'll tell you that. You had to, you had to really like find a lane and we, you know, we found lanes where we can go compete with Amazon, but it was, it was, it was brutal. Their, their, their execution was extraordinary.
48:03Bryan Cantrill:At this company, I saw that you started out as a VP and then you transitioned to CTO at some point. Yeah. What's the difference in the roles? That's a great question. I actually gave a talk on this with Joy and CTO at the time on the contrast between VP of engineering and CTO. And, you know, I'm not sure how much I buy the difference now. I mean, I think in both capacities you're serving as an engineering leader. And I think that, you know, I guess you can argue that a CTO is more outward looking for sure. Chief travel officer is kind of the pejorative for it. You're on the road talking to customers a lot.
48:39You are a VP of engineering, maybe more focused on some of the necessary mechanics that you have in an engineering organization. For me personally, I mean, they brought me in as a VP of engineering because they frankly already had a CTO. So, I mean, again, it's just like the grade I was at Sun, I didn't particularly care. What I did care about is when the CTO had left and then another CTO that we had, the CTO who had been a founder of the company and when he left. So there was kind of like the empty CTO position. I didn't care. What I did care was that we didn't hire externally for that because I did.
49:19So that I did care about a lot about. Like, look, if there's going to be a CTO, I'm happy to be VP of engineering in perpetuity. But like, I would rather like, if there's going to be a CTO, I would like to not hire externally for that, please. Or let me be involved in that anyway.
49:32Bryan Cantrill:But yeah, I was later with the CTO. And why not hire externally? I just didn't want to deal with like having to bring in. I didn't need that. That's not what we needed at that time. What we needed at that time, especially, well, we got rid of the CEO and we really were, we needed really a terrific CEO, which we later got. And so then you started Oxide. Started Oxide in 2019. And what's the story behind you starting your own company? Well, I knew, again, I kind of had in my mind that like I want to start a company. and the thing that I knew is I want to start a company with Steve. Steve and I had worked together at that point.
50:13I mean, Steve was the, when I went to Joyent, I had not talked to Steve prior to going to Joyent and I was going to Joyent in part because I was running away from Oracle and it was going to allow me to hire folks and so on. But I didn't talk to Steve until after I came to Joyent and I'm like, this guy is amazing. And Steve and I just worked very closely together. Steve came up on the go-to-market side, on the sales side. And I knew, I'm like, I definitely want to start a company with this guy. And fortunately, he felt the same. So we both felt like, all right, whatever we do next, we do it together.
50:50And so now it's like, all right, well, now what? Now we've got to figure out what we want to go do. And we had these long walks in the city because we were working in San Francisco. And we had so many bad ideas. I mean, it was just basically one bad idea after another. So then we're trying to come up with ideas that like were a better match for the kinds of things that people would fund. And we recommend people not do this. It's understandable. I did it. I don't understand. But we're trying to like come up with things that people would fund. And coming up with things that were just like not in our heart.
51:24You know what I mean? Like this is like, okay, I can do this. But like really? I mean it would be fun to do it with Steve. But it just doesn't feel like that's not going to – I want to do something that is like – that is this next long chapter of my career. And so as we're kind of struggling with that, and I was trying to figure out, like, okay, we actually need to start talking to venture capitalists at some point. We need to, like, start, like, get this ball rolling and understand, like, and I had always known venture capitalists and had gotten lunch with them over the years, but had not really, like, you know, kind of gone deep.
51:53And I'd known the venture capitalists associated with Joyent for sure. And so I got, I was reminding myself of the email address of one VC in particular, actually a very famous VC. and but someone I had known since early early early in his career and he and I just got in lunch periodically through our careers from when he was first in venture and I was in engineering and we it's like and he'd kind of become uh come pretty famous and I was just wanting to remind myself the email address and the last email he had sent to me which was maybe you know 18 months prior was like hey Brian really enjoyed getting lunch with you today I just want to remind you I will fund literally anything you put in front of me.
52:31I think like, wow. And I was like, Steve, you know, reminding myself of this guy's email address. He said, he will fund literally anything we put in front of him. So like, we should just go big. We should do the thing that is in our heart. And Steve's like, what do you mean? I'm like, we should build the computer that we want to build. We should build a rack scale machine. And he's like, yeah, that'd be amazing. Like, do you think we can get that funded? And I'm like, yeah, I think so. And, you know, that was very much in our heart. That was what we had lived at. He had lived at, Steve had been at Dell prior to Joyant.
53:18He'd been at Dell for a decade. I'd been obviously at Sun for 14 years. And then together at Joyant for another decade. And this was truly in our marrow. And we found like, okay, we can go. And as we started talking to VCs about this, about building, and we, again, envisioned rack scale design. We wanted to do our own board design, do our own switch, do our DC bus bar based design, do all of our own software. Build the machine that we ourselves wish we could have had at Samsung after Samsung acquired Joyent. and what was very catalyzing actually was going to, you know, you were at what would have been Facebook at the time before they renamed it and going to their open compute, going to the open compute summit and looking at like Tioga Pass.
54:05And you're like, what is this? Like Tioga Pass, like, I mean, it was like, I would liken it to discovering Unix as an undergrad when I had been living with DOS and be like, what is this? And you go look at Tioga Pass, you're like, this is what a computer can be? Like, this is gorgeous. This is amazing. We got to go build this for the enterprise market. And what we discovered is this was very contrarian. But things that are contrarian are attractive to venture. So we would get this and people would actually be pretty interested in it. And I mean, you don't have to tell you how the story ends, but we went back.
54:45We actually talked to a bunch of venture capitalists before I went back to that same VC that sent me the email. and I get maybe 45 seconds into describing the problem we want to go solve at Oxide. He's like, Brian, Brian, stop, stop, stop. If you are talking about starting a computer company, I want nothing to do with it. And I'm like, you know, it's funny. You sent me an email years ago that said you would fund literally anything I've put in front of you. And he said, doesn't sound like me. I'm like, well, okay. What do you want me to do with that one? I'm like, you sent me the email. It's like, is your admin writing all of your emails?
55:18I was probably like, I don't, did you have your kid write the email? I don't know what to do with that one. Like you didn't send me the email. Are you calling me a liar? I mean, and I'm like, all right, fine. And it's like, fine. And we go over to the phone. I go to hang up on him. And of course, like VCs, this is just like, it's in the animal brain, right? If you, you go to hang up on a VC, they'll be like, wait, wait, wait, wait, wait, wait, wait, wait, wait, wait. I was like, oh, okay. He's like, wait, wait, wait, wait, wait. Because I'm like, fine. Got it. He's like, wait, wait, wait, wait, wait, wait, wait.
55:41wait, I'm not going to invest. And I'm like, I know you're not going to invest. And I knew the reason I knew he wasn't going to invest is he's had some big zeros in this department. And when a VC has had zeros in something that looks close to what you're doing, they're like, I want nothing to do that again. Like, nope, nope, nope, nope, nope, nope. Was in a bad relationship with one of those. Don't want to do that again. And in part in their defense, it's often because like, actually I understand this problem a lot better. And now I understand all of the headwinds. And now I can, I mean, in some ways, like you need VCs to be, and they need themselves to be like naive at some level.
56:14Optimistic is a better way of phrasing it, where they can like envision the world as it could be as opposed to getting all mired in the way the world is. You gotta be kind of blind to the odds to a certain degree. And I knew that he was not blind to the odds because he'd had two big zeros. And so I knew that he was gonna be like, and one zero that like looked a lot like oxide. And so he's like, look, I'm not gonna find it. I'm like, again, I knew that, but I do wanna help you. like okay that's great and i always tell people like when you are vcs will ask this a lot especially a vc that's like well you're not a fit for them you're not a portfolio fit for them you're not a thesis fit whatever it is you're not a stage fit if they like you they'll be like look i'm not going to invest but how can i help and you always want to have an answer to that question of how you can help and i had an i i knew how he could help i had a very concrete idea it's like one of those zeros um i want to talk to him i want to talk to the i want to talk to the founders i want to understand everything that went wrong.
57:11And I did. He's like, okay, that I can do. He made the intro and it was really, really interesting. And like the mistake that they, that that company had made, and again, had a thesis that looked like oxide, but they, they didn't raise a lot of, they raised kind of arguably too little capital. They got something working that's smaller than what we built at oxide. Minimum viable product at oxide is a rack. It's big. Took us three years, three plus years to develop. They developed something a little bit faster, but as much smaller as basically it, You could view it as like Nitro circa like 2013.
57:42Nitro from the Antiparone acquisition at AWS does a lot of really important offload for AWS. So you could view it as like very early Nitro, but it didn't really have a market, but they had a customer and they got a customer and they're like, great. And the customer was happy and they wanted to use it in particular on their Active Directory servers. Great, we have product market fit. Raised a bunch of money, hired a huge go-to-market team. problem is that customer huge bank only wanted to run it on like their six active directory servers so they were going to buy like quantity six and this is one of the world's largest banks you're like uh-oh so you're like how many world's largest banks are there like well they're like a couple of others but like we're gonna sell like you know two dozen of these things like we got it and they by the time they realized that they had a lot of mouths to feed on the on the go-to-market side and uh they that wasn't a zero it they were acquired but they were acquired in a way that left the founder extremely bitter um and really felt um like he like the vcs had pumped too much capital and i'm at the wrong time had gotten him to do the wrong thing and was then trapped at the acquiring company and was really not happy about it he was also the one so i was describing what we were to do at oxide he's like that is a suicide mission and i just remember writing down a little notebook almost like writing down suicide mission kind of underlining it like
59:05Bryan Cantrill:okay we're on a suicide mission that's fun when i think of rack scale compute especially these days i think of racks of gpus yeah right more than cus yeah is that something that you're building yeah right yeah a very reasonable question and when we set out we're like we i mean again set out in 2019 the gp gpu is was around obviously and important but that's not what we were focused on We were really focused on general purpose compute, general purpose compute, general purpose storage, general purpose networking. And our belief had always been like, that's what we actually want. There is so much to go build there and go differentiate there.
59:44And of course, along the way, people are like, what about an accelerator? What about an accelerator, a GPU? And the problem is that the way we want to build systems, we want to really build systems from first principles where we have components that have transparency at that hardware software interface. and we want to write that lowest layer of software. We are, the company, I mean, ultimately we are building a hardware software co-design product. In order to be able to do that, you need to be able to write very low level software. The problem is that's really not compatible with NVIDIA. NVIDIA is a pretty proprietary company.
1:00:15Executes well, but a very proprietary company. And what that meant is there are effectively two doors for Oxide. One is labeled compete with NVIDIA and the other is labeled partner with NVIDIA. And I didn't want to do either of those things. I have not wanted to do either of those things because I certainly don't want to compete with NVIDIA. And I think that that's getting more plausible now, but we can't partner because we just have a very different view of how systems should be built. And NVIDIA wants to like, their view is like, we should own the whole stack. Like, forget you, whoever you are.
1:00:46So like, okay, that's fine. We're going to be, we're going to focus on general purpose CPU. We got plenty to do over here. I think the thing that's been interesting and a bit surprising is that because the GPU landscape is so cluttered, I mean, you've got this very aggressive, the very well-executing company in terms of NVIDIA. You've got a lot of competitors around it. It's a little, it's gory right over there. And meanwhile, on the general purpose CPU side, it's like HP, Dell, Supermicron, the same companies that are doing the same kind of junk, honestly, that they have been doing. And so we are by our lonesomes in terms of a hardware software product over there.
1:01:29So over and over and over again, we have had people come to Oxide that we think like, no, no, we're not a fit for you because you like you do a lot of GPU. You've got a ton of GPUs like you company famously have a lot of GPUs. No, no, no. We do have a lot of GPUs. We also have a lot of CPU, as it turns out, because certainly the emergent AI workloads, not just AI workloads, but certainly AI workloads, but high-performance computing workloads, there's a lot of general-purpose CPU that's attached to the special-purpose compute. You know, when you're sitting there on ChatGPT and it's surfing the web, you got the little spinny saying it's surfing the web, that is not a GPU that's surfing the web.
1:02:06That is a CPU that's surfing the web. And the CPU is really, really important. So for us, we are more focused than ever on the general purpose CPU. And there is a ton to go do there, fortunately, to get this product to be where we believe it can be. And I think we will do an accelerator at some point. But, you know, I've been kind of saying it's like 18 months away for a while or 18 months that we would really start thinking about it. And, you know, again, I know we'll do it in the limit. But, boy, not in the foreseeable future. We've got a lot to go do as it is.
1:02:38Bryan Cantrill:I think coming to the end, I want to ask you some career reflections and kind of just all over the place type of questions. You wrote a tweet a while ago. I thought it was a really interesting idea, which was you said it would be interesting to have a conference called In Retrospect, where presenters revisit talks that they've given prior and describe how their thinking has evolved since. And I pulled a bunch of stuff that you've, I guess, written or said in the past. I'm curious if your perspective has evolved since then. So we'll go through each of those. So first one, which is actually really famous, when I saw it, I kind of did a double take.
1:03:21Bryan Cantrill:So in 1996, as a new grad, there's this, I don't even know what Usenet was. I had to do research, actually. yeah but there's a guy who he writes this long technical response david s miller yes and a part of it too it's it's not nice either this i saw there's a line in there it says linux is lightweight solaris is a pig which solaris is what i guess the sun was yeah yes and then he writes this long thing and you reply with just a few words you say yeah have you ever kissed a girl yeah oh first of i want to know the context behind it and then also knowing what you know now oh definitely in the regret department, if that's what that's asking.
1:03:59I've got very few regrets in my career, but like you can put that one like pretty firmly in the regret column. Yeah, no, that was, and also had no idea that this was going to live in perpetuity. That, I mean, if you could have told me in, I think 1997 is maybe when I posted, maybe it was, it was 96, it was 96 or 97. Certainly like, I'm like 22. too. Like I'm, I'm very young. If you had told me like, Oh, by the way, 30 years in the future, you're going to be asked about this. I'd be like, what the hell? No, no. Trust me. It's like the world gets weird. You're going to be asked about this. I, the, uh, so it was actually a, okay.
1:04:40This is, I'm not defending it. I just want to be sure that I want to be clear that like, it was a mistake. Um, the, uh, it was actually a reference to a Saturday Night Live sketch. So there's an SNL sketch that is from an era of Saturday Night Live that it's like you can't even find the video. But they have – so the – William Shatner is guest starring on Saturday Night Live. And the skit is that William Shatner is at a Trekkie convention. And the Trekkies are asking him all of these questions. And they're asking him questions that, of course, like, you know, in episode, you know, this season, this episode.
1:05:18what was the combination on the safe? He's like, what? I don't know that. I don't know that. Why would I know that? Like, that's not even, and he's like, these two people are kind of arguing themselves. And they're asking him questions that are like this, that are all about like the kind of the canon of Star Trek. And then he's like, hey, can I just say something? Get a life, people.
1:05:35Bryan Cantrill:You, have you ever kissed a girl? That was where, you know, going to a 30, going to John Lovitz when like Vulcaneers, John Lovitz, do you know? Yeah, no. Yeah, I've done that. I was like lost to history. Why am I doing this? And kind of like looks down at himself. And so like, it was actually like an obscure Saturday Night Live reference, which again, like I'm not, it doesn't make it any better. The, yeah, that was, that's definitely in the regret department. What did he say back to that? Oh, he had a whole lot to say about that. And I actually did have a longer post kind of taking apart what he had said about the, about like, all right, like a lot of what you've said here is actually wrong.
1:06:19And so like really going through kind of point by point, I think, you know, I've actually never, I've never met him. They're talking about that. So he's a very, very talented guy. I think he actually, I actually did read, I think it was in the, with the rebel book about Linux. Remember him reading that he's like, yeah, I kind of like was shooting my mouth off and a son engineer kind of put me, put me back in my place. And I'm like, man, if that is his read on it, he's being very generous to me. So I'd like to believe that maybe he and I both regretted a little bit. We were both like a little, you know, a little young and excitable.
1:06:52But yeah, that was definitely, that was a life lesson. I would say that history forgot about that though.
1:06:58Bryan Cantrill:So on another tweet. Yeah, sorry. Yeah, here we go. This is great. This is like the cleanse. Yeah. Okay, this is in 2022. You wrote a tweet. He said, if you're tempted to blame a team for a startup's failure, please don't. Success is often due to a great team, but failure is almost always due to bad leadership. I wrote that. That's a good one. That's a good one. I don't remember writing that. That's it. I agree with that guy. He's onto something. I guess the question - What was I responding to, I wonder? I missed something that day on the internet. There's some weather on the internet. I'm subtweeting Paul Graham there somewhere, I think.
1:07:32That must have been it.
1:07:33Bryan Cantrill:But - 2022. I'm curious. Do you think that's true? Yeah. For Sun, because Sun ultimately failed. So, okay, I don't agree that Sun failed. I don't agree that Sun failed. Because Sun, again, Sun is founded in 1983 and is invaded in 2008, 2009. That's a good run. That's a really good run. Sun was a public company. Sun was in the Fortune 200. Lots of people, like, kids went to college because their parents were able to work for Sun. And you got, you know, so I don't view, I do not view Sun as a failure. Sun is like, Sun did not, I mean, arguably did not, or not maybe inarguably did not succeed to the scope of its own ambition.
1:08:17But Sun to me is not a failure. Sun is a success.
1:08:19Bryan Cantrill:Was its collapse at the end, I guess, changeable in hindsight with different leadership? I think so. So I think that there are – I mean this is a classic power game of like why did Sun ultimately not survive as an independent entity and why is that? I think there are a bunch of reasons. I think that the – I think that there's a degree to which Sun got very strung out on the very high margins during the dot-com boom and never quite like got off of that. Never – like we embraced x86 too late. we kind of thought of ourselves I mean the company itself became fractured the layoffs didn't help I mean I think we at Fishworks we were developing a storage appliance I felt that we could have been an example of an exemplar of what the kinds of products I felt Sun could develop an independent Sun could develop but it was going to be there's a lot of like stuff that needed to be changed for that and you needed leadership that really was very very interested in that And it's like that just wasn't – that's not what we had.
1:09:26And in hindsight, it was probably time for a change. It was – it's like kind of the way a forest fire – in a normal healthy forest fire is kind of a part of the life cycle of a forest. And you need that to have rebirth. And I think that that – I mean ultimately I think that sun had succeeded but had also run its course. and it was it was time for had its time it had its time absolutely had its time um okay and that
1:09:57Bryan Cantrill:next past take of yours you you wrote in 2022 um perhaps this shouldn't have been surprising but musk has absolutely no idea what he's doing and this is about the takeover of twitter and yeah i actually don't even know what's going on twitter because it's private excuse me i'll i will thank you to not refer to spacex that way oh right it has been acquired by xai and then xai has been rolled into SpaceX. So like we're now, I guess Gwen Shotwell now runs, runs Twitter. So I guess, do, do you still agree that it's run poorly? Oh God. Yes. Yes. Yeah. I definitely agree that. I mean, cause it, yeah, definitely.
1:10:34It's so, I mean, yeah, yes, yes. I mean, yes. I really, I like, I literally feel dirty being specific about that. But when, I mean, when there's a lot of, there's rampant bad behavior on Twitter. Community notes. Yes. Community notes. Great. Everything else, pretty much a tire fire. What's your number one thing that is tire fire? The number one thing of tire fire is that they, they, they're all, we'll tell you this. The reason that we at Oxide don't engage on Twitter, I can't have an Oxide tweet that is sitting next to some of the tweets that I've seen. Oh, you see. It's like the level of racism, bluntly.
1:11:16I mean, crazy racism, crazy, crazy racism, crazy anti-Semitism, crazy and crazy anti-Islam, like just crazy hate, crazy levels, the kinds of things that you literally could not say. and they're like, oh, it's free speech. It's like, it's not free speech. It's so deeply offensive and reflective. It's like, it's so deeply offensive that I don't want my content to be anywhere near it. I don't want someone to be looking at that and looking at my content. I'm sorry. We're just not going to do that.
1:11:57Bryan Cantrill:And you lived through a bunch of booms and busts. And honestly, I don't even know exactly if we're in a boom or a bust right now. I mean, AI is going crazy and there's all these layoffs. Crazy. Yeah, that's a good point. But what advice would you give, given your experience through the booms and busts, for people who are in today's market? Yeah. And I would say that some of this I do think is endemic. I mean, when I first moved out here, I'm like, oh, this is great. My grandfather was a petroleum engineer. And so I kind of grew up with stories of like plants that were going to be built and then shut down or pipelines that were going to be built and then shut down.
1:12:31Like everything tracking the price of oil, right? The oil patch is very boom and bust. And I'm like, oh, this is great. I'm in software. Like I'm immune from booms of us. I remember thinking this, like, you know, you're just like, and of course, looking back at it now, you're like, oh my God, no, no, we are, they are a bit endemic and they're endemic for reasons that are somewhat endearing in that, like, we get so optimistic that we kind of get ahead of ourselves from an optimism perspective. We also get ahead of ourselves from a pessimism perspective. And what I would say is like you got to be really careful about listening to other people.
1:13:09People will tell you that this is going to be the future or that thing is dead. And you got to be like, just be your own judge. I had people tell me that operating systems are done in 1996. I'm really glad I didn't listen to them. Really glad I didn't listen to them. People tell us you can't start a computer company in 2019. I'm really glad we didn't listen to them. VC firms, we only fund SaaS. Those VC firms are like, well, that's like SaaS is struggling right now. But I would also say similarly, like if SaaS is in your heart, as an example, where people are like, right now people are like, SaaS is going to be, the Gen AI, the LLM-assisted coding is going to really put a squeeze on the SaaS companies.
1:13:53And I think there's definitely truth to that. But if one's heart is in that, you should ignore the pessimism or treat the pessimism and the optimism with a grain of salt. Be your own judge and be true to what you want to do. Don't do the things that like, well, I'm doing this because it's like a hot space. It's like you should do this because I think it's – and there are plenty of people for good reason. I mean these things are amazing. I mean, where we are with respect to these LMs is just bonkers. And you can easily say, I want to be very, find a great deal of intrinsic appeal to that. But that's the reason that you should be going into these systems is because you think like, no, no, no, this is, to quote Steve Jobs, this is the dent I want to kick in the universe.
1:14:41Bryan Cantrill:I notice your career, almost everything's driven from fulfillment and intrinsic motivation. is there a time in your career that you look at and say that's the happiest time of my career yeah that's a great question we ask this at oxide we ask you when have you been happiest and why um for exactly that reason and i would say that like there it's not the it's not necessarily an era um it is it is the it is times that i've been happy i mean bluntly like i'm pretty happy right now. Oxide's great. We have the moments for me, and this was an important kind of question for me to reflect on as we were starting Oxide.
1:15:20And this is actually due to a friend of mine who had been at a startup and he and I were taking a walk in San Francisco as kind of Steve and I are talking about bad ideas. And he was like, you really need to answer for yourself. Why do you want to do this? What is drawing you to start a company? And because it wasn't financial return for me and people should not start a company for financial return. That's just not a good, that's not good life advice. But what was drawing me like, well, the thing that's drawing me actually is that the moments that have been the happiest have been working on an incredible team and being on a team that where everyone individually is like, I don't think we can pull this off.
1:15:59Like this is actually too difficult to pull off. And then everybody works together, compliments one another and you pull it off, man, that is, that feeling is extraordinary. And the times that I'd had that, I'd had it with D-Trace. I had had it at Fishworks. I'd had it at Joyent a couple of times with LX, with Triton. Those times have been like, oh, that's what's amazing to me. And so, I mean, in many ways, like the bedrock of Oxide is like, what if we found a company around, part of the reason we were appealing, the larger problem was appealing to us is like, we're going to be able to attract an extraordinary team.
1:16:37And we have a team that is, it is so uplifting to be on a team. I've always said that the organizational model for Oxide is a heist movie. You know, you've got your safe cracker, you've got your getaway driver, your demolitions expert, right? Heist movies are great because of that. And like, because it's the group coming together, everyone's skill sets kind of coming in at exactly the right moment. And man, I love that. I love that so much. And Steve loves that. I mean, that's part of like our shared bond is he and I are both very, very team oriented. We built a company around that. And it's extraordinary.
1:17:12It is truly, truly extraordinary. It's why we've been able to pull off what we've been able to pull off with the small team that we've got. I think people are kind of shocked at how small a team that we've got given what we've been able to pull off.
1:17:22Bryan Cantrill:You know, when you look back on your whole career, is there a particular top regret that you have? I mean, I made an extraordinarily bad hire at joint. I think the worst hire in human history, many people in Silicon Valley will say like, well, that can't be the worst hire in human history because I feel I have made the worst hire in human history. And as I tell people like, look, I'm happy to give up the crown, but you should know that my guy presented himself under an assumed name and just got off parole for violent felonies from San Quentin. And it's not what made him a bad employee. And usually people are like, no, no, no.
1:17:55I think you've made the worst hire. I'm like, thank you. Thank you very much. Um, that was a bad experience. It was also very eyeopening because everything I was doing about hiring was wrong. And we, after we rectified that situation and got him out, we stripped hiring to the studs and really rethought hiring from the, from the very first principles, that hiring process, a very writing intensive process, one that really gets to intrinsic motivation became the hiring process at Oxide. and there was a moment where I'm like, oh my God, like this extraordinary team at Oxide, very much, I think, related absolutely to the hiring process that we have, this hiring process that I built because I made the worst hiring hire of all time.
1:18:37I needed that guy. So you don't regret it. I don't regret it. I don't regret it. In fact, I'm even like, to kind of go back into the time machine and remove it, I think Oxide, I don't know if Oxide makes it because I would have continued to hire the way I was hiring, which was naively. It was hiring not rigorously. It was not selecting people based on their values. So no, I absolutely needed it. So I think, and I view that way of a lot of things that have maybe not gone the right way, but all of those failures were really, really important. And it's very hard to go back and you don't want to take those away.
1:19:14I mean, if I go to the time machine, maybe I would take away the Usenet post and maybe that wouldn't have any long-lasting consequences, but boy, that's about it.
1:19:21Bryan Cantrill:Awesome. And then last question is, if you can go back to the beginning of your career, knowing everything you know now, what advice would you give yourself? Jesus, don't fuck it up. Don't fuck it up. I would just think, because I feel so lucky. So I've been so lucky in so many regards. I've been in the right place at the right time, so many different times over. And I've trusted my gut when sometimes that was not the thing, that when that was kind of a controvertising thing to do. I mean, I would be scared to give myself advice because I would be worried that I would somehow tamper with what I feel has been an extraordinarily lucky career where I have been able to do so much with so many extraordinary people.
1:20:08I've been blessed with so many incredible colleagues and I, that has been so essential for everything that I've done. And I wouldn't want to do anything to endanger that. So I'd be going back to my past self. I'd be like, I got nothing to say, like, just, yeah, I don't want to screw anything up. Like I just, because I feel that I feel really, really lucky. And it wasn't always because, because again, it's like I made mistakes along the way, but the mistakes became load bearing and important. And I wouldn't want to not make those mistakes.
1:20:39Bryan Cantrill:Those mistakes were really important. Well, it doesn't get better than that. And thank you for your time today. I really appreciate it. Absolutely. Thank you for the thoughtful questions. Really great conversation. And thanks for doing the hall of shame here on the past tweets. That was a lot of fun. Yeah. Awesome. Thanks so much. Thank you. Thank you for listening to the podcast. It's a passion project of mine that I really enjoyed building. Another passion project that I've been working on, kind of in secret, is building an ergonomic keyboard that I wish existed. And I finally have a prototype, so I'd love to show you what we've built.
1:21:13Bryan Cantrill:It's ultra low profile and ergonomic, and I couldn't find anything like it on the market. So that's why we built it. I'll put a link to the keyboard in the description. You can take a look and learn more about the project there. We could definitely use your support. Also, if you have any feedback for me about the show, I'd love to hear it. comments on YouTube have led to guests coming on like Ilya Grigorik and David Fowler I wasn't aware of them until someone dropped a comment also feedback in the comments helped me learn to reduce the number of cliffhangers in the intros so your comments definitely make a difference please keep letting me know what you'd like to see more of in the show and I'll see you in the next episode
From the publisher
Bryan Cantrill was a distinguished engineer at Sun Microsystems and has now founded his own company called Oxide Computer Company. We discussed his career experiences through boom/busts, what competing with Bezos was like, and career regrets.
𝗣𝗼𝗱𝗰𝗮𝘀𝘁 𝗹𝗶𝗻𝗸𝘀:
• YouTube: https://youtu.be/qhSL-5GtmQM
• Apple: https://podcasts.apple.com/us/podcast/the-peterman-pod/id1777363835
• Transcript: https://www.developing.dev/p/distinguished-eng-on-stack-ranking
𝗘𝗽𝗶𝘀𝗼𝗱𝗲 𝗹𝗶𝗻𝗸𝘀:
• Link to the part in the talk on Oracle/Sun we discussed - https://youtu.be/-zRN7XLCRhc?si=eExjIMZROGjJcDsw&t=1977
𝗧𝗶𝗺𝗲𝘀𝘁𝗮𝗺𝗽𝘀:
00:00:00 - Intro
00:00:42 - Working at Sun Microsystems
00:10:17 - His growth to distinguished eng
00:19:14 - Why goaling on promotion is bad
00:29:34 - Stack ranking and layoffs
00:36:00 - Why he hated the Oracle acquisition
00:44:19 - Why Bezos is the apex predator of capitalism
00:48:04 - Differences between CTO and VP
00:49:58 - Starting his own company
01:02:37 - Grilling him on his past
01:11:57 - AI boom and bust advice
01:14:41 - When he was happiest in his career
01:17:22 - Top career regret
01:19:21 - Advice for younger self
01:20:57 - Outro
𝗪𝗵𝗲𝗿𝗲 𝘁𝗼 𝗳𝗶𝗻𝗱 𝗕𝗿𝘆𝗮𝗻:
• LinkedIn - https://www.linkedin.com/in/bryan-cantrill-b6a1/
• Twitter/X - https://x.com/bcantrill
• Personal Website - https://bcantrill.dtrace.org/
• His company - https://oxide.computer/
𝗪𝗵𝗲𝗿𝗲 𝘁𝗼 𝗳𝗶𝗻𝗱 𝗥𝘆𝗮𝗻:
• Newsletter: https://www.developing.dev/
• X/Twitter: https://x.com/ryanlpeterman
• LinkedIn: https://www.linkedin.com/in/ryanlpeterman/
• Threads: https://www.threads.com/@ryanlpeterman
• Instagram: https://www.instagram.com/ryanlpeterman
• TikTok: https://www.tiktok.com/@ryanlpeterman




