- Feature Articles
- CodeSOD
-
Error'd
- Most Recent Articles
- Stop Poking Me!
- Operation Erred Successfully
- A Dark Turn
- Nothing Doing
- Home By Another Way
- Coast Star
- Forsooth
- Epic
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
You have MUCH to learn, young Padawan.
Admin
Admin
My school abolished Assembly language from its curriculum right after I graduated... Go figure.
Admin
Puns, double entendre, innuendo and wordplay in general are the height of humor, enabling us to slip the surly bonds of earth and dance the skies on laughter-silvered wings.
Admin
I'm currently on version 5 - from rock star to on the way of becoming a dinosaur
Admin
What "rock star programmer" would take a job coding Visual Basic? Of course they sucked.
Admin
Also I can't see the second page. It's that "An Error Occurred" page that still says "Worse Than Failure" in the title bar.
Admin
I showed my project manager the image and said "Hey, I found a picture of you!"
Admin
-Harrow.
Admin
Then explain it, oh so brilliant one. How is it anything other than a jab at conservatives?
This is a serious request.
Admin
That should have been quoting this:
Admin
One time my company royally screwed in my review, and I got a pittance of the full raise they had promised me after pulling many extra hours and taking on extra projects. So I applied my rule and gave myself a raise. (Came in later, left earlier.)
It's amazing the number of companies that expect work ethics from their employees and yet have no pay ethic.
Admin
Sounds like the perfect time for some dinosaurs to insist on a raise.
Admin
Good for you! If a company only pays you enough to keep you from leaving... you should only work hard enough to not get fired.
Admin
i agree with the point of this post, and have had similar experiences. when talking about the question of why the 'dinosaur' developers aren't trained on newer technology, nobody has suggested that those old school developers rarely want to learn anything new. i'm a contract unix developer who does a lot of work for larger companies who tend to have a lot of legacy mainframe apps they're trying to convert or at least document. i can't tell you how many mainframe guys i've worked with who absolutely refuse to learn anything new. any discussion of any technology quickly devolves into 'everything works better on the mainframe', etc.
as far as the question of why younger folks aren't trained on older tech, businessmanprogrammersteve got it exactly right. unless you're willing to purchase an as/400 or mainframe, you can't learn those technologies on your own. oracle, java, linux, sqlserver, websphere, etc. can all be downloaded for free (if only in some demo version). if you genuinely want to learn these technologies, all you need is a decent workstation and an internet connection. you can't say the same for mainframe technologies.
Admin
Hmmmm.
I must admit that this strikes pretty close to home. My job just got eliminated because of outsourcing to a dev team in India. Though I'm a bit divided about it.
On the one hand I don't have a job and I have to go through the hassle of getting another one.
On the other hand I don't have to deal with a database design that requires 9+ joins just to get anything worthwhile.
On the gripping hand I'm at home, surfing the web and having a cold beer.
Life ..... is good. :)
Admin
Admin
Admin
Actually in my post way up there (number 2) I implied it. As a company you state that you are moving forward, you bring in some new guys, a few of the old ones leave, some stay. You can assume the ones that leave are the ones that don't want to learn, the ones that stay are looking at the future.
Admin
Wow, sounds like the job I just left. Nothing was human readable unless you performed like 27 joins in the database.
The guy who designed it thought it was a great idea. I'm all for normalization but joins can be an expensive operation too.
Admin
Admin
Admin
I agree but often the good back end is running on machines/os's platforms that are being end of lifed. Eventually those dibol programmers are going to want to retire and there aren't going to be many new ones (if any).
So sometimes a complete tech refresh isn't a bad idea.
Admin
Admin
I'm a leftist and I didn't find the comic particularly funny. Actually I was trying to figure out what the joke was. I was thinking it was somehow poking fun at liberals. I guess I was over thinking a rather poor attempt at humour.
Admin
The idea is once you've rewritten the front end, you can work on replacing the back end. This is often safer and faster than replacing the whole lot at once.
Admin
If I had access to magic pixie dust, I wouldn't be wasting it on work.
Admin
Depends on how well the interface between front and back end designed. Sometimes the only way to fit into what exists is to just recreate the same crap you're trying to replace.
Admin
Indexed data files are not a WTF. Every database is some kind of organized file format.
A poorly designed SQL schema can be far worse than indexed files stored on VMS. Someone chose proper indexes on the VMS. Do you think the rock stars put in equivalent SQL indexes?
Many COBOL-style data files are ISAM format. MySQL even uses an ISAM derivative for its table-files.
Admin
A guy I work with has a photocopied T-Rex on his wall from 15 or so years ago. The caption? "The mainframe is back ... and its pissed!"
Admin
True, for this to succeed you need a well designed interface. A strait forward Transaction A == Screen A is not likely to work well.
Although often (and it appears to be the case here) it's not that the old stuff is crap, it's just that it's getting to old to maintain.
Admin
What is this "proper documentation" that you speak of ?
Admin
Admin
Admin
[quote user="A Gould"][quote user="jetcitywoman"] Seems a shame that no-one is learning established systems anymore...[/quote]
Come see some of the unis around here. I just started a unit that includes a section on thinnet. No mention of ADSL or anything modern, but the classics are well covered.
Admin
Don't be a tool. It's saying that most tech workers aren't 'conservatives'. Of course, 'conservatives' aren't really conservatives either.
Admin
So write a front end that screen scrapes the current system. Come up with a datamodel/architecture that can be migrated piecemeal, and move things from screenscraping to direct access bit by bit. Incremental approaches work better
Admin
seriously? that was a lame story.
Admin
sad but oh so true
Admin
BWAHAHAHAH you make me laugh :)
What a curious concept you have put forth.
Admin
[quote user="FredSaw"]Shouldn't this topic be titled, "Jurbuttic Programmers"?/quote]
It definitely should have. At work, I cannot open a page that has "ass" somewhere in the URL (a true WTF in itself). In "full article" mode I could read it, but not open the comments.
Admin
The flip side is that the 'boss' sees conservatives as 'dumb' because he has no response to their arguments (or mean, if dumb is an obvious miscast).
Admin
Die, asshole!
Admin
Admin
(Interesting: change the CAPTCHA and the spamming starts. Still, it's not exactly hard to read. But irrelevancies aside...)
Evolution? That's the development process that involves accepting a failure rate of over 99%, right?
Admin
And therein lies the problem with fresh blood. You think you can redesign the application from the ground up.
You know how there are WTFs on this site? You will be contributing your own.
Admin
Alex, great article! As a 23-year veteran with Synergex, the company that continues to enhance the original DIBOL language (now Synergy/DE) to keep it current with today's hardware, OSs, databases, web interfaces, APIs, etc., (Ok, I'll stop with the shameless plug), I have encountered numerous experiences similar to yours—most of them with the same outcome you described. Just yesterday, literally, I received a call from a customer who said their non-technical upper management wants to rewrite their 32-year old [successful] Synergy/DE-based application that is running on OpenVMS to a Windows-based VB .NET/SQL Server system. The genesis of this direction was an acquaintance of upper management who offered inexpensive offshore resources to rewrite the application.
Years ago, I used to fret over such calls. Now, I still fret—but more about how much time and money the company is going to waste by making these hasty decisions without first defining what their "business-based" objectives are--just to ultimately return to their original [successful] application. After all, isn't the only reason to have computers and applications in the first place to either reduce costs or increase business? How will the rewrite really affect their bottom line? Will they have more business when their applications are rewritten? Will they require less resources/personnel as a result? What are the expected costs of the rewrite? Etc. Etc.(This is a whole subject in its own right.)
Companies could save a whole lot of money (and anguish) if they just took time to ask themselves some fundamental questions before making these leaps—questions like, can we achieve our business objectives by evolving our existing (time-tested) applications to new technology instead of making revolutionary changes? In my experience, you can't take an application based on 20 years of development by multiple developers and rewrite it in a new environment in 5 years (not to mention 1 or 2, which is what is often expected at the beginning of these projects). It's mind-blowing how much time and money is spent on rewriting applications just for the sake of rewriting them -- often at the request of what you call "rock stars" -- just to determine that the original environment was as good as or better than the new one which may or may not ever be achieved.
Anyway, I'm preaching to the choir -- thank you again for the article and for sharing your story.
Bill
P.S. If that customer you referenced still wants to achieve their business objectives, utilizing the experienced dinosaurs to "evolve" the applications, have them give me a call.
Admin
DIBOL?
DIaBOLic? ]:->
Admin
Oh boy. Three years ago I was the graduate. Fortunately for me I was hired by a start-up company. I wasn't even hired for IT, but due to need and my fresh IT degree I became a in-house developer. The lessons I learned were invaluable to me, but looking back letting people with as much experience as I had then build something for SALE... Idiotic is the word.
Admin
Is it just me who utterly loaths the new buzzword term "rock star programmer"?
The term is used as if it's a good thing. To me, the term immediately means something bad - "rock star" when prepended to "programmer" or "developer" is the diametric opposite of "good software developer" or "good programmer".
To me, the words "rock star" imply the following, especially when applied to "programmer" (even more so than "rock star" on its own):
Which I think are the attributes you absolutely want to avoid in a good software developer. To me, a good software developer should be humble enough to (a) recognise when they have made an error, (b) not get stroppy when someone tells them this (even if it's a junior colleague). A good software developer should always be aware of their own limitations, and quietly and without fuss learn what's needed to try and address these limitations. A good software developer should be persuasive when arguing a technology issue not by shouting down the other party, but by making well-reasoned, rational and adult argument.
Most of the very good and very competent software developers I've worked with have fit this. In my last life, code inspections were a way of life, and there was nothing worse than doing the code inspection with the "rock star developer" because of the arrogant, egotistical attitude. Fortunately, we only ever had one of these "rock star developers" and they left.
We're going to be hiring a new person to our team eventually. When we do, I've got half a mind to write the ad in two parts actually advertising the same position, but one half of the ad asking for a "rock star" and the other with a more humble description...then immediately reject the CVs (tr. US: resume) of anyone who responds to the "rock star" half - because any software developer who calls themselves a "rock star" is obviously full of themselves and will be a nightmare to work with. It reminds me of that study that was done a few years ago - the incompetent vastly overrate their skills, whereas the competent are continuously paranoid that they might not actually be competent and tend to underrate their skills.