An interactive report that executives will ignore until they ask for the same data… in an Excel sheet.
Corporate for "I forgot what this is about but I need to make noise before someone notices".
Technologically frozen in 1995. Still thinks "the cloud" is for rain and refuses to click anything newer than Solitaire.
Because raw data is just too ugly.
The art of making sure analysts don’t work with garbage.
Demands data-driven decisions then overrides everything because their morning shower had "different vibes."
A structured way to work with large datasets.
The family tree of your data, assuming you can track it.
Just because two things happen together doesn’t mean one caused the other. Like, eating more cheese doesn’t actually make you better at math.
A data point that’s way off from the rest—could be an error, or could be the next big discovery.
Extract, transform, load—the classic data pipeline approach.
500 commits in 3 hours. No documentation and no survivors.
Grouping similar things together—useful for customer segmentation, but also how your closet naturally organizes itself into chaos.
Spotting the weirdos in your data—because outliers can mean fraud, errors, or just bad luck.
No one understands the report, but we’re pretending we do.
Worships clean metadata and version control. Lives for data lineage and will fight you over naming conventions.
The programming language everyone pretends to know.
Letting a neural network go crazy with layers upon layers of computation—basically AI's version of overthinking.
Builds the data highways, then spends half the week fixing potholes caused by everyone else driving like maniacs.
Guards their "secret metric" like it's launch codes when it's really just page views in a trench coat.
When one team gets credit for your analysis, and you get nothing.
When talking about talking becomes your main deliverable. Bonus points if you can turn it into a self-congratulatory Linkedin post.
Because reading rows one at a time is for chumps.
“Can you analyze all our data from the last 10 years for a report we’ll ignore?”
Learned SELECT * yesterday and now wants database admin privileges – what could go wrong?
Corporate deity whose random breakfast thoughts outrank your entire research department.
Keeping track of all the ways hackers can ruin your day.
Keeping data within borders—because governments say so.
Keeping unauthorized users out - until someone shares a password.
Feeding your data pipeline a never-ending buffet.
Rules about data that everyone agrees on but nobody follows.
When two teams argue over whose data is right until they both give up.
Load first, transform later—modern data integration in action.
The buzzword architects love, but engineers fear.
Checking your data before it embarrasses you.
That thing you forgot to set up before the system crashed.
Wants to monitor every client blink without a clue what to do with it.
Running a ton of random simulations to predict outcomes—because guessing with math sounds fancier.
The fine art of deciding who gets in and who gets a "403 Forbidden."
“We need better numbers, but we don’t want to change anything.”
Redefines success metrics faster than politicians backpedal after an election.
The theoretical version of your data that reality refuses to match.
Slicing and dicing data until it fits your argument.
The behind-the-scenes details of how data was collected.
Stripping away identities because privacy lawsuits are expensive.
Organizing data at a scale where things will go wrong.
Treats your dashboards like a digital coloring book.
The badge that says “We take security seriously” (but still have breaches).
Making sure data stays trustworthy—or at least looks like it.
Digging through massive datasets, hoping to strike gold.
Stalking customers, but make it “data-driven.”
Double-checking data before it makes a fool of you.
A chaotic attempt to explain why the numbers don’t match across reports.
The reason healthcare companies fear data leaks.
Would slap glitter on a bankruptcy report because "data doesn't pop without gradients!"
The science of figuring out whether A actually causes B, or if it’s just a coincidence (like ice cream sales and shark attacks).
Stripping personal details so data looks anonymous (but isn’t always).
The science of making sense of data—assuming it’s not lying to you.
A passive-aggressive way to say “this will be your problem soon.”
Making sure your data descriptions don’t live in someone’s forgotten spreadsheet.
Getting access to the full raw data without documentation or guidance.
“This data connector technically works, but barely.”
Doing more work with fewer complaints—on a good day.
The awkward silence between launch and someone actually using it.
Brings structure to chaos with dbt and a folder hierarchy that could win awards.
“This report is valid until next quarter, when everything changes.”
Someone else’s computer, but shinier.
Your code, but only when someone remembers it exists.
Goes to every conference and is part of every newsletter. Needs an intervention.
Hiding sensitive data so developers don’t see what they shouldn’t.
When your model suddenly starts making terrible predictions because the real world refused to stay the same.
A flowchart-like model that makes decisions—think "choose your own adventure" but with math.
Microsoft’s latest “one tool to rule them all” attempt—until the next one.
Fake data used for training models when real data is too sensitive, messy, or non-existent.
A digital breadcrumb trail for when things inevitably go wrong.
The key metrics leadership suddenly decided to care about this quarter.
Because mistakes were made.
Metadata management to keep track of your ever-growing data jungle.
A central place for data that everyone fights over.
“Yes, our data platform supports SQL. That’s not a selling point.”
Creates JIRA tickets to track their JIRA tickets while drowning in chaos.
When you pivot data just to confirm what you already knew.
Europe’s way of reminding companies that data privacy matters.
Like moving houses, but with more downtime and crying.
Granting permissions based on job roles, not personal favorites.
The reason your computer fan sounds like a jet engine.
When bad data leads to even worse decisions.
Frankenstein’s monster made of expensive software.
Rules everyone agrees on but nobody follows.
The reason your database admin hates you.
Idea-vomiting buzzword dispenser.
Transforming categorical data into numerical form—because computers just don’t get words.
Invisible data hero who's seen SQL horrors that would make junior devs cry.
Data about your data—because keeping track of what your numbers mean is harder than it should be.
The art of torturing data until it confesses something useful—or at least makes a nice chart.
The go-to event for data professionals who want to rethink how governance is done. Join experts reimagining the future of what AI-readiness looks like
Like conducting a symphony, but with way more screaming.
“I have 10 dashboards to fix and zero time for your ad-hoc request.”
Nesting IF statements like Russian dolls and defending their desktop spreadsheet hoard like a caffeinated dragon.
When you can’t commit to a single cloud provider.
A table that tells you how often your model gets things right (or, more realistically, how often it screws up).
When your system crashes but pretends it never happened.
Lives in a command line, thrives in mayhem. Breaks things just to make them better. Somehow delivers magic at 2 AM.
Urban data dictionary powered by
