、代码片过长。一个函数代码过长。



2、常量到处是数字，（原则上，每个常量都有明确含义，既然有含义就应该用#define符号化。



3、printf用，scanf也用。输入输出不喜欢用文件，手工敲数据或把测试数据当静态常量数组方式存放在代码里。



4、没有测试函数



5、不知道如何区分C文件。要么一个main搞定。要么刻意给我增加N多C文件。



6、不知道简单的makefile的规则和使用。



7、代码总量小于500行，改改还能应付，超过2000行，基本调整不动了。这边改了那边错，那边改正确，这边又错。



8、我能猜出（有时需要努力一下）他的代码片想干什么，但我不猜不出这种写法和目标有什么联系。



我这里说的一些方法，主要是针对程序原创的设计，例如我现在针对GIT的源码的学习和后期的改动属于另一种方法，和下面说的方法不一样。-The accuracy of cientific observations and calculations is always at the mercy of the scientist s timekeeping methods. For this reason,scientists are interested in devices that give promise of more precise timekeeping.

In their search for precision, scientists have turned to atomic clocks that depend on various vibrating atoms or molecules to supply their "ticking" .This is possible because each kind of atom or molecule has its own characteristic rate of vibration. The nitrogen atom in ammonia , for example, vibrates or "ticks" 24 billion times a second.

One such atomic clock is so accurate that it will probaly lose no more than a second in 3000 years. It will be of great improtance in fields such as astronomical is a sesium atom that vibrates 9.2 billion times a second when