busterbenson
There's definitely stuff I can do to make AWS cheaper. Starting with just remembering to pre-pay for my instances ahead of time. One of my least favorite things to do is to log into the AWS console, so I try to do it as little as possible.
The CPU intensive part is due to autosave. When a lot of people are writing concurrently (even on the order of hundreds), that was usually what would take down the site in the old days. The site is weird in the sense that there are 10x more writes than reads, and then doing all of the linguistic analysis, badge granting, stats generating cause spikes when they happen as well. I'm @buster on Twitter if you want to continue the discussion there.
I also added a breakdown of costs to another comment deeper in this thread, in case that's of interest.
And wow, the other comments to this comment really made my day. I haven't been to Hacker News in a while but it's amazing to see that it's turned into a positive environment.
2018 costs:
48% to salaries and contractors (my wife and I are the only people on payroll, and draw $60k salaries for ourselves)
12.1% to operations (health insurance, renting a desk at WeWork, minimal travel, lot of SaaS subscriptions, misc equipment and other costs)
7.5% to PayPal fees (I really need to renegotiate this)
4.9% to AWS
4.2% to payroll taxes and other business administration
23% to profit (goes to saving up to quit my job last year, finish my book, and then dedicate ourselves to this full time)
Hope that's useful! Let me know if you have any other questions about this stuff and I'll do my best to be as transparent as I can without revealing every little detail.
Update: I should also mention that the salary we draw is in now way sufficient to actually support a family of 4 in Berkeley, so since quitting my tech job last October, we've been draining our savings and preparing to find a way to turn this little business into something that could sustain us longer term. I call it our flying rickshaw (the opposite of a rocketship). Outcome still uncertain.
http://enjoymentland.com/2009/04/21/locavores-first-month-in...
Hope that helps!
It sounds like you have a few of these qualities... choosing your work hours, for example... but what about measuring results. Do you have any specific tips on how to measure results without getting too confused or attached to the a new incorrect metric?
Are you willing to share a bit more detail about the timeline of the first year when you went from 2 people to ? people... when you hired, how much you spent on salaries versus how much you were making in revenue (exact numbers not required), and how certain you were that revenue would continue to grow at the pace required to support your staff.
Also, what were the "other means" by which you supported yourself until GitHub was able to support you? Your jobs? Or something else?