HNHacker News
TopNewBestAskShowJobs

bcantrill

13,259 karma · joined August 15, 2010

http://dtrace.org/blogs/bmc
submissionscomments
bcantrill··on Our $445M Series D
If it's of any solace, the feeling is almost assuredly mutual: your hypothetical candidate materials at Oxide would likely reveal that you are more interested in picking fights than solving problems. So you would likely not be welcomed at Oxide simply because you wouldn't make the cut -- quite aside from whatever social grievances you may foster.
bcantrill··on Our $445M Series D
Yes, it is normal, especially at the salary that we pay (currently $275K). To take but one domain: at that salary, you are (roughly) at the level of a school superintendent for a school district with thousands of students (like, large town/small city). If you have ever been associated with hiring someone in that kind of position, you will see a VERY time intensive process, with many hours of interviews with many stakeholders. So yes, we have an intensive process -- but we take hiring very seriously, and we believe that it shows in our extraordinary team.
bcantrill··on Our $445M Series D
Thanks! And don't worry -- there were PLENTY of reasons for skepticism in 2019! We got lucky many times over, hitting on stuff that turned out to be really important in ways that we couldn't know at the time.

The hiring process is a very concrete example of that. What still blows my mind (at least a little) is that our process came directly out of one of the worst moments in my career: making an absolutely terrible hire about two years before we started Oxide. For a while after that, I wished I could go back and warn my previous self to not make the hire that would be so destructive to the organization -- but in the years at Oxide I have come to realize that that terrible hire was in fact essential for the future Oxide: it was the impetus for putting together a writing-intensive process, and there is no doubt in my mind that I had I not made this atrocious hire, I would have continued to hire the (broken) way that I had been hiring. (I described this a bit in my conversation with Gergely Orosz on hiring.[0])

Anyway: don't get me near the time machine -- I'll only screw things up.

[0] https://oxide-and-friends.transistor.fm/episodes/hiring-proc...

bcantrill··on Our $445M Series D
Well, bullshit actually. When I went to Sun in 1996, I was flown out for a full day of interviews (9 hours!) plus both lunch and dinner. (And this was true for more or less every company I interviewed with.)

I'm not sure why people are indexing so hard on the interviews, as we matriculate very few candidates into conversations; if you want to complain about something, complain about the written nature of our hiring process.[0]

[0] https://rfd.shared.oxide.computer/rfd/0003

bcantrill··on Our $445M Series D
Well, in this case it was actually literally paying our taxes. (In the photo, Steve is about to initiate a wire to the IRS.) At our size, it's not a check -- and certainly not a credit card.

As to why we're paying taxes: while tax minimization is certainly a thing (and we have taken advantage of things like R&D tax credits), we're paying taxes because we're profitable.

bcantrill··on Fool's Expertise
You're snidely dismissing the obstacles as being restricted to _today_, projecting into an arbitrary future to the point of being science fiction, and then complaining about "smug hand-waving"?
bcantrill··on What Sun got wrong
I have long since accepted that this one is going to follow me to the grave, and I have (repeatedly?) expressed remorse over it,[0] but if you want to hear a longer discussion about this, Ryan Peterman asked me about this very directly on his podcast and we had a good conversation about it.[1]

[0] https://news.ycombinator.com/item?id=9041086

[1] https://www.youtube.com/watch?v=qhSL-5GtmQM#t=1h02m37s

bcantrill··on What Sun got wrong
Well, definitely read Jason's blog entry that I linked to[0], which gets into the structural problems. To be clear, there were some extraordinary sales folks at Sun (as was said to me when I first came to Sun: "Remember that our sales folks are so good that they sold Solaris 2.3 on Viking!"), and I always personally got along very well with them. I was happy to be put in front of customers, and they were happy to use me -- and some of my fondest memories were with sales folks in some of the geographies which were particularly strong (shout out to Sun Canada, Sun Australia, and to the Wall Street and Itasca offices in the US).

