Ben Leonard

the lack of searchability and there we like layered additional indexing on top of it and like a meta document to keep track of everything. But then some benefits too, like it's much easier to have multiple authors simultaneously. Yes.

the lack of searchability and there we like layered additional indexing on top of it and like a meta document to keep track of everything. But then some benefits too, like it's much easier to have multiple authors simultaneously. Yes.

But I think it's fair to say that we're weird for our obsession with ASCII doc. Is that right? I think so.

But I think it's fair to say that we're weird for our obsession with ASCII doc. Is that right? I think so.

Yeah.

Yeah.

I haven't looked at the numbers for like years, but even then it was overwhelming.

I haven't looked at the numbers for like years, but even then it was overwhelming.

That is amazing and profoundly unsurprising.

That is amazing and profoundly unsurprising.

Well, on that, some of that was learned from what we had done at Delphix, which was that you weren't, you were, maybe you weren't allowed, but you were certainly highly encouraged to have a co-author. Like we kind of didn't want solo authors and things. And part of the reason for that was we thought it made for stronger documents.

Well, on that, some of that was learned from what we had done at Delphix, which was that you weren't, you were, maybe you weren't allowed, but you were certainly highly encouraged to have a co-author. Like we kind of didn't want solo authors and things. And part of the reason for that was we thought it made for stronger documents.

We thought that even if it was somebody's deep held idea, having a co-author to walk them through it and convince them of it and get them on board would strengthen the quality of the document. I'm sure many of my collaborators on those RFDs would also hasten to point out that I like to do a half-assed job and then leave the rest to them. But I prefer to think of it as cross-pollination as well.

We thought that even if it was somebody's deep held idea, having a co-author to walk them through it and convince them of it and get them on board would strengthen the quality of the document. I'm sure many of my collaborators on those RFDs would also hasten to point out that I like to do a half-assed job and then leave the rest to them. But I prefer to think of it as cross-pollination as well.

So I would also say, folks who are wondering, when someone joins Oxide, then what? Do you just spend the first three years reading? Good question. I think, and Brian, you probably have the data on this, I feel like we're on escape velocity. I feel like it is impossible for me to read every RFD that is being produced, even if I dedicated...

So I would also say, folks who are wondering, when someone joins Oxide, then what? Do you just spend the first three years reading? Good question. I think, and Brian, you probably have the data on this, I feel like we're on escape velocity. I feel like it is impossible for me to read every RFD that is being produced, even if I dedicated...

Well, for Woodsworth, I had not heard of ASCII doc before joining Oxide. So I had to become a convert in a hurry.

Well, for Woodsworth, I had not heard of ASCII doc before joining Oxide. So I had to become a convert in a hurry.

I feel on Google docs. One of the, I mean, huge downsides is like, you can have a great discussion in a comment or whatever. And someone closes that comment and it's like gone forever. And I think one of the benefits of, of the GitHub history is like, it's not gone forever. It's all there. Just hard to find.

I feel on Google docs. One of the, I mean, huge downsides is like, you can have a great discussion in a comment or whatever. And someone closes that comment and it's like gone forever. And I think one of the benefits of, of the GitHub history is like, it's not gone forever. It's all there. Just hard to find.