104 karma · joined September 7, 2021
I’m assuming you meant “sunk” not “suck”. Not familiar with the suck fallacy.
“We filtered first instead of reading an entire table from disk and performing a lookup”
Where both OLAP and OLTP dbms would benefit.
To your point, it’s clear certain workloads lend themselves to OLAP and columnar storage much better, but “an endless sequence of misbehavior” seems a bit harsh .
Pivoting a decent sized BI shop toward using one instead of splashing the same SQL all over the place is *tough*. It's one of those: "the analyst could have been building important report for director and you want them to create re-usable logic??? we'll do that later, get report done now. Just copy/paste that SQL over here"
This is how you end up with the the 1000 model, "the numbers don't match up", hot mess situations that gain momentum and are hard to slow down.
Anecdotally, I desire to hang out with people who share my interests and want to do similar activities that we both enjoy.
I’m a few years removed from college now, and it’s highlighted to me just how special living closely with people of similar age and interest does for one’s social life. Once you spread out, gain dependents, work, etc… it’s much more of an effort to stay in touch.
Just because someone doesn’t reciprocate your effort to connect doesn’t necessarily mean they don’t want to hang out with you.
“Table already exists…”scheduled job run failure galore, fun times.
I assumed you meant that this created a sense of reflection in the requester as to the value of their ask.