4 ms·
I worked on a six-month contract project for a large US retailer; the fact that everybody else I worked with was laid off the second week probably should have t
by CommieBobDole 3y ago
I worked on a six-month contract project for a large US retailer; the fact that everybody else I worked with was laid off the second week probably should have told me something was wrong, but they kept paying me so I kept showing up.
Anyway, the only task they ever gave me was to build Cisco router ACLs to match existing traffic in the stores; they needed to implement access control but wanted to make sure they weren't blocking anything important. Because many of the stores had been opened years before, there wasn't necessarily a consistent IT stack in the store; there were a lot of one-off solutions so they wanted a universal set of rules with per-store exception lists.
So, every week, someone would drop a few terabytes of network logs in an FTP server, separated by store, and I would distill them down to a set of rules; if something was being used in more than X number of stores, it went in the universal rule list, if it wasn't it went in a store exception list. At first I was doing it semi-manually, but eventually I built a database and wrote some SQL to mostly automate it - got it down to about two hours a week, most of it waiting for the DB, by the end. Once it was done, I would send all of my updates to a network engineer who was the designated point of contact for the access control project.
They had a lot of stores, and for some reason could only supply a certain amount of logs weekly, so when my contract was up there were still a number remaining. I tried to set up a meeting with the network engineer to go over the work to be done and the automation I'd built, but he never responded. Eventually I tracked down his desk in the vast corporate complex and paid him a visit. He was pleasant but told me that he wasn't even on the access control project and he thought it had probably been canceled at some point. He had been dutifully copying my updates to a network share somewhere in case they were ever needed. I gave him the SQL scripts and the database info and he put them out on the share where they probably still are today, a decade and a half later.
So that was six months of my working life.
- blantonl 3y agoSo that was six months of my working life >> /dev/null
- Aloha 3y agoIf the retailer is still in business that data has probably been lovingly migrated twice, and is now in a sharepoint somewhere.
- bombcar 3y agoIt’s even more amusing to have something like that, it gets shelved in the archives, and five years later it somehow ended up being half rolled out because some bright eyed intern found it and thought it was procedure.
- MajimasEyepatch 3y agoIt’s probably been leaked as well, maybe sitting in an unsecured S3 bucket for a while after one of those migrations.
- nothrowaways 3y ago> they kept paying me so I kept showing up. What a line.
- tmountain 3y agoIf this was your main gig, congratulations on getting a big chunk of your life back to do whatever you wanted. I really enjoyed reading your story. It reminds me a little of “the story of Mac”. https://wm-help.net/lib/b/book/2895812152/59 https://wm-help.net/lib/b/book/2895812152/59
- warner25 3y ago> ...he never responded. Eventually I tracked down his desk in the vast corporate complex and paid him a visit. He was pleasant but told me that he wasn't even on the access control project and he thought it had probably been canceled at some point... I love it. A co-worker of mine told a similar story. For at least six months, his only regular responsibility was to compile a report every week and email it to a distribution list for the headquarters one echelon above us. It wasn't a ton of work, but it was all manual and he was meticulous. He dutifully did this without any feedback until someone finally replied to simply say, "We do not require this report, and have never required it. You may choose to either continue or discontinue sending it."
- araes 3y agoBS: "Well just a second there, professor. We uh, we fixed the glitch. So he won't be receiving a paycheck anymore, so it will just work itself out naturally." BP: 'We always like to avoid confrontation, whenever possible. Problem solved from your end.'