If there wasn't a massive 800-pound gorilla scowling at you from across the room.
I learned a new swear word in the class: Legacy System. Yes. Legacy System (all caps like He Who Must Not Be Name). Next time someone does something ridiculously stupid, infuriating and stubborn but I lack the power to ask them to leave, I will refer to them as a Legacy System. While they're laughing off my stupid insult, I'll understand the vitriol of my comment (and regret it later).
Seriously, from firsthand experience, a Legacy System can hamstring a company's progress by years. System inefficiencies gobble up man power (which costs money) on tasks that should be controlled by simple button clicks. Data spread throughout multiple systems can't be accurately compared, updated or tracked in a useful ways. And overall data management picture is a sloppy mud puddle.
This best way to describe a legacy system is like this:
Which data management system should we choose?
This one? This one looks good.
At some point in the future, you might have a problem.
And you might think you've solved it...so you go to lunch or home or an amusement park.
Good times...
But Legacy System hates good times.
Really? The system just did WHAT!?!
Legacy System reveals itself for the first time.
You threaten to replace it but, inside, you know how empty that sounds.
Legacy System mocks your hard work and effort with frustrating displays of inefficiency.
And that's on Monday...
(special thanks to Alien in Pictures)
1 comments:
I'm going to enjoy reading this blog. I'd read it even if I didn't have to grade it :-)
Post a Comment