We could have rewritten the whole code several times over.
我们完全可以改写整个代码好几次。
Finally, and most important, don't test the whole code base at once.
最后,也是最重要的,就是不要一次测试整个代码基。
Is anyone adept at scanning the whole code base, looking for pervasive issues or opportunities? Are less expensive tweaks and hacks preferable over doing it right (but expensively) the first time?
有没有人善于浏览整个代码库,发现普遍的问题和机会?更喜欢代价低的调整和删改还是第一次就把事情做好(但是代价高)?
I'm much better having an exception get handled at the time of input than to let that prop -- that value rather propagate through a whole bunch of code until eventually it hits an error 17 calls later, and you have no clue where it came from.
不是我期望的格式,这时我最好有一个异常处理,而不是让其传下去,这个值传到代码的整个分支,最终会导致一个错误17调用的发生,并且你不知道这个错误是哪里来的。
It takes an int; deal with it when you get to it and then once you look through the whole file, should you find -- ultimately find the actual code that defines or impliments this thing.
它携带一个int数,当你获得了它就处理它,然后一旦你查看整个文件,最终你将发现实际代码中,定义或执行了这个东西。
应用推荐