1. Library
  2. Podcasts
  3. To Be Continuous
  4. Ep. #12, Payment Strategies for Developers
To Be Continuous
32 MIN

Ep. #12, Payment Strategies for Developers

light mode
about the episode

In this episode Edith and Paul talk about the clash in OSS between developers looking to get paid and software companies looking for things for free.

For more on Continuous Delivery you can follow To Be Continuous on Twitter at @continuouscast.

Writing Open Source to Scratch an Itch
Free Software and Risk
Contributors and Volunteers
Jerks on the Internet
Busy People and Instant Replies
Funding Open Source
Heartbleed and the Tragedy of the Commons

transcript

Paul Biggar: I clearly have mixed feelings about this whole thing.

Edith Harbaugh: Paul, I hate to say this, but I agree with you.

Paul: So I don't mean to come across as a curmudgeon for all of mankind.

Edith: Too late.

HipChat and Slack are kind of like, it treats you like a genie in a bottle. I don't want to come to the bottle right now.

If it's 90% done and you don't publish it, it's actually 0% done.

Paul: It's 0% done, yeah.

Hi, I'm Paul Biggar, founder of CircleCI.

Edith: I'm Edith Harbaugh, CEO and co-founder at LaunchDarkly.

Paul: And you're listening to To Be Continuous, a podcast about continuous delivery and software development.

Edith: You can get in touch with us anytime at our Twitter handle, @continuouscast.

Paul: The show is brought to you by Heavybit. To learn more, visit heavybit.com. And while you're there, check out their library, home to great educational talks from other developer company founders and industry leaders.

In today's To Be Continuous, we're talking about the clash in open source between developers looking to get paid and software companies looking for things for free.

Writing Open Source to Scratch an Itch

Edith: So Paul, what do you like about open source?

Paul: So I guess that depends on whether we're talking about writing open source or using open source as part of a company. Writing open source, I like just having all my code out there, and I'll do that as often as possible. Anytime I start a little bit of code, a little library, I'm looking to open source it and have a readme and have it out there for other people to use.

I had a very long discussion, which I eventually won, at the...

Edith: I like the way you think of all discussions as won or lost.

Paul: Well, yeah, yeah. It was more on the argumentative side of discussion, but with the other co-authors of the PHP compiler I wrote, which was originally GPL. And I argued very strongly that I actually don't care if people give back. I just want people using my software. So to me, open source is a way of having people using my software.

Edith: So that's really interesting. So I liked what you said about beginning, about, like, you liked open source because it meant getting stuff out sooner. Because I'm a big fan of that.

Like, I always say you should just publish stuff. Like, my co-founder John said something really good at our team meeting last week.

He's like, if it's ninety percent done and you don't publish it, it's actually zero percent done.

Paul: It's zero percent done, yeah.

Edith: Yeah. And that's like a hard lesson, because you always strive for perfection, but if you don't show it to anybody...

Paul: Well, I think there's also some really hard downsides about that. So when you publish something before it's ready, before you...

Edith: Well, ready.

Paul: Oh, but so ready, ready, but let's say ready is, let's say you publish it before you clarify what the software is to do, or the values or the mission of the software. And then you get contributors who are saying, "Oh, this is great, but I really wanted to do this other thing." And you're like, "Oh, that's not exactly what I was going for here."

Edith: I'd say most open source projects are so lucky as to get contributors at all.

Paul: True, true, true. So I'll give you an example. I wrote the V8 bindings for Clojure. So a binding that allows you to write JavaScript and run it in Clojure. And I did that for a purely selfish thing, for an asset pipeline that I was building called Stefon.

And then people came along and they wanted to do other things with it. They're like, "Okay, let's add a binding for this other thing."

Edith: That's kind of like a pivot.

Paul: It is, it is, but I really wasn't that interested in it. I'd rather someone took it over, took over the project and actually ran with it where they want to go, and I can stick on the old version or I can see if the new version solves it for me, but I wasn't interested in becoming a maintainer in this thing.

I was interested in solving my itch. And I just happened to open source it because I felt it might be useful for other people.

Edith: And it was. So Paul, I hate to say this, but I agree with you.

Paul: No, not again.

Edith: Not again. No, I mean, I think what you said is exactly right, that you said, I did this for this reason and I want somebody else to take it over now. I think where open source runs into issues where people are like, it's only this purpose and you can't do anything with it besides my original thing.

Free Software and Risk

Paul: So you think that's a good thing, or you think that's a problem? Or it causes problems in the community?

Edith: I think open source is so misused for so many different purposes that it's hard to even say. Like, so in Europe, people say open source is good because it means free software.

Paul: Libre or gratuit?

Edith: I'm sorry?

Paul: Free as in beer or free as in, what's the other side of that?

Edith: There's no such thing as a free lunch. Is that what you're talking about?

Paul: No, no, no. Like, people say open source software. It's like free as in beer software, as in software that has no cost versus software that has no price tag versus software that is, they use the French word libre for it.

Edith: Oh yeah. That's what I was talking about. So I remember I went to Europe in, I think it was 2004, 2005, and they just had this big push for open source because they thought it meant free.

Paul: Oh, this is like the German government and that sort of thing.

Edith: Yeah, so literally, like, so I went to this customer and they're like, it doesn't cost you any more to give us an extra copy. So why shouldn't just everything be free?

Paul: Oh, right, yeah. Well.

Edith: And so I think open source has been misused by many businesses who think of it as just like, hey, we get all these developers working for free.

Paul: So I think that the main advantage to a business of open source is not that it's free, but it's that it's low risk.

Edith: Low risk?

Paul: Lower risk. So what I mean is that it removes a certain element of risk from it. So there's, Joel Spolsky wrote a blog post about how you shouldn't use, I think it was a database that you didn't have the source code to.

Edith: Well, so I'll argue the reverse. And I think open source is sometimes more risky. Because I talk to people now who are like, nobody's maintaining this open source project that I depend on.

Paul: Right, right, right. But versus a closed source version.

Edith: Well, so the opposite risk is that you end up that you are responsible for this open source project, and you're like, well, actually, I just wanted to use this thing. I didn't want to be the maintainer.

Paul: Absolutely, you don't want to end up the only person that, well, it's actually fine to end up the only person which is using this thing.

Edith: Well, no, that's not...

Paul: It's not ideal.

Edith: Many people are using it, but nobody is paying money, and then you're stuck.

Paul: Because no one is maintaining it.

Edith: No one is maintaining it, you depend on it.

Paul: Right. So but imagine that no one maintained it and all that you could get was like a binary blob. That's the real problem.

The company goes out of business. You have random database version seven, the binary, that only runs on 32-bit, that you're maintaining, like, companies are literally maintaining COBOL, Fortran things from 30 years ago. It sits in a machine, you can't touch it, you can't fix it, you can't apply security updates to it.

Edith: Yeah, that's fair. So Tim Chou, he's an awesome guy, he was early at Oracle. He said that people don't buy, when they buy software, they're not buying it what it is today. Because basically anything that you're buying today, you could just hire 20 engineers, they could build it.

Yeah, what they're buying is a promise of stability, that it will continue to be maintained. That there is a vision. And that's actually, I went over to a big customer who won't let us use their name yet, but they said they love LaunchDarkly because we thought every day about feature flags.

Paul: Right, right, exactly. I mean, this is why people buy SaaS, because people think all day about CI, about QA as a service, about queues, or whatever it is, from various Heavybit companies that I just shilled for there. You can probably figure out yourself which ones they are by looking at the homepage.

Edith: Paul, by the way, thank you very much for wearing your LaunchDarkly t-shirt today. It looks very handsome.

Paul: I definitely agree that the benefit of the thing is that you use it every day. But you can do that with open source as well. You can have open source software that, so for example, our front end is open sourced.

Edith: Oh, I'm absolutely a fan of open source. Like, we use open source every day. Our client libraries are open source.

I'm not saying that it's, I don't think it's a religious thing, versus open source or not. I just think that many times people assume open source is something that's not.

Paul: Yeah, fair enough. Fair enough.

Edith: I mean, that if you have open source, that it just means that developers spring out of the ground willing and happy to update your software every day.

Paul: A mixed blessing, definitely. If it even happens.

Edith: Like, I remember, so I remember when Sun, so I used to be at Epicentric and we had a portal server, and we were killing Sun. Absolutely killing Sun. And this was in 2003. So what they said is, "Oh, we're gonna make our portal server open source."

And so Sun had this whole thing where, like, everything will be open source, and, like, developers will spring into the ground. It's like, well, no, developers do not wake up every day like, "I'm gonna work on your thing."

Paul: Right, right. They will if it's sexy or exciting. There's lots of developers who are showing up at Mozilla just to contribute. And in fact, they fought through incredibly large hurdles to contribute to Mozilla software.

Edith: Well, that's fascinating, because I see so often the reverse. So what do you think about Mozilla made people want to contribute?

Paul: Well, I think the fact that it was an open source first company and that was a nonprofit, and it was all about the free and the open web and that sort of thing. Also, people had had very good experiences with Firefox for, like, a decade at this point, about the time I was there. Well, maybe seven years, but yeah.

Contributors and Volunteers

Edith: It's fascinating, because I went to a dinner last night with the CEO of MySQL. And I don't know if I should say this, but he said...

Paul: This is Marten Mickos?

Edith: Yep. So he gave a talk.

Paul: He has a new startup?

Edith: Called HackerOne.

Paul: Oh, he joined HackerOne.

Edith: Yeah, he's the new CEO. So the dinner was kind of like a debutante ball for him.

Paul: Nice, nice.

Edith: So what he said was that somebody asked him flat out how much of MySQL was actually from contributors. He said 1%.

Paul: Seems about right.

Edith: He said the open source is more just like a branding thing. So, like, it wasn't actually like a productivity thing, it was more just a branding thing.

Paul: So you have this in Mozilla as well, that anytime that there was a really avid contributor, that Mozilla would hire them.

Edith: Yeah, that's what he says.

Paul: And if Mozilla didn't hire them, very often they stopped being a contributor. Like, it was a real sort of a double-edged sword.

So someone who did it for six months, they were doing it for the love of the game. They weren't doing it to be hired at, at least I think for the most part, they weren't doing it to be hired at Mozilla. And then, you know, six months in, someone's like, "Well, you know, you're doing a really great job." "Wouldn't you love to work on this full time?" They're like, "Yeah, that's so exciting." They're flown out for an interview. And then it's like, "Yeah, actually, I don't think so."

Edith: Wait, they didn't want to work for Mozilla, or Mozilla didn't want to hire them?

Paul: Mozilla didn't want to hire them. I mean, this isn't a particular case, but, you know, some subset of people Mozilla didn't want to hire. And then what happens? Well, you kinda don't want to keep contributing to the company that just told you to fuck off.

Edith: Yeah, I mean, it's so true. I mean, I think there's a very human thing about volunteering.

I volunteer, I was the moderator for a long time for the Lean Startup Circle. And somebody new came on and they're like, "Yeah, I'd love to raise some money so that we can get paid." I'm like, they cannot afford to pay me. Like, I don't do this to get paid, because

Paul: It's an altruism that people are trying to do.

Edith: Yeah, I was contributing like 10 to 15 hours a week, and I'm like, my going rate, it's not... Yeah, I'm like, I'm not doing this to get paid, I'm doing it because I like giving back.

Paul: So there's this thing that we were talking about earlier, about the current discussion around people getting paid in open source.

Edith: Yeah. And I think a lot of what has fueled open source is the whole twenty percent time. Like, that Google will give their engineers twenty percent for open source. And I know that other big companies like Twitter and so on do that too. So these people are, in its essence, getting paid.

Paul: Right, right. In most companies, most startups at least, there's an unspoken rule that you're expected to contribute to the libraries that are in your application and that sort of thing.

If you're spending time upstreaming a patch that you've deployed, that's work.

Edith: Yep. So I think we're agreeing, which, I thought we agreed that we were not gonna agree.

Paul: No, that's it.

Edith: It's funny, because I'm Twitter friends with a guy I've never met, who's, he started Django, and right now what he tweets a lot about is...

Paul: This is Jacob Kaplan-Moss?

Edith: Yeah.

Paul: Okay.

Edith: That people are working their nights and weekends and contributing to open source, and then just people are kind of, for lack of a better word, jerks. Like, people are...

Paul: People are jerks.

Edith: Yeah, like...

Paul: Even when you're paid, people are jerks.

Edith: But it's more aggravating.

Paul: Right, right. Because you're doing it for free or whatever.

Edith: Yeah, for free. And so people, like, you know, they like, "I have this pull request and it's been open for two hours. Why haven't you reviewed it?"

Paul: I mean, we get the exact same thing. We get customers who email us, or more often it's the people who are using the free version, who send us a support request and then 30 minutes later they're on Twitter going, "I can't believe Circle hasn't solved my problem yet. It's been thirty minutes."

Edith: What do you think drives that?

Jerks on the Internet

Paul: There's a pattern across just the population in general that people are dicks. Like, humankind is not really the greatest people in the...

Edith: So Paul, I think people are the kindest people on the planet.

Paul: There are lots of people out there, and many, many of them are dicks. If you have a bell curve of the people, all of the people who are in the dick category are on the internet. And they are the ones who are going to Twitter to tell you what an awful person you are for not having responded to their thing in two hours. Or half an hour. Whatever it is.

Edith: But on the other hand, I'd say, like, I mean, I think most people are honestly very helpful.

Paul: So I don't mean to come across as a curmudgeon for all of mankind.

Edith: Too late.

Paul: It's more of a statistical argument. There are a lot of people out there who get off on the idea of, you know, Twitter outrage or whatever.

Edith: Well, that goes back to the whole, the founder of Linux, where he's like, "I'm a jerk because I have to be a jerk."

Paul: I think one of the major problems that afflicts our industry is people who believe that the open source development model is the right way for people to develop software.

Edith: I think it's also something a little bit larger, which is that people see people who are jerks who are successful.

Paul: So people look at a successful open source project and they think that this is a thing to be emulated. And so for example, Linus Torvalds is just an unmitigated asshole. And I've never met the guy, so I'm basing this on the internet, but, like, I don't think he would disagree with me.

Edith: Well, it's funny, 'cause my mom was recognized at the same banquet as him, because they both contribute a lot to IEEE, and I was like, "That's kind of a mixed blessing, Mom."

Paul: Yeah, yeah, yeah. So other people look at him being an asshole and they say, "Well, you know, I want to be an asshole."

Edith: Well, no, I've seen this, you confuse correlation versus causation. You're like, is he successful because he's an asshole, or is he an asshole because he's successful?

Paul: There's also a lot of people who contribute to open source are younger, don't have, you know, life responsibilities just yet. So they have lots of time to give.

And I think that there's a tendency, and I recognize this in my younger self as well, to be an asshole on the internet when, you know, you just kinda haven't learned to treat people well. That's an affliction of people in their teens and early to mid twenties.

Edith: Well, but Paul, you're always spectacularly polite.

Paul: Right. But you're meeting Paul of thirty-four, not Paul of twenty-four.

Edith: Well, I knew you when you were thirty-three.

Paul: But Paul of twenty-four, I think, would have written, like, long rants about how right he was and how that was really important, that I was right and that everyone recognized that I'd be right.

Edith: Well, let's loop back to the beginning, where you said, like, you'd won an argument. I don't ever think you really win an argument. Like, all you really do is...

Paul: True, true. Yeah. I actually agree with that. I'm kind of being a little bit facetious on this, for the sake of dramatic storytelling.

Edith: No, I think it is true. I mean, I look back at how I was when I was twenty-two, and I was a bomb thrower. I don't know if I would have liked myself.

Paul: Right. So this is the problem. This is one of the many problems. A lot of the people, they see a good example in Linus, who clearly never grew out of his twenty-two-year-old self. And they are themselves, you know, twenty-two and full of, what's the word, full of...

Edith: Vim and vinegar?

Paul: Yeah, there we go, spit and vinegar. One of those things. And, you know, they have a chip on their shoulder, and they look around at all the software and they're like, "This software is shit. I'm gonna write my own software."

Edith: I thought the Irish said it "shite."

Paul: Sometimes. Sometimes.

Edith: I feel like...

Paul: The person that I'm imagining in this story isn't Irish, so I'm putting their words in the words that they would use.

So you make a pull request and, you know, two hours later,

Edith: Nobody's responded.

Paul: What are they doing?

Edith: What are they doing?

Paul: How dare they? It's 3 a.m. Are they not up working on their software?

Edith: Oh my god, this was me. So I was moderating this email list and it was a global list. We put this policy on that if you were a first-time contributor, you had to be moderated. And people would send me the angriest emails.

Paul: About being moderated.

Edith: And they're like, "How come you haven't responded?" Like, "Dude, like, I'm in San Francisco. I was asleep."

Paul: I just go straight to archive. Or sometimes mark as spam. I feel that people feel that you have a responsibility to them because you're a person on the internet.

And I'm perfectly happy with the idea. Sometimes I'll email someone famous, or someone who gets a lot of email. I'm not expecting a reply.

Edith: Oh no.

Paul: I mean, I hope that they will reply. I try to write things in the nicest possible way so that I will get a reply, but, like, people are busy.

Busy People and Instant Replies

Edith: Oh, I was so shocked. So Dave McClure is one of our investors. And he literally has this autoresponder like, "I'm under a large rock, I never read any emails."

Paul: Right. There we go, right? He's a guy who's doing shit. He doesn't have time to respond.

Edith: But I was shocked, so I sent out our monthly investor update. And he responded, I was just like, "Oh, yeah."

Paul: I'm sure he filters it into the actual important shit versus the, you know, things people send me on the internet.

Edith: Well, no, he responded, and, like, so our engineer just had a baby, and he wrote back, he's like, "Congrats on your baby and your month over month revenue growth." I was just like, "Oh my god, Dave reads our emails."

Paul: Nice. When I was getting Dave to invest, I literally had to text him, and I texted him again, and then I called him.

Edith: And then you showed up at his door with flowers.

Paul: It was six PM on a Sunday. It was a very unreasonable time to call someone, but I had saved fifty K space for him, and I was determined that this was going to happen. And it did in the end.

Edith: Well, it was funny, because I just sent him an update kind of as a courtesy, because I assume he's not gonna read it, but he read it. He said congrats to our engineer who'd had a baby, and he's like, "Great job, love your month over month growth." I was like...

Paul: So people are busy on the internet, and people assume that they have a right to their time.

Edith: That's so true. I mean, that's kind of my pushback against stuff like HipChat and Slack. And I think there's already starting to be a little bit of a backlash.

Paul: I don't know what you're talking about.

Edith: Well, so people are like, "It's great. I can chat anybody anytime on Slack or HipChat, and they'll respond." It's like, well, great, you're responding instantly and you're not doing something else.

Paul: Oh, right, right, right, right. Yeah. Yeah, I mean, I think people should turn their notifications off. This idea of an instant reply is a terrible, terrible idea.

Edith: Why do you think it's terrible?

Paul: Just to start, like, coding is an activity that requires concentration. And the sort of ADD set of ways that you're supposed to be multitasking and that sort of thing, it just doesn't gel very well with writing software. Like, if I'm trying to actually write software, I put my phone in airplane mode, I turn off notifications, and then I write some software.

Edith: I think HipChat and Slack are kind of like, it treats you like a genie in a bottle. Like, somebody asks you and all of a sudden, like, you're supposed to, like, poof out and answer your question. It's like, well, actually, like, I don't want to come to the bottle right now. Like, I have stuff I'm doing.

