mojombo

16 ms·

181.
by mojombo 16y ago
Yes. Our equity offers are quite generous. Invested employees are motivated employees. Ownership is a huge factor in job satisfaction.
182.
by mojombo 16y ago
Reading code is one of the best ways to become a better programmer. You can learn so much so quickly by trying to understand how other people you admire solve problems in code. Making it easy to find, follow, and read code is what GitHub is
183.
by mojombo 16y ago
Not having a set work schedule allows us to work when we're most effective, leaving more time available for taking care of personal affairs. If you want to take Wednesday off because your Mom's in town, then that's what you do. We all work
184.
by mojombo 16y ago
Making the user the namespace for code instead of the project. Growing slowly and embracing the constraints of a limited budget in the early days. Hiring only the absolute best people that we could find. Hiring people that we knew through t
185.
by mojombo 16y ago
The new shipment of Fork You shirts will arrive at our office today. We will get the inventory online right away! The BitBucket/Atlassian deal is interesting. Especially the price points they think they need to establish in order to make th
186.
by mojombo 16y ago
I can neither confirm nor deny that we're working on kickass improvements to GitHub Issues.
187.
by mojombo 16y ago
Quora doesn't make it easy to compile a bunch of questions and answers in one place. This is a much better forum for these discussions.
188.
by mojombo 16y ago
It took three months to go from inception to private beta. We used an invite only system to introduce artificial scarcity and drive buzz on Twitter (each new signup got five invites to use). After six months we launched to the public and st
189.
by mojombo 16y ago
There is some great advice in Getting Real, but I don't remember being particularly influenced by it. I was more influenced by Ricardo Semler's book Maverick. And by wanting to build a company that I myself would want to work for, regardles
190.
by mojombo 16y ago
It's not a figure that we publicize, but let's just say it's enough to support thirteen well paid employees, a San Francisco office, 34 physical machines at Rackspace, and plenty left over to put in the bank account.
191.
by mojombo 16y ago
We actually haven't talked to Linus. He only takes part in discussions around Git when he notices something wrong. The model that the Linux kernel uses for contributions is pretty well set in stone (and email) and so it's likely that GitHub
192.
Optimize for Happiness (Followup to my Startup School talk)(tom.preston-werner.com)
36 points by mojombo 16y ago|6 comments
193.
Ask Tom Preston-Werner, cofounder of GitHub, anything Today, Mon 18 Oct 2010.
144 points by mojombo 16y ago|139 comments
194.
by mojombo 16y ago
The code behind the Git-based wiki is also open source so you can view and edit your wiki locally via a nice web interface, and build your own tools using the API: http://github.com/github/gollum
195.
by mojombo 16y ago
With a lot of effort I think they all could have been successful. But when you have to work your day job to make a living, you need something you can bootstrap on the side without investing huge amounts of unrewarded effort up front. That's
196.
by mojombo 16y ago
Not really. I didn't have much money to use for marketing so I just focussed on getting it in front of people that would be interested and spread the word. That meant sending emails to people I didn't know and introducing myself. Sometimes
197.
by mojombo 16y ago
This is a hard question to answer. I work on a lot of side projects in the form of open source libraries and whatnot. It's possible that any of those could blossom into a business, but I've never really pursued many of them. As for other bu
198.
by mojombo 16y ago
I started both Gravatar and GitHub as side projects. I sold Gravatar to Automattic after several years (though it was never profitable and became quite painful to run during the last year that I owned it). GitHub has been profitable since t
199.
by mojombo 16y ago
The benefit of doing your design in a Readme over doing it on a whiteboard or elsewhere is that it becomes a nice piece of documentation sitting right there in the root of the project. The first place you look for an explanation of what the
200.
by mojombo 16y ago
Sure. The documentation for those projects looks great!
201.
by mojombo 16y ago
You may also be interested to see how the Readme evolved over time as I implemented what I had specified. http://github.com/github/gollum/commits/master/README.md Writing your Readme first doesn't mean you should never change it. It shoul
202.
by mojombo 16y ago
All of those things are approaches to crafting better software. It is my observation that a lot of projects developed with these methodologies still lack proper documentation. And I see documentation, especially in the form of a good Readme
203.
by mojombo 16y ago
As an example of a project that was written with RDD in mind (I wrote this while I was writing this blog post), see http://github.com/github/gollum . This is my notion of the scope and specificity that a nice Readme should have.
204.
Readme Driven Development(tom.preston-werner.com)
242 points by mojombo 16y ago|57 comments
205.
The way GitHub helped Erlang and the way Erlang helped GitHub(infoq.com)
18 points by mojombo 16y ago|3 comments
206.
by mojombo 16y ago
Where's the Readme? It's hard to tell if the YABT approach has any merit without any documentation.
207.
by mojombo 16y ago
We've had discussions about selling Haystack licenses before, but that requires a fair amount of work to get it in shape to do so. It's possible we will open source it someday instead. Nothing has been decided at this point.
208.
by mojombo 16y ago
We're a bootstrapped company and the initial capital outlay for servers would be a serious investment at this stage. Rackspace gives us access to hardware on-demand at monthly prices that fit our budget. In addition, we have a partnership d
209.
by mojombo 16y ago
If you have any questions about our infrastructure that were not addressed in the video, I'll be happy to answer them here!
210.
by mojombo 16y ago
Archives are generated when they are requested and cached for fifteen minutes. This cache length results in an average of 3.5GB of cached archives on disk at any given time. We have to serve a large number of archives for arbitrary revision

More ›