"Pragmatic Programming"
- Good enough software ==> design and make it run as soon as possible, then redesign, refactor to achieve better performance software.
Zen of Python
在Python中import this可以得到：
>>> import this The Zen of Python, by Tim Peters Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch. Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea -- let's do more of those! >>>
|
刘未鹏 |
1. 编程的首要原则是什么
ref：http://blog.csdn.net/pongba/article/details/3974110
学习一项知识，必须问自己三个重要问题：
- 它的本质是什么
- 它的第一原则是什么
- 它的知识结构是怎样的
对于编程而言，最重要的两个原则：
- KISS - Keep It Simple Stupid
- DRY - Don't Repeat Yourself
| VCZH |
1. 程序员如何做笔记
ref：http://www.zhihu.com/question/23576293/answer/25001601
我的方法简单粗暴，对感兴趣的东西，先学一下，用几天，然后自己做出来，然后对比一下，再做第二遍，然后就全部写进脑子了，脑内索引比sqlserver还高级，从来没有笔记。
千万不要说着很浪费时间，只要你造的轮子足够多了，每一个都很快的。
| fuliangcheng（http://blog.chinaunix.net/uid-26611383-id-3761754.html） |
1. 从时间轴上纵向、动态的理解一门技术：
我比较喜欢搞清楚一个技术本身的发展历程，简而言之就是这个技术是怎么发展而来的，在这个 技术之前存在哪些技术，这些技术有哪些特点，为什么会被目前的技术所取代，而目前的技术又解决了之前的技术所存在的哪些问题。弄清楚了这些，我们才能比较 清晰的把握某一项技术。有些资料在介绍某个概念的时候直接就介绍这个概念的意义，原理，而对其发展过程和背后的原理丝毫不提，仿佛这个技术从天上掉下来的 一样。