5 ms·
This is my theory: we have missed a critical element of how FOSS got adopted in the industry in the first place. That blind spot explains a lot of the problems
by hinkley 5y ago
This is my theory: we have missed a critical element of how FOSS got adopted in the industry in the first place. That blind spot explains a lot of the problems we have had with getting compensation to FOSS authors, which has created a whole other set of problems for us to deal with.
In the middle of the S curve for adoption, software development teams were struggling with the fact that someone in finance laughed at the idea of spending money to make money. R&D is a cost center, and anything that reduced costs would make life better for the company. Well, any costs except labor, which are some magic other shade of money that can't tell that you just spent 1000 man hours on something that should have taken 300 but you first had to squeeze another application onto aging hardware that was slower than what some of the developers have at home.
In some cases these people were power tripping. They seemed to enjoy being able to say 'no' to any requests, able to use their purchasing veto power to make you do what they want you to do. Everyone had one of these stories. Many had one about the current employer.
Then along came Open Source. When you said, "I want to use X" and this person said, "We're not paying for that, no," you could cheerily shoot back, "Oh but that's the best part, it's free, so you don't have to pay for it. Have a nice day!" and tralala your way back to your desk while they are left trying to think of a way to force you to do things their way. That is why it's used everywhere. Because nobody could stop us.
So we've democratized the power dynamic quite a bit (you still have general managers forcing teams to use Oracle because otherwise they have to explain why they have been sending that much money to Oracle if half the applications are running on Postgres, so they pull the dick move of banning Postgres), but that money problem is still there, as it always has been. If I can't buy copies of TeamCity, which is commercial software with a commercial license, I sure as hell can't get the company to send $100 with no contract to some internet randos just because I say they're saving us a million dollars a year.
You can't educate your way into fixing that problem. People have been trying literally for decades. There's a plumbing problem here, and until that gets fixed you can plead with people all you want to fund OSS, but it's not going to happen.
- jka 5y agoInteresting - so, to reinterpret: are you saying that one of the significant changes that open source brought about has been to remove purchasing approval barriers for software usage? ...and that we're stuck in a local minima where we now have to get over other, similar approval barriers to send money back towards open source projects? (in the case of projects that accept funding, at least) (it's possible I've misinterpreted; and, for what it's worth, I think there are other reasons that FOSS has succeeded in addition to what you say - but I like that way of looking at the current landscape)
- hinkley 5y agoIn a nutshell, yes. I observed a number of people say one thing in a group setting but would confess to other things off the record. The purse string issue was high for a lot of people, but as you say that wasn't the only motivation. I think too that we oversold the Enlightened Self Interest value to the company in open sourcing internal tools. People worked hard on code that they didn't want to have to write again somewhere else, especially not several times. My current and future job satisfaction are elevated by convincing my bosses to free the code, the Greater Good is also improved by doing so. Nothing makes me want to leave like feeling trapped, and any work I do that has value past my expiration date is a big part of feeling like being here still is a choice. But I think only a few companies ever enjoyed the fruits of that effort to the degree that we were all telling them they would. Sun Microsystems in particular. But the industry benefited enormously, so history will probably be fairly kind.
- JonChesterfield 5y agoIt is _really_ annoying to write the same code repeatedly because the last time was inside some other company, especially when there's no plausible IP involved.
- hinkley 5y agoEspecially when you make half of the same mistakes every time. No argument here.
- xxpor 5y agoThe funny thing is, every eCommerce site already knows this at least implicitly. We've all heard the "every X ms of additional latency on the site reduces our conversion rate Y bps". Adding friction to anything means it's much less likely to get done. Even for commercial software, if it were easy to purchase, I'd still have to figure out how to make sure we comply with the licensing, get the key into the server, figure out how to deploy it (and not be able to inspect the software to see how it works if I need to). Or I can just go to github, make sure it has an acceptable license, and run import-from-pypy foobar==1.0.
- deleted 5y ago[deleted]
- cheesedoodle 5y agoAn OSS project that a previous company heavily relied upon, pleaded that they needed funding or would seize maintenance. As the project manager at the time, I told the R&D manager to start funding this OSS project. In return, we'd get maintenance and features that we otherwise would handle in-house. Roughly a 10kUSD/y handout from a Fortune 500. "How much do we pay today?", asked the R&D manager, "Nothing", I said, "its open source". "Then we will continue to pay nothing". So many companies take OSS projects for granted and as a once OSS core developer, I have seen many sides of this. Don't expect anyone to pay you for the work you are doing, and if you find your self not having the capacity to continue, try to see if there's any other maintainer ready to continue it for you, if not, even if it hurts, just leave it alone...
- WrtCdEvrydy 5y ago> "How much do we pay today?" "Not as much as we'll pay replacing it"
- hinkley 5y agoThis is the game, and people who don't like it still play it, which makes it worse. Boss knew we were using our integration box for customer demos. I don't know how many times I explained that the entire team would be blocked by 1 pm on demo day, and some people would be blocked as early as 10 am, for want of a cheap box. I had to make a chart that showed man hours lost versus the cost of the new machine. Six weeks. The new server would pay for itself in six weeks. He said something sheepish about how he thought I meant a '"server" server', not a workstation class machine. Still don't know what he was thinking. A "server" server still would have paid for itself in six months, and he would have the luxury of me not bitching at him every time he forgot why almost everything that didn't get done on a Thursday slipped to Monday afternoon and asked me again about slippage.
- cheesedoodle 5y agoWell, yes. But clearly, the 3rd party project is not the core business but would be if there was no alternative. The company would just develop it them self, if deemed necessary. The idea is that the knowledge would be retained within the company instead. The term "its free real estate" comes to mind.
- asah 5y agoAs a mid-level manager, I'd just whip out my personal credit card and expense it. In 20 years, nobody blinked. Ditto with taking a tax deduction from the IRS for my personal consulting work, which depends on FOSS. IMHO the issue is that users are lazy and have truly-zero risk tolerance, and that in turn means that FOSS developers need a lot more money per donor, which in turn means fewer donors. I'd like to see a single consolidated donation per unit time, that's then divvied up __based on your usage__ i.e. homebrew/apy/yum nags you from time to time and makes it one-click to make a decent-sized donation to the 100+ projects you actually use. (obviously, there's disagreement about what "use" means, but the UI would make it easy for the donor to make adjustments...) (and yes, I'm volunteering to work on something like this and/or help fund it)
- hinkley 5y agoWas that something you learned from someone else, or something you did because you didn't agree with how others had done it? I haven't run into a story like this often. Not in my own history, or talking to others over beers. I think you might not realize how unusual your reaction is, in the grand scheme of things. If you could try to convince some of your peers to do the same, a lot of people you never meet will benefit greatly by it.