seeing this one and being like "ah using ETL principles to make sure your application isn't completely fucked"
anyway you have no idea how bad big companies data warehouses can be :)
ah yes i totally love how the front-end application at my last job let people just change policy numbers in place with no way for me to know that happened except that my audit controls are now failing because the policy count no longer matches to the source and target
0 */4 * * * /home/dba/backfill.pl
if this ever misses running more than once in a row we will be in immediate SOX, GDPR and ASBJ violation and we're all going to double-jail
oh god if you're at a company large enough to have to comply with sox controls you should NOT be using cron for ANYTHING
It runs on an old Dell Optiplex in a wiring closet on the third floor that's still running Linux 2.6.32 because everyone's afraid to touch it. It was implemented as a temporary hack in 2002. We'll be getting rid of it as soon as the Oracle deprecation is complete (ETA 2032)
One of the projects I was on is I had some reports that reported on network circuit utilization for the Infrastructure team. The process I inherited was some SSIS bullshit that was reading a series of text files that were being written out to a share path by some windows XP laptop living in someone's cubicle.
We eventually got onto Solar Winds which can like, actually export a single CSV file and I rewrote the whole thing in informatica because fuck SSIS
Edit: did i mention I did this at the end of 2020
see those were jokes but the IBM minicomputer that a certain organization at my old job had that was so old it no longer ran updated AIX, could not be feasibly made Y2K compliant and so to keep the DB2 record system that was required for legal compliance running they did, indeed, slop in a cronjob that ran date 010100000099 every night? not a joke. so very, very real.
alright you win that's the most fucked up shit i've ever heard
