呵呵，网上看到软件学院的新年祝词，感觉挺有意思，转帖在这里

祝大家在新年里
男生象Oracle般健壮
女生象Vista般漂亮
桃花运象IE中毒般频繁
钱包如Gmail容量般壮大
升职速度赶上微软打补丁
被男/女生追的像木马一样猖獗
生活像重装系统后一样幸福

周末毕豪影院为您播出

饮食男女：

卧虎藏龙：

今天从CSDN看到：

              在技术上专注一点
              在关系上热情一点
              在大事上强硬一点
              在老板那忽悠一点
              在同事那坦诚一点

这可能是怀旧的一种形式。

地球2100：

有些人的脑子是不是进屎了！！想访问Python 3.1的文档也要我走代理！！

周末毕豪影院为您播出：

9：

http://kankan.xunlei.com/vod/movie/57/57205.shtml

世界是平的 Outsourced：

女生篇(90s) + 男生篇(30s)

[video]

女生篇(30s)：

[video]

她是我最好的姐妹

嗯… 可后来… 一个男生让我们俩分开了

(撕) 你不是我的姐妹~

没想到十年后，她会在人人网上找我

十年了我终于把这张照片，粘(nián)好了，呵…

(吸)

找回你曾经的真情，(吸)上人人网

男生篇(30s):

[video]

我当年要是没有他，我的脚就废了

啊~ 啊~~ 啊~~~

背着我到医院，背着我回家… 一直就那么背着

毕业后就，没有跟他联系了

我没想到他在人人网上找到我了

都没来得及跟他说声谢谢

好兄弟，不用说

找回(呵呵呵呵)你曾经的真情，上人人网

周末毕豪影院为您播出：

District 9：

http://kankan.xunlei.com/vod/movie/46/46515.shtml

尼罗河上的惨案：

大李小李和老李：

这个短片以前看过，据说是“刺激美国人反思教育挑战”的。但是看过的人都会有些启发。

[video]

墙把youtube挡在外面的作用开始显现了，其一就是养活了youku和土豆之类国内视频网站。但是这着实不方便，让人感觉非常不爽，比如公司或者一些大学的技术会议或者lecture的视频，第一时间都是在youtube上发布，等相同的视频出现在youku上不知道是什么时候了，有些甚至根本就不会出在现国内的视频网站上。而国内视频网站的视频内容更多的是些娱乐方面的东西…

这墙简单的分割带来的影响可不是简单的事情。作为一群在中国做墙的人，你们能否让自己的工作看上去有些技术含量。你们做了这么多年墙了，技术上总要有所发展了吧。现在这种一股脑把一个网站挡掉的方式简单粗暴得像城管，难道你们想把自己和城管归为一类人么？说这些话时我不知道在向谁说，但我希望你们能够看到。

国安终于夺冠了……

上半场

下半场

LRC歌词来自：http://lrc.aspxp.net/lrc.asp?id=267482&id1=244699&t=lrc&ac=dl

最近有需要了解一IA 方面的东西。最开始从字面的理解，我感觉IA应该是和TIBCO现在所做的东西是很符合的。即解决企业内部甚至是企业间不同系统的信息如何组织的问题。但是查阅了些资料，却发现，IA目前的应用似乎更多地集中在图书馆或者Web设计方面。这让我感到有些不爽。

以下内容转自：http://articles.techrepublic.com.com/5100-22_11-5074224.html

10 questions about information architecture

by Guest Contributor | Sep 29, 2003 7:22:00 PM

Takeaway: Very few people understand exactly what information architects do and why we need them in Web design. CNET Builder.com answers your top 10 questions about IA and information architects: who they are, how they get there, what they do, and why in the Web world.

By Shel Kimen

Information architecture. IA. Industry buzzwords? Fancy degrees? Web firms can't hire information architects fast enough, but, while the field has been around and growing for years in software, engineering, and library science, very few people understand exactly what information architects do and why we need them in Web design. And we do need them.

With today's complex, superfly, dynamically driven database Web sites and networks, information architects have become critical to--if not the cornerstone of--most large Web design projects. Blending the technical and the visual with a keen sense for organizational structures and usability, IA is a multidimensional field that puts place in space. Knowing the demand, CNET Builder.com answers your top 10 questions about IA and information architects: who they are, how they get there, what they do, and why in the Web world.

