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.
Technologically frozen in 1995. Still thinks "the cloud" is for rain and refuses to click anything newer than Solitaire.
Grouping similar things together—useful for customer segmentation, but also how your closet naturally organizes itself into chaos.
Because raw data is just too ugly.
Spews directives like "make it intuitive" with all the specificity of a drunk fortune cookie.
Transforming categorical data into numerical form—because computers just don’t get words.
Ignoring that data quality issue until it causes real problems.
Poking around in your data to find trends, outliers, and problems before they ruin your model.
Keeping unauthorized users out - until someone shares a password.
Where your data goes to sleep.
Someone else’s computer, but shinier.
A gradient boosting algorithm that wins Kaggle competitions—because sometimes brute force just works.
Hacking yourself before someone else does.
The easiest SQL query that someone still wants to call a "data-driven insight."
Makes dashboards for people who will ignore them and then ask you for the same numbers in a spreadsheet.
Because bad data leads to bad decisions and lots of excuses.
“Can you analyze all our data from the last 10 years for a report we’ll ignore?”
Sifting through data, hoping for something insightful.
Data’s glow-up into something actually useful.
Blueprints for security that companies try to follow.
Getting access to the full raw data without documentation or guidance.
Schedules pre-meetings for the pre-meeting's pre-brief because they couldn't read an email to save their life.
Because manually checking your code is for the weak.
Corporate deity whose random breakfast thoughts outrank your entire research department.
Invisible data hero who's seen SQL horrors that would make junior devs cry.
Protecting user info while secretly monetizing it.
“We ran the same SQL query but indexed a column, so now it’s 2% faster.”
Workflow automation, so you don’t have to babysit data pipelines.
Doing more work with fewer complaints—on a good day.
The dashboards and reports that will be outdated within a week.
A fancy term for “don’t let hackers steal our stuff.”
Trying to guess the future based on past data—like a digital crystal ball, but with spreadsheets.
Artificially inflating your dataset so your model learns better—kind of like stretching the truth on a résumé.
A digital breadcrumb trail for when things inevitably go wrong.
A checklist of rules to follow… until regulations change again.
Nesting IF statements like Russian dolls and defending their desktop spreadsheet hoard like a caffeinated dragon.
The thing everyone blames but nobody fixes.
Because mistakes were made.
Because spreadsheets just don’t scale.
The reason your software updates faster than you can blink.
Fluent in stakeholder management, and can turn vague requests into scarily accurate dashboards. Built half the team's workflows on vibes and somehow made it work.
Because “I have no idea where this data came from” is not a great answer.
Digging through massive datasets, hoping to strike gold.
Double-checking data before it makes a fool of you.
A corporate delusion tactic to feign control, optimism, or progress in the face of complete chaos.
A free tool for tracking website traffic—until privacy laws step in.
Slapping AI on the same old nonsense.
Transforms your bullet point into 40 slides featuring at least two mountain-climbing metaphors.
All the missing data that everyone pretends doesn’t exist.
Holding onto data just long enough to avoid legal trouble.
When you pivot data just to confirm what you already knew.
Fine-tunes LLMs like they’re sourdough starters. Has five GPU credits left and no intention of using them responsibly.
The numbers that make up your analysis—sometimes useful, sometimes just noise.
The never-ending battle between hackers and IT teams running on coffee.
A bunch of decision trees working together to make better predictions—because one tree alone isn’t enough.
The reason your database admin hates you.
The frustrations of explaining, again, why two reports don’t match.
Load first, transform later—modern data integration in action.
Creates JIRA tickets to track their JIRA tickets while drowning in chaos.
Data that refuses to fit into neat tables—think text, images, and the chaos of the internet.
Cutting down the number of variables in your dataset—because sometimes, less is more (especially in Excel).
Talking to inanimate objects because humans are worse.
Keeping multiple copies of your data in sync.
The buzzword architects love, but engineers fear.
The universal answer to every data question, forever and always.
We built it for five people and are praying it doesn’t break at ten.
The algorithm that helps machine learning models learn—think of it as slowly rolling downhill to the right answer.
Getting machines to do the boring stuff for you.
“This data connector technically works, but barely.”
“This dashboard is broken, but let’s not discuss it in front of leadership.”
The magic that makes your slow queries slightly less slow.
Predicting trends over time—useful for stocks, weather, and figuring out when your Wi-Fi will crash again.
The fine art of deciding who gets in and who gets a "403 Forbidden."
When economics meets statistics and things get extra nerdy.
The magic behind neural networks—basically, trial and error on steroids until the model gets it right.
“I have 10 dashboards to fix and zero time for your ad-hoc request.”
A job posting for a data analyst who can also engineer pipelines and train AI models.
“Throw some data models at the wall and see what sticks.”
Worships clean metadata and version control. Lives for data lineage and will fight you over naming conventions.
Turning numbers into narratives people might actually remember.
When your model is too smart for its own good and memorizes the training data instead of learning useful patterns.
“I forgot to check the dashboard before this meeting.”
Because SQL SELECT wasn’t fancy enough.
Making sure your data descriptions don’t live in someone’s forgotten spreadsheet.
Turning raw data into fancy charts that people ignore.
A passive-aggressive way to say “this will be your problem soon.”
Teaching models with labeled data—kind of like school, but for algorithms.
The Costco of structured data.
Feeding your data pipeline a never-ending buffet.
“This report is valid until next quarter, when everything changes.”
Where your data has commitment issues.
A central place for data that everyone fights over.
“We’ll consider all possible factors… except the ones that make us look bad.”
Stalking customers, but make it “data-driven.”
When your system crashes but pretends it never happened.
Where structured data goes to drown.
Spotting the oddballs in your data, because sometimes anomalies are fraud, and sometimes they’re just mistakes.
Automating code merges so your team doesn’t go crazy.
Teaching computers to recognize patterns so they can pretend to be smart—until they overfit and fail.
Making your inefficient queries slightly less embarrassing.
Cutting back on data storage costs until everything runs painfully slow.
Preparing for disasters that will still somehow surprise you.
Urban data dictionary powered by
