[gnosis]

There are still COBOL jobs. But are they the kind you're interested in?

If you're interested in, say, web programming, you're probably going to have a hard time finding a job doing web programming in COBOL.. no matter how great your interviewing/job-hunting skills are.

The same goes for many other preferences regarding work, from location to the kind of company you'll be working at or people you'll be working with. If most jobs you're interested in largely have openings for people who know language X, you'll probably be better off knowing that language.

On the other hand, it's certainly a good idea to have well-rounded skills. So if you're particularly weak at people skills, or job-hunting skills, it's a good idea to work on improving those, as often being a good programmer is not enough to land the job you want.

[gjm11]

> you're probably going to have a hard time finding a job doing web programming in COBOL

Nah. See http://www.coboloncogs.org/ . :-)

[ahlatimer]

I can easily find you a job doing web programming in COBOL. The first tech company I worked for decided to build their new task system in COBOL. I can't really remember the framework they were using (RMCOBOL, I think), but they had somehow managed to find a way to get Apache installed on a HP 3000 that communicated with a COBOL web app.

Keep in mind, I'm 20, and I only really started working when I was 18. This all happened two years ago, and I seriously doubt they've stopped using COBOL in that time.

[GFischer]

The best-paying jobs advertised at the state telecom are for Senior COBOL programmers. That definitely makes me wish I knew it a bit better :P (I did have COBOL classes at college, and I'm 29)

[ahlatimer]

It's an easy enough language to master. There aren't a whole lot of constructs. The difficulty is wrapping your head around the massive lines of code that any COBOL program of reasonable complexity is bound to have. Not to mention every variable being defined by what it looks like, no notion of scope, no syntactic sugar like for or while loops, and no notion of methods. It's all supposed to read like English, but while English can pack a lot of meaning in a few statements, COBOL can't do anything in a few statements.

[ivenkys]

"I worked for decided to build their new task system in COBOL" - this cannot be true .

[ahlatimer]

It is indeed true. They had a pre-existing task system that ran on the HP3000 that was built in COBOL. They modeled the new one (that was supposed to be web based) on the old one, and they decided to build it all in COBOL. I'm guessing they repurposed [1] some code, and they definitely repurposed the database. I think the goal was to have employees continue to use the command-line based task system while allowing customers to input tasks on the web. I think they also wanted employees outside the main office to still be able to access the task system if they were, say, at a client's office.

I left right around this whole project got started. I even mocked up the original interfaces. Twice. The first time I didn't do the whole thing in a table and my manager couldn't understand it, so I had to rip out any CSS and divs and go back to the 90's. They had two "graphic designers" on staff, so I'm not entirely sure why I was given that task, but there it is.

My whole time there seemed like some weird trip back in time. It took me a while to get used the copyright date on the COBOL compiler being two years before I was born.

[1]: "Repurposed" is used loosely. The way you build web apps in COBOL is so convoluted that it's extremely hard to use pre-existing code.