Paul: Right. I will go back every couple of hours, I'll check my email, I'll check Slack, take my phone out of airplane mode, and then I'll deal with the, you know, the list of people I want to talk to. And this gets a little bit tricky when there's something that you have to keep on top of, and you only want to be notified for this, and there isn't really enough control around this sort of thing. But, you know, I think that's one of the problems of our age that will eventually get solved.

Edith: Oh, I think it's just gonna keep getting worse and worse.

Paul: Exactly. It'll keep getting worse and worse, and then eventually people will freak out and they'll fix it.

Edith: Well, I mean, like, I know Google Glass tanked and Apple Watch is in the ditch, but, like, at some point we're all gonna have, like, implantables in our eyeballs that just flash text messages all day.

Paul: There was a talk at, I think, DICE in 2010, someone gave a talk about how they're going to gamify everything. And it's like, you know, if you want to watch this TV show, you should be drinking a can of Coke and, you know, show it to the camera or whatever, and you can watch the show. But the suggestion was that this will actually be good for society.

Edith: What?

Paul: That you'll start to get things like, you know, your kid got a report card, you get some points, right? And then your points become redeemable.

Edith: For Coke?

Paul: No, for whatever. And then eventually you're...

Edith: Does everything just come back to Coke?

Paul: Well, then your points become redeemable for, like, a tax credit or something like that. Everything kinda ties together, and, you know, there becomes just points everywhere, and then, you know, it incentivizes good behavior. Probably bad behavior too.

Edith: And the good behavior is that you take a picture...

Paul: Presumably good behavior is that you yell at someone on the internet for not responding to your pull request in two hours.

Funding Open Source

Edith: Yeah, I think, so to circle back from a long detour, I think the open source is used for so many different things, including that there is this always-on population of developers who are dying to work on your product.

Paul: Right. You were talking before about the backlash about people not getting paid.

Edith: Well, I think there's two separate backlashes. One is from businesses who thought that they would get software for free.

Paul: Right. Fuck 'em. They should have known better.

Edith: And the second is from developers who are like, "Well, why am I working for free?" And I think there's so much good in open source, but I think both populations are right when they're like, "Okay, I..."

Paul: So I have, you know, in my big long list of business plans, one of them is proper open source funding. So the problem as I perceive it is that there isn't really a funding model for open source.

There's a very obvious funding model for open source, which is to ask all the companies that rely on it for money.

Like, have actual salespeople rock up to the door of Heroku and say, "Give us $100,000 a month." And then recurring revenue, I think that's the kind of key thing. People get, like, little shitty donations here and there.

Edith: The Wikipedia model.

Paul: Right, right. So I think it's like, you know, get, I don't know, one percent of revenue from companies that do open source or that use open source heavily, apply it directly to the things that affect their business or are the riskiest. And I think, you know, this OpenSSL thing is kind of a key example. But, you know, if your company is on Python, then, you know, send it to Django or whatever.

You know, say, "I want this money that I'm giving funded into this niche or this niche or this niche," or whatever the things that you use. Perhaps it could even, you know, automatically look at your Gemfile or requirements.txt or whatever and know what you actually use and all that.

So that's kind of one side of it, that people should be asking people with money for money and not just complain on the internet about it. And then the second thing that I'll say, and I'm gonna launch straight into that rather than discuss the first...

Edith: Because I'm stewing over so many comments.

Paul: Right, exactly. The second thing is that if you're paid for it, it's a job.

Edith: Yep.

Paul: Right?

Edith: Which is not a bad thing.

Paul: Well, it is and it isn't. So if you already have a job and you hobbyist this stuff on your spare time, then you're not gonna want the second job of actual, like, you think people complain when you're, you know, you wait two hours for a pull request. What happens when they gave, you know, their ten-dollar monthly donation or their hundred-dollar monthly donation, and now they feel entitled to your time, 'cause you're taking money out the other end of that?