1. What is information architecture?
At its most basic, information architecture is the construction of a structure or the organization of information. In a library, for example, information architecture is a combination of the catalog system and the physical design of the building that holds the books. On the Web, information architecture is a combination of organizing a site's content into categories and creating an interface to support those categories. It stems from traditional architecture, which is made up of architectural programming and architectural planning.

Traditional architectural programming
The traditional discipline of architecture, which is the design of buildings and physical space, involves problem-making and problem-solving. It requires a thoughtful analysis (programming) to manifest a thoughtful synthesis (design).

Architectural programming is an objective approach to understanding the nature of the task so that a specific problem can be identified as something for space planners and designers to solve. The programmer establishes goals, collects and analyzes facts, uncovers and tests concepts, determines needs, and states the problem. The programmer's responsibilities include: client interviews, research and understanding of emerging technologies, reviews of case studies, budget planning, scheduling long-term deadlines, anticipating the future, and formulating functional requirements. The research results in a program document that specifically outlines the limits of the project and any unique problems.

Traditional architectural planning
Between the analysis and synthesis stages exists what William Pena, author ofProblem Seeking: An Architectural Programming Primer, calls the synthesis gap. In large projects, a space planner manages this gap by taking the program document and defining the space to be designed, aligning the rooms, and assigning priorities to the interior structural elements. The space planner works with both the programmer and the designer to develop a structure that accommodates the function as well as the form. (Although sometimes, depending on the firm, the space planner is also the programmer or designer.)

In Web design, a person who helps develop programs and also plans is an information architect. The information architect maps the entire structure of the site and organizes the positioning of pages within sections, developing a functional and intuitive plan to get the user from point A to point B on the path of least resistance.

2. How do information architects fit into a Web team?
Some Web design firms have highly compartmentalized departments that separate problem finders from problem planners and problem synthesizers, but flexibility is the key to success. Information architects should meet with clients to help define a project's scope, as well as plot the path to meet the objective and work with the designers and technologists to develop engaging and intuitive visual interfaces. It is important for them to be present during all three phases and to get a client's objectives firsthand. Poor secondhand interpretations can be a project's death. It isn't that managers are inept at translating clients desires, but architects have special architectural questions that a business manager or producer might not be able to intuit.

It's also important for information architects to work closely with visual designers, helping to maintain the balance between form and function. Design effects architecture as much as architecture effects design. Working in a vacuum of compartmentalized skills isn't good for anyone, and it's definitely not good for the end result. Information architects also bridge architecture with development and work with technologists, database engineers, and HTML coders.

Most of the larger Web firms, such as Organic, Razorfish, Studio Archetype, andAgency, have established IA departments operating under various names. Some firms base their definitions on software design, while others take a more traditional, physical structure architecture approach. It's impossible to say what works best, because it's relative to the overall environment and work process. In general, it's good to take elements of software design, library science, traditional architecture, and industrial design and sift through for the elements that most apply to Web design and its nuances.

3. What do architects create for clients?
If there were a template or system for what information architects need to prepare, no one would need them. While there are certain key deliverables that most projects require, the work is most often determined on a case-by-case basis dependent on scope and function. Presentation is as much about showing information as it is about showing information in a way that is understandable to each client's specific Web knowledge and thought process. Some people prefer paper, while others need to see things clicking and moving in order to make sense of it.

Some of the basic deliverables include:

Site Maps: Maps reflect navigation and main content buckets. They are usually constructed to look like flowcharts and show how users navigate from one section to another.

Content Maps: Detailed maps that show what exists on each page and how content on some pages interacts with content on other pages.

Page Schematics: Black and white line drawings or block diagrams to hand off to a visual designer. These may, or may not, reflect layout and are used mostly to inform the designer and the client exactly what information, links, content, promotional space, and navigation will be on every page of the site. Schematics also help illustrate priority.

Text-Based Outlines: Sometimes information architects want to show architecture as indented text outlines and lists.

Interactive, Semi-Functional Prototyping: In some cases, information architects are responsible for outlining or storyboarding functional prototypes, and in others they actually build prototypes with HTML, Flash, Director, or PowerPoint.

Anyone who has seen the effects of unplanned projects--Web or otherwise--knows why it is important to have a plan before starting to build. Some clients don't understand the expense--and professional information architects are expensive. Also, due to the complex nature of information architects' work--representing sites with thousands of pages on 11-by-17 pieces of paper and presentation boards, director prototypes, and HTML schematics, for example--clients are sometimes confused and unable to see the value. It's important for any company that builds information architecture into its structure to support that structure by educating clients on its value. It's the responsibility of everyone on the team to help the client understand why every member is there.

