有哪些老鸟程序员知道而新手不知道的小技巧？

<code style="box-sizing: border-box; font-family: Menlo, 'Liberation Mono', Consolas, 'DejaVu Sans Mono', 'Ubuntu Mono', 'Courier New', 'andale mono', 'lucida console', monospace; padding: 0px; color: inherit; border-top-left-radius: 0px; border-top-right-radius: 0px; border-bottom-right-radius: 0px; border-bottom-left-radius: 0px; word-wrap: normal; background-color: transparent;"><span id="LC1" class="line" style="box-sizing: border-box; display: inline-block;">1.重构是程序员的主力技能。</span>
<span id="LC2" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC3" class="line" style="box-sizing: border-box; display: inline-block;">2.工作日志能提升脑容量。</span>
<span id="LC4" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC5" class="line" style="box-sizing: border-box; display: inline-block;">3.先用profiler调查，才有脸谈优化。</span>
<span id="LC6" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC7" class="line" style="box-sizing: border-box; display: inline-block;">4.注释贵精不贵多。杜绝大姨妈般的“例注”。漫山遍野的碎碎念注释，实际就是背景噪音。</span>
<span id="LC8" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC9" class="line" style="box-sizing: border-box; display: inline-block;">5.普通程序员+google=超级程序员。</span>
<span id="LC10" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC11" class="line" style="box-sizing: border-box; display: inline-block;">6.单元测试总是合算的。</span>
<span id="LC12" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC13" class="line" style="box-sizing: border-box; display: inline-block;">7.不要先写框架再写实现。最好反过来，从原型中提炼框架。</span>
<span id="LC14" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC15" class="line" style="box-sizing: border-box; display: inline-block;">8.代码结构清晰，其它问题都不算事儿。</span>
<span id="LC16" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC17" class="line" style="box-sizing: border-box; display: inline-block;">9.好的项目作风硬派，一键测试，一键发布，一键部署; 烂的项目生性猥琐，口口相传，不立文字，神神秘秘。</span>
<span id="LC18" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC19" class="line" style="box-sizing: border-box; display: inline-block;">10.编码不要畏惧变化，要拥抱变化。</span>
<span id="LC20" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC21" class="line" style="box-sizing: border-box; display: inline-block;">11.常充电。程序员只有一种死法：土死的。</span>
<span id="LC22" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC23" class="line" style="box-sizing: border-box; display: inline-block;">12. 编程之事，隔离是方向，起名是关键，测试是主角，调试是补充，版本控制是后悔药。</span>
<span id="LC24" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC25" class="line" style="box-sizing: border-box; display: inline-block;">13. 一行代码一个兵。形成建制才能有战斗力。单位规模不宜过大，千人班，万人排易成万人坑。</span>
<span id="LC26" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC27" class="line" style="box-sizing: border-box; display: inline-block;">14. 重构/优化/修复Bug，同时只能作一件。</span>
<span id="LC28" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC29" class="line" style="box-sizing: border-box; display: inline-block;">15. 简单模块注意封装，复杂模块注意分层。</span>
<span id="LC30" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC31" class="line" style="box-sizing: border-box; display: inline-block;">16. 人脑性能有限，整洁胜于杂乱。读不懂的代码，尝试整理下格式; 不好用的接口，尝试重新封装下。</span>
<span id="LC32" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC33" class="line" style="box-sizing: border-box; display: inline-block;">17. 迭代速度决定工作强度。想多快好省，就从简化开发流程，加快迭代速度开始。</span>
<span id="LC34" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC35" class="line" style="box-sizing: border-box; display: inline-block;">18. 忘掉优化写代码。过早优化等同恶意破坏；忘掉代码作优化。优化要基于性能测试，而不是纠结于字里行间。</span>
<span id="LC36" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC37" class="line" style="box-sizing: border-box; display: inline-block;">19. 最好的工具是纸笔;其次好的是markdown。</span>
<span id="LC38" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC39" class="line" style="box-sizing: border-box; display: inline-block;">20. leader问任务时间，若答不上来，可能是任务拆分还不够细。</span>
<span id="LC40" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC41" class="line" style="box-sizing: border-box; display: inline-block;">21. 宁可多算一周，不可少估一天。过于“乐观”容易让boss受惊吓。</span>
<span id="LC42" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC43" class="line" style="box-sizing: border-box; display: inline-block;">22. 最有用的语言是English。其次的可能是Python。</span>
<span id="LC44" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC45" class="line" style="box-sizing: border-box; display: inline-block;">23. 百闻不如一见。画出结果，一目了然。调试耗时将大大缩短。</span>
<span id="LC46" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC47" class="line" style="box-sizing: border-box; display: inline-block;">24. 资源、代码应一道受版本管理。资源匹配错误远比代码匹配错误更难排查。</span>
<span id="LC48" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC49" class="line" style="box-sizing: border-box; display: inline-block;">25. 不要基于想象开发， 要基于原型开发。原型的价值是快速验证想法，帮大家节省时间。</span>
<span id="LC50" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC51" class="line" style="box-sizing: border-box; display: inline-block;">26. 序列化首选明文文本 。诸如二进制、混淆、加密、压缩等等有需要时再加。</span>
<span id="LC52" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC53" class="line" style="box-sizing: border-box; display: inline-block;">27. 编译器永远比你懂微观优化。只能向它不擅长的方向努力。</span>
<span id="LC54" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC55" class="line" style="box-sizing: border-box; display: inline-block;">28. 不要定过大、过远、过细的计划。即使定了也没有用。</span>
<span id="LC56" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC57" class="line" style="box-sizing: border-box; display: inline-block;">29. 至少半数时间将花在集成上。时间，时间，时间总是不够。</span>
<span id="LC58" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC59" class="line" style="box-sizing: border-box; display: inline-block;">30. 与主流意见/方法/风格/习惯相悖时，先检讨自己最可靠。</span>
<span id="LC60" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC61" class="line" style="box-sizing: border-box; display: inline-block;">31. 出现bug主动查，不管是不是你的。这能让你业务能力猛涨、个人形象飙升; 如果你的bug被别人揪出来.....呵呵，那你会很被动～≧﹏≦</span>
<span id="LC62" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC63" class="line" style="box-sizing: border-box; display: inline-block;">32. 不知怎么选技术书时就挑薄的。起码不会太贵，且你能看完。</span>
<span id="LC64" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC65" class="line" style="box-sizing: border-box; display: inline-block;">33. git是最棒的。简单，可靠，免费。</span>
<span id="LC66" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC67" class="line" style="box-sizing: border-box; display: inline-block;">34. 仅对“可预测的非理性”抛断言。</span>
<span id="LC68" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC69" class="line" style="box-sizing: border-box; display: inline-block;">35. Log要写时间与分类。并且要能重定向输出。</span>
<span id="LC70" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC71" class="line" style="box-sizing: border-box; display: inline-block;">36. 注释是稍差的文档。更好的是清晰的命名。让代码讲自己的故事。</span>
<span id="LC72" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC73" class="line" style="box-sizing: border-box; display: inline-block;">37. 造轮子是很好的锻炼方法。前提是你见过别的轮子。</span>
<span id="LC74" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC75" class="line" style="box-sizing: border-box; display: inline-block;">38. code review最好以小组/结对的形式。对业务有一定了解，建议会更有价值（但不绝对）。而且不会成为负担。管理员个人review则很容易成team的瓶颈。</span>
<span id="LC76" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC77" class="line" style="box-sizing: border-box; display: inline-block;">39. 提问前先做调研。问不到点上既被鄙视，又浪费自己的时间。</span>
<span id="LC78" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC79" class="line" style="box-sizing: border-box; display: inline-block;">40. 永远别小看程序媛(╯3╰)</span>
<span id="LC80" class="line" style="box-sizing: border-box; display: inline-block;"></span>
<span id="LC81" class="line" style="box-sizing: border-box; display: inline-block;">作者：大狐狸</span>
<span id="LC82" class="line" style="box-sizing: border-box; display: inline-block;">链接：https://www.zhihu.com/question/36426051/answer/76031743</span>
<span id="LC83" class="line" style="box-sizing: border-box; display: inline-block;">来源：知乎</span>
<span id="LC84" class="line" style="box-sizing: border-box; display: inline-block;">著作权归作者所有。商业转载请联系作者获得授权，非商业转载请注明出处。</span></code>