心情不好于是再骂一下新浪微博好了

twitter通过in_reply_to_status_id把信息平等的串在一起,所以可以有比较长的讨论和分支,有storify这样的服务能整理这些讨论。微博的结构在comment里面讨论的话长一点就没法看,在转发里面讨论很快就由于字数限制也没法继续。微博是个不鼓励讨论而鼓励弱智追星的地方。

说到追星,每条微博都醒目的标着转发数和评论数,每个人都带着粉丝数和各种花里胡哨的标记。整个微博世界充满了铜臭味和沽名钓誉之徒,哦,还有垃圾粉。

新浪微博有很多很病态的feature,评论并转发,转发并评论,悄悄关注,关注但屏蔽。。。基本上没什么用户能搞清这些东西究竟是在干什么。完全没有美学可言。

新浪微博还盛行长微博这种东西,无法检索,无法自由流通,阻碍互联网上信息的传播。

微博上你关注的人之间通过评论进行的交互不会出现在你的timeline上,我觉得这一点就决定了微博这东西很难用。

变态的审查不算新浪微博的错,但是用微博被审查的感觉很不爽。

新浪微博本质上还是个论坛,每个帐号就是一个版块,这个帐号是版主,这个帐号发的每篇微博都是这个版的一篇文,然后评论就是跟帖,转发就是转帖。思路上落后了一个时代。而落后了一个时代的民众也就玩这个玩得开心,新的玩不转吧。

=========================FACEBOOK上一些followup=============================

Timminn Dy y do you 呵呵 at the comparision between twitter and weibo? if there was no language barrier weibo beats twitter like shit. honestly weibo is one of the very few chinese products that outstands and shines on international market.
Thursday at 4:13pm · Like

Wei Wei twitter通过in_reply_to_status_id把信息平等的串在一起,所以可以有比较长的讨论和分支,有storify这样的服务能整理这些讨论。微博的结构在comment里面讨论的话长一点就没法看,在转发里面讨论很快就由于字数限制也没法继续。微博是个不鼓励讨论而鼓励弱智追星的地方。

说到追星,每条微博都醒目的标着转发数和评论数,每个人都带着粉丝数和各种花里胡哨的标记,充满了铜臭味和沽名钓誉之徒,哦,还有垃圾粉。

新浪微博有很多很病态的feature,评论并转发,转发并评论,悄悄关注,关…See More
Thursday at 7:11pm · Like

Timminn Dy 好吧,

第一段的那些观点我没深入了解

追星那些是行政策略, 有好有不好, 看个人喜好观点. 我觉得那是个符号, 潜在鼓励大家加强关注. 这仅仅是市场策略而已. 垃圾粉\僵尸性浪是有打击的. 不过力度我能说肯定不够….See More
Thursday at 7:59pm · Like

Timminn Dy 长微博是为了打破140字符限制的work-around, 可以接受的. 不能检索是不好, 但是嗯? 你肯定不能自由流通??
Thursday at 8:01pm · Like

Timminn Dy 剩下的以后再回应一下吧
Thursday at 8:01pm · Like

Timminn Dy 变态的审查不算新浪微博的错,但是用微博被审查的感觉很不爽。<<<<<<<<<<完全同意 Thursday at 8:01pm · Like -- Wei Wei Good thoughts. 长微博我觉得是审查制度下的畸形产物,以及中国网民的使用习惯(对链接本能不信任?)造成的。我觉得在一个正常的生态里直接放链接要好很多,除了检索之外还有一个重要因素是给原网站credit。 我对那些繁杂的功能的看法确实比较主观,会去进一步了解一下。 Thursday at 8:18pm via mobile · Like

Toggl to JIRA

A tiny side project for day to day works, hosted on GitHub.

Basically it’s a tool to import time logs from toggl to JIRA. It reads logs on toggl by toggl REST API, then pushed them to JIRA by some ruby wrappers (soap4r and jira4r) of JIRA SOAP API.

JIRA is heavily used in FreeWheel. In my current group, almost everything I do can be tracked by a JIRA issue. JIRA serves as the todo, report, and bug tracking system here, and keeps everything visible to everyone.

Fortunately we just upgraded JIRA from 3.x to 4.4 so the SOAP API is much better than JIRA 3. This upgrade made it easier to import work log to JIRA because the API is upgraded a lot. If we had JIRA 5, the new JIRA REST API would be an even better option.

I have been trying to track and manage my work time for a while. Most time-tracking tools are designed for works with billable hours, such as freelance programmers or outsourcing workshops. But I think it’s also beneficial to keep time logs for other jobs. I had tried quite a few ways or tools before, none of them worked very well until I found toggle:

  • Directly log on JIRA: In this way you’re “estimating” how much time you spent after finishing a task. What I need is a “timer” to really track it, different and better. Also, it’s easy to forget to log time in JIRA. When a process brings more troubles than tangible benefits, people will tend to forget or ignore it.
  • A very simple OSX dashboard widget I can’t remember its name. It’s too simple. Features like idle detection or exporting logs are still necessary for me.
  • Harvest. A very powerful one. I used it on iPhone for a while, but found it didn’t work very well because I often forgot to stop/switch timer. “Idle detection” is actually more crucial than it looks. And Harvest is only free for 30 days.
  • JIRA worklog assistant. It seems really nice at first: seamless integration with JIRA, lots of useful features. But soon I found the Mac client crashed so often and had lots of bugs. A tool with such a bad quality won’t be accepted by the team.

Toggl is the best tool I found so far. Its client is very well designed and polished, easy to use and intuitive. It has a REST API  so I can export the log and import to JIRA easily. Toggl also has pretty nice report features, but I still want to keep all records in JIRA for maximum visiblity. And all my needs can be satisfied by Toggl free edition, sweet.

In the last, I want to clarify: the purpose of tracking time allocation is definitely not to measure “how hard you work” or “did you work 8 hours a day”, but to analyze “where are our time spent” and “how long a project/task actually takes”.

Read “JavaScript : The Good Parts”

A nice and short book. The author, Douglas Crockford, is a man who really understand why and how JavaScript was designed and evolved. So the book feels like an interesting tale told by a grandpa.

JavaScript is a language, also a system. Like every complex system, it has bad parts. The basic idea of this book is: we can turn JavaScript to a better language by “avoid using its bad parts”. This probably also applies to most systems. Actually smart people do this naturally, as long as they realize which part is good and which is bad. When bad features of a system are realized by more people (just realized, probably not understood, since bad parts are usually difficult to understand), more ppl will get around them or even invent replacement features. In this way bad features died out gradually. That’s why we can see different features in a system covering the same thing.

Another important point in this book is to keep codes human-readable. It’s easy to write machine-understandable codes, but costs much more efforts to make it easy to understand and transfer among humans. Lots of “bad parts” listed by this book are simply because they “mess codes up” more than the benefits they were designed for. An additional point is the most dangerous features are those who bring in hard-to-find bugs, not those notorious features that everyone will pay attention to.

This book is pretty short, but as the author says, it worths reading time to time.