We started down that path with free billing seats. But in the end, per seat just never felt right.
As a business owner (I have some other companies) my favorite software to pay for was everything that didn't charge per seat. I'd like my own software to be the same and thus the change.
Correct there are some limits still. At some point you have to make a decision, but at least not with every seat. The hope is to keep increasing those limits.
Correct. We also had two other products, which they sold within a year of acquisition (and we didn't buy back).
The only thing that made it an acquisition more than an acquihire is that we had products that were generating revenue, so they couldn't just give us jobs and regular options packages.
Our employees started at GitHub with regular options packages, but Steve and I got a little more because we were the owners.
At the risk of being seen as a rails douche, my response is that there is a strong culture in ruby and rails on authoring styles so it is not as painful. Beyond that, I am not saying that 100% of your problems are solved just looking at code. What I was trying to point out is that reading code is important and often times the answer. Google should not be your own tool. Hope that clarifies! :)
Exactly. Except I would not use inflammatory as the word. More I use titles like that to get people to read something that might not have, not to anger them. :)
I definitely feel the opposite. While there is a lot of crappy code out there, if you look, you can also find a lot of good code, which you can learn from.
We started down that path with free billing seats. But in the end, per seat just never felt right.
As a business owner (I have some other companies) my favorite software to pay for was everything that didn't charge per seat. I'd like my own software to be the same and thus the change.