Wordpress 2.3以后就自带tag了。不过由于使用dreamhost的方便的one-click install，导致我才发现这个新增的功能(也从来不看dashboard上的信息)。于是花了些时间看了一下并修改了自己的theme来支持tag。

看上去一切都工作了，有时间的话就给每个blog entry都加上tag。是不是应该把tag加到meta里去，以加强SEO？不过我这个丑陋的theme连h1都没有输出过，就还是不SEO了吧。 :p

主要用到以下几个新增的方法:

the_tags($prefix, $separator, $postfix); // in single page and archive page

wp_tag_cloud(); // tags page

single_tag_title(); // archive page or tag page

Just tried a little. Pretty cool.

1. Really modern IDE (based on Eclipse)
2. Zend Framework support
3. Refactory support (poor…… so far)
4. Debug and Profile
5. PHPUnit
6. PHPDoc
7. SVN and CVS
8. BIRT
9. Other Zend stuffs integration
10. WYSIWYG editor
11. FTP
12. Database

NO! I can say dev is same as Testers.

Today I just read an interesting thread. Some guy is looking for documents which mainly help to introduce the Scrum to developer.

Actually besides the Product Owner and Scrum Master, there is only one another role in Scrum. It is the “Team”! Within Scrum the team should be self-managed. In another words, there are three managers in Scrum — Product Owner, Scrum Master and the Team. And their one and only goal is achieving their commitments. The three roles do have different responsibilities, but act as a team role, the teammates in the team should share responsibilities of the same commitments. So no excuse to be blocked by specific as Dev or Tester, your goal is delivering your commitments. Dev and Tester should help each other to complete their tasks via focusing on different aspects which they are good at. Remember, your team should always act as one team, not individual team members. So never be blocked internally. Even when you think you are really blocked by your teammate, adjust youself or the team! If it’s kind of external blocking issue, ask Scrum Master for help.

But I still found one documentation which is pretty nice in that thread. “Scrum in five minutes”, http://www.softhouse.se/Uploades/Scrum_eng_webb.pdf.

沟通，无论做什么都会强调的一点。

前阶段接受过的一个英语培训中，老师说到这么一组数字。在沟通中一些方式所占的比重，且不论数字真实与否：

文字(Words)：7%

语音语调(Tone)：38%

影像(Visual Expression)：55%

从这组数字中我们可以很明显的看到文字的地位，在沟通中文字远没有想想的重要。

前几天在《User Stories Applied》一书中也看到这么一个故事，

父亲和往常一样给女儿放水洗澡，然后让女儿试一下水温。女儿试了一下告诉父亲说：“make it warm”。而父亲试了一下水温以后发现，水不但不冷，而且还比平时的水温更高。父亲思考了一会，才意识到误解了女儿的意思。虽然同样都是“Warm”这个词，但对于成年人来说就是“increase the temperature”。然而对于他女儿来说却是“Make it closer to the temperature I call warm”。

面对面的交流尚且如此，更何况写下的文字。这也是为什么agile的开发总是那么强调沟通，强调反馈。