6,111 karma · joined July 21, 2008
Here is how it looks: http://img.skitch.com/20110620-1mewpjkhy72hbhghw2ycmtjjpa.jp...
He phrases this as an attempt to regain "our" trust, which implies an understanding that they have lost it. I suppose this is the best we could ask for - here's hoping for the best.
Scribd is hiring for a few different positions.
We work in ruby, but there is plenty of java, python, and other variety mixed in when it makes sense.
The engineering team is comprised of many of HN readers who genuinely enjoy what they do and are driven to solve challenging problems. If you are interested, you can check out our jobs page or email me directly with any questions.
I'm an engineer at comparably-sized RoR based company in SF, and we are looking for more people to join the team. If you'd like, please get in touch: quin@scribd.com
I'd be interested in hearing about your goals and filling you in on the engineering culture here.
Scribd is hiring for a few different positions.
We work in ruby, but there is plenty of java, python, and other variety mixed in when it makes sense.
The engineering team is comprised of many of HN readers who genuinely enjoy what they do and are driven to solve challenging problems. If you are interested, you can check out our jobs page or email me directly with any questions.
This is just a series of classic correlation versus causation mistakes. Even beyond the purely statistical view of the issues here, it is clear to anyone with some basic knowledge of photography that most of their conclusions are flawed.
Hopefully they'll correct some of the wording to remove logical implication or just do a better job next time.
Sorry for the inconvenience.
Job postings are more often than not (imo) poorly worded. The main idea is that you extract what they are actually looking for, which you can in most cases. If they ask for your github account and you do not have one - tell them you don't and send them some significant code samples. If they ask for a twitter/SO account and you don't have one - say you focus most of your commentary on HN and give them your username here. I don't know of any companies that will ignore/discount you if you provide them with the data they are seeking.
We work in ruby, but there is plenty of java, python, and other variety mixed in when it makes sense.
The engineering team is comprised of lots of HN readers who genuinely enjoy what they do and are driven to solve challenging problems. If you are interested, you can check out our jobs page or email me directly with any questions.
Page 14: http://www.scribd.com/doc/34239119/Ceglia-v-Zuckerberg-compl...
http://www.scribd.com/doc/34239119/Ceglia-v-Zuckerberg-compl...
Page 11: http://www.scribd.com/doc/34239119/Ceglia-v-Zuckerberg-compl...
Last page: http://www.scribd.com/doc/34239119/Ceglia-v-Zuckerberg-compl...
http://www.scribd.com/doc/15556326/Structure-and-Interpretat...
At the volume and price you want, the Silvia is likely the best choice. You don't get great precision/consistency, but with some practice you will get great shots, and it will last a long time. It should be paired with a grinder like the Rocky at the very least.
I've had the chance to work at a large scale website based completely around a wiki, and the successes and failures therein became quite evident. There is definitely room to innovate, especially on the editing side of the experience. I have some interesting friends in the wiki community, so feel free to ping me if you want to chat about it some more and I can probably put you in touch with them.