11 ms·
Trek is making a huge mistake IMHO. As a developer I can think of nothing more helpful than to get a "steam-of-consciousness" excerpt from our users. This is s
by joshstrange 14y ago
Trek is making a huge mistake IMHO.
As a developer I can think of nothing more helpful than to get a "steam-of-consciousness" excerpt from our users. This is something no analytics package can tell you, if you want to make your "product" easy to use then this is the exact feedback you need. Delverworld was outlining the various pitfalls of getting started with ember.js and a core contributor shrugs it off because he didn't like the guys attitude?
No one likes having their shortcomings pointed out but it would have made much more sense for Trek to admit that getting started could be made easier and that the Ember.js team would look into ways to make it easier. Ignoring the issue like he is "above it" is pretty fucking pretentious if you ask me.
- mootothemax 14y agoNo one likes having their shortcomings pointed out but it would have made much more sense for Trek to admit that getting started could be made easier and that the Ember.js team would look into ways to make it easier Agreed. I recently had a new user point out in quite spectacularly a direct fashion how unfriendly the "Getting Started" section of one of my apps is. It made painful reading, but I would happily pay for users to get in touch like that.
- joshstrange 14y agoSame here, I used to be much more of a "hot-head" when it came to things like this (I'm still not perfect, far from it) but I try not to take things as personally, at the end of the day if it makes my product better then I should shut up and be happy.
- vanderZwan 14y agoI'm studying interaction design in Sweden at the moment. This is exactly the point they're drilling into our arrogant heads: you're not a genius, listen to your users. And then you actually have to convince your clients that they are not geniuses, that being an expert can also make you blind to things, and that they need to listen to their users. http://en.wikipedia.org/wiki/Participatory_design http://en.wikipedia.org/wiki/Participatory_design
- k__ 14y agoTrue story. I've seen 2 extremes in my career: 1. The "product makers" think they know everything and force the users to do it the way they want. This often results in a bad to use product. 2. The "product makers" think the user knows best and do everything the users say. This often results in a too specific/unflexible product.
- slantyyz 14y agoI'd add to your point #2 - It can also result in a product that is way too broad and not particularly good at any one thing. i.e., the Homermobile.
- vanderZwan 14y agoOh, absolutely. It basiclly comes down to having a proper dialogue instead of one party dictating to the other what to do. It's just that in practice nr 1 seems more common.
- skarmklart 14y agoWhere in Sweden are you at?
- tixocloud 14y agoYou're absolutely right. I have seen this sort of attitude from quite a few domain experts - if you didn't get it, you aren't smart enough and "don't deserve to be in our group". It's very sad because this is exactly the perfect feedback to know what the heck is wrong with your approach. We collect feedback for the tools that we put up on the web - these are usually non-technical people but people around me always dismisses it as "they aren't smart enough to get it" which annoys the hell out of me. Making things easy to understand and easy to use is what drives adoption rates. It's what made Apple the dominant. Sometimes handholding is necessary until knowledge has been successfully transferred over.
- CJefferson 14y agoYes, I agree. Just a couple of days ago I had a similar interaction with the mercurial folks, where I posted a (slightly overly annoyed) e-mail saying that their page about GUIs was awful. In that case I got a nice reply, and they clearly took the suggestions on board and have massively improved the page. It gave me an excellent impression of the developers of mercurial.
- daleharvey 14y agoAs someone developing a Javascript library, this a thousand times. At some point I thought my library was easy to use and reasonably well documented for a very early stage library. Then I sat down at a little hack day with people trying to use it answering question over question about all those details that I had just assumed people would magically know, at the same time I though about for each of those questions there could have been hundreds of those that tried to use the library without me sitting next to them and gave up. If I could get this type of feedback from every use, it would be amazing.
- daleharvey 14y agoWriting this I remember at some point for an old startup I used http://feedbackarmy.com/ http://feedbackarmy.com/ to have people run through the getting started tutorial for my app. When I get to release and am happy with the state of the documentation I will likely try the same thing.
- seivan 14y agoIt's not the first time. I've been in their IRC. They are friendly and helpful. Especially Yehuda, but there seems to be this idea that if you "don't" get it, you might just be stupid... http://twitter.com/trek/status/302811479135092736 http://twitter.com/trek/status/302811479135092736 I got this tweet and I constantly look at it before deciding against giving Ember another try. So far I'v done Backbone, Angular and Batman and I've had no problems with either of them! I decided to go with Batman.js unless I need extreme performance, then I'd go with Angular. Embers concept of iOS seems broken. I'm an iOS developer. They don't follow the same pattern. The best they could have done would be to use the same API structure. But no... "@Seivanheidari @ahazem we'd love to know the root cause of your difficulty. Most people seem to be successful with guides + api docs now."
- rachelbythebay 14y agoI came to a conclusion some years ago: if too many users are wrong, it's probably your fault. There's not some conspiracy by a bunch of unrelated users to all trip over the same things. It probably represents an actual problem. I learned this myself with a dumb little proxy instruction web page. http://rachelbythebay.com/w/2011/07/15/ui/ http://rachelbythebay.com/w/2011/07/15/ui/
- trek 14y agoI have admitted that, publicly, very often, in other topics on discuss.emberjs.com, on websites, on twitter, on videos, and elsewhere. It's no secret I'd like to improve the documentation for Ember.js and I'm already well aware of the places that people are facing difficulty right now. There's work, if people spent a moment reading the top topics in the forum, on a getting started guide with a direct call for feedback http://discuss.emberjs.com/t/todomvc-based-getting-started-guide/433 http://discuss.emberjs.com/t/todomvc-based-getting-started-g... I've been extremely vocal in soliciting actionable feedback on that. I'd like to help! Discourse isn't for making places like hackernews, where a playful, sometimes discouraging culture of dickitude is acceptable and encouraged. The goal of Discourse (a "Civilized Discourse Construction Kit") and our use of it is to create a place where civil discussion can take place to improve Ember.js as a framework. Delvarworld's tone strayed into territory I don't think remains civil because of his use of sarcasm: "are you serious?" "oh god this is going to be fun, isn't it?" "by the awful grace of god" "3 more results linking to the first dead article! FANTASTIC!" And so I signaled that I empathize with his frustrations (because I do) but I can't participate in that discussion because it violates community norms I'd like to uphold. If he'd like to rephrase his topic, I'd be glad to help. Ego and pretension have nothing to do with it. Contributing to OSS is something I make a personal decision to do with my time. I wish I had an infinite amount of time, but I don't. Most people associate me with Ember.js, but I'm very active elsewhere. Did you know I regularly run through all the TodoMVC examples looking for bugs https://twitter.com/trek/status/313015370728501248 https://twitter.com/trek/status/313015370728501248 ? Most people don't, because it's just something I quietly do. Less quietly now, I suppose. In addition to working on OSS, I'd love to maybe find a nice boy to date (https://github.com/trek/lonely_coder https://github.com/trek/lonely_coder), see my friends, visit my aging, ailing parents more often, maybe catch a moving once in a while, or eat a meal I'd don't grab on the go running from one obligation to another. Like most OSS contributors, this isn't my job. It doesn't pay my bills or put food in my belly. I do it because I'd like to improve the tools I work with and share those improvements with the larger tech community. In the finite time I can offer, I have to make decisions about where to expend energy. I choose to do that in places where I can have the most impact. I don't feel that I can be helpful when people approach with sarcasm. Rather than remaining silent, I let people know I'm happy to engage when we trend towards civility.
- rxcfc 14y agoKnowing Trek, I think his frustration here is in large part with himself. He cares very deeply about giving users a good experience with Ember and knows that we aren't achieving that as well as we'd like. We've been planning and working on an improved Getting Started story for a while now but, because all of us on the Core Team are very busy with our day jobs, it's been slower going that we would have liked. To have more people point out your shortcomings when you're already well aware of them is very frustrating. I think this is what we're seeing in Trek's response. Now that doesn't mean that I think his response is helpful - it's not. But I do want it to be clear that we do care about these issues and sometimes maybe too much. When our new Getting Started Guide is finally released, I promise that we will do our best to address all of the different comments and complaints we receive from our users. -Peter Wagenet, Ember Core Team Member
- Uchikoma 14y agoIf he cares that deeply, I'd suggest walk instead of talk and fix the problems now instead of hand waving. The Emberjs documentation problems have been there since the beginning. Instead of commenting on #HN how awful ungrateful sarcastic users are, write a new "Getting started" page.
- mgrassotti 14y agoI don't think trek called anyone ungrateful. He's just tired. Also he already is working on a new getting started page. A few days ago he posted to the forum outlining his plan and asking for feedback. http://discuss.emberjs.com/t/todomvc-based-getting-started-guide/433 http://discuss.emberjs.com/t/todomvc-based-getting-started-g...
- jackmaney 14y agoWhy was the Getting Started Guide not at (or near) the top of your priority list for documentation?
- mgrassotti 14y agoIt is. http://discuss.emberjs.com/t/todomvc-based-getting-started-guide/433 http://discuss.emberjs.com/t/todomvc-based-getting-started-g...
- k3n 14y agoAlthough he's already replied to you, I wanted to point out that a refusal to respond to a post in no way indicates whether or not the communication has been received. In other words, he's not ignoring the feedback, he's just refusing to engage in discourse which he sees as already unproductive. Quite the opposite, he sympathizes with the OP to begin with, and so he most likely read it. He just doesn't want to engage in what could easily turn into a flamefest.
- joshstrange 14y agoWith all due respect I don't think that this is what happened here. That's fine if he felt no need to help, to problem is when you go out of your way to let someone, someone who is trying to learn, that you think they aren't worth your time due to the tone of their post. I understand where the OP is coming from, the frustration at trying to learn something and constantly hitting roadblocks. Was he a little sarcastic? Yes, however I would be too if I couldn't find any help. This situation was escalated by the fact that his cry for help was met with a core contributor taking the time to tell him he wasn't going to help. I would compare that to going up to a homeless man and telling him you weren't going to give him any money. There just wasn't a good reason to post something like that.
- k3n 14y agoGood points, and you're probably correct. However, to your last point, I can see how it'd be challenging to convey your stance that you won't allow uncivil discourse other than how he did so. If you go ahead and respond normally, you're just reinforcing the bad behavior, ergo it makes the "discourse must be civil" an empty promise/threat. Perhaps he could have replied, with a caveat that further uncivil posts would be ignored, but I can also see getting tired of that sort of behavior (and as a former forum mod, continually having to 'remind' people of the rules that they've already agreed to wears out really quickly).