- Feature Articles
- CodeSOD
- Error'd
- 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
The company I work for depends on a small program written in the early 1990s. It was written to handle a single stream of data.
Over the years it expanded, with many variants of the same core program tucked away on the network.
Now, the application was somewhat thoughtfully designed.
As it starts it draws configuration information from a database file.
But instead of one central file, keyed by version ID, each deployment has it's local copy of that file.
Keep in mind that there are ten year's worth of this program scattered across the network.
Some are doing important work.
Some are doing nothing.
But we can't just kill 'em off, because there's no good way to tell which ones matter and which ones don't.
We upgraded a third-party library.
Unfortunately, naming conventions and such prevented us from reusing the existing path.
A solution was at hand, as this had been foreseen oh so many years ago.
Just update the configuration field for the path - in every copy of that file.
Oh, my aching head.
Admin
I realize this is a long dead thread, and likely no one will ever read this, but I just have to say: You gave them code? I'd have said screw these nimrods...
Admin
I read it. :)
Admin
Admin
I read it too. And yes, he gave them code. But he didn't say the code was VB. He probably gave them C++, which they couldn't read!
Admin
I still think you should've tried to sell it to them for 10k. I mean, heck, that's over 50% off!
Admin