CIO careers cut short due to poor coding

By Stuart Sumner

08 Apr 2011

Comments: 3

Businessman pointing at viewer

CIOs would have longer careers if they focused more on coding.

That's the opinion of Vincent Delarouche, chairman and CEO of software measurement and analysis firm CAST.

Further reading

"Most CIOs only care that the graphical user interface is sexy and that functionally [the software] must work. But what's inside the box? They don't care. And if you don't care, do you expect your staff to care?"

Delarouche argues that most CIOs are not interested in coding. As long as systems function in the specified manner, they are happy.

He concedes that software can work without necessarily being well coded but he sees good coding as adding to the security and reliability of a company's software.

"Good code should be secure, easy to maintain, reliable and efficient," he said.

He adds that the quality of the software on which a business operates impacts the bottom line.

"There is a correlation between the agility of your business software and your business performance," he said.

Delarouche identified three factors that are needed to fix the problem and deliver better software: the industry needs to define acceptable coding standards, these standards need to be enforced and CIOs need to be educated in the perils of poor coding.

This is having an impact on the length of a CIO's career.

"The average tenure of a CIO is well under two years. If a CIO goes in front of the CEO for the second time to say that a key piece of business software is late or inadequate, he'll be fired," said Delarouche.

Analyst firm Gartner's 2011 CIO Survey doesn't quite go as far as Delarouche, stating that the average CIO tenure in the UK is under five years.

Reader comments

Code delivered - ready or not

My experience is that the business give IT unrealistic deadlines with late, inadequate requirements. Is it any wonder corners get cut and software is not properly tested.

Posted by: Will  11 Apr 2011

Chris.. I don’t believe I said that..

.. “a CIO who sees his CEO for the second time to say that a key piece of business software is late should be fired.” I do think however that because it’s technical in nature, CIO don’t really care about their software – and I understand how much they have in their plate. The thing I wanted to convey is that if the leader doesn’t care, no one in the organization will care (mid-management, developers and suppliers). Also, that the best way to fix issues (security, resiliency, and the growing tech debt) is to look at the root of the problem. It’s interesting to realize that most vendor SLAs still don’t say a word about coding practice, while all agree that better coding and architecture would have a big and immediate impact on the business.

Posted by: Vincent Delaroche  09 Apr 2011

Good code is essential

But you shouldn't be fired for something being late. Mostly because you should never have agreed to a fixed delivery date in the first place, more of a rolling beta programme that one day you declare as released...

Posted by: Chris Puttick  08 Apr 2011

Have your say on this article

All fields required. Your email address will not be displayed on the site.

By submitting a comment you agree to abide by our Terms & Conditions

  • Digg
  • Tweet

Newsletters

Sign up for our FREE newsletters

Technology Patent Wars

Large companies such as Microsoft, Facebook and Google have been hoovering up technology patents recently. Is this stifling innovation?

88 %

4 %

8 %