Having root access to the machine would allow you to optimise some things and probably raise those numbers, but then you don't get the convenience of using Heroku.
1,235 karma · joined September 6, 2007
Artillery - test everything you build & run in the cloud.
We're hiring! join us to help build the future of testing for DevOps.
https://www.artillery.io
Twitter: https://twitter.com/hveldstra
Email: h@artillery.io
Having root access to the machine would allow you to optimise some things and probably raise those numbers, but then you don't get the convenience of using Heroku.
In general, I'm interested in projects with novel UIs, interesting interactions, and new ways to present information, like I would totally love to work on http://moonbase.com
h@veldstra.org
As far as someone is concerned. You misunderstand what a Black Swan event is. A Black Swan is at the root an opacity problem, and not one of forecasting. 9/11 certainly wasn't a Black Swan event for the hijackers or the masterminds, but it was for everyone else.
Luck is necessary but not sufficient. You also need to be in a position to disproportionately benefit from luck. I think PG's latest essay outlines what a venture in such a position looks like.
There are qualitative differences between startups that are going for $10m and those going after $1bn. The biggest is variance, which luck is a multiplier for.
YC was never about the money.
For an insight into PG's motivations, you might want to re-read his essay on cities (it's more likely to be "power", as in your influence on the world). The footnote in the Black Swan essay linked above seems to corroborate that.
Getting a shirt that will fit well ranks much higher in most people's priorities than using only HTML-based webapps.
(only half-joking)
Love the design of the site.
Stock market is a fool's game by its nature.
(Based on reading Nassim Nicholas Taleb and conversations with people that worked on trading floors.)
What about when you download some library from Github and want to quickly get an idea of how it all works?
I use Emacs 99% of the time, but when I need to look through a codebase I'm not familiar with I use TextMate for its project panel.
I consider erudition, a sense of history, and curiosity to be some of the most important qualities in any professional. Someone who hasn't read classics such as Why FP Matters, the original Lisp papers, the YACC paper, Codd's papers, The UNIX Time-Sharing System etc would show a complete lack of all of those.
Especially if it was indeed as clear at the time that Flex was doomed as the author claims. Hindsight is 20/20 - "the history test" is BS without the benefit of it.
At scale it is. More here:
http://www.quora.com/Hunch/Is-Hunch-actually-doing-anything-... (this one got a vote from one of the founders)
Impressive back-end tech (the recommendation engine) that can now process millions and millions of items on eBay to help increase sales (something like a quarter of Amazon's sales come from recommendations).
...and a different syntax. That's my main objection to CS. I'm already working with 5 different syntaxes: Python, Javascript, Erlang, HTML, and CSS. Adding yet another one isn't appealing.
Perhaps if you're writing an app on top of the Node.js stack, you can use CoffeeScript everywhere. What I would've liked to see is CoffeeScript with a syntax as close to Javascript's as possible.