2020-07-26
We’ve been doing a lot of mob programming at work the last year or so and I’ve seen that I have a different attitude to naming things than others on my team. When I see that a name can be improved I always think this is priority number one. My colleagues often say “later”.
I also saw something related recently when doing a programming course internally at work. I sat and helped a guy with an issue he was having. I saw a really bad variable name and recommended he change it. He said “later, I just need to fix this first”. I pushed the point once more saying “trust me” and then left him to his devices. A few minutes later he asked for help again, being totally stuck. Renaming the variable got him immediately unstuck. He had wasted lots of time because the name put him in a mental trap.
My philosophy is: there are only two acceptable types of names: good names and metasyntactic names
. If you have a name that is bad or just a bit misleading it’s better to rename it to foo
NOW.
I believe good (or metasyntactic) names lead to easier problem solving and less effort in programming. It’s not just something we add at the end to make the code more understandable to others or future you. To me the primary thing we work with in programming isn’t numbers or computation, but language.
以上就是本文的全部内容,希望本文的内容对大家的学习或者工作能带来一定的帮助,也希望大家多多支持 码农网
猜你喜欢:本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
Structure and Interpretation of Computer Programs - 2nd Edition
Harold Abelson、Gerald Jay Sussman / The MIT Press / 1996-7-25 / USD 145.56
Structure and Interpretation of Computer Programs has had a dramatic impact on computer science curricula over the past decade. This long-awaited revision contains changes throughout the text. Ther......一起来看看 《Structure and Interpretation of Computer Programs - 2nd Edition 》 这本书的介绍吧!