News for hackers. Stuff that matters.
Re:Lessons from GitHub's First Year by DavidChouinard on Tuesday March 29, 2011 @05:26PM (#2384570)
This is a great article. I especially like this:

Here’s a seemingly paradoxical piece of advice for you: Listen to your customers, but don’t let them tell you what to do. Let me explain. Consider a feature request such as “GitHub should let me FTP up a documentation site for my project.” What this customer is really trying to say is “I want a simple way to publish content related to my project,” but they’re used to what’s already out there, and so they pose the request in terms that are familiar to them. We could have implemented some horrible FTP based solution as requested, but we looked deeper into the underlying question and now we allow you to publish content by simply pushing a Git repository to your account. This meets requirements of both functionality and elegance.

Re:Lessons from GitHub's First Year by jacques_chester on Tuesday March 29, 2011 @06:23PM (#2384775)
Customers want a solution to their problem. To save time they will formulate what they think is a solution and give it to you, in the hope that it will speed up proceedings.

Think like a doctor. When the patient turns up, he or she may have a diagnosis in mind. But it is up to you to study the symptoms and deduce the condition independently of what the patient thinks.

Remember: a potted request from a client is a symptom of some deeper problem they wish to solve.

Re:Lessons from GitHub's First Year by 6ren on Tuesday March 29, 2011 @06:40PM (#2384830)
"It's really hard to design products by focus groups. A lot of times, people don't know what they want until you show it to them." Steve Jobs http://www.wired.com/gadgets/mac/commentary/cultofmac/2006/0...