Legacy Issues

Future Legacy

I’m going to talk a little about Legacy issues and my problem with them.

In a word: E V E R Y T H I N G

In case anyone is wondering what a Legacy issue would be let me paint a little picture. I’m in the process of putting together documentation that explains a new way of guiding a user through a specific application. I’ve changed some of the interaction, I’ve changed a some of the visuals and I’ve changed the language. I’ve gotten all the way to the point where the concept looks like a banana whereas the original application looks like a peanut butter and jelly sandwich… on rye.

I’m pretty proud of the work – it’s not groundbreaking but it does introduce some new concepts to a rather old application.

And then I had a meeting.

Scott – “So this is what I’m proposing”

Old person – “I don’t get it”

Scott – “That’s fine, let me explain so you can understa-”

Old person – “No don’t, it’s not going to change because”

Scott – “Why?”

Old person – “Because that’s how we have always done it and I’m too old and broken to understand anything beyond DOS.”

So that’s my situation – Thanks god for the weekend.