8 raisons de ne pas l'être, 5 de l'être : Meridith Levinson se penche sur le cas des informaticiens qui voudraient devenir DSI... ou pas.

8 Reasons Why a Developer Would NEVER Want To Be a CIO

1. Software developers live to write code.
Writing code is the light of a developer's life. The fire of his loins. His sin, his soul. (Thank you, Nabokov.) Writing code is a compulsion for software developers. They have to do it-often at the expense of personal grooming, developing their social skills and cultivating relationships with the opposite sex. Becoming a CIO would take them away from their one true passion.

2. They like to see the fruits of their labors.
Developers don't want to spend their days in meetings, manage petty squabbles among subordinates or beg for budget dollars. They want to do *real* work. They want to have something to show for their work. They want to point to a software application and say, "I built this," not, "My team built this."

3. No habla Ingles.
Many developers express themselves better in Java or C# than they do in English. That doesn't fly for CIOs, who have to be able to clearly and convincingly explain to their management teams and boards of directors IT's value.

4. Revenge of the nerds.
The dream of becoming a legendary hacker is far more exciting to a software developer than the prospect of becoming a CIO. It's also a much more realistic career goal. Landing a good CIO job these days isn't easy.

5. Developers don't aspire to be anyone's bi***.
Let's face it: Much of the CIO role requires sucking up to the CFO and CEO. Developers prize their integrity and think corporate politics is for wonks. What's more, they'd rather cannibalize Cowboy Neal than report to and take orders from executives who don't understand technology.

. Web-profils.com, la place de marché du conseil et de l'ingénierie