HN user
http://bleikamp.com
It's free for up to 3 people if you want to try it out, after that the pricing starts at $199/mo for 10 seats; we've been working with early customers iterating on pricing that makes sense, so we're happy to talk more to learn what works for you.
If you want to try it out, you can sign up at https://app.cased.com/signup
Who slogs through producing the documentation, and keeping it up-to-date? Once a new product/feature is launched, who sticks around for the bugfixes, support, etc., since presumably everyone will be more excited to allocate themselves to the next new big thing?
Doing this work is part, and perhaps the most important part, of shipping a feature. It's not just boring work. If someone isn't prepared to support something, they shouldn't ship it.
It's currently very simple.
The mobile app is just part of our main web app. We use the same models and controllers as our desktop views. We have separate markup, different bundles for mobile JavaScript and CSS, and separate view models[1].
A few of the other projects that people are working on: GitHub for Mac, GitHub for Windows, libgit2, internal tools, ops, Gist, Git
That's the difference between Ikea and a company like http://www.urbancase.com/. Craftsmen don't think that way.
Why should internal tools be ugly? Well designed tools help people work better and more efficiently—putting a little bit of thought into them is not a waste of time.
Depends on what opportunities were out there. I'm not opposed to starting my own company, I just don't think it's the only way to happiness.
Citing ample evidence without links to it. Amazing.
Yelp's filtered reviews fluctuate as well. Reviews that are filtered can be unfiltered if the system decides the reviews aren't actually spam.
It's not worth mentioning. Almost every case has been a coincidence and they've gone out of their way to explain the review filter (which functions similarly to Google's PageRank algorithm and attempts to filter out spammy reviews using various factors).
Each court case related to this has been thrown out.
If you trust Google to be fair with PageRank then there hasn't been any evidence that should make you more concerned about Yelp.
Business owners complain about getting demoted in Google's PageRank algorithm quite a bit, too.
That's not the actual logo. It's a variation that is only used in the header.
The official logo includes the Social Coding tagline.
What browser/OS are you in? It looks pretty reasonable in Chrome on OSX; we spent a decent amount of time trying to get it as close as we could. Some browsers do weird math on resizing.
We do it so that when people zoom in on the site (using `⌘ + +` on a Mac) the image doesn't become pixelated and ugly.
We do it with most other images, too.
3 offices (SF, NYC, Phoenix), approaching 1000 employees, servers, marketing costs, etc. — gets expensive.
Open sourcing an operating system as nothing to do with executing well.
Releasing a music product with serious UX issues isn't that impressive.
The Gmail redesign is nice. But not in direct competition to Apple.
It's not a democracy - Yelp pushes the best reviews to the top. Most people read a couple of reviews, it serves Yelp's interest to make sure they read the best ones.
There are significantly more stories of businesses having a great experience with Yelp than a bad one. But it's not exactly a great story for the Chicago Tribune to highlight all of those businesses.
What does it say to you that a judge threw the case out?
I am not sure what you mean.
Why would filtered reviews distribution match up to the unfiltered reviews?
Typically a "fake" review is either going to be someone who is raving about a business to try to boost the rating or someone who for some reason wants to bad mouth the business (e.g. a competitor) so it makes sense that 1 and 5 star ratings are the most filtered.
I worked at Yelp on their product management team for about 18 months.
It's essentially impossible for anyone in the company to manipulate, delete, or add a review to a business page unless the reason is related to Terms of Service. Even then, you cannot do it without someone noticing and double checking that the reason something was removed was legitimate.
The algorithm is (in my mind) similar to Google's PageRank—it's not a trivial piece of software, it takes a full time team to maintain, edit, update, fix, improve, etc. Whether or not a business is an advertiser is never taken into account.
Yelp puts consumers first - that means sometimes they remove legitimate reviews. Everyone on the product and engineering teams knows this, realizes it sucks for businesses, but would rather err on the side of all reviews being legitimate. The reason they keep working on the algorithm is to improve this and make it more accurate.
The sales staff has strict rules on what they can and can't do, they do not have access to editing, managing, or deleting reviews and I never once saw an email come to product asking for a review to be removed or added.
Thousands of businesses work with Yelp, are happy with Yelp, and have happy customers. Even businesses with 5 stars get negative reviews sometimes. You cannot please everyone.
There aren't really any deadlines.
For the most part people are working on things they're excited about, so everyone wants to ship as quickly as possible.
While we have fun, goof off, and can work whenever we want, we're all professional and respect each other. If I am blocking someone I am not going to take the day off.
GitHub has erred on the side of hiring people who don't need measurement—we all work hard regardless of who's watching.
Also, everyone is smart. No one is assuming number of commits is a correlation to productivity. Some days sitting at home thinking about a problem is productive.
I personally work more productive hours in a week at GitHub than I ever did at a company where I was in the office 10 hours a day. But no one is counting them.
Coming up with extremes is a really valuable skill. So clever.
"I've run a team of Solaris sysadmins and yes I could have hired Linux sysadmins…"
Now you're comparing system administration to design - this doesn't really work. Technical skills like this don't translate well, and I never claimed they do.
The post is about UI and interaction design and those principles are the same across all platforms. Design patterns for a specific device, operating system, or medium (e.g. the browser) are not something you need to be a specialist to learn, analyze, or pick up - you need to understand the fundamentals of design.
Early iPhone designers who built great apps had spent much of their careers designing on the web. They had to learn and come up with new design patterns, but since they were good, it was well within their skill set.
It depends on the privacy setting for the status/post.
This thread on Quora provides a lot of great advice: http://www.quora.com/How-can-I-learn-to-be-a-good-product-de...
Two of the people on the team were experienced hardware hackers, others were experienced iPhone developers.
I believe they did some minor planning beforehand to get the write components to build things.
(I work at Yelp)
It was only 48 hours ;)
YC isn't about money, it's about the relationships and the network of YC alumni and the prominent angels and VCs who show up at demo day.
I think another issue is their solution to the problem is flawed. Most users don't have a desire or the ability to run their own server.
Running a basic application on a web server seems trivial to nerds, but to average users it seems impossible.