- Whether to mention a pregnancy in a job interview
- A possible meeting protocol
- What are an end-user's responsibilities?
- Another take on opening PCs, or not
- Getting some process going
- Selling a more open environment to management
- Running an effective meeting
- Licensing rules for virtual machines
- The ROI of metrics
- Legal challenges to virtual machines
January 13, 2007 | Comments: (0)
How to interpret COBOL statistics
Dear Bob ...
Consider the following items allegedly gathered from various Gartner reports:
* There are 310 billion lines of legacy code operating in the world (65% of all software).
* Five billion lines of new COBOL code are being written every year.
* Fifteen percent of new application development is written in COBOL.
* Thirty-four percent of coding activities are in COBOL.
* Seventy-five percent of the world's business data resides on mainframe systems.
* There are 38,000 legacy systems at more than 10,000 mainframe sites worldwide.
* COBOL developers are retiring much faster than they are being replaced as educational institutions emphasize more cutting edge technologies.
I am a 20 year software developer (IBM midrange, RDBS, OLAP, Windows) who happens to love what he does and has no aspirations to move into management. However the impact of globalization on the field seems to be driving more and more of the development work overseas. Would I be crazy to consider moving into COBOL development to keep doing what I love best? What recommendations or alternatives would you suggest?
- Planning my career
Dear Planning ...
Like so many published statistics, what's there can serve to conceal what isn't there. For example:
* Five billion lines of new COBOL code are being written every year.
* Fifteen percent of new application development is written in COBOL.
What's the trend line - is the number of new lines of COBOL code declining? The percent of all application development? And assuming it's declining, how steep is the decline? If Gartner were to subtract the COBOL work that's been taken offshore, how much is and will be left for developers located in the U.S.?
* COBOL developers are retiring much faster than they are being replaced as educational institutions emphasize more cutting edge technologies.
Are they retiring faster than the rate of decline of new COBOL development, and especially the rate of decline within the U.S.?
* Fifteen percent of new application development is written in COBOL.
* Thirty-four percent of coding activities are in COBOL.
Put these two statistics together and you reach a fascinating inference - it appears that COBOL coding is almost exactly half as efficient as coding in other languages. That is, the amount of coding is double the amount of development.
Which leads to another unknown - how much of the COBOL work is adaptive rather than truly new - that is, how much of it is going into interface maintenance and minor enhancements, to support new functionality being created using Java, Visual whatever, SOA development tools and so on?
My opinion: COBOL is in decline. If you're looking for job security, you can probably achieve it in the COBOL domain for at least another decade. My expectation is that wages will be stagnant, and most of the new, challenging, enjoyable work will be in more modern development environments.
I'll also say this: More than the technology, the future lies with versatile developers who can interact productively with the end-user community at all levels to understand what they need to do and can translate that into working software without creating volumes of documentation artifacts.
Just my opinion, of course.
- Bob
Posted by Bob Lewis on January 13, 2007 08:08 AM
RATE THIS ARTICLE:
-
- COMMENTS
If there are specific positions requiring Cobol that Planning has in line, I might go for it (assuming those positions seem to have a solid future). On the other hand, there are many more jobs where Java and related technologies are required. If I were to put some effort into learning a new field, Java is where I'd go. (Speaking as an old Fortran coder who *is* learning Java, among other interesting new things).
I work in a very niche market -- replacing aging VAX computers with emulated hardware. It's a good place for me, a 1-person shop. However, this market will eventually disappear.
I have experience and certifications in Linux and other server types. I market these other skills as being "cross platform". There's almost no company of any size that doesn't have systems from multiple vendors, multiple OS's, multiple languages, etc.
Sure, invest in some Cobol training (I've thought about it myself), but keep learning "new" stuff, too.
Remember: only you can be in charge of your career. 20 years old, or 70 years old, you'll have to keep learning or die.
Posted by: Stanley F. Quayle at January 19, 2007 07:39 AM|
Three books. Three ways to change the world, your life, or at least Bob Lewis' bank account. Leading IT: The Toughest Job in the World distills the world of IT leadership into eight learnable skills and gives you concrete, practical techniques for each one of them. Bare Bones Project Management: What you can't not do makes project management manageable, even for first-time project managers with no formal training in the discipline. ManagementSpeak: What managers say/What they mean … well, it won't help your career, and won't make you a better manager. Mostly, it will make you chuckle, guffaw, and maybe even chortle. Make friends - it's the perfect gift for anyone who has ever suffered through one of those meetings. Order your copies today! |
TOP STORIES
ADDITIONAL RESOURCES
- Virtualization: A Step by Step Approach to Success
- Dialing up Agility with Business Transformation
- 5 Things You Need to Know About Storage Virtualization
- Is your smaller organization ready for High Availability?
- Is system maintenance doing more harm than good?
- Virtual Test Lab Automation: Manage development infrastructure