4. How do architects evaluate or design a site?
First, even before evaluating an existing site for architectural improvements, it's extremely important to find out who's using it, who's building it, and what its goals are. Maybe the hardest part of information architecture is to help identify a focus--a necessary component of intuitive form and function. But after focusing, evaluation is all about anticipated user paths, logical process flows, and determining how to balance efficiency with ease of use. Good, consistent information architecture will help users build relationships and trust with the technology and product. So, a good place to start is to look for the ways sites are, and are not, consistent.

When designing a new site, it's always best to start with all the pieces, though this is seldom the case. You'll probably be hard-pressed to find a client who didn't change their minds half a dozen times over three phases of project architecture. And architects can change their minds because it is often difficult to predict all the pieces beforehand. It is the responsibility of the design firm and architect to ask the right questions, and it's client's responsibility to understand what they are trying to build.

Architecture can and should be an extremely collaborative and iterative process, which evolves somewhat organically in as much structure that can be defined up-front as possible. Anything an IA can do to ask as many questions and get as many answers up-front will ultimately help the process. Architects also need to focus on who will be using the site, strategic and business goals, key usability principals, technical constraints, and future needs.

5. What kinds of IA problems are difficult to solve?
The latest Web site trends all point to scaleable, personalized, and customizable portals with dynamic content, which usually involves a mix of onsite content creation and third-party vendors. Integrating the complexity of these requirements into a single user-friendly interface is difficult at best.

• Scaleable is a polite way to say no one knows exactly what content will be included, so the site needs to be flexible to expand to house unknown amounts and types of information.
• Personalization requires an intelligent back-end to filter demographic information and track user preferences in order to provide content that is relevant to an individual user.
• Customization, on the other hand, is what users do to set their own preferences for a site experience. Building interfaces that are modular enough for a user to customize is extremely difficult, and setting a structure so that a user can select what he or she wants is even more difficult.
• Dynamic Content is another tricky one because it mandates that content will be produced on the fly, based on any number of parameters, including copy length. Since the proliferation of the portal, sites have begun to aggregate content (collect it from other sites), which presents further design and architecture issues: Whose server holds the content? Who is responsible for third-party design and interface? And how are the partner sites effected when third-party providers change their service offerings?

In addition to these difficulties, there are standard issues, such as understanding--and defining--the target audience, determining how much and what type of information should be on a page, knowing when it's important to lean more toward visual cues (MSNBC) or more toward text (Yahoo), and choosing a content-based or contextual navigation system.

6. What software do architects use and need?
Unfortunately, the perfect tool hasn't been invented yet. There seems to be an abundance of tools for software architecture that are suitable, but they aren't necessarily great for presentation. And there are a few Web-specific tools that don't come close to fully demonstrating the complexity of a dynamic, contextualized navigation system.

However, the word on the street is that Adobe has heard the information architects' cries and is working fast and furious to produce a tool that gives them the best of precision layout and quick drag and drop objects. Until then, other options include Dreamweaver, Photoshop, and Visio, but ultimately it depends on what type of document you are trying to make. A versatile suite of tools is the best way to go for now.

7. Are there evolving standards for IA?
Like any discipline, industry standards set the pace, for good or bad, for most mainstream development. Some of the more common standards for information architecture revolve around navigation, transaction processes, and link use.

Structural Navigation
Most Web surfers have experienced what designers call the inverse L, which is essentially a navigation system that runs top-level categories--or buckets--horizontally across the top of the screen with secondary and tertiary links listed down the left side. Another standard is a horizontal tabbed metaphor, which has two--sometimes three--layers of links that are stacked. Clicking one of the horizontal links reveals a second row of horizontal links that relate to the clicked item. While it's important to break from these standards, it's also important to note that this is what people have gotten used to, and deviations are sometimes extremely confusing--even if they offer better solutions.

Financial Transactions
Transactions that involve the exchange or transference of funds tend to involve at least three steps: submit, verify, and confirmation of order received. The middle step, verify, is usually a page that shows the user what s/he has just submitted. It is a good idea tonot allow users to make changes on the verify page but to send them to an edit screen instead. After the edit screen, they will see a new verify screen. Allowing users to make changes on a verify screen increases the margin for error. Removing or mistyping even a single number in a financial transaction is easy to do and potentially disastrous.

