| Dawei: profilDawei's SpaceFotografieBlogSeznamy |  Nástroje  Nápověda |
|
10.1.2008 雨夜又是驱车在雨夜
黑色的马路
昏暗的街灯
望着那看不见的地平线
二十岁时装出来的沧桑
如今变成了笑脸 还是一颗赤子之心没有华丽的语言 一天又一天
一年又一年
理想看似渺茫
却从未泯灭
一年又一年
一天又一天
我在寻找着幸福
不是时间，不是金钱
我只要一双“美丽的”慧眼 31.12.2007 拥抱20082007年是个多灾多难的一年。先后遭遇10年不遇的大劫难一次、中小劫难数次。感叹自己并没有被打倒、一蹶不振，反而知耻后勇、愈战愈猛。首先自我表扬一下（鼓掌）。塞翁失马，焉知非福？古老智慧绝非阿Q精神。如若10年前高考我如愿所偿上了第一志愿核物理系，而不是稀里糊涂的学上了计算机，十有八九没有现在处境好。当时可是万念俱灰啊，回头想想老天给我安排了最好的选择。劫难亦或偏得许多年后才看得清。但至少这丰富的07人生经历，俺是先整到手了。挺好！
公司里的事情，07年突飞猛进。FaceBook和微软的第一个项目就是基于我来到微软后第一个独立设计的项目。虽然仍是Alpha版本，每日已经有过百万的请求。我和同事打赌，2年后新的服务器占有50%请求。为此我还赌了一美元（争取用人民币结算）。最感谢的还是我的老板。支持我从零开始设计新的架构，我把80%程序重写了一遍。很感激他这么地信任我，我自己也捏了一把汗。创造一个新世界，比改变旧世界要简单很多。08年，我们要对旧的服务器架构进行一次大手术，很可能我主刀。这关乎到Windows Live未来，这一点和老板达成共识，不忽悠。另外国内，要正式运作酝酿近1年半的“二次革命”。想一想6年前的一次革命，不成不怕，国父十次革命才推翻满清。就算不成，俺还有8次机会呢。
俗话说：否极泰来。我不奢求运气会变得多好，只要正常发挥对得起我实实在在的努力就满足了。在2007年最后一天，对着庄严的Windows Live Spaces誓师：有信心，有能力同时打胜两场战争，没有困难创造困难也要赢！
有人怕黑，实际上是害怕看不见的东西。我不怕黑，但坦白说，我会害怕看不见的未来……但是时间在嘀嗒，唯一能做的就是热情洋溢的拥抱2008！08年将是人生重要一步。成也罢，败也罢。
报告完毕，祝大家新年快乐！ 22.12.2007 Identities, Contact and the Real Person OfflinePosted at http://blogs.msdn.com/dawei
“Miscommunication” Scenarios in Daily lifeI want to start with some stories to illustrate miscommunication examples that happen in the real life. I am sorry that I have to mess up Bob and Jill’s life again. They are my favorite use case actor and actress since when I was in Pittsburgh. Scenario 1: Bob is preparing a Xmas party. He is trying to call his old friend Jill’s cell phone +1(425)555-5555. However, Jill changed her cell phone a month ago. Then Bob tries Jill’s office number +1(425)666-6666. Since it is Friday 6PM, no one picks up the phone. Then Bob dials Jill’s home phone +1(425)777-7777, still no luck. So he just left a voice mail. Scenario 2: Thanks to the new technology and the Internet! Bob is using Windows Live Events to create a party invitation to all his friends. He found Jill’s Gmail account jill@gmail.com and sent her the invitation as well. When Jill returned the call on Monday, Bob realized Jill is only checking Gmail account once a month. As Jill suggested, Bob sends invitation again to Jill’s Hotmail account: jill@hotmail.com Scenario 3: The party went well. Bob took quite some photos of Jill and shared them on Windows Live SkyDrive with Jill by granting access permission to jill@hotmail.com. Jill just got a new Windows Live account jill@live.com and starts using it every day. However, she has to log back to jill@hotmail.com to view those photos. Scenario 4: Jill is very upset after seeing the photos, as they are not as pretty as she had thought. She decided to block Bob’s from Windows Live Messenger for a while. Unfortunately, Bob found Jill was trying to block him because Jill has two Messenger accounts for Bob bob@msn.com and bob@hotmail.com, and she forgot to block both. Have you seen some glitch here? What’s the root cause? Identity-based Communication is ProblematicBefore we continue, I want to clarify the definition of identity. I do not want to start a philosophical discussion. Rather I want to put it in a practical way, as long as you know what I am trying to say. It is good. Identity is anything that we can use to distinctively identify an offline person. Identify can be: phones, emails, IM addresses, physical addresses. It can even be devices exclusively owned by the person. As long as we can uniquely identify the device, we can consider the device is an extension of the person. The miscommunications scenarios given above are Identity-based communication pattern. It is problematic for two fundamental reasons: 1. Identities change frequently. People change phone number, email address and move to different cities. Communication channel will be broken as identity changes. 2. Identities are swarming. You can easily enumerate 10+ identities that people can reach you. The more identities you have, and the more complicated the communication pattern will be. Identity-based communication is legacy from old days for ages. Unfortunately, the legacy constraint is too strong for us to break through. Even for new technologies, we still build the systems in the identity-based way, which is exactly what Bob and Jill have experienced. Fortunately, we realize the problem and making progresses to change the situation. A Better Solution by Linking IdentitiesThere are many good examples of improving identity-based solution by linking identities. Our life is getting better, even though sometime we do not realize what kind of problems those solutions are trying to resolve. Example 1: Google Grand Central provides a unified phone number solution. For example, in scenario 1, Bob just dial one number, all Jill’s phones will ring until one of them is picked up. Therefore, Bob just need to remember one phone number, rather than three phone numbers to reach Jill. It is an example of linking phone identities. Example 2: Windows Live Linked ID provides a solution to easily switch between Windows Live IDs. Therefore, in scenario 2, Jill can switch from jill@live.com to jill@hotmail.com without login back and forth. It is an example of linking email identities. Example 3: Windows Live Messenger provides a solution to unify Email and IM Address. People might be confused: “hey, what are you talking about?” Yep, one simple fact that people do not realize is that: “Email is email, and IM is IM”. Email and IM are totally different communication channels. They happen to have the same address does not mean they are the same thing. For example, in China, QQ is IM, but it is not email. Another example, IM with @passport.com domain looks like email but there is no mail box associated with that domain. (Emails sent to @passport.com will be rejected.) The fact that many IM systems using email as IM address is a great example of linking between IM identity and Email identity. Example 4: Many web sites provide functionality of “register my computer”. So, next time user does not have to manually login again. It is an example of linking the user’s device identity with the user’s account identity. You can also consider finger print reader as a similar example as well. Example 5: There is another great example of linking email identity and phone identity. However, I do not think I can talk about it now. Linking identities makes our life better. However it is still not the ultimate solution as it did not resolve those two fundamental problems of identity-based communication: identities are frequently changed and swarming. Contact-based Communication – One Level Abstraction and the Ultimate SolutionLet’s think over about the first thing of software engineering – requirement elicitation. And let’s go back to scenarios between Bob and Jill, and figure out what are the real requirements. Scenario 1: Bob is trying to reach Jill via phone. Bob does NOT care +1(425)555-5555 or +1(425)666-6666. Scenario 2: Bob is sending Jill invitation via email. Bob does NOT care jill@gmail.com or jill@hotmail.com. Scenario 3: Bob is sharing photo with Jill. Bob does NOT care jill@hotmail.com or jill@live.com. Scenario 4: Jill is blocking Bob’s IM address. Jill does NOT care bob@hotmail.com or bob@msn.com. We realize one thing: people are only caring about the real person, rather than his/her identities. When bringing the business online, what we really need is the one-to-one online abstraction of the offline person, rather than the person’s online identities. For the one-to-one online abstraction thing, we reuse and redefine the concept of contact. Contact is the one-to-one online abstraction of the offline person. It is the collection of the person’s online identities. After clarifying the definition of identities and contacts, the ultimate communication solution can be described in three phases. Please note: we consider any interactions between two people (requester and recipient) are within communication problem domain, which include email, phone, IM, mailing, and even permission granting and revoking etc. 1. Communication endpoints (requesters and recipients) should be contacts rather than identities. 2. Requester decides communication channel. 3. Recipient decides the binding of his/her identities and communication channels. For example, Bob decides sending invitation to Jill’s personal email. Jill decides which email address (jill@gmail.com or jill@hotmail.com) is used as her personal email. ConclusionWhen the offline people come online, they are shielding behind their identities. Over years, software systems are designed based on people’s online identities. Due to the fundamental weakness of identity, those systems are running into problem when trying to resolve communication problems. Ultimately, we need to shift the design principle from identity-based to contact-based solution, which is one level up abstraction and one-to-one mapping of the real person offline. 1.11.2007 感受《在路上》这次回去对我触动最大的就是这首《赢在中国》的主题曲《在路上》。每一句都深深触动着我。
深深地祝福为了理想与抱负不懈努力的兄弟们！ 《在路上》 那一天，我不得已上路 |
|
|
