Contribution 1

From WikiContent

Revision as of 19:58, 9 May 2008 by NitinBorwankar (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

Don't put your resume ahead of the requirements.

Often as engineers we recommend technologies, methodologies and approaches for solving problems because deep down we want to have these on our resume and not because these are the best solution for the problem. Such decisions very rarely result in happy outcomes.

The best thing for your career is a long string of happy customers eager to recommend you because you did the right thing by them and for the project. This goodwill will serve you orders of magnitude better than the latest shiny object in the latest shiny language or the latest shiny paradigm. While it is important, even critical, to stay abreast of the latest trends and technologies this should never happen at the cost of the customer. If the project isn't cutting edge or challenging enough for your current career needs then find one that is.

If you can't do that and you are forced to be in such a project, then you and everyone else will be happier using the right technology for the customer rather than for your resume. With the right solution, the project will have a happier team, a happier customer and overall far less stress. This will often give you time to go deeper into the existing older technology or to learn the new stuff on your own time. Or to go take that painting class you always wanted to do. Your family will love you for it, too - they'll notice the difference when you get home.

Overall always put the customer's long-term needs ahead of your own short term needs and you won't go wrong.

By Nitin Borwankar

This work is licensed under a Creative Commons Attribution 3

Back to 97 Things Every Software Architect Should Know home page

Personal tools