Wednesday, February 4, 2009
10-promising-free-web-analytics-tools
Friday, September 26, 2008
Official Google Blog: Project 10^100
I few hours ago, I posted an idea to Google's project 10^100.
It's a simple idea but I think it's hard to turn to reality:
1. build a web community
2. people can come to this community and write down what they like and what's their style.
3. Match via following ways
a. System match the people together via their style and their preferences.
b. People can write down their style and where they will show up in which day
4. System can give them some symbols to those people who might meet together(in the subway or shopping mall, etc)
5. People takes photos or leave messages for their meets.
Source of idea: more and more people feel alone in the modern cities, we found a way for them to meet similar people and make friends each other, or each just for funs.
Imaging:
100 cars will meet together in a weekend 3 PM at Wangfujing Street, and they wear the same color clothes or wear same brand hats.
Give people a chance to know you, give people a chance to talk to new face friends. And then keep in touch in a community.
I think this will solve many social or mentality problems of people.
Hope project 1-^100 can find more funny ideas from people.
Monday, September 22, 2008
Ajaxian » What if we didn’t lump all “accessibility” requirements together?
This is the similar question with my last post.
What if we didn't have all "accessibility, usability and availability, etc" requirements?
Using prototypes to demostrate your design is okay, but it may need more involvement of user.
It's easy to demo or create a new page, but it's hard to define the BEST.
80/20 policy is used here. And we need user's agreement on the requirements defined.
This is the key.
InfoQ: How to Handle Unfinished Stories?
In Chris Sims' post, he summarized the experiences of David Starr of dealing with unfinished Stories.
One way to track progress is to give 80% of the point value of the story to the team for the current sprint. At first blush, this approach seems to accurately reflect the state of things, and may help keep the team's recorded velocity from varying up and down, sprint to sprint. It also has a certain amount 'feel good' value for the team. However, this approach has significant risk. The story is not verifiably done and the amount of time and effort that will be needed to get to 'done' isn't really known.
A second possibility is to split the story into smaller stories and take credit for the ones that can be considered done. To the extent that some of the smaller stories are truly 'done', this can reduce the risk associated with the 'partial credit' approach. It also allows the product owner to make some decisions about the relative importance of the unfinished stories.
In our projects, we seldom met the same issue. Most of the time, we can finish the stories on time, but sometimes we will also find that we were getting trouble on a certain user story. Most of the time, the issue is, the user story is developed, but it's not the same as expected of user. It's a common issue that user doesn't really aware of what they need. But in a formal development team, we must count our efforts so that we can really know our TRUE velocity in a certain cycle. In this case, usually we will adopt the second approach of David. We will split the user story into smaller user stories, and keep higher priority for unfinished user story in the next iteration.
But here comes my question, if the user story is finished, but we found it's not perfect enough for user, what should we do?
To satisfy user is one of the most important thing we should be aware of in an agile project. But most of the time, user only say "I need something but I don't know what it exactly looks like, I need your help". You can not exactly define what's the final quality requirement of user. So, you will get the feedback like "Yes, it works, but I think there are something we can improve, but I don't know where they are...".
How you deal with this in your experiences?
Friday, September 19, 2008
我的9型人格
| 第三型 | 成就者、事業型、成就型、實踐型 14% |
| 第八型 | 領袖型、能力型、挑戰者、保護者、權威型 13% |
| 第七型 | 快樂主義型、豐富型、活躍型、創造可能者、享樂型 12% |
| 第二型 | 助人者、全愛型、助人型、成就他人者、博愛型 12% |
| 第五型 | 智慧型、觀察者、思想型、理性分析者、思考型 11% |
| 第六型 | 忠誠型、忠誠型、尋找安全者、謹慎型 11% |
| 第一型 | 完美主義者、完美型、改革者、改進型、秩序大使 10% |
| 第九型 | 和平型、和平者、和諧型、維持和諧者 10% |
| 第四型 | 藝術型、浪漫者、自我型、憑感覺者 8% |
- 第一型
- 第二型
- 第三型
- 第四型
- 第五型
- 第六型
- 第七型
- 第八型
- 第九型
你精力充沛,總是動力過人,因為你有很強的爭勝慾望。你喜歡接受挑戰,會把你自己的價值與成就連成一線。成就型的你會全心全意去追求一個目標,因為你相信「天下沒有不可能的事」。動力十足的你,適合做領袖帶領其他人。
主要特徵:- 看重自己的表現和成就。
- 講究效率。
- 喜歡競爭,避免失敗。
- 相信愛情來自你能提供甚麼,而不在於你是誰。
- 只關注事物積極的方面,不理會消極負面的信息。
- 重視效率、比賽、贏。
- 難以瞭解個人的感覺。在工作的時候把感情放到了一邊。
- 為爭取認可而打造有利形象。公眾形象屬於社會高層人物。
- 在真正自我和工作角色之間會產生困惑。
- 通過集合思維的方式集中注意力,通過多渠道來尋找問題的答案。
- 能夠下意識地調整自我形象,以為調整地形象就是個人的真我。
Monday, August 25, 2008
跨国公司 领导人培养的经典案例 - 挂树上的蚂蚱 - gyqdf - 和讯博客
摩托罗拉的领导力4E:
Envision前瞻,即要有远见与创新精神;
Execute执行,要迅速行动和实施,以结果为导向;
Energize激励,要能够激励自己和领导团队达到目标;
Edge果断,在复杂的情境中勇于决策,敢于冒险。
Sunday, August 17, 2008
成功者十三个价值连城的习惯-转自世界经理人社区
http://forum.ceconline.com/FORUM_POST_900001_900008_892142_0.HTM?sources=pose_20080811_my成功是一种习惯,失败也是一种习惯。你的习惯无法改变,但可以用好的习惯来替代。成功很简单,只要简单的事情重复做,养成习惯,如此而已。 以下是成功者十三个价值连城的习惯,我们称之为"百万元的习惯"。
习惯一:成功者清楚地了解他做每一件事情的目的。
成功者虽重视事情的结果,但更重视事情的目的,而目的的清楚则有助于他达到结果并且享受过程;
习惯二:成功者下决定迅速果断,之后若要改变决定,则慎思熟虑。
一般人经常在下决定时优柔寡断,决定之后却有轻易更改;成功者之所以能迅速下决定,因为他十分清楚自己的价值层级和信念,了解事情的轻重缓急,因此能有系统的处理;
习惯三:成功者具有极佳的倾听能力。
倾听并非是去听对方说的话,而是去听对方话中的意思。倾听的技巧包括:一、倾听时不打断对方的谈话;二、把对方的话听完;三、即使不需要记录,你都可以听出来对方的意思;四、把所有的问题记在脑海,等对方说完后在一同发问。
习惯四:成功者设定"当日计划"。
成功者在前一天晚上或一早就会把当天要处理的事情全部列出来,并依照重要性分配时间。他管理事情而非管理时间。
习惯五:写日记。 写日记的法则:一、保持弹性,重表达思想,而不用太多严格规则;二、持续;三、用来设计你的生命价值和中心思想;四、记录每件事情的差异化;五、记录特殊时刻及事件;六、解决问题;七、学习问更好的问题;八、在日记上写下自己的宣言;九、把每日写下的东西在月底复习;十、深刻自己的记忆和经验。
习惯六:做喜欢的事。
习惯七:勤于练习基本动作。
习惯八:运用自我暗示的力量。
自我暗示就是把目标用强烈语气不断念出声音,告诉自己,让潜意识无法分辨真假,因此相信它。
习惯九:运用冥想的技巧。
当你不断想象自己达成目标是情景,潜意识会引导身体作出那些效果。
习惯十:保持体力或创造更多精力。
习惯十一:成功者人生的目的通常超越自我,立志为大多数人贡献自己的力量。
使命而非为金钱工作。
习惯十二:成功者有系统。
成功者都有一套方法来整理思想、行为,因此能不断实践在自己身上,并且教导别人。
习惯十三:成功者找方法,失败者找理由。
成功者愿意做失败者不愿意做的事情。
如果你能断采取以上做法,进而养成习惯的话,这些习惯对你可能不只是百万元的价值,更可能带给你金钱和心中的富有