1. he was NOT the genius they thought he was, just because he knows more than his customers doesn't make him anything more than smarter than non-techies
2. looks like he wrote shitty code
3. he's an asshole
Josh and his company needed one thing to happen so be successful, fire his ass at the first sign of idiocy. refuse to help your team, gone. treat a customer like shit, gone.
the problem with this story is clueless and spineless management letting a bad situation escalate.
Josh was a moron, not a genius. rename the thread appropriately.
COBOL on the mainframe processes data like you would not believe.
if you have boatloads and boatloads of data and you need it massaged, there is no other tool that can outperform COBOL on big iron, unless it SYNCSORT on the mainframe.
besides, the side effect of needing to write JCL makes COBOL that much cooler.
so what if some bozo in a suit calls something "legacy"
"legacy" is simply any application that's in pure maintenance mode. hell, in some cases, legacy is simply a reference to an application that's no longer sporting that new code smell. Legacy is also simply a term to disparage, based on nothing other than the speakers opinions.
Lets see management CHANGE that code. that costs money. and working legacy code is much cheaper than writing a new system.
At my company, a VERY large one with an IT shop of thousands....the Python dudes won a culture war against the Perl dudes (and VB dumbasses, Korn dudes and others) and mandated that no more new Perl would be written, as Python was the new Grail. Lets see, that was about 5 years ago, and that same group begrudgingly had to approve Komodo purchases to "do perl" about 3 months ago.
yeah, they whined, they stonewalled, they demanded, but in the end, we just kept writing in Perl. with full management support.
because when the rubber hits the road, most front line IT managers are not complete idiots, and when presented with a whopping estimate to do essentially "busy work", even the most determined IT suit will capitulate to reason.
They may as well dictate the friggin' Weather as mandate all code in X be rewritten in Y (especially when X works perfectly fine)
1. he was NOT the genius they thought he was, just because he knows more than his customers doesn't make him anything more than smarter than non-techies
2. looks like he wrote shitty code
3. he's an asshole
Josh and his company needed one thing to happen so be successful, fire his ass at the first sign of idiocy. refuse to help your team, gone. treat a customer like shit, gone.
the problem with this story is clueless and spineless management letting a bad situation escalate.
Josh was a moron, not a genius. rename the thread appropriately.
my goodness, if lies = stink, I suspect the Obama's needed some air fresheners to even set foot in the white house.
this thing can populate your machine with virues, trojans, adware, scamware and other Microsoft products faster than ever!!!!!
still can't spell CSS
I must say what an awesomely incredible waste of good hardware
good work IBM
now fix Clearcase
let your buffoonish boss you intend to speak to the FBI (assuming this is in the USA) about being blackmailed, and legal counsel.
bottom line in this country, they can't say boo negative about you, all they can do is confirm employment.
if you already have a new job, then call in sick for 3 weeks. or just leave.
hell, if you have any proof (witnesses) that can attest to this, you may never need to work again.
I bet most of congress doesn't know what a router even is
she snarled, hissed, then peed on it
I look forward to the new and inventive ways to hide toxins in consumer products.
No Cisco, no gov't hack.
we need credible change
their main university has COCKS on their hats.
too bad this is happening so soon in the year, when the "dumbest stuff of the year" awards are held, this might be overlooked.
call it
"My incriminating evidence"
and then put in the terms of service that one must use it for all evidence of illegal activity
you mean the snake bit the entity that carried it across the river?
nothing to learn from this, move along
because eventually some of them will evolve into real hotties
COBOL on the mainframe processes data like you would not believe.
if you have boatloads and boatloads of data and you need it massaged, there is no other tool that can outperform COBOL on big iron, unless it SYNCSORT on the mainframe.
besides, the side effect of needing to write JCL makes COBOL that much cooler.
I don't even have to list one my disgusting ideas for what to call their website when links.
use your own imagination, hang it off this thread....
wall street gets their free cash, but not from taxpayer wallets.
win-win
nice new abuse of the word.
I guess when Microsoft facilities people decide to change brands of Toilet paper it's called "innovating taking a dump"
He did his routine, now it's time for the next comedy act.
I thought his routine was a stinker, but then again, he didn't have good material to work with.
sounds like if Palin falters, McCain has his new running mate
check the reservoir, they like to mess up water supplies
this is the worst thing that could ever happen to IT.
until you've coded Perl using ISPF/PDF
to sell a joke?
Of course Perl isn't dead.
so what if some bozo in a suit calls something "legacy"
"legacy" is simply any application that's in pure maintenance mode. hell, in some cases, legacy is simply a reference to an application that's no longer sporting that new code smell. Legacy is also simply a term to disparage, based on nothing other than the speakers opinions.
Lets see management CHANGE that code. that costs money. and working legacy code is much cheaper than writing a new system.
At my company, a VERY large one with an IT shop of thousands....the Python dudes won a culture war against the Perl dudes (and VB dumbasses, Korn dudes and others) and mandated that no more new Perl would be written, as Python was the new Grail. Lets see, that was about 5 years ago, and that same group begrudgingly had to approve Komodo purchases to "do perl" about 3 months ago.
yeah, they whined, they stonewalled, they demanded, but in the end, we just kept writing in Perl. with full management support.
because when the rubber hits the road, most front line IT managers are not complete idiots, and when presented with a whopping estimate to do essentially "busy work", even the most determined IT suit will capitulate to reason.
They may as well dictate the friggin' Weather as mandate all code in X be rewritten in Y (especially when X works perfectly fine)
if only there was a terror threat from space. NASA would be up to their eyeballs in no-need-to-account-for cash.