Technologically frozen in 1995. Still thinks "the cloud" is for rain and refuses to click anything newer than Solitaire.
Corporate for "I forgot what this is about but I need to make noise before someone notices".
An interactive report that executives will ignore until they ask for the same data… in an Excel sheet.
The unlucky souls tasked with keeping data under control.
Demands data-driven decisions then overrides everything because their morning shower had "different vibes."
A 57-slide PowerPoint where 3 slides actually contain useful charts.
Because reading rows one at a time is for chumps.
When your model is too smart for its own good and memorizes the training data instead of learning useful patterns.
The dashboards and reports that will be outdated within a week.
Making teams promise they won’t break each other’s data pipelines.
Getting access to the full raw data without documentation or guidance.
How much pain your system can handle before collapsing.
The reason your reports make no sense.
Wants to monitor every client blink without a clue what to do with it.
The terrifying process of taking your machine learning model from theory to the real world, where it can finally embarrass you.
Absolute chaos agents.
The magic behind neural networks—basically, trial and error on steroids until the model gets it right.
Where we test new models and hope no one deploys them to production by accident.
The science of making sense of data—assuming it’s not lying to you.
Doing more work with fewer complaints—on a good day.
Data about your data—because keeping track of what your numbers mean is harder than it should be.
The serial focus assassin. Everyone knows at least one.
Because sometimes, you actually want long-winded responses.
The fine art of deciding who gets in and who gets a "403 Forbidden."
Holding onto data just long enough to avoid legal trouble.
Making sure data stays trustworthy—or at least looks like it.
Corporate deity whose random breakfast thoughts outrank your entire research department.
The one number we stare at while ignoring the iceberg.
Because mistakes were made.
Treats every email address like nuclear launch codes and speed-dials Legal when someone shares a first name.
When your system crashes but pretends it never happened.
When your model suddenly starts making terrible predictions because the real world refused to stay the same.
Spotting the oddballs in your data, because sometimes anomalies are fraud, and sometimes they’re just mistakes.
Idea-vomiting buzzword dispenser.
What you just got assigned because you asked a question in the meeting.
A flowchart-like model that makes decisions—think "choose your own adventure" but with math.
The Data Lake’s evil twin.
A structured way to work with large datasets.
Hoping two systems eventually agree on reality.
The lazy friend of machine learning—it just looks at its closest neighbors and copies them.
Sharing resources and pretending everything is fine.
Spews directives like "make it intuitive" with all the specificity of a drunk fortune cookie.
Spotting the weirdos in your data—because outliers can mean fraud, errors, or just bad luck.
Frankenstein’s monster made of expensive software.
Extract, transform, load—the classic data pipeline approach.
Treats your dashboards like a digital coloring book.
Slapping AI on the same old nonsense.
All the missing data that everyone pretends doesn’t exist.
Someone else’s computer, but shinier.
The "we'll fix it in production" person. They're just one misplaced comma away from getting fired.
When real-time isn’t worth the hassle.
Fine-tunes LLMs like they’re sourdough starters. Has five GPU credits left and no intention of using them responsibly.
When you can’t commit to a single cloud provider.
Making sure your data descriptions don’t live in someone’s forgotten spreadsheet.
Microsoft’s favorite way to make bar charts look really dramatic.
Making sure data doesn’t become a dumpster fire.
Protecting user info while secretly monetizing it.
Hiding sensitive data so developers don’t see what they shouldn’t.
Google’s way of making your SQL queries cost a small fortune.
Lives in a command line, thrives in mayhem. Breaks things just to make them better. Somehow delivers magic at 2 AM.
When economics meets statistics and things get extra nerdy.
The illusion of structure in your chaotic data world.
Removing errors, duplicates, and someone else’s bad decisions.
The one dashboard we all agreed on… until someone else made a new one with different numbers.
“I don’t trust your analysis, so let’s keep poking at it until it fits my narrative.”
The mess left behind when shortcuts meet data analytics.
Following data laws just enough to avoid fines.
When processing big data was still cool.
The reason your database admin hates you.
Metrics that executives obsess over (but don’t always understand).
Keeping track of all the ways hackers can ruin your day.
That thing developers ignore until the database breaks.
Stripping personal details so data looks anonymous (but isn’t always).
A strategic delay tactic used to avoid commitment in meetings with more than three directors present.
“We need to filter this data in every way possible until it agrees with us.”
A central place for data that everyone fights over.
Because winging it with data governance isn’t a long-term strategy.
DIY data anarchist whose unholy Excel concoctions somehow hypnotize executives despite breaking every statistical law.
Poking around in your data to find trends, outliers, and problems before they ruin your model.
A fragile house of cards filled with hidden errors, broken formulas, and misplaced decimal points.
Training models on decentralized data—because sharing is caring, but privacy lawsuits are expensive.
Grouping users to prove that trends aren’t just luck.
The never-ending battle between hackers and IT teams running on coffee.
The moment of truth when your model actually makes predictions—hopefully not embarrassingly bad ones.
Telling you whether your results matter or if they’re just a fluke—like winning the lottery.
Predicting continuous values, like sales figures or how many coffees you'll need to survive Monday.
The behind-the-scenes data that keeps everything (barely) organized.
The programming language everyone pretends to know.
A table that tells you how often your model gets things right (or, more realistically, how often it screws up).
Making sense of numbers so businesses can pretend to be data-driven.
Code for “this could’ve been a Slack message.”
Turning monolithic problems into distributed chaos.
“We made a pretty chart—please pretend it changed your decision-making.”
Making sure standard data values stay standard—good luck with that.
Turning raw data into fancy charts that people ignore.
Teaching machines to "think" so they can replace humans (but mostly just generate weird chatbot responses).
The thing everyone builds but nobody documents.
Feeding your data pipeline a never-ending buffet.
Because SQL SELECT wasn’t fancy enough.
The reason your computer fan sounds like a jet engine.
A checklist of rules to follow… until regulations change again.
Builds the data highways, then spends half the week fixing potholes caused by everyone else driving like maniacs.
Blueprints for security that companies try to follow.
Urban data dictionary powered by
