I was recently asked to share some thoughts on characteristics that make a great employee. It made sense to me to start by noting behaviors seen in those that set themselves apart and excel.
The Journey
I decided to liken the journey of a developer or tester (I am a tester) to that of an outdoor activity that I relate to. I love hiking and taking part in remote outdoor adventures, including backpacking and canyoneering. Some very beautiful sights can be had, and they usually come at several costs. Besides the physical toil required, there is – in many cases – a preparation phase of readying tools, devices, and all manner of provisions to make the journey safer, more comfortable, and in some cases, doable at all. There is the mental preparation of understanding the terrain and physical barriers you will be up against, as well as a grasp of what conditions to prepare for weather wise. Bottom line is, you pay the price up front; you examine charts and maps, you have a plan, and you take with you what you will need. These all lead to a safe and enjoyable journey and minimize the scenarios you are not prepared for. I would liken our finished product in software to the beauty that nature has to offer.
Just as proper foresight and careful planning in hiking can lead to a rewarding outing in nature, similar preparation in development can lead to more robust, quality, and beautiful software products.
“If I had 6 hours to cut down a tree…I would spend 4 hours sharpening the axe.”
- Abraham Lincoln
Creating Value
What are you doing to create value for yourself and your employer, now and in the future? How do you stay current? How hungry are you?
Here are some tips for keeping yourself sharp and valuable:
- Make yourself accessible to your coworkers
- Get yourself in the loop
- Communicate and be responsive
- Make your product look good
- Make your producer (project manager) look good
- Ask those around you what you can do to be more helpful
Followed by tips for staying current:
- Follow blogs (RSS, etc.)
- Participate with user groups
- Books
- Explore new technology
Robert C. Martin, in The Clean Coder, suggests developers spend 60 hours per week at their profession. The first 40 for their employer, and the remaining 20 for themselves by means of practice, working with new technology, learning a new language, etc. I would offer that those who sufficiently prepare will reap the most satisfying rewards.



