Reference: codeproject
Original article:
For me,InSoftware development, itIsAll about why. I feel a very strong need to understand why I am doing everything and
Anything IDo. Furthermore, I am upset with myself when I cannot clearly state why, and on the flip side take prideInKnowing
Why: Why I choose a minimum of three layersInDarn near any application, why I rarelyIfEver read books on a language, why I
Don't blindly choose auto numbersForPrimary keysInDatabases, 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. 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 tryingGetAnything DoneInThe first place. ThereIsA real problemIfWe cannot explain why we
Take any action, andIfWe cannot agree on why we are taking action. I feel validated today. I guarantee you thereIsMore than one developerInYour midst right now who cannot tell you why he or
She does things the way theyDo. "That's how everyone does it," or "It's better," or "It's easier", or"It's simpler"DoNot
Count. I'm lookingForA deeper understanding of purpose. ** want a telling interview with a perspective hire? Ask them why theyDoThe things they say theyDo. Do they put little prefixes
On variables to denote data type? Ask them why. Do they employObject-Oriented development techniques? Ask them why. Want to be a better developer? Work to understand why youDoThe things youDoAnd to understand why you don'tDoSome other
Things. Sounds like common sense, but appears not to be commonly practiced. ** Side Note: OneShortAnswer that I have becoming increasingly alrightIs"I am comfortable with this."If you understand
Both sides of a debate, and everything seems relatively even, being comfortable with a demo-can easily tip the scalesAsThe
Comfort level may make you more efficient and even happier.
Translation: