引用:CodeProject
原文:
For me, in software development, it is all about why. I feel a very strong need to understand why I am doing everything and
anything I do. Furthermore, I am upset with myself when I cannot clearly state why, and on the flip side take pride in knowing
why: why I choose a minimum of three layers in darn near any application, why I rarely if ever read books on a language, why I
don’t blindly choose auto numbers for primary keys in databases, why I prefer business-object-oriented development, why I don’t
bother arguing with people about how they want to define scope on their variables, etc, etc, etc, etc, etc, etc. The author of one of the books I am currently reading (Getting Things Done) stresses that getting anything done starts from
understanding why we are trying to get anything done in the first place. There is a real problem if we cannot explain why we
take any action, and if we cannot agree on why we are taking action. I feel validated today. I guarantee you there is more than one developer in your midst right now who cannot tell you why he or
she does things the way they do. “That’s how everyone does it,” or “It’s better,” or “It’s easier”, or "It's simpler" do not
count. I’m looking for a deeper understanding of purpose. ** Want a telling interview with a perspective hire? Ask them why they do the things they say they do. Do they put little prefixes
on variables to denote data type? Ask them why. Do they employ object-oriented development techniques? Ask them why. Want to be a better developer? Work to understand why you do the things you do and to understand why you don't do some other
things. Sounds like common sense, but appears not to be commonly practiced. **Side Note: One short answer that I have becoming increasingly alright with is "I am comfortable with this." If you understand
both sides of a debate, and everything seems relatively even, being comfortable with a decision can easily tip the scales as thecomfort level may make you more efficient and even happier.
译文: