Me right now, discovering that our archives data have file sizes… sometimes in bytes, sometimes in kilobytes. I found some pattern this morning thinking I could know which was which, then the pattern collapsed at some date in the past.
Joy.
You wanna know why this dashboard takes a full minute to load? It’s because it joins every table in the fucking database because some people can’t be bothered to look at a separate page for certain information.
How many widgets have we transferred to acme this year?
Simple enough question right?
But then when you look at the data, each region works with acme’s local offices differently. Some transfer using one method, some offices mark the transfer in the system as “other firm”. Oh, and we don’t even get a data feed from the north west region because they still haven’t upgraded their shit so I can request a spreadsheet but it’s in a different format than everything else.
Then inevitably Acme has a different number of widgets that have been transfered. Because if a transfer gets kicked back or cancelled, it’s easier to just create a new transfer rather than go fix an old one because that process is laborious and requires tons of approvals so they just create a new transfer and send it over.
But yea, 20 minutes should be enough time to get you that before your meeting with Acme.
You forgot the 3 paragraph WHERE clause to get every data point of a wednesday of an even year of a person who stubbed their toes on a roomba in their parent’s basement.
Add comment