Wednesday, September 29, 2010

推荐几个不错的网站元素链接 | FREE

1) flashmo.com
免费的Gallary,button,网站制作,直接下载修改。非常有用!

2) flashxml.net
http://www.flashxml.net/banner-rotator.html,我就是被这个banner rotator吸引住的。对会做flash的人来说,可能很简单——可是对我这种flash外行来说,这个banner简直是太好用了。只可惜还是有watermark,不过还算蛮小的,基本可以接受。

3)http://visionwidget.com/inspiration/web.html
说起来,这个网站不算是资源网站,而是“推荐”资源网站。虽然本身没有很多free的资源,但是介绍和推荐的链接大多不错。

4) flashvillage
这是个很不错的网站,很多free template都是以论坛帖子形式放出来的的,完全免费。有很多千奇百怪的创意,可是好像大多是flash的,不会用……还有一个缺点是很多template不能preview。不过网站上有一些flash教学贴,对我这种初学者来时很有用。

5) dafont.com
提供了很多好看的字体包。不过资源太多找起来也麻烦。http://visionwidget.com/resources/fonts/564-free-script-fonts-for-calligraphy.html这个链接上挑出了一些不错的样例。

暂时看到的就这么几个。以后再逐渐更新。
话说,MySpace的关闭,Gatech把毕业生踢出Prism,倒是让我又重新考虑开始折腾一下个人网站了。还好blogspot还没出问题,不过现在已经决定直接弄个web host了:www.judyzhu.com(虽然现在还是毕业前的旧网站),同时支持MSN一回,MySpace转移到wordpress。

Tuesday, September 28, 2010

很像我干的活——要注意

  CIO其实在公司就是扮演了一个沟通中转站的角色,既要对公司业务层面有着深入的了解,也要对IT建设情况了如指掌,还需要能将这二者很好的协调起来,这就对CIO的沟通能力提出了较高的要求。既要跟其他高管等非IT人员沟通IT的情况,又要与IT工作人员沟通业务层面的情况,CIO如何在沟通上存在着不足,将影响着工作的效率与推进。

  以下是CIO经常犯的10个沟通错误,CIO应尽量避免。

  过多地使用专业术语

  使用专业术语与IT部门之外的同事交流,是各层次的IT从业者最明显、最常见的错误。交流咨询公司Lundberg Media总裁Abbie Lundberg认为,CIO过多地使用术语,就像技术专家经常会假设别人也是内行,能轻易理解他所说的行话一样。

  North Star Financial公司的前任高级副总裁和CIO Craig Blad认为,过于强调一些专业术语,会使CIO和其他高管之间产生隔阂。IT咨询师、拥有CIO和CTO职业经验的Peter Kretzman认为,如果CIO总是用专业术语,会让管理层产生这样的想法:我们需要一个能让我们听懂他的话的人,这样我们才知道他究竟想要干什么。

  随便抱怨技术问题

  哈佛商学院的CIO Stephen Laster早年就犯过这样的错误。当时他和同事开了个技术讨论会,讨论数据中心遇到的问题。

  Laster回忆说:“当时我讲得过于深入,给他们留下的惟一印象就是:Stephen看来的确是遇到了大麻烦。那次会议让他们变得更加紧张。”

  Laster的老板会后告诉他,应该让其他部门的同事远离IT遇到的问题,因为这只能使他们对IT部门失去信心,而无法信任他。“问题并不在于你把这些问题拿出来谈,但你应该用我们能够理解的语言来说,并告诉我们应该做些什么。”他说。

  像销售人员一样行事

  Kretzman曾经看到,有的从业务部门成长起来的高管,在负责IT部门工作时,像对待销售人员一样对待IT员工。他们会举行一个培训会议,希望激发员工的激情,而没有意识到技术人员不会为之所动。

  “如果我这么做,那我肯定会受到嘲笑。人们会离开会议,打瞌睡,或者打开他们的笔记本电脑或黑莓手机来做其他事情。”Kretzman很有自知之明,“你必须用他们的方法来和他们打交道。”

  出言不逊

  在办公室出言不逊表面上看来并不是什么大问题,但可能导致CIO丢掉工作。

  Kretzman回忆说,曾经有个业务能力很强的CTO,在与项目经理举办的会议上说:“你们要做的就是,去跟业务部门的人说,让他们见鬼去吧。”他还说了不少比这更严重的脏话。这个CTO在9天后就离开了公司,因为人们无法接受他的行为。

  不擅长提问

  “杰出的CIO,会问一些有意义的问题,并且能认真聆听答案。”Lundberg说。这能帮CIO得到关键的信息和深刻的洞悉,加强CIO的吸引力,还能帮他们和其他部门的同事建立起良好的关系。

  “大多数IT人员不愿意问问题的原因,是因为他们害怕被人认为他们不知道答案。”Lundberg分析说。

  不懂协同作业

  CIO在技术方面应该具有相当强的自信,并且具有最佳的途径来将这些想法付诸实践。但有时候,他们却对自己的想法过于自信。他们会想:“我是CIO,我知道得最多。”但他没有意识到让别的人参与到他想法的实现中来有多么重要。

  哈佛商学院的CIO Laster说,他自己就曾经犯过类似的错误。当时他的IT部门正在考虑实施一个大平台,以及形成支撑其的架构策略。Laster认为他采用的方法是正确的,并强力推动它,而没有留给他的团队足够的时间去适应他的方法。

  “结果,因为我的忽视,我们延迟了采购时间,导致流程延期了两个月。”他说,“于是我们回顾和审视了我们所做的工作,让每个人都参与进来,最后项目圆满完成。”可见,协作非常重要,只有好的想法,而没有大家的支持是不能实现目标的。

  用恐吓方式推销想法

  Kretzman指出,在解释为什么要进行某项技术投资时,有的CIO错误地运用过于夸张或简化的言论去博得对IT不了解的业务部门的赞同。比如说,为了让管理层赞成新硬件采购计划,IT部门负责人可能会说:“如果我们不马上买10台新服务器,就活不下去了。”

  Kretzman认为,这种夸张说法会激怒业务部门,让他们感觉IT部门在向他们卖东西。他建议,参加业务会议时,CIO不应该只带着一个技术解决方案,而是列出一系列解决方案,并陈述各个方案的优缺点。他还建议CIO应该关注业务的关键影响因素,包括对财务、业务和客户的影响。

  过于依赖事实

  Lundberg指出,尽管事实是实施任何IT投资项目的先决条件,但CIO也不应该对此过分依赖。那些在公司里地位不及其他高管的CIO,经常只会依赖事实。她认为,这是一种错误,因为要打动别人,必须要有感情的投入。

  Lundberg建议CIO讲故事,让人们展开想象:“当我们想要打动别人时,是在进行一种销售行为。而销售能力是走技术路线成长起来的CIO们所缺乏的东西。”

  不会充分展示IT的价值

  每个CIO都知道,他们有责任用业务语言来描述IT的价值。但Lundberg指出,有些CIO和其他企业高管谈话时,大部分时间都在讲技术,而没有真正描述IT的价值。比如说,他们可能会说:“我们能够获得更准确的客户信息,因为我们的业务智能工具可以获取这些信息。”但是,她补充道,他们需要进一步举例解释这样的洞悉能怎样改变业务,帮助公司卖出更多产品,为客户提供更好的服务。

  Craig Blad认为,CIO如果不能很好地描述IT项目的价值,项目可能不被通过。

  滥用乏味的PPT

  “人们经常滥用PPT。”Lundberg感叹说。这包括幻灯片的数量太多,文字太多,或充斥着花哨的动画效果,呈现给人们太多信息。她认为,真正有效的PPT演示,能够让观众保持足够的注意力,完全被讲演者所传达的信息所吸引。

  Lundberg建议CIO认真考虑一下,PPT到底是不是最有效的传达信息的方式,或者是否应该另辟蹊径传达信息。例如,情景剧式的演示肯定要比单纯的PPT能给人留下更加深刻的印象。

忽然有种时曾相识的感觉。

都是水。往哪里走,都是水。

看不见路。

不能停下。哭也好怕也好,还是得走。

继续走。

Friday, September 24, 2010

Bill Gates speech: 11 rules your kids did not and will not learn in school by Kent Summers

Rule 1: Life is not fair - get used to it!

Rule 2: The world doesn't care about your self-esteem. The world will expect you to accomplish something BEFORE you feel good about yourself.

Rule 3: You will NOT make $60,000 a year right out of high school. You won't be a vice-president with a car phone until you earn both.

Rule 4: If you think your teacher is tough, wait till you get a boss.

Rule 5: Flipping burgers is not beneath your dignity. Your Grandparents had a different word for burger flipping: they called it opportunity.

Rule 6: If you mess up, it's not your parents' fault, so don't whine about your mistakes, learn from them.

Rule 7: Before you were born, your parents weren't as boring as they are now. They got that way from paying your bills, cleaning your clothes and listening to you talk about how cool you thought you were. So before you save the rain forest from the parasites of your parent's generation, try delousing the closet in your own room.

Rule 8: Your school may have done away with winners and losers, but life HAS NOT. In some schools, they have abolished failing grades and they'll give you as MANY TIMES as you want to get the right answer. This doesn't bear the slightest resemblance to ANYTHING in real life.

Rule 9: Life is not divided into semesters. You don't get summers off and very few employers are interested in helping you FIND YOURSELF. Do that on your own time.

Rule 10: Television is NOT real life. In real life people actually have to leave the coffee shop and go to jobs.

Rule 11: Be nice to nerds. Chances are you'll end up working for one.

Sunday, September 19, 2010

W3C recommendation

In accord with the W3C Process Document, a Recommendation progresses through several maturity levels.

Working Draft (WD)

At the working draft level, the standard is published for review by "the community". A WD document is the first form of a standard that is publicly available. Commentary by virtually anyone is accepted, though no promises are made with regard to action on any particular element of said commentary.

At this stage, the standard document may likely have significant differences from its final form. As such, any who implement WD standards should be ready to significantly modify their implementations as the standard matures.

Candidate Recommendation (CR)

A candidate recommendation is a version of the standard that is more firm than the WD. At this point, the group responsible for the standard is satisfied that the standard does what is needed of it. The purpose of the CR is to elicit aid from the development community as to how implementable the standard is.

The standard document may change further, but at this point, significant features are mostly locked. The design of those features can still change due to feedback from implementors.

Proposed Recommendation (PR)

A proposed recommendation is the version of the standard that has passed the prior two levels. The users of said standard have had their say, and the implementors of the standard have likewise had a chance at providing input. At this stage, the document has been submitted to the W3C Advisory Council for final approval.

While this step is important, it rarely causes any significant changes to a standard as it passes to the next phase.

W3C Recommendation (REC)


This is the most mature stage of development. At this point, the standard has undergone extensive review and testing, under both theoretical and practical conditions. This standard is now endorsed by the W3C as a standard for wide deployment in its problem domain.

Later revisions
Main article: World Wide Web Consortium

A Recommendation may be updated by separately-published Errata until enough substantial edits accumulate, at which time a new edition of the Recommendation may be produced (e.g., XML is now in its fifth edition). W3C also publishes various kinds of informative Notes which are not intended to be treated as standards.