Redundant Links
It has been proven that people like to click, and when users are confused, they start scanning pages for whatever clickable links they can find. This is why sites such asAmazon.com have so much redundancy. In some cases, there are as many as three different links on one page to a single book or article somewhere else on the site. Some of these links are graphic, some are text, some are mixed into content areas, and others are highlighted on the side. No matter how perfect a site architecture may seem, because we all interpret information in different ways, it is important to be as inclusive as possible and provide as many points of entry into content that will fit on a screen without cluttering it.

8. How does usability relate to IA?
Usability testing ranges from observing how users react to color palettes to timing how long it takes someone to find a log out button. Sometimes testing is one-on-one, with a moderator asking an individual tester to go through the process of using a Web site--asking questions along the way about what they like and don't like, what is easy and difficult, and how it could be improved. Other times it consists of 10 to 20 person focus groups that also work with a moderator to determine preferences of target audiences and look at big picture issues, such as color treatment and content needs.

Some firms employ entirely separate departments for usability, while others look to information architects for this skill. It's a logical connection because IAs are responsible for making it easy it to find information and create most products with a focus on user-centered design (thinking of the user first). But even if they aren't usability experts, IAs usually think about usability testing as they are planning the site structure. They keep notes about what might be confusing and design prototypes specifically for user testing in order to isolate issues in navigation, process, and understandability.

Basic Rules for Usability Test Scripts
While there are entire books on usability test script writing, the best rule is to keep it simple and straightforward. We try to keep questions as objective as possible. For example, instead of asking, "Was it easy to use this site?" we would ask, "How would you rate using this site?" with check boxes for Very Easy, Easy, Not Easy or Difficult,Difficult, and Very Difficult. Five is a good number for choices, leaving room for a neutral response. It's good to ask questions with one word answers as well as request that testers write out some comments in their own words, as they often suggest ideas and feelings that site creators and project managers never imagined related to their product. A good book to help understand usability testing is Handbook of Usability Testing by Jeffrey Rubin, and some good web sites include:

IBM Ease of Use Web site--User Centered Design
An outstanding look at the process and concept of user-centered design. While it won't go very deep, it will give a good overview of the process of design as it applies to human-web interaction.

Alert Box
Current Issues in Web Usability, a biweekly column by Dr. Jakob Nielsen, principal, Nielsen Norman Group, covers everything from bandwidth issues to micropayments.

9. How do I become an information architect?
The best way to find a job in information architecture is to look at the Web sites of companies that produce work you admire. If the company doesn't have an IA department, it may be developing one, so you could get in early if you contact them.

If the company already knows that information architects are important to the design process, chances are they are probably on the hunt for qualified people because there are more positions available than people applying. Most large Web design and software design companies hire architects, as do consulting firms, banks, insurance companies, and public relation agencies. Basically, anyone who runs a large Web site, designs large Web sites, or hires people to design large Web sites has the need for an information architect.

The Skills You Need
Attention to detail and a strong sense of organization are the most obvious skill requirements for a position in IA. It isn't so important how one organizes information so much as that the organization is consistent. Information architects require strong logic and analytic skills, as well as the ability to ask appropriate questions and communicate effectively to a broad range of people: designers, executives, artists, marketers, producers, and technical staff. Information architects also need to be able to conceptualize the abstract and manufacture the concrete to explain it.

The Schools
Carnegie Mellon University has some excellent programs: Communication Planning and Design (CPD) and Information Design (ID) offer master of design degrees, and there's also a master of arts degree with emphasis on writing. Both programs lead to information architecture depending on the way a student structures coursework.

Similarly, Rennessler Polytechnic Institute offers a master in communications, a master in interactive arts, and a graduate certificate in human computer interaction with emphases in writing, design, or technology. New York University offers an Interactive Telecommunications Program and has sent dozens of people into information and interface design careers in the last few years. The program has traditional information technology offerings (Introduction to Computational Media and Elements of Visual Language) as well as flexible build-your-own theoretical studies (New Media and Interpersonal Behavior and Information Contours).

That said, any school that offers strong computer science, design, and writing programs will be able to build a liberal arts program in information architecture. The University of California at Berkeley, the Massachusetts Institute of Technology, University of Illinois, and Stanford University are all great places to start.

If you want to read more about information architecture, you can try these books:

• Envisioning Information, Visual Display of Quantitative Information, and Visual Explanations by Edward R. Tufte
• Information Graphics by Robert L. Harris
• Information Architects by Richard Wurman
• Handbook of Usability Testing by Jeffrey Rubin
• The Art of Human-Computer Interface Design edited by Brenda Laurel
• About Face by Alan Cooper

10. What is the future of IA in Web design?
In the immediate future, information architecture will have more room for creativity because more Web sites may stray from a standardized navigation system and a consistent toolbar on every page.

Looking further into the future and watching the portal trend, information architecture might not only be about architecting individual Web sites, it also will be about architecting massive networks, and even cities. In any case: think big. Information architecture is soon going to be about architecting customizable and personalized views of the entire Internet, along with entirely new business and social models to go with it.

The world will need a lot more information architects over the next few years.

Shel Kimen is an information designer for Razorfish, Inc., New York, a strategic digital communications company. She has been online for a very long time and holds a B.A. in human environment and design with emphasis on architectural theory and planning.

试用了google wave。感觉如牧牧兄所说，基本上是个大聊天室和bbs的混合体。是一个复杂的聊天软件。而且可能因为很多快捷键不知道，总要用鼠标点来点去，感觉用起来有点累。形式貌似自由，但是带来的是混乱，或者说不正确地使用会比较容易引入混乱。一个topic下参与讨论的人越多越混乱。但是可以看到google意识到这个问题，加了很多小功能来帮助理清一个topic下的层次。大的功能上目前比较单一。但是还是比较期待wave的后续发展。

结合之前漏出来的有关google os的内容，感觉wave里有些google os的影子。从wave的组织形式上看，好像可以看出一个类似文件系统的雏形。个人认为好像和IBM的Lotus的nsf组织方式比较像。即基本元素是document，document本身是一个rich的object；整个系统的主要任务是组织编排这些document；整个系统的功能基本上是以前面两点来实现，比如，每条留言都是一个这样的rich object，除了文字以外，可以插入给类媒体文件等；同时setting设置之类的数据也是记录在同样的rich object里，对设置的修改也是通过edit这些rich object来实现。这么多的rich object是通过一些设定了特定搜索条件的view来进行组织；你可以通过添加特定的search来组织你的rich object。

这么一说就真的跟nsf太像了。可以把wave想成一个无序(其实其内部肯定是有序的)乱七八糟的纸篓，里面放的都是同样的纸团，每个纸团上写了些数据。这么乱的纸篓是不方便存取信息的，所以用search，google拿手的也是现成的东西，提供一些视图(view)，把想要的一类纸团组织一起。这种组织是肯定是虚拟的，纸团的实体只有一个，但是同一个纸团可以“出现”在不同的views里。上面说的是high leve，而在细节方面，通过定制更细致的search，将一个话题下的message根据发布时间或其他信息像串乌龟蛋一样串联起来，而在展现时让他们看上去是topic下的一组会话。会话里套小会话可是通过增加一些额外标志来实现。感觉这个wave应该不会费google什么劲就搞出来了，因为很多东西都其实是现成的。

我觉得强的地方是把那些rich object可以做得很rich，很强。相信以后会更rich，支持更多灵活的行为。

这样的组织方式如果要向google os发展，在high level上也是比较容易的。并且完全可以和google现在的那些应用整合。完全可以把rich object看作文件，比如它可以被包成一个word文档，然后直接调用google的word就可以直接打开处理。之后就是google专心把这个平台做好，提供足够的扩展性和自由度，再把自己用的些代码包成友好易用的api发布出来… 喔~ 准备好沃土和农具，再吸引来农民来更重，很快就能长出大片的庄稼了。

其实看google旗下各产品的发展和这些产品相互作用会发现一些东西。产品的初期，或某个产品刚被google收购的时候看上去是独立的。但是随着他们后续的发展，会发现这一个个元素被组织了起来，产生了新的产品，产生更巨大的影响。看待这个过程的发展让人不由得感到激动。你能感觉到一只有力的大手正在一点点、按部就班地形成，它伸向的方向是那样明确，他的发展势头让看的人感受到他的坚毅，感受到他的力量，感受到他对目标的渴望和实现目标的决心。google太伟大了，我仿佛看到一个新的巨人正在慢慢成形，尽管他目前的样子可能只有这个巨人的15%。天下的道理大概是相似的，从google的发展里也可以体会出一些积极做人的道理，这让我想起simple dollar里谈到的31 days to fix your finances。

Google Wave: A Complete Guide

在这里崇拜一下一位曾经的同事、一位传说的牛人：http://www.linkedin.com/in/jerryyz

谨把此人当作照亮我前进方向的一盏明灯。在这一行，踏实肯干，注意思考和总结，总会有好结果的。

另，另一盏明灯Hari现在linkedin.com工作。

湘北的流川枫在神奈川的名声很响，一半是因为篮球打的好，另一半是因为该人，实在是太酷了。此君对所有人一视同仁不假辞色，不要说笑容难得奉送一个，便是说起话来也是能用两个字就坚决不用三个字。
某日在英语课上新来的老师误打误撞要流川同学起立朗读课文一篇，流川同学一看课文，怕不有上百字之多，这如何使得，便摇了摇头：“不会。”
年轻老师想起念过的教育心理学，亲切鼓励：“没关系，大胆地念。”
流川不耐烦起来，据实以告，“太长。”
老师猝不及防愣在当场，想发作又恐失去风度，耐下心来说，“那你念一段好了，剩下的让后面的同学念。”
流川拿起书，念了一句：“Lesson Two.”念罢朝老师点点头，坐下了。
教室里盲目崇拜的小女生倒下一片，这怎一个酷字了得？
一来二去，男生们不免怨声载道，这流川枫无节制地耍酷，搞得本校外校神奈川各中学的小女生们人心惶惶、神不守舍，视其他男生若无物，长此以往哪还有大家的活路？
陵南的仙道乃是神奈川另一大帅哥，不过采取和流川截然相反的风格，亲切开朗，助人为乐，周围的人如沐春风。
一日和同学课余打混，又听得兄弟们纷纷抱怨流川，仙道仔细听听，发现在流川众多让人吐血的行为里，别的不提，最可恨的便是这惜字如金的作风。
仙道颇不以为然：“这有什么？他是凑巧没碰上需要多多说话的机会而已。”他话音刚落，立刻有好事的人设了赌局，打赌看仙道能不能让川变得非常饶舌。很没有面子的，仙道赢的赔率是一赔十。仙道微笑：“原来大家对我这么没信心。”
有几个意志薄弱的家伙在仙道柔和的压力下几乎将钱压在仙道赢那边，但一念及流川那毫无表情的面容，犹豫再三还是压在了仙道输上。仙道拂袖而去。
放学的时候，流川照例来找仙道打球，冰冷冷地说，“一对一。”仙道亲切地说，“我正有此意。”然后拉流川去打了一晚台球，将流川赢了个落花流水。
第二天放学的时候，流川照例来找仙道打球，冰冷冷地说：“一对一，篮球。”
仙道非常亲切地说：“我正有此意。”然后拉流川去打了一晚电脑篮球游戏，将流川赢了个落花流水。
第三天放学的时候，流川照例来找仙道打球，冰冷冷地说：“一对一，篮球，在场地上。”仙道笑眯眯地非常亲切地说，“我正有此意。”
然后拉流川去借爱知县爱知中学的篮球场打球，结果路途遥远只能坐长途汽车，到了爱知天已经全黑了，只好坐末班车回来。不过好在一路的风景还不错，流川也睡得很香。
第四天放学的时候，流川照例来找仙道打球，冰冷冷地说：“一对一，篮球，场地上，在你家旁边的小公园。”仙道开心得很：“和我想到一块去了。”
然后坐着流川的自行车一同走，途中去了超市（买晚饭便当）、海边（吃晚饭便当）以及陵南（仙道后来想起来忘了东西在学校里），等流川骑着自行车将仙道带到那里，流川已经累得快动不了了，仙道又将流川赢了个落花流水。
第五天，……
第六天，……
……
……
这一天放学的时候，流川照例来找仙道打球，说：“仙道，我们去打篮球吧，我今天来的路上看见一个小球场很好，也没什么人，只有四五个人在打球。我问了他 们，他们顶多打到6点，我们可以接在他们后面用。他们说那个球场晚上的灯很亮，打到10点没问题。你现在能走了吗？所有要带回家的东西都拿了吗？明天要交 的作业都做了吗？你仔细想好了，别现在以为都做了，待会又想起来没做。你现在想起来，还来得及和同学借个作业抄抄，回头等回了家你再想起来，到哪里找同学 去，人家也回了家了。你今天晚上要吃什么？我今天不要吃太辣的，也不要吃太咸的，最好也不太甜。今晚海边是不能去了，我听了天气预报，风有七 级……，……，……”
说明——人都是被逼出来的，流川枫也可以变唐僧。