Edith: It goes back to when I was volunteer and I'm like, "I don't want to get paid."

Paul: Right, right, exactly. Right.

Edith: If you're paying, 'cause if you pay me ten dollars an hour, yeah...

Paul: Right, exactly. So I mean, even if you got, like, you know, a proper hourly rate, let's say a good developer hourly rate,

Edith: 100 to 150.

Paul: 100 to 150, right, exactly. And if you're getting paid 100 to 150, then you're suddenly actually culpable for doing a good job. And this is your nights and weekends. You know, you can't just blow off the coding that you're planning to do to spend time with your family.

Edith: Which is important. I'd say family is far more important than code.

Paul: Coding is fun, and once you get paid, coding is a responsibility as well as fun. But, like, a job is never as fun as the thing that you're doing in your spare time. So I think I'm not saying that people shouldn't get paid for this. I'm not saying that developers shouldn't be able to quit their day jobs and focus on Django or whatever in their full time. But I'm saying that I don't think people are gonna find it that much fun.

Edith: Well, and then it gets back to what does really open source mean. And I think the word open source has been overloaded.

Paul: Go on.

Edith: Open source has been overloaded to mean free software. Open source has been overloaded to mean I contribute when I want to. Open source has been overloaded to mean, like, anybody can use it at any time.

Paul: Right. I mean, it's actually none of these things, and also all of these things.

Edith: And that's what I mean by, and I use the word overloaded very deliberately because it's an old C++ word about you overuse a word.

Paul: I completely agree. You're always gonna have a clash where people with different values and different missions are interacting in the same space. And if one person's, the value that they have in open source is that they get, you know, a free web server, and another person's thing is that they're looking to contribute in their spare time...

Edith: Or they're looking for a job.

Paul: Or they're looking for a job. I mean, there's so many things that people look for in open source.

Edith: Or, like, here's this project that nobody's buying, so I'm just gonna open source it. Which is what Jut just did. They're like, "Nobody's buying our software, so we'll open source it."

Paul: As in, like, it'll solve all our woes, or just, like, we're giving up and shutting down and you may as well have it?

Edith: Ambiguous.

Paul: When people try to solve problems, they imagine that everyone knows what the problem is. And in fact, generally, people don't share the same problem.

Edith: Well, this goes back to what you said at the beginning, about how you'd updated, you said some, was it Clojure?

Paul: Yeah, yeah, yeah, yeah.

Edith: And you'd try to solve this particular problem, then everybody's like, "Well, we want to use this for this other thing."

Paul: Right. This larger thing, this is the next step in it or whatever, and I didn't feel confident in reviewing the code, and so, like, I don't really know. Like, is this a priority? Kind of doing other stuff at the moment.

Edith: As you should.

Paul: Right. Although, I mean, it's still flagged in my inbox as a thing to do someday. So, you know, I clearly have mixed feelings about this whole thing.

So I talked before about the problem, solution, implementation framework that I use for getting people on the same page. And, you know, the pull request that comes in is always the implementation. Or, you know, the people who say, you know, open source should do this or should do this or should be this.

It's always an implementation, right, right. I want money in open source, right? And I think that there isn't necessarily a problem or a goal that everyone is agreed on, because there isn't a single set of values for what open source is or should be.

Edith: I think that's the very definition of open source, though. I mean, open source is basically that anybody can contribute any time. I think that's what's so fun and dangerous and risky. Like, any time you're depending on the work of everybody to get something done.

Heartbleed and the Tragedy of the Commons

Paul: Right. I mean, it's that OpenSSL issue, right, is a really good example of it.

Edith: Do you want to talk more about that?

Paul: Yeah, so there was a couple of giant vulnerabilities in OpenSSL. I think Heartbleed was the, you know, best publicized one.

Edith: And that was a very good branding, by the way.

Paul: It was.

Edith: And if you just said, like, "OpenSSL three dot seven vulnerability," nobody would have cared.

Paul: Exactly. So it was a big problem and it had slick marketing behind it, there was a logo. People were very angry about the fact that there was a logo before they knew about it, and so on.

Edith: Why were they angry?

Paul: Because people are angry on the internet.

Edith: Oh, is that the way it is, Paul?

Paul: I think that's how it works.

Edith: Gosh.

Paul: Yeah, this is why you should never go on Twitter.

Edith: You still haven't followed me.

Paul: Oh, I thought I... Oh yeah. I will fix that. So after Heartbleed, people realized that OpenSSL was basically not maintained. And so, you know, there was one guy working on it in his spare time, he wasn't even paid for it.

Edith: And that's the thing. And everybody's like, "Well, why did this guy work harder and prevent it?" It's like, well, he wasn't paid.

Paul: Right, right. It wasn't his job. And there was even an article about him in Wired, and they asked him, you know, "Why aren't you getting paid?" And he's like, "Well, you know, I like the code and I don't really like the fundraising aspect of this." Which goes back to what I was saying earlier, that there should be this nonprofit that raises tens, hundreds of millions of dollars.

Edith: Developers for everyone.

Paul: And so there's this problem for everyone, that OpenSSL was just fucked. And everyone used OpenSSL.

Edith: It's so the tragedy of the commons.

Paul: It is a tragedy of the commons, yeah. Like, I mean, all of open source, almost, is a tragedy of the commons.

Edith: So this poor guy who's getting paid no money and everybody's yelling at him, he's like, "Well, I don't get paid. I was just doing this 'cause I liked kind of working on software in my free time."

I mean, the tragedy of commons is like, it's a classic econ example of, if you have a piece of land and anybody can graze their cattle on it, nobody has an incentive to not put their cattle there. And the converse is nobody has an incentive to maintain that ground, because they don't own it. Because they don't get a return.

Paul: Agreed.

Edith: So it's like, so there's this common piece of land. If you put effort into, like, hey, let's put some fertilizer out, what happens? Everybody comes in and brings their cows there.

Paul: I'm not sure that the tragedy of the commons is a great analogy for software.

Edith: No, I think for open source it is the perfect analogy.

Paul: No, I think it's the opposite, because if you put fertilizer down, everyone gets advantage of that fertilizer. Like, it's free for it to propagate.

Edith: But you paid the money for the fertilizer and you put it down, and then everybody...

Paul: But you get to use your fertilizer. Everyone gets to use your fertilizer. And if someone else also puts money down, you'll get to use all of their fertilizer.

Edith: No. Let me rephrase.

Paul: I do understand the concept of tragedy of the commons and how it applies.

Edith: No, it was more like, so you want your cattle to come graze there. So if you put more, like, seed down to get more grass to grow, which is basically what developers are doing, you don't get really any return back. So everybody just comes and takes your grass.

Paul: But you do, because the grass is software, and software can be reproduced for nothing.

If you pay for a contributor to work on a thing, everyone gets the benefit. That's why open source is beautiful.

Edith: But I was saying, if you pay for your contributor and you don't get any money back, like, what's your advantage to keep paying?

Paul: Well, you're not getting money back, but you're solving your problems. You're reducing your risk, you're, you know, fixing the holes in SSL, whatever the thing is. I don't think it's a straight model of tragedy of the commons.

Edith: I think it's a direct model.

I think this is a good time to thank Paul for hanging out with me and talking about software.

Paul: Arguing about what software is or should be.

Edith: Paul, do you have any final thoughts?

Paul: Just that we're really bad at ending all of these podcasts.

Thanks for listening to this episode of To Be Continuous, brought to you by Heavybit and hosted by me, Paul Biggar of CircleCI and Edith Harbaugh of LaunchDarkly.

Edith: To learn more about Heavybit, visit heavybit.com. While you're there, check out their library, home to great educational talks from other developer company founders and industry leaders.

Subscribe to Heavybit Updates

You don’t have to build on your own. We help you stay ahead with the hottest resources, latest product updates, and top job opportunities from the community. Don’t miss out—subscribe now.