О ныках

Tuesday, 10 October 2006 06:27
scoon: (tarakan)
Добрый дедушка Нильсен написал пару слов о том, как помочь пользователям перестать ныкаться по углам и начать вносить свой вклад. Если убрать из статьи воду, то останется вот это:

  • Make it easier to contribute. The lower the overhead, the more people will jump through the hoop. For example, Netflix lets users rate movies by clicking a star rating, which is much easier than writing a natural-language review.
  • Make participation a side effect. Even better, let users participate with zero effort by making their contributions a side effect of something else they're doing. For example, Amazon's "people who bought this book, bought these other books" recommendations are a side effect of people buying books. You don't have to do anything special to have your book preferences entered into the system. Will Hill coined the term read wear for this type of effect: the simple activity of reading (or using) something will "wear" it down and thus leave its marks -- just like a cookbook will automatically fall open to the recipe you prepare the most.
  • Edit, don't create. Let users build their contributions by modifying existing templates rather than creating complete entities from scratch. Editing a template is more enticing and has a gentler learning curve than facing the horror of a blank page. In avatar-based systems like Second Life, for example, most users modify standard-issue avatars rather than create their own.
  • Reward -- but don't over-reward -- participants. Rewarding people for contributing will help motivate users who have lives outside the Internet, and thus will broaden your participant base. Although money is always good, you can also give contributors preferential treatment (such as discounts or advance notice of new stuff), or even just put gold stars on their profiles. But don't give too much to the most active participants, or you'll simply encourage them to dominate the system even more.
  • Promote quality contributors. If you display all contributions equally, then people who post only when they have something important to say will be drowned out by the torrent of material from the hyperactive 1%. Instead, give extra prominence to good contributions and to contributions from people who've proven their value, as indicated by their reputation ranking.
Новизна самих методов, в сущности, нулевая -- польза статьи в том, что Нильсен собрал вместе именно те методы, которые оптимальны по критерию цена/качество.
scoon: (Default)
Добрая статья: "Creating a Baseline Calendar". Я таким способом обрабатываю наиболее неприятные виды деятельности (в частности -- обработку ошибок в ClearQuest). Подумываю поставить такую же задачу на вычистку Inbox'а.


Wednesday, 8 March 2006 13:15
scoon: (Default)
Добрая статья о том, каким должно быть портфолио дизайнера: The Right Portfolio.

Меня она заинтересовала не конкретными советами -- все ж таки создание дизайнерского портфолио в мои личные планы не входит. Просто натолкнуло на мысль: а почему программисты (в самом широком смысле этого слова) никогда не имеют портфолио.Read more... )
scoon: (Default)
В период предновогоднего безумия упустил из виду статью "Ruby off the Rails".

Статья довольно милая:
Before I can even begin this article, I need to clarify something. First, this is not an article about Ruby on Rails. If you want to read about Rails, articles and blogs are published weekly (maybe hourly) extolling the manifold features of this exciting framework; see Resources for a list to start from. Second, this article does not foretell the collapse of the Java platform in the face of better languages, tools, and frameworks like Ruby on Rails. So this article is about neither of the subjects most commonly associated with Ruby of late.

Don't get me wrong -- I think Rails is fabulous! It's amazingly powerful and has clearly changed the face and pace of Web development. My only point is that there's more to Ruby than Rails, especially from a Java developer's perspective.

Beyond Java

Thursday, 22 December 2005 15:00
scoon: (Default)
Несколько дней назад добрый человек Bruce Eckel написал заметку "The departure of the hyper-enthusiasts".

Не смотря на то, что во многих местах его мнение кажется мне неправильным, но спорным, я все же согласен в первичной посылке:
The Java hyper-enthusiasts have left the building, leaving a significant contingent of Java programmers behind, blinking in the bright lights without the constant drumbeat of boosterism.

But the majority of programmers, who have been relatively quiet all this time, always knew that Java is a combination of strengths and weaknesses. These folks are not left with any feelings of surprise, but instead they welcome the silence, because it's easier to think and work.
Пи... ой... То есть -- аминь. Может быть, вскоре мне уже не придется интервьюировать в год по 20 программеров, которые пишут на Java потому, что это круто...
scoon: (Default)
Статья с большими буквами и красивыми картинками: "The Website Development Process"

scoon: (Default)
Добрый человек Dirk Knemeyer в статье Rethinking Application Design дает несколько добрых советов об организации работ. Must read для небольших веб-студий.
  • Use the smallest design team you possibly can
  • Put an interface designer in charge of the interface design team
  • At all costs, avoid design by committee
  • Invest in fewer, more senior people
  • Let the design team operate outside of the traditional organizational framework
  • Treat user testing as a data point, not the driver

Кстати, лично мне очень понравился последний пункт. Цитата:
I've written previously on the insidious nature of a usability culture on design. The results from supposedly objective, quantitative usability testing and evaluations often end up driving design. This not only limits innovation, it also results in design being dictated by unnatural testing environments and analytical observations from non-designers instead of use by real people in real situations. This offense is particularly pointed in application design, where success is less about how "intuitive" a design is and more about the value it provides from extended use. User testing provides valuable insight, but it is not meant to serve as the arbiter of design decisions.
scoon: (Default)
На LtU дали добрую ссылку на статью "Lowering the Barriers to Programming: a survey of programming environments and languages for novice programmers" (PDF, 2M). Довольно любопытно, но местами спорно.



Tuesday, 25 October 2005 06:39
scoon: (Default)
Добрый челоек Erin Kissane пишет о зомбучьих текстах и о том, как с ними поступать: "Attack of the Zombie Copy".

Вообще, "зомбучьи тексты" в русскоязычной части сети распространены просто ужасающе. Забросив невод, сразу поймал фразу: "Мы разрабатываем и внедряем организационные изменения. На сегодня у нас, по-видимому, самый большой опыт по реальному внедрению изменений в российских компаниях." Типичный текст-зомби. "По-видимому" (а мы и сами не уверены), "реальному внедрению" (а еще бывают нереальные, виртуальные и теоретические внедрения -- мы это тоже умеем)... :)

June 2013

10111213 141516


RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags