about the search funtion in zetero

zetero的搜索功能还是第一次正式使用,结果发现很方便.
比如你要检索, 所有某个杂志的文章,可以非常容易的检索出来,并且可以保存这个搜索,而且搜索输入里还具有自动完成这个提示功能,非常容易设置.

win7 小结

升级到win7 64 已经有5天了吧。

感觉很好，当然问题还是遇到了的，比较严重的是 打印机的驱动安装，确实还真是遇到了不小的问题。 弄了几个小时才搞定。

如果比较新的话，直接本地安装找到先装好，然后修改port ，local port，然后给路径和打印机名就可以了。

如果不是很新的话。

去打印机的官方下载 ，或者在微软的站点搜索 http://catalog.update.microsoft.com/v7/site/search.aspx

下载之后还是一样，本地安装，然后修改port搞定。

对于 准确的路径名，可以先通过 网络local 添加的时候确定，确实之后拷贝下来，然后修改本地的时候直接输入，不然很容易因为路径名不对而导致无法正确的修改。

总体来说，win7  看出来成长，看出来 健壮，用着非常的舒服

xp x64 realy no sp3?

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=923231&kbln=en-us#step2



2个包的结果

大家都用哪些源生64应用软件

大家都用哪些源生64应用软件

序言：
64位 系统随着 win7 应该也算得上开始普及了吧，不知道现在64位系统的朋友多不多。
我xp 64 快1年了。

当然 32 位的应用依然很多可以很良好的运行在64下，而且也无什么差别，不过还是下意识的钟情于 源生64位的应用软件。

开这个帖，同64位系统的朋友一起收集和谈谈自己喜欢的源生64 位应用。 当然，开这个帖可能是一时的冲动，并不一定能想全，但是我会列出我日常必备的。

PDF-XChange Viewer  作为每日必用的pdf阅读装备，历经adobe 和 foxit，现在来到了 pdf-xchange
优势，功能非常接近adobe，速度飞快，我的看法是比上面两个都要快，而且大文件更加明显。 而且 源生64，foxit 官方有64，可是安装后依然是32，不知道是什么原因，感觉不是源生。

Paint.NET  图片处理在当今时代亦可谓是家常便饭， 走过 商业版的PS，流连过开源的Gimp （源生64），现在终于落脚在Paint.NET.
ps和gimp可谓不相上下，不过个头都非常的大，启动和操作速度都因为这个庞大的软件而时有疲惫的状态出现。
Paint.NET 非常小巧，印象里好像是不足10M，源生64，速度非常的快，功能却异常强大，完全可以pk上面两个具有大家风范酷软。可能大家会怀疑可能吗？其实优势的 原因在于它，基于.NET, 系统要求装有.NET 3.5。不知道是不是普遍，我的系统里面.net很早就装全了，没办法专业内的软件都需要这些的支持。
界面和ps 和 gimp类似，非常容易上手。关键是快。

MyDefrag

很不错的免费磁盘碎片整理程序，这个没有什么太多说的，具体的去主页看一下，一目了然了。

CleanMem
现在用到过的，内存整理最有效的一个，效果还是非常明显的，比如对于firefox这样的一些有可能吃内存的软件。大家可能不知道运行前后的区别，大家在 运行前打开任务管理器，然后看physical memeory, 里面的available 运行前后的有效内存变化就是 效果。

其他用到的一些 源生64 软件：

gsview64

winrar, 7-zip  (这两个我都装了，虽然其实很想支持开源的7-zip，可是winrar确实做的不 错，有它有优势的地方)  TC里面 用的时候也很明显，7-zip的菜单只能出现在 x64的下面，使用起来很慢，不方便， 同样是 源生64版本，winrar直接出现在TC的右键菜单，没有任何问题。 而且RAR压缩我们遇到的可能比zip的还要多。

安装了但不太使用的 64软件：

firefox，thunderbird 当然64有它自己新的名字，不用的原因主要是 64插件还非常的有限，而有些插件是每天必用，无法离开的，所以还不能转向64，不过这些软件32运行的都很良好。

结语：
可能因为还在学校的原因，系统里大多的软件还是主要和研究和学习有关的多（我的专业软件基本都是64的解算器 : )），休闲软件接触的还不是很多，新年快到了，在这里祝大家 新想事成~

my firefox

火狐讨论区 有一个展示自己firefox的帖子，说明自己的配置，比如用了什么来完成这个效果等。
感觉应该是不需要什么配置，
下面是我的效果图，什么也不需要，只是拖拽摆放就可以完成，
目的就是最大化页面窗口而又不失其他功能的方便性
一些简单的比如主页等，可以用鼠标手势来完成，或者快捷键，其实这些习惯了就好了

Firefox Add-ons alerts

这个问题是最近发生的，一直比较疑惑，不过也想不出自己做过什么不当的事情
今天还是请出 google 检索了一下
https://support.mozilla.com/tiki-view_forum_thread.php?locale=ru&comments_parentId=484183&forumId=1
看来还很普遍
解决办法很简单

Forgot to add, if the DNS solution works and you don't want to change your DNS servers, you can add this line to windows/system32/drivers/etc/hosts

63.245.209.115 services.addons.mozilla.org

修改之后及时生效，虽然感觉是一个很被动的方法，不过暂时也没问题，而且我觉得这样的方式速度可能会更好，至少不会有影响

Step-By-Step: Use BootVis to improve XP boot performance

Windows XP was designed to optimize the boot process so users can boot
their machines and access the operating system as quickly as possible.
For the most part, XP is successful. There is, however, almost always
room for improvement, and BootVis.exe< a free Microsoft utility, can help you get the best boot performance possible from an XP system.

How the Windows XP boot process works
A main cause of slow boots with Windows NT/2000 was their method for loading drivers. Prior to XP, Windows versions loaded drivers sequentially. Windows XP, however, loads drivers concurrently. It also records which applications are launched during startup. This information is written to the C:\WINDOWS\Prefetch\Layout.ini file.

When the Layout.ini file is created, XP performs a partial defragmentation on the files listed in Layout.ini. This defrag process attempts to make the files listed in Layout.ini available in one contiguous area on the hard disk, allowing these files to be accessed, and the associated drivers to be loaded, more quickly. This process is run in the background approximately every three days.

There are four factors affecting the defrag process:

• The system must be idle for XP to perform the defragmentation.
• There must be enough free, contiguous disk space to contain all the files listed in the Layout.ini file.
• The partial defrag performed by XP will not create the necessary contiguous disk space. That can only be accomplished by running a full defragmentation with the XP defragmentation tool or a third-party disk utility.
• The XP defrag process will not use a third-party utility to perform the defragmentation. Any external tools must be run on their own.

BootVis, which Microsoft describes as a "performance trace visualization tool," actually performs the same tasks as the XP boot process, except that BootVis allows the information obtained during a single boot to be used for optimization, rather than monitoring the system over a period of several days. Click here to download the BootVis self-extracting archive directly from Microsoft. Extract the BootVis.exe utility by double-clicking the archive file, selecting a location for the Bootvis.exe file, and clicking OK.

Opening BootVis and running a trace
To run BootVis, simply double-click the BootVis.exe file and the BootVis screen, shown in Figure A, should appear.

Figure A

Here is the BootVis main window.

The first step in tweaking or troubleshooting your boot process is to run a boot trace. To do so, click File | New | Next Boot + Drivers Trace. The Trace Repetitions window, shown in Figure B, will prompt you for the number of repetitions (reboots and traces) to run. Go with the defaults and click OK. BootVis will now provide you with a 10-second countdown before it reboots the system and performs the trace, giving you time to cancel the reboot and close any applications you might have left running. Click Reboot Now to bypass the countdown or Cancel to cancel the reboot.

Figure B

Select the number of reboots and driver traces for BootVis to run.

Once the system reboots, BootVis restarts automatically and provides individual graphs for the following system activity areas (This can take a few minutes, so be patient.):

• Boot activity
• CPU usage
• Disk I/O
• Disk utilization
• Driver delay
• Process creates

Reading the boot activity graph
The Boot Activity graph (as shown in Figure C) breaks the boot process down into the following components:

Disk: The time required to detect all devices in the nonpageable device path. This entry can include any device from the CPU to the boot disk. This value should be around two seconds.

Driver: The time required to initialize devices.

Prefetching: The time required to read pages that are later used to initialize devices. This entry also includes Winlogon, services, the shell, and any applications loaded when the system boots.

Registry + Page File: The time required to read the registry and initialize the page file.

Video: The time spent setting the display mode and refresh rate. This time is affected by both the video BIOS, and the video driver used.

Logon + Services and Shell: The time required to startWinlogon, any services, the shell and any applications, such as firewall or antivirus software, that are run when XP starts.

Figure C

Here is the BootVis boot activity graph.

The components are displayed in the order in which XP calls them and are read from the bottom up. Each component's bar begins at the point in the boot sequence when the component was called and the bar's length reflects the time in seconds required to load the component. To determine the time required for any individual component activity, place the cursor over the title for the component.

To get the most important number, the time used to boot the system, place the cursor over the vertical line that crosses through all the components. This line represents the time the system took to boot. In the example in Figure C, the system required 33.84 seconds to complete the boot process. One item of note, this boot time is dependent on the time it takes the user to enter the logon password, if one is required. Make sure to enter the password as quickly as possible when testing a system.

Optimizing the boot process
Now that you have an indication of how well the boot process is going, the next step is to optimize the system. To optimize your system boot, click Trace | Optimize System. Again BootVis will present you with a 10-second countdown before rebooting. When the system reboots, the window shown in Figure D will appear, indicating that BootVis is using information gained from the previous boot and the current boot to optimize the system.

Figure D

The next window, shown in Figure E, appears when BootVis actually begins to place the files specified in the Layout.ini file in the area of contiguous disk space created during the defragmentation process run prior to using BootVis.

Figure E

This shows BootVis organizing files on the hard disk.

When the window shown in Figure E closes, restart BootVis and run another boot trace by clicking File | Next Boot + Driver Trace. This will allow you to see how much improvement was gained from the optimization process. Figure F shows the results on my test machine. After running the optimization, the boot time was reduced to 30.85 seconds—a difference of almost three seconds. As I mentioned earlier, this value is affected by the time it takes to enter a logon password, so enter the password as quickly as possible. While three seconds may not seem like a lot, I have seen this value change by as much as 10 seconds. And in today's world, where we expect instant-on computers, every second counts.

Figure F

BootVisreduced my test machine's boot time by nearly three seconds.

Identifying driver problems
Now that you know how to optimize a machine's boot process with BootVis, let's look at how to troubleshoot boot issues involving problem drivers. BootVis can identify drivers that cause problems during the boot process and will indicate them on the Driver Delay graph, shown in Figure G, with a red bar. Fortunately, my test machine has not had driver issues. If it did, I would check the manufacturer's Web site for the latest drivers.

Figure G

BootVisreports no driver delays on my test machine. If it did, they would appear in red.

BootVis can only do so much
BootVistries to optimize the XP boot process as much as possible, but let users know that it can't work miracles. If a machine loads antivirus, firewall, and/or e-mail programs when booted, BootVis can only do so much. Remember the phrase “Your mileage may vary,” and use BootVis within the context of how you use your system. This will help you achieve a compromise between a fast boot and a system you can work with as soon as it boots to XP.

Identifying driver problems
Now that you know how to optimize a machine's boot process with BootVis, let's look at how to troubleshoot boot issues involving problem drivers. BootVis can identify drivers that cause problems during the boot process and will indicate them on the Driver Delay graph, shown in Figure G, with a red bar. Fortunately, my test machine has not had driver issues. If it did, I would check the manufacturer's Web site for the latest drivers.

Figure G
BootVisreports no driver delays on my test machine. If it did, they would appear in red.


BootVis can only do so much
BootVistries to optimize the XP boot process as much as possible, but let users know that it can't work miracles. If a machine loads antivirus, firewall, and/or e-mail programs when booted, BootVis can only do so much. Remember the phrase “Your mileage may vary,” and use BootVis within the context of how you use your system. This will help you achieve a compromise between a fast boot and a system you can work with as soon as it boots to XP.

a good way to control the services

usually we control the services by manager.

but the listed in manager are not all.

the bellow example will show how to change the service state from regedit.

1. Start the Registry Editor by pressing the Start-button and Run... this command:

   Regedit

2. Browse through the left tree to where Services are found:

   [HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services]

   
   
   
3. Within the Services-key find go to the short-name of the wanted service (Here RpcSS aka. Remote Procedure Call (RPC)):
   
   

   [HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services \RpcSS]
   

   
   
   
4. Double-Click the Start-value in the list to the right.
   
   
   
   
5. Change Value data: to the wanted state:
   • 0 = Boot
   • 1 = System
   • 2 = Automatic
   • 3 = Manual
   • 4 = Disabled
6. Press Ok and exit the Registry Editor.
7. If setting a service to Disabled or Manual, then execute this command to stop the service:

   Net Stop RpcSS

8. If setting the service to Automatic, then execute this command to start the service:

   Net Start RpcSS

Note in this guide the short-name of a service is shown just in parenthesis next to the "Process Name".

漂亮的 popping

http://blog.naver.com/sonamoo9608?Redirect=Log&logNo=20086458174&vid=0

据说是韩国街舞的名将

关于 研究系统的构架

图书和文档的管理利用 zotero, 文档的存储采用日期归类方式，具体就是以年，月为文件夹，然后里面放入以日期为文件名的文件夹作为每天的文档处理，然后把这个关联给zotero去管理。

关于计划和头脑风暴部分，为了采用网络同步方式，这样的好处是面向未来的发展方向。虽然有一些好的完全网络方式的版本，不过本次主要通过Adobe 公司的最新构架AIR来作为使用对象。
actionmethod 作为 GTD工具来处理 日程和计划
simpletimer2 作为细化任务的时间驱动器
EasyQA 可以作为简单的case的总结，当然这个也可以由我们的客户端evernote来完成
所有当时无法进行的细化和分解以及暂存部分都可以先备份到evernote，或者scribeifire里面，等有网络的时候进行更新。

头脑风暴部分我打算采用 纸来进行处理。（不过残留一个问题就是 随着研究的深入，如何更有效的对以往工作和进度进行汇总和分析）

每日的时间安排 初步订以周为 循环周期。

 1-2 调研+头脑风暴+赛选
 3 完全design，所谓完全design，就是分解，只做设计，不做仿真，周三的任务就是把1-2所有的预选的 idea进行Design。
 4 批处理然后 仿真， 随时对出来的结果进行分析 并 给出 redesign的想法 以备下一周的再次循环需要
 5 总结 有效的结果，并对有价值的完成报告，或者对有用的设计技巧写出心得然后保存。

补充：
关于 1-2 调研
调研应该采用什么方式？ 我想 针对 杂志进行也许是一个不错的选择，对杂志的文章进行全面的分析 并从中获取一些结论。
业内重要的杂志或者网站资讯也要定时获取信息。杂志的分析工作要结合zotero,这样便于管理和查找，但是这部分工作要和 下面提到的 weekly work文件夹区分开来，调研的文档要采用最开始提到的时间日期文件夹存储方式来进行管理和保存，区别就是文档位置相对固定，而Weekly work 文件夹 每周都要进行更新，位置也不固定。

对于上述提到的设计和仿真过程中的文件，同样采用时间序列方式来存储，这样一来，我们在桌面上留一个文件夹“weekly work”
针对 赛选出来的idea建立文件夹 ，每个文件夹下一个 txt文档对idea和设计思路进行说明. design 目录保存设计文件，子目录可以针对不同的仿真软件。总结也可以用txt文件来完成。

关于 韩语和英语的学习，我们抽出空隙的时间来做。
早晨工作时间定为 10点， 一般9点多来到实验室，首先安排这一天的具体时间表，然后按照计划进行。有时间的话，在10点前可以学习韩语。 语言学习 争取保证在每天的早和晚。 其他的就按照说的空闲时间。

体育锻炼坚持在下午或者 8点左右。

关于 ADS等软件打印pdf的问题

比如从 schematic 或者从 smith chart 打印 到 pdf 的时候

不一定唯一，不过下面的方法有效

不用使用全屏，找一个合适的窗口大小，这样尽量保证两边都是没有什么空隙的状态。

然后 第一次pdf 打印，出来，在foxit或adobe中测量一下 实际的大小。

然后根据 这个大小在pdf 打印的属性里面新建一个 上面测试的尺寸的大小作为纸张的尺寸。

这样再次打印出来的文件就完全符合了，纸张的大小而且又没有空隙。

另外一点就是这样打印得到的 pdf 为矢量图，所以对后期的编辑非常有效

之后如果需要 标量图的话，直接用 adobe保存成png就可以了。

pdf to ps

为了准备MWCL ，看了一下 作者向导。

基本上来说，都是为 tex 用户准备的，word虽然也可以接受，不过好像不是很推荐。

另外的一个需要注意的地方就是，图片需要单独发送过去，格式很奇怪的没有 pdf, 而是 ps , 我看了一下，很简单，只要用 acrobat pro版本，打开pdf然后另存 ps就可以了。效果一样 也是矢量形式，没有问题。

估计 origin 也支持 ps 输出。 所以这个问题也ok了。

不过看起来 MWCL 要求非常国际话和严格话，硬仗 啊。

pdf 矢量图 插入的问题

看起来这是一个很棘手的问题，问题发生在如下的情况，如果会议或者杂志只提供了 word 模板，那么在插入图片或者最终生成pdf的时候就会遇到图片失真的问题。

解决方法如下，一般来说 数据图都来自origin, 这样直接导出 emf 文件格式插入到 word即可，不失真。

而从其他途径创建的 pdf 矢量图，在这里就遇到问题了。word 虽然支持插入，可是效果很不好。已经不是矢量图。

所以，解决这个一直没有什么好的办法，哈哈

其实，很简单，首先，从word生成一个 pdf ，然后用 acrobat pro 版本，对生成的 pdf 进行编辑，删除原来的那个图，然后通过插入 水印的方式，插入 pdf矢量图到指定的页码和位置，这样我们就完成了，矢量pdf的插入，没有任何失真，非常完美。

java 1.4.2 版本

献给 和我一样 比崇尚升级，怀念股东的朋友们

https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=j2re-1.4.2_19-oth-JPR@CDS-CDS_Developer

今天 awr的 PA的讲座，需要real，需要jvm 所以 就有了一番查找

64 系统下 tcpip 连接数修改

好多都不支持64系统
所以找到了下面这个，很强大。
http://half-open.com/download_en.htm

偷懒在家一天

昨天格外的累，今天就没有去学校

打算借机会把虚拟调试系统装上，最开始考虑vmvare，可是很不幸，绿色版本都有些问题，好象主要原因还是64位系统的支持和配置不同。

试了一个 雨浪飘零的版本，无效。所以 转投 微软

visual pc sp1版本  还不错 去年更新的sp1
http://www.microsoft.com/downloads/details.aspx?FamilyId=28C97D22-6EB8-4A09-A7F7-F6C7A1F000B5&displaylang=en#filelist
现在系统已经搭建起来了，因为使用的是 lit版本，所以没有语言支持，只能英语。

不管怎么样，OD已经可以顺利的运行了。

双核系统还是不错的，好多时候，一个cpu资源没了，还有另外一个可以用 呵呵，不错。

明天去学校 ，继续加油

计算量的一个评估值

sonnet的当家人有出来说话了，估计12版本完成对他来说也是一个很大的飞跃，他当然有资格和更多的基础来发表一些说法。

大家对EM的时间和量都想有一个估计，这里给出一个值供参考

20,000x20,000 matrix 运行在 2.3 G core centrino notebook 1.5G 内存上，需要14分钟

我的配置 2.53 G , 4G 内存，看来 15分钟内是肯定可以完成。 也就是 具体一点，我如果在sonnet里面仿真，subsection 20,000。那么以我的配置，15分钟应该就可以ok 。

明天一个朋友回国，过去看看她，文章还没看完，不过已经受益匪浅，好多概念虽然原来我看过他的文章，有了解，不过看来他又精进了。

明天继续。 暂时写到这里

Rhythms, 旋律？

今天 翻看的时候发现了标题为 Software Development Rhythms: Harmonizing Agile Practices for Synergy 的一本书。

想到的是 匆忙的在社会上生活的我们是否 好多本能的东西都随着这个社会 谈话或者丢失与社会的大家庭中了呢？

真的该反思，并且找回自己生活的旋律

也许真的和软件有不解之缘吧

列出 章节题目 可以做为思考

PART I: ESSENTIALS.

Chapter 1: No Programmer Dies.

1.1 Developing Software vs. Building a Tunnel.

1.1.1 The good old days?

1.1.2 The more things change the more they stay the same?

1.1.3 Behind Software Products.

1.1.4 Deal or not deal.

1.2 Do-Re-Mi Do-Re-Mi.

1.2.1 Iterative Models.

1.2.2 Code and Fix.

1.2.3 Chaos.

1.2.4 Methodology that matters.

1.3 Software Development Rhythms.

1.3.1 Stave Chart by Example.

1.3.2 Game Theory.

1.3.3 IN-OUT Diagram.

1.3.4 Master-Coach Diagram.

1.3.5 No Mathematics.

1.3.6 Where to Explore Rhythms.

Chapter 2: Understanding Programmers.

2.1 Personality and Intelligence.

2.1.1 Virtuosi.

2.1.2 Meeting your team.

2.1.3 Recruiting Programmers.

2.2 Outsourced Programmers.

2.2.1 Programmers in Their Environments.

2.2.2 Programmers, Cultures, and Teams.

2.3 Experienced Management.

2.3.1 Being Casual about Causal Relationships.

2.3.2 Not Learning From Experience.

2.3.3 Doing things right right now.

Chapter 3: Start with Open Source.

3.1 Process and Practice.

3.1.1 The 4Ps of Projects.

3.1.2 Agile Values.

3.1.3 Zero-point collaboration.

3.2 OSS Development.

3.2.1 Software Cloning.

3.2.2 Software Quality.

3.2.3 Starting Processes.

3.2.4 Open Source Development Community.

3.2.5 Ugrammers.

3.2.6 Participant Roles.

3.2.7 Rapid Release.

3.2.8 Black-box Programming.

3.2.9 Open Source Software Practices.

3.3 OOS-Like Development.

3.3.1 Agile Practices.

3.3.2 Communication Proximity.

3.3.3 Loose and Tight Couple.

3.3.4 Co-located OSS Development.

PART II: RHYTHMS.

Chapter 4: Plagiarism Programming.

4.1 Plagiarism.

4.1.1 Existing Code.

4.1.2 Social Network Analysis.

4.1.3 Being Plagiarized.

4.1.4 Turn everyone into a programmer.

4.1.5 Pattern Language.

4.1.6 Software Team Capability.

4.1.7 Rough-Cut Design.

4.1.8 Training is not a solution.

4.2 Nothing Faster than Plagiarism.

4.2.1 Immorality.

4.2.2 Unprecedented Code.

4.2.3 People Network.

4.2.4 Rhythm for Plagiarism.

4.2.5 Plagiarism at Work.

4.3 Business and Rhythm for Plagiarism.

4.3.1 15 Minute Business Presentation.

4.3.2 Marketing Research.

4.3.3 Chatting Robot.

4.3.4 Old Song New Singer.

Chapter 5: Pair Programming.

5.1 Art and Science.

5.1.1 The Right Partner.

5.1.2 Noisy Programming.

5.1.3 Just Training.

5.1.4 Pay to watch.

5.2 Two Worlds.

5.2.1 Moneyless World.

5.2.2 Money-led World.

5.2.3 Economics.

5.2.4 Mythical Quality-time.

5.2.5 Elapsed Time.

5.2.6 Critical Path Method.

5.2.7 Why two not three: Anti-Group.

5.2.8 Software Requirements are Puzzles.

5.3 Programming Task Demands.

5.3.1 2 and 4 is 6.

5.3.2 2 and 4 is 4.

5.3.3 2 and 4 is 3.

5.3.4 2 and 4 &ge; 2.

5.3.5 2 and 4 is unknown.

5.4 Pair programming is more than programming.

5.4.1 Design by Code.

5.4.2 Pair Design.

5.4.3 Rhythmic Pair Programming.

5.5 Pair programming Team Coached.

Chapter 6: Repeat Programming.

6.1 Controversies in Pair Programming.

6.1.1 Is Programming a Unique Work?

6.1.2 Are Three Minds Better Than Two?

6.1.3 Un-replicable Experiments.

6.2 Repeat Programming.

6.2.1 Variances.

6.2.2 Principles.

6.2.3 Triple Programming Unproductive.

6.3 Rhythm: Pair - Solo - Pair - Solo.

6.3.1 Persistence.

6.3.2 Connection.

6.3.3 Motivation.

6.4 An exception that proves Brooks’ Law.

6.4.1 Low Morale.

6.4.2 Communication Costs.

6.4.3 Rhythm for Late Projects.

Chapter 7: Agile Teaming.

7.1 Project Teams.

7.1.1 Self-organizing teams.

7.1.2 Teams in Team.

7.1.3 Project Team Composition.

7.1.4 Team Life Cycle vs. Learning Curve.

7.2 Productivity.

7.2.1 The Illusion of Productivity.

7.2.2 Collective Code Ownership.

7.2.3 Accountability, Responsibility and Transparency.

7.3 Problems and Problem Owners.

7.3.1 Rhythm: Trouble - Restructuring.

7.3.2 Teaming Principles.

7.4 Failing Projects Rescued.