http://www.hudong.com/wiki/%E5%AD%A6%E4%B9%A0%E6%9B%B2%E7%BA%BF

学习曲线

目录

• 1 学习曲线
• 2 正文
• 3 配图
• 4 相关连接

学习曲线 学习曲线

       学习曲线（learning curves）有时又称练习曲线（practice curves），人们为了知道学习进程中的现象和进步的快慢的详情，作为以后努力的指针，应用统计图的方法作一条线，把它表示出来。

学习曲线 正文

学习进程及其效果可用曲线图表示，这种图解就叫学习曲线。学习通常都要经过一定的练习，把历次练习的进程及其效果用统计的方法处理，然后绘制成曲线图解，就可以看出学习过程的进步情况。因此，学习曲线也称练习曲线。通过练习曲线可以看出学习过程的效率、速度、准确性等方面的变化和特点。练习曲线的这种图解方法，可以广泛地运用于知识、技能的学习以及行为习惯的形成等各个方面。不过，因为有些学习现象非常复杂，学习效率较难测定，所以，在心理学中，练习曲线较多地运用于技能和熟练的形成的研究中。
　　学习曲线的坐标式图表，一般以横坐标表示练习的次数、练习日数及练习的总作业量；纵坐标表示单位时间的作业量、完成作业所需的时间及完成作业的成功或错误的数量。学习成绩一般是逐步提高的，它表现在速度加快和准确性提高上。速度加快的标志是单位时间内所完成的工作量增加或每次练习所需的时间减少。准确性的提高表现为正确数增加或错误数减少。如果以单位时间内完成的工作量和正确数为纵坐标，由于工作量随着练习的进程而增多， 则学习曲线呈上升的趋势 （图 1,a）,如以每次练习所需时间或每次练习的错误数为纵坐标，由于每次练习所需时间或错误数量逐渐减少，则学习曲线呈下降的趋势（图1,b、c）。

　　学习的进步，练习成绩的提高，虽然一般说来是逐步提高的；但由于学习内容的性质和难易不同，学习方法不同，以及学习者的能力、知识经验、学习动机和意志努力不同等原因，学习的进步情况也就不同，表现在学习曲线上也就有不同的趋势。一般情况如下：
　　①学习的进步先快后慢。在多数情况下，练习初期进步较快，以后逐渐缓慢(图2)。练习的进步先快后慢的主要原因是：开始练习时,学生对已熟悉的部分任务,可以利用过去的经验和方法，而且开始时教师往往把复杂的学习分解为一些比较简单的任务进行练习，比较容易掌握，加之练习初期兴趣浓，情绪饱满，比较努力，所以练习初期进步较快；后期，可以利用的已有经验相对地逐步减少，而且要把整个的学习联系和协调起来，比简单的局部学习任务复杂而困难，加之后期学习积极性可能会降低，所以成绩提高较慢。教师在指导这类学习时，应加强后期的指导和训练。
　　②学习的进步先慢后快。在有的情况下，练习初期的进步比较缓慢，以后逐渐加快(图3，a)。一些复杂的学习，在开始阶段需要掌握有关的基础知识和基本技能，所以进步较慢，但经过一段练习后，由于掌握了有关的基础知识和基本技能，进步就加快了，如学识字、学游泳就是如此。教师在指导这类学习时，应着重加强练习初期的基础知识和基本技能练习和训练。
　　③练习的进步先后比较一致。在较少的情况下，练习的进步先后没有明显的快慢之分，比较一致(图3，b)。
　　在学习困难的无意义音节时进步速度先后就接近一致，这时练习曲线接近于直线。
　　④高原现象。在练习中期往往出现进步的暂时停顿现象，即练习曲线上的所谓“高原期” (图3，c)。 高原现象产生的主要原因有二。一是由于学习成绩的进一步提高需要改变旧的学习活动结构和方式方法，而代之以新的活动结构和方法。在学生没有完成这种改造以前，学习的进步就会处于停顿状态，甚至在这种改造过程中学习成绩还可能暂时下降，当完成了改造过程，成绩又会提高。二是学生经过一段时期的学习后，学生的学习兴趣降低，情绪厌倦，身体疲劳，或发生疾病等，也会造成学习进步的暂时停顿现象。如果学习活动结构较简单，又没有主观上的原因，在练习过程中就不会产生这种现象。当学生出现高原现象时，教师要帮助学生分析原因，指导他们改变活动结构，采用新的方式方法，鼓舞其学习信心，突破高原，继续进步。另外，一个人在掌握技能，特别是在掌握动作技能的过程中，当发展到较高阶段时会出现成绩相对稳定，曲线上升呈停滞的状态，似乎练习发展已达“极限”。应当指出，所谓“极限”是相对的。一个人掌握技能的水平与其机体和神经系统的工作能力有密切关系。从这个意义上讲,生理限度是不能否认的,超过这个限度是困难的,不可能的。但是，实际上一个人所掌握的各种技能并没有达到"极限"，进一步提高的潜力是很大的,尤其是青年学生更是如此。许多优秀运动员一次次地打破世界纪录，先进生产者不断提高生产率的事实，就是很好的证明。所以不能轻易说某人的技能水平已达到生理极限，不可能再发展了。应当指导他们改进活动结构，采用新的学习、练习方式与方法，鼓励他们突破纪录，争取更大的成绩。
　　⑤练习成绩的起伏现象。在各种学习过程中，都可以看到成绩时而上升, 时而下降的现象(图2)。这种现象产生的原因不外有两个方面：一是客观条件的变化，如学习环境、工具和教师指导的改变等，二是主观状态的变化，如学习兴趣、注意力、情绪、意志努力、学习方法以及身体状况的变化等。一般说, 练习成绩的起伏现象是正常的，但当学生成绩有突然急剧的下降时，就应引起注意，教师要教育和指导学生分析成绩下降的原因，克服缺点和困难，提高其练习的积极性，使练习顺利进行，并取得更好的成绩。
　　学习的进程，常常因人而异，在练习曲线上明显地表现出个别差异。练习曲线上表现的个别差异的原因有：学生的个性特点不同，知识经验不同，努力程度不同等。因此，教师必须分析产生个别差异的具体原因，分别采取不同的具体措施，使学生的学习顺利地进行和提高。
参考书目
潘菽主编：《教育心理学》，人民教育出版社，北京，1980。
　〔苏〕斯米尔诺夫主编， 朱智贤译：《心理学》，人民教育出版社，北京，1957。

先用这个找资源，或者说找到你要观看的youtube视频的id号

https://soproxy.appspot.com/youtube.com

再用这个进行观看

http://apps.hloli.net/gfwtube

比如，要观看的youtube页面地址是：http://www.youtube.com/watch?v=hgUTkX9QAYo

则在第二个一面里将地址中?v=后面的部分hgUTkX9QAYo ，即id号，输入搜索框，找到目标视频，即可进行观看了。

其生成的可观看视频的url是:http://apps.hloli.net/gfwtube/hgUTkX9QAYo/

以后也可以直接修改这个url后面的视频id来达到同样的目的。

虽然上班路上经常看到孵化器，但看了李开复的这个innovation works才对孵化器这个东西恍然一大明白。开眼啊。

这个孵化器有创意pool和人才pool。从前者选择好的创意，然后从后者选出适合的实施者，孵化器投入资金把一个创意变成一个公司，一个可以盈利的实体(各个实体间还可以有分工合作，也会有意营造竞争的环境)。但是这个孵化器不仅提供资金的支持，更重要的是，这个孵化器会提供创业辅导或者说经营辅导，帮助没有经验的创业者提高成功的可能。做到一定程度，再帮助拉来更大的投资。孵化器本身通过从成功的公司里分成来盈利。

李开复这个名字乍一看已经足以换来这个孵化器所需要资源，使整个事情看上去更加靠谱。我仿佛已经看到一个个新公司如雨后春笋在今后了两三年里不断涌现。这个时候再来看看这个孵化器的名字——创新工厂，真的是再贴切不过了。

社会发展到今天，建立一家公司也已经有了一些模式化的东西。原本的工厂直接生产产品，但是现在我们可以开办工厂的工厂。

感兴趣的可以看看视频。时间虽短，但是意思已经表达得很清楚，勾勒出了一大幅美丽的画卷。