• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Revisionist history sure is fun

Exterous

Super Moderator
One of the fun things about long term IT Infrastructure projects is how easily people forget, revise or alter the account of why things are they way they are and who was responsible for what over the following 5+ years. I guess I've been here long enough now that now I get to play Official Timeline arbiter.

"Blarg! I can't believe this group made this decision on their own 5 years ago! It would have been so much better if they had talked to us!"

Er...no they actually spent a lot of time talking to other groups, including yours and getting input. I know you have some complaints but you also have to look internally for the cause of that.

At least my group has good collective memories but some of these others really like to morph history so they didn't have any involvement in 'poor' decisions
 
That is why email chains are important xd. I create multiple PSTs.
These days companies like to delete emails after a year, unless legally required to keep any. It's really annoying.
 
I mean I usually don't have to bring out the emails or meeting attendee list but I sure do have to remind people about historical context a lot
It's a back pocket thing. If you need to bring that out it is already too late.
 
We had a project come back to bite us a couple years ago. I was in the "who signed off on this dog?" club. I pulled the project file and I signed off on the damn thing fifteen years prior. I still have no recollection of working on the project. 😛
 
These days companies like to delete emails after a year, unless legally required to keep any. It's really annoying.
I guess there must have eventually been adequate outcry from the right people here, they implemented a 13 month policy here a couple years back, and just recently changed it to 24 months.
 
We had a new guy come in a few years back and he immediately bashed the guy he was replacing.... It told me right away that the new guy didn't have any real work experience with technology because he didn't take someone else's seemingly piss-poor SQL code as a clue that we have absolutely no data governance and literal monkeys doing data entry. Most of the time, I just code around the inconsistencies and report the issues to the data entry groups so I can say they were made aware of their errors and poor decision making.

Pertaining to the new guy, I've had to school that joker on numerous occasions since he stepped into his role. He messaged me just this week asking about data sources in the database and I not only mapped the sources within the reports/database, but the data entry teams I mentioned. Of course the issue was he was looking at the wrong data source to start with. Hopefully he learns something before he dies.
 
Back
Top