A job I got to help put myself through college involved computers (back when computers were not well-understood outside of IT circles). They wanted me to take account information from an old DOS-based database and transfer it manually over to their new Windows 3.11 database. This involved opening the old database file and the new database file and manually entering the information from the old one to the new one. There were about 40 fields per account, and this was long before the days of dual monitors, so I’d be alt-tabbing back and forth 40 times - each account migration took about 10 minutes. There were thousands of accounts.
They figured I’d be at it for years (really huge insurance company, and this database had all of their customers in it).
Well, I figured, there’s gotta be a smarter way to go about doing this:
All of the information on the old database’s display was always in the same place on the screen, so I wrote a macro that used keyboard navigation to pop to each field, copied the information, then alt-tabbed to the new database and pasted it. Then it would go back, pop to the next field, and repeat. What had taken 10 minutes per entry now took about 30 seconds. And it could run all night, when I was at lunch, etc.
Long story short, in 3 weeks, the migration was done. They were very impressed and congratulated me. Even gave me a little company logo mantle clock thing that they usually gave to long-time employees on their nth anniversary.
And the next day I walked in and they fired me. “Well, we don’t have any more work for you to do. Sorry.”
That taught me a very important lesson about not thinking your way out of a job!
The coda that somewhat delights me is that this insurance company no longer exists. It had efficiency problems, wasn’t making much money (how the hell do you not make a ton of money in the insurance game?) and was bought at a fire sale by a competitor. Perhaps if, instead of firing me, they’d had me go look at their other ultra-inefficient processes, they’d still be around