So this isn't about the people at all (they will express the same frustration!) but about leadership that wasn't interested in running a business. I do want to stop short of overly personalizing it, but the simple truth is: Scott visited customers where they lived -- and Jonathan more or less didn't.

[0] https://fullhoffman.com/2006/03/20/the-sun-doesnt-shine-on-m...

bcantrill··on What Sun got wrong
Heh, yeah, we're hearing that a lot. We'll find a way of getting these out to people, but we're still debating the best way to do that (running an online store isn't zero work -- but it's also not an unsolved problem!). Stay tuned!
bcantrill··on What Sun got wrong
Oof, the killing and subsequent unkilling of Solaris x86 in 2002 brings back very bad memories -- Sun management at its worst. It also highlighted the relative power of Sun's engineering in that everyone in Solaris knew it was the wrong decision, and we more or less disobeyed orders: during that period (January 2002 to August 2002, when it was reversed), we didn't change our treatment of x86. (And in particular, breaking x86 was grounds for a putback to be backed out.)

When Solaris x86 was unkilled (and then became increasingly important as x86 eclipsed SPARC), there was damage done that I don't think we ever fully repaired.

bcantrill··on What Sun got wrong
I actually haven't read a ton of these, so would love to be pointed to what you have found. But yes, everyone will be biased, and I am too. I think that the organization that I was in fucked up plenty (when I joined the company in 1996, SunSoft was led by truly one of the most incompetent executives I have ever encountered, a bumbling oaf that Sun kept putting in charge of different business units, letting him asphyxiate them one by one), but the fact that everyone also sees something else wrong probably tells you a few things: everyone at Sun earnestly wanted the company to succeed; Sun did a bunch of stuff right; Sun did a bunch of other stuff wrong.

Ultimately, the leadership of the company needs to bear the responsibility for the outcome -- and I think it's pretty telling that Sun's executive leadership basically went on to do more or less nothing after Sun. I loved Sun -- but it was a breeding ground for engineers, not executive leadership.

bcantrill··on The contagion of fear
Saying that we don't need to fear human extinction in the next ten years (or even the next hundred?) does not feel like an extraordinary claim?
bcantrill··on Your intellectual fly is open (2025)
I mean, fine, it's anecdotal -- but the numbers are also overwhelming (and don't seem to disagree with the tenor here).

And look: you're obviously free to ignore me because you feel that the survey data is "completely worthless" and just slop your way to success -- all I'm doing is trying to explain why you shouldn't expect me (and people like me) to read what you create.

bcantrill··on Your intellectual fly is open (2025)
And in that piece, I think I explained why it's important to take it seriously even though (and in fact, because!) it's self-reported?
bcantrill··on The revolt of the reader
Interesting! Amusingly, if I feed that detector this blog post, it identifies it as confidently robot (97 out of 100 test passages). And running through my last five blog entries, they are all over the map, with three deemed at least "likely robot." Looking further back in time (and taking a somewhat random example), a blog entry from 2008, "Concurrency's Shysters"[0], is also deemed as similarly confidently robot (also 97 out of 100); do you expect this high a false positive rate?

[0] https://bcantrill.dtrace.org/2008/11/03/concurrencys-shyster...

bcantrill··on The revolt of the reader
My experience is using Pangram quite often with lots of writing of all flavors (including a bunch of known origin).

As for my own writing, I didn't do this experiment, but one of my co-workers did -- and over 176 posts spanning 22 years, all 176 (well, 177 now with my latest) are 100% human. This is not hugely surprising in that (in addition to me having actually written them!) my voice is very... distinctive. What would be more entertaining would be to try to get an LLM to write like me and fool Pangram that way. I still think that this would be difficult based on the experiences that I've heard, but it wouldn't surprise me if you could pull it off (and I would assuredly find the result entertaining!).

In the dimensions that we use Pangram in the most actionable sense (namely, to audit our own public writing), I am unconcerned about false positives, and leave it to Oxide authors to rework/recast as needed. (Though it sounds like Freddie didn't even need to do that -- he just needed to provide a longer sample.)

bcantrill··on The revolt of the reader
Well, give it a shot -- you'll likely find that that technique doesn't work nearly as well (at least with Pangram 4) as you think it might. When we had Max on the podcast[0], Adam explicitly asked him about exactly this (after all, you can give an LLM access to Pangram and let it iterate!), and Max reported that someone had attempted to do this -- and ended up burning through $700 in tokens and had a "sad Claude." Another interesting bit: according to Max, newer models are diverging more from human writing not less. I think that that was more anecdotal than quantified, but an interesting comment nonetheless.

[0] https://oxide-and-friends.transistor.fm/episodes/ai-detectio...

bcantrill··on The revolt of the reader
Right?! When I hit "That work was genuinely valuable" I literally hollered in exasperation.
bcantrill··on The revolt of the reader
Yeah, fair -- and definitely not: I am earnestly just a fan of what they built (and I also think it's really important as a way of getting a check against rampant LLM use).
bcantrill··on The revolt of the reader
This is (obviously?) false, but considering how well-capitalized we are at the moment, you do have me wondering what a quid pro quo would be for; perhaps in this fictional universe Pangram has lucked into some of the PCIe clock buffers that we've been scrambling to secure enough of?
bcantrill··on The revolt of the reader
That is honestly the highest possible praise -- thank you. And when this piece was starting to boil inside of me last night (triggered, I'm sorry to report, by an obviously LLM-authored guest blog entry from the Rust Foundation[0]), I messaged one of my colleagues: "Time to do what I do best: bluntly say what lots of people are thinking."

Glad those words proved prophetic!

[0] https://rustfoundation.org/media/how-the-rust-standard-libra...

bcantrill··on Being ambitious and being a dad
Wow, thanks for that shout out! When we started Oxide in 2019[0], my kids were 15, 12, and 7, so out of those time-consuming younger years. But when we started Fishworks[1] inside of Sun in 2006, that 15-year-old (now nearly 22) was not yet 3 -- and his brother and sister were still in the future. Point being: I worked plenty hard with young kids.

More generally, I have always believed that the choice between work and parenting is broadly a false dichotomy (especially in our domain and age, which affords quite a bit of flexibility). In my role as a parent, I served on the board of the kids preschool (hello, SOMACC!); I was the president of the elementary school PTA (originally called the Mothers' Club!); I led the kids' Cub Scout Den (hardest parenting job no question); I coached baseball several times over; and I have been (and still am!) the scoutmaster of the kids' Scout troop.

These experiences were all time consuming (and truthfully, there were moments with each of them when I wondered what I had signed up for!) -- but they also made my life richer, and that very much includes my professional life. There are many dimensions of this, but to take one very concrete example: anyone who is familiar with scouting will see an echo in Oxide's values[2] -- but a subtler influence can be found in our hiring materials[3], the open-ended questions of which coming from an adult training that I did in 2017.

I won't profess to the quality of my parenting (it's... really hard), but it's something that I've certainly spent a lot of time on -- and it has paid surprising dividends to my professional life.

[0] https://bcantrill.dtrace.org/2019/12/02/the-soul-of-a-new-co...

[1] https://bcantrill.dtrace.org/2008/11/10/fishworks-now-it-can...

[2] https://rfd.shared.oxide.computer/rfd/0002

[3] https://rfd.shared.oxide.computer/rfd/0003

bcantrill··on Kubernetes on Oxide: How customer needs shaped our integrations
"Light on details" is not often a criticism that we get, but I think you might be looking in the wrong place: for the kind of detail that you're looking for, you should be heading into our RFDs -- specifically (for the issue you seem to be most interested in), RFD 26.[0][1]

[0] https://rfd.shared.oxide.computer/rfd/0026

[1] https://news.ycombinator.com/item?id=41515447

bcantrill··on Kubernetes on Oxide: How customer needs shaped our integrations
(I think you meant "like hotcakes", not "like cupcakes"?)

In any event: from the beginning, we have always been targeted at the enterprise buyer who is looking at annual public cloud bills in the tens, hundreds or (in some cases) thousands of millions of dollars per year. We love the enthusiasm that Oxide engenders among the home lab set, but that's not how we have geared the business (for lots of good reasons).

Also, for whatever it's worth: people do want to buy them, it turns out.

bcantrill··on Kubernetes on Oxide: How customer needs shaped our integrations
Are you referring to our RFD system?[0][1] Because if so, good news![2]

[0] https://rfd.shared.oxide.computer/rfd/0001

[1] https://oxide-and-friends.transistor.fm/episodes/rfds-the-ba...

[2] https://github.com/oxidecomputer/rfd-site

bcantrill··on Oxide Computer raises $445M (SEC Form D)
Ironically, not only are you entirely wrong on the facts themselves, but the historical record in this case is incredibly (and unusually) crisp: the Merger Proxy Statement that Sun had to file with the SEC[0] has, in accordance with Delaware law, the full narrative of the acquisition.

In the "Background of the Merger" section of that document, there is an incredibly detailed (and interesting!) story of three companies: Party A, Party B, and Oracle. (As was well-known at the time, Party A is IBM and Party B is HP.) As that narrative makes clear (and contrary to your assertion), it was Sun that rejected IBM's definitive agreement, not the other way around. You can certainly argue that IBM's acquisition of Sun would have failed to complete for other reasons (regulatory and so on) -- but your assertion that "IBM did an offer that was shortly thereafter withdrawn" is simply (and demonstrably) wrong.

[0] https://www.sec.gov/Archives/edgar/data/709519/0001193125091...

bcantrill··on Oxide Computer raises $445M (SEC Form D)
This all became pretty personal over here!

To answer these questions (or accusations?): Yes, I was at Joyent for the acquisition by Samsung -- but I also was not a founder, did not have a board seat, etc., so the involvement that I had, while substantial at some level (working with the Samsung team when they were doing their significant due diligence, for example) was also ultimately limited. My job was to make the acquisition work, not to determine the fate of the company for which I was ultimately an employee.

It's also absurd to call the sale a "sellout" -- the company was not for sale when Samsung came calling. The deal that Samsung proposed was a good and fair one, and if I HAD been on the board, I would have absolutely voted for the acquisition. (It should be said that Samsung themselves had a very high threshold to close the deal -- 97% of shares IIRC?)

And all of THAT said: while I was supportive of the acquisition by Samsung of Joyent (and worked hard to make that acquisition work), when we started Oxide, Steve and I had (and have!) zero interest in building a company to be acquired. Oxide is our life's work (and I mean that "our" broadly, as many at Oxide feel that same calling), and our objective with Oxide is to build an independent, generational company. Indeed, this Series D is all about advancing that objective!

bcantrill··on Oxide computer 3D rack guided tour
Clearly, you find Oxide's approach very upsetting; in the words of Laurie Bream, "look inward."
bcantrill··on Oxide computer 3D rack guided tour
Thank you for rooting for us! One important point of clarification: I am the CTO -- the CEO of Oxide is my co-founder, Steve Tuck. Long before we know what we wanted to do (or had a name for the company!), Steve and I knew we wanted to do something together; it's worth getting to know Steve (and our collaboration) in his own words![0][1]

[0] https://www.youtube.com/watch?v=eVkIKm9pkPY

[1] https://www.youtube.com/watch?v=d_XqNYt0cY0

bcantrill··on Oxide computer 3D rack guided tour
I appreciate that our approach to compensation leaves some with overwhelming feelings of whataboutery, but no, we (of course?) do not have equal equity: as we have said (several times?) equity broadly compensates for risk -- and risk has gone down over time. (I used to tell people to "value the equity at zero"; I don't say that any longer because it plainly isn't.)

In terms of the cap table: that's a bit of an odd request? On the one hand, there are no real secrets hanging out on our cap table -- but on the other, based on your tone, it doesn't feel like the request is terrible earnest? (And, I hasten to add, transparency is a value -- not a principle.[0])

[0] https://rfd.shared.oxide.computer/rfd/0002

Page 1 of 32Next →