7.4.1 Project Traffic Light.

7.4.2 A Business Case.

7.4.3 Steering Committee Meeting.

7.4.4 Agile Teaming in Action.

7.5 Beware of Iago.

Chapter 8: Incremental Design.

8.1 Modeling and Planning.

8.1.1 Agile Planning.

8.1.2 Design by Functional Modules.

8.1.3 Simple Design.

8.1.4 Total Cost Concept.

8.2 Rework or reuse.

8.2.1 Unpreventable Rework.

8.2.2 Improvisation.

8.2.3 Up-front Design.

8.3 Just-in-time Software Development.

8.3.1 The CMM Rhythm.

8.3.2 A Factory Tour.

8.3.3 Walking Worker.

8.3.4 Just-in-time Software Development.

8.3.5 Incremental Design.

8.4 Requirements Complexity.

8.4.1 Forgotten Requirements.

8.4.2 Conflicting Requirements.

8.4.3 Rapid Changing Requirements.

8.4.4 Requirements and Design.

8.5 Refactoring.

8.5.1 Refactoring Activities.

8.5.2 Refactoring by Challenging.

8.5.3 Refactoring for Design Patterns.

8.5.4 Making Deliberate Mistakes.

Chapter 9: Test-Driven Development.

9.1 Reverse Waterfall.

9.1.1 Design - Code - Test.

9.1.2 Test - Code - Design.

9.2 Test-First Programming.

9.2.1 Testing and Verification.

9.2.2 Break-point testing.

9.2.3 Supporting Practices.

9.3 Rhythm: Test - Code - Refactor.

9.3.1 Simple Example.

9.3.2 Automation.

9.3.3 Revolution in Consciousness!

9.3.4 Test Case for Collaboration.

9.4 Rapid Software Process Improvement.

9.4.1 Training Program.

9.4.2 Project Planning.

9.4.3 Project Tracking.

9.4.4 Software Quality.

9.4.5 Software Configuration.

9.4.6 People Discipline.

Epilogue: Medley.

Appendix I: Nammik.

References.

乱码解决

因为新机器，新系统，所以软件当然都是新下载安装的。

以前的配置都没有了，最近发现msn乱码这个问题越来越严重了，影响生活了，所以google了一下。 解决方案 真是 挺多的。

我倒是 先看了一下配置，发现在 converstaion里面有这么一项 Font 里面 挑钩是 use font from theme
所以我想我们可以从这里下手，简单修改就解决

我们去掉这个挑钩，然后制定一个 utf8编码的字体，那不就解决问题了吗

我选上了 Tahoma 10

重启 pidgin ，Ok  中文没问题了，原来的中文记录也没有乱码了。 呵呵

这个字体就是 TC采用的字体，我也是这样知道他支持 中文的

VLC 看 哈利又遇到问题 乱码

晕死

处理起来很简单，字体指定为一个中文的就可以了。有些不好的地方是，浏览过去无法选择，所以需要自己手动属于 字体的位置，然后就ok了

蛮喜欢VLC的

bios go back to F.11

事情真的很巧合，本来我 失误，更新bios到 F.13，后来也没发现什么问题，就觉得无所谓了。

今天在ZOL发现有人回我的帖，而且 提供了一条消息，F.13的bios有些问题，接外接键盘的时候，小键盘灯 无效，而原来的F.11版本工作良好。

所以我就再次 google了一下，找到了DV5-系列的其他型号的F.11版本的 bios链接。
确实通过链接我找到了F.11 版本 bios
可是我又发现了一个问题，就是 这个链接是隐藏的，也就是说，hp在发布新的版本的 bios之后，就把链接更新了，所以我们访问不到原来的bios版本的原因是，链接没有了，如果你原来有那个链接，那么那个链接依然有效。

所以我推算，我的型号的 F.11 bios也同理，依然存在。

所以我对比了一下， url地址，找到了其中的 差异，比较就得出了我的型号的 bios F.11的地址。

不过 话说回来， 其实DV5系列的bios 是一致的，所以虽然我找到了我的那个F.11，其实他和其他的F.11是一样的 呵呵。 只是这样做，让自己更放心。

更新之后，上面提到的问题，立竿见影的解决了。

还有一个惊喜，就是进windows的速度 提升了，这个到底为什么，我不知道。

我原来需要 9圈，现在不到6圈 就进去了。 呵呵  意外吧