Ben Leonard

It was very much this body of senior engineers, air quotes around that, but folks who had been doing this for a while and felt like they were the parole board of what could be and what could not be. It was.

It was very much this body of senior engineers, air quotes around that, but folks who had been doing this for a while and felt like they were the parole board of what could be and what could not be. It was.

Oh, and there's, there's a lot of that too, where it was like, I don't know, you would kind of work, work these folks a little bit beforehand, you know, the politics of it was, was onerous.

Oh, and there's, there's a lot of that too, where it was like, I don't know, you would kind of work, work these folks a little bit beforehand, you know, the politics of it was, was onerous.

Or even better, even if you've already decided, whether you're equivocating or not, it's something that doesn't matter, but is a delightful shed for them to discuss the color of.

Or even better, even if you've already decided, whether you're equivocating or not, it's something that doesn't matter, but is a delightful shed for them to discuss the color of.

It was literally a single text file under RCS control. RCS control, sir.

It was literally a single text file under RCS control. RCS control, sir.

And every bug had to be summarized on a single line of text, ideally within 80 columns. Yes. Anyway.

And every bug had to be summarized on a single line of text, ideally within 80 columns. Yes. Anyway.

So spot on. In particular, just encouraging people to get over the hump of not letting the perfect be the enemy of the good. Just write the thing down. Doesn't need to be perfect. Better written, better sent. Let other people work on it. Love that sentiment.

So spot on. In particular, just encouraging people to get over the hump of not letting the perfect be the enemy of the good. Just write the thing down. Doesn't need to be perfect. Better written, better sent. Let other people work on it. Love that sentiment.

You'd be like, yeah.

You'd be like, yeah.

We were using, at Delphix, we had a sort of similar system. I mean, born of some similar problems. When I joined Delphix, the problem I saw was that like everyone in engineering was very clear on what they thought we should do. And everyone's idea was different and everyone felt ignored, but ignored without having really raised the issue.

We were using, at Delphix, we had a sort of similar system. I mean, born of some similar problems. When I joined Delphix, the problem I saw was that like everyone in engineering was very clear on what they thought we should do. And everyone's idea was different and everyone felt ignored, but ignored without having really raised the issue.

So we started a process fairly similar to, to let people express those ideas, express, you know, why they thought we should do them, that kind of stuff. And yeah, kind of have their day in court as part of a group discussion.

So we started a process fairly similar to, to let people express those ideas, express, you know, why they thought we should do them, that kind of stuff. And yeah, kind of have their day in court as part of a group discussion.

So it was somewhere between what you're describing at Joyent and a little bit of the PSAR case without some of the rigmarole and like council of elders, but more focused on product discussions. But yeah, what we did was mostly in Google Docs, which I think has some downsides in particular what you're alluding to about like,

So it was somewhere between what you're describing at Joyent and a little bit of the PSAR case without some of the rigmarole and like council of elders, but more focused on product discussions. But yeah, what we did was mostly in Google Docs, which I think has some downsides in particular what you're alluding to about like,