Skip to comments.10 dying IT skills (No matter how good you are with these skills, you won't get a job today)
Posted on 07/21/2009 5:31:52 PM PDT by SeekAndFind
click here to read article
Learn .NET and Silverlight. Nice combo right now.
You have to make the time to keep current. It isn’t easy but it is necessary in this field.
Good. I only heard of one of those 10 things anyway.
COBOL is dead, dead, dead. Yes, there are people still doing it and getting good money but it is a dead language meaning nothing new happens to it.
Many languages die: it is fine.
Currently I use .NET, C#, Silverlight, Office integration, and other techs sometimes.
Yes, I have used COBOL, JCL, SyncSort, MVS, Unix, etc. but I stay moving. This is not an industry that forgives dust on a resume.
My buddy just talked to a client today that purchased a Dell with 48 logical cores and 128GB RAM for under 25K. That, and years of it, spells death for a lot of older systems (and languages) due to mainframe licensing policies.
Most popular languages and how they are doing.
I have a hard time believing this one. You have to write several pages of code in COBOL to do what you can do in one page in C or Fortran or Visual Basic....
I think it’s because, as a rule, bank managers don’t particularly like math and don’t like people who do....they’d rather rely on the old code than try to develop something better.
bump for the good old skills
Does anyone care an iota about APL?
I haven’t yet gone to the suspenders.
LOL! Dumps, I remember reading dumps at 3 AM.
She left something off the list:
11.) Editing and writing news and features for online and print.
12.) Creating and launching news Web sites
13.) Cisco Systems
Nope. As I tell my friends, never trust a computer that you can lift. :-)
Reminds me of when C++ came out. The COBOL people were going to create an object-oriented version called “Add One to COBOL” :-)
Piece of cake, actually. It’s just a language that defines the environment in which a program runs.
Not bad for a language that was only released a couple of years ago.
"An Equestrian's View of Deferred Mounting"
"The Pope Speaks Out on Unit Affinity and Separation"
"Camper's Guide to the Link Pack Area"
and so on. I know that dates me - especially as I have it only in hardcopy.
So SAP experts make in the neighborhood of 65-70 bucks an hour?!!!
Wow, time for me to go to school I guess...
135 - 145K a year to work in SAP all day long....
Maybe that’s still not enough. I really hate school!
Sounds like a plan. I can remember avoiding the use of index registers because not all S/360s had them - was a priced feature, as was the decimal instruction set.
And I remember looking up instruction timings for real-time code to optimize it.
Overlay programming, anyone?
I earned every one of these gray hairs!
hehe.. And that reminds me, during college we had Niklaus Wirth visit to give a lecture on language design using his Modula-2 as an example. It turned into a two hour rant about C.
I have switched to using Apache Wicket for web development. It’s great! No more embedded scriptlets, or tons of XML configuration. Just plain HTML and Java backing classes. I can use any HTML editor to design the look and feel with CSS.
Why can't you just code in B? /Pointy-Headed Manager
I’ve been looking at Scala. It runs on the JVM and combines the best of both Object-Oriented and Functional programming languages (like Erlang). I could see it one day replacing Java as the primary JVM language.
The fact that VB is still going up disgusts me. What was kept around to lure VB programmers to .NET so they can be weaned off onto a real language is actually being used for real production. It can’t even natively multi-thread.
It’s just strange that any company would seriously consider programming any new application in VB. Use the skill for maintenance maybe, but rewrite it as they go if they’re smart, to c# if staying on Windows.
I've worked with those, "My code is perfect. You won't be able to find one thing wrong with it." Famous last words.
It's an attitude problem. Anyone who takes QA dings as a personal offense needs to find another field. Anyone who sees QA as a chance to improve his code is someone I want to work with, since that's the kind of programmer I am.
emacs has everything but a nice text editor. vi forever!
How is that a skill? Any UNIX guy who doesn’t want to be caned like a American teenage painting graffiti in Singapore can script in multiple languages.
If we didn’t keep deciding every few sprints that we’ve got a better plan we might actually accomplish something. Seems just at the point where it’s starting to look like an application the etch-a-sketch shake happens. But even without all the reboots I find user stories just insulting.
I can draw a snowman in GWBASIC, but my Turbo Pascal skills are getting rusty.
It was just an observation on the language itself. Why the hostility over it?
It’s important to be partners in making a better product. I always try to keep in mind that it’s my job to call the developers’ baby ugly and that it’s understandable for them to get a little defensive once in a while and to just ride that initial wave so we can get to productive talk. And it’s important for me not to be accusatory, always try to avoid phrases like “screw up” and “your bug”, keep it neutral, it’s a bug they happen now let’s fix it.
But some guys just can’t handle it. I had one always argumentative developer tell me that since he had a masters he didn’t believe anyone with less that a bachelors should be testing his code, I replied that it didn’t even take a high school diploma to double click on the icon and watch his application crash and maybe he shouldn’t be worrying about our qualifications. Nobody liked Pierre.
Well, course you have to picket outside MuSnot and chant about how proprietary software is the same as theft! Free beer, code and sex all around! Oh, wait, we don’t have any girls....scratch that last part!
I [don't] Enjoy DP.
Are you kidding me? After about 15 minutes, I'd be asking to borrow the drill.
Heck, I can thank my COBOL and MVS/JCL skills for surviving the last purge where I work. Even though I'd not used them much in the past 20 years, the fact that I could and WOULD program in COBOL and even a little BAL was the tipping point between me and another guy in my department.
With all the COBOL love flowing here, let’s take a second to remember that great comptuer pioneer, Admiral Grace Hopper, the mother of COBOL (and finder of the first literal computer bug and the one who first implemented language standards). It may look antiquated now, but it was revolutionary in the 60s.
COBOL if it still works, why fix it.
What do you guys think about Visual Basic for Applications (VBA)?
Very true. I work for a small section of the Dept of Education that is using such an old legacy system that there is only one (very old) employee left in the whole nation who knows the programming (”Easytrieve”).
When he retires I don’t know what we’ll do. No contractor wants to get involved with such old boring stuff, and no federal employees can seem to learn to program.
We can’t get a new system because when we try to get new huge expensive contracts to do so, they somehow fall apart and fail.
I guess that also leaves out anyone who can re-punch an employee’s payroll information on a card when the damn reader eats it? (sarc. extreme)
I had a buddy who received a panic call about some machine that he had done that had some bug that couldn't be described very well but which it was imperative had to be fixed immediately. So he gets on a plane, goes to the plant and checks in. He's sent out to the machine to check it out. Well, he operates it a few cycles and can't seem to find anything out of order. Tells the powers that be, who say they'll send out the operator to demo the problem. So the guy comes out and he presses several buttons on the control panel simultaneously, while reaching way out with his foot to trip some sensor in the machine, causing the machine to malfunction in some way. That was the "bug".
I knew another guy who was on site commissioning some equipment which was functional enough to use and needed to be. So during the day, he would do software things he could do online (the platform allows online edits without a restart), then after hours do more invasive things he couldn't do while running. So he comes in the next morning and is told the machine won't start. Goes over to the machine, presses "Start" on the touchscreen, and wham-o, magick-o it starts. Turns out the operator can't read (!) and has learned to operate the touchscreen by remembering button positions. The guy had moved the location of the start button the previous night to make room on the screen for some added features.
So anytime you think you've constructed a foolproof system, the universe simply starts supplying a better grade of fools.
Old school data processing.....those were the days!....Mag tapes dumping in the vacume column...cards getting mangled in the reader. That damn ball and string on the master console breaking during an IPL....Many bars were filled with D.P. people after hours.....
So long as the COBOL systems function, can be updated at moderate/reasonable costs, and developers/maintainers can be found, COBOL will continue to thrive. There’s just too much vested in those systems to risk making a multi-billion-dollar transition to a new system which does exactly the same thing.
One fact of programming: legacy systems embody a great deal of wisdom which is not otherwise documented or known. Wholesale replacement of a system is a tremendous risk precisely because those creating the new system don’t know what vital yet obscure processes are performed by the old. Such replacement rarely happens unless there is an imperative to do so, such as outright parts obsolescence or skyrocketing cost of maintenance. In the case of big-iron legacy systems, it’s cheaper to teach someone an old language.
Kinda like Latin: allegedly dead, yet there is still great value in learning and using it in narrow yet big-budget “systems”.
Gracie Hopper! (Doffs hat, hand over heart). Ur-Geek before being a geek was cool and even before being a geek wasn’t cool.
The latest incarnation is Object-Oriented Cobol for the Java Virtual Machine. Much as we want it to be, and as terrifying as that concept is, COBOL isn't dead yet.
If it finally dies, methinks it will be because no self-respecting programmer will learn it.