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.
Corporate for "I forgot what this is about but I need to make noise before someone notices".
“We need better numbers, but we don’t want to change anything.”
Corporate deity whose random breakfast thoughts outrank your entire research department.
The reason your software updates faster than you can blink.
Sharing resources and pretending everything is fine.
Like conducting a symphony, but with way more screaming.
“Can you analyze all our data from the last 10 years for a report we’ll ignore?”
Because manually moving data is for people who hate themselves.
The behind-the-scenes data that keeps everything (barely) organized.
For when the cloud is just too far away.
A data point that’s way off from the rest—could be an error, or could be the next big discovery.
Translating raw data into real-world meaning so it’s actually useful.
The endless cycle of finding new ways to blame bad data for bad decisions.
A table that tells you how often your model gets things right (or, more realistically, how often it screws up).
Convincing everyone that my version of the dashboard is the truth.
The mess left behind when shortcuts meet data analytics.
When search meets machine learning and everyone gets confused.
When your data is so bloated no one knows what to do with it, but it sounds impressive.
Following data laws just enough to avoid fines.
The programming language everyone pretends to know.
Because spreadsheets just don’t scale.
A marketing term for "we kinda fixed the Data Lake problem."
A structured way to work with large datasets.
“We made a pretty chart—please pretend it changed your decision-making.”
Because SQL SELECT wasn’t fancy enough.
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.
Shipping code faster than your team can fix bugs.
A structured way to describe data relationships (or overcomplicate things).
The awkward middle child of structured and unstructured data.
The family tree of your data, assuming you can track it.
Sifting through data, hoping for something insightful.
Machine learning for people who don’t want to do machine learning. Push a button, get a model—hopefully, a good one.
Digging through massive datasets, hoping to strike gold.
Where your data has commitment issues.
Holding onto data just long enough to avoid legal trouble.
Grouping users to prove that trends aren’t just luck.
Making sure data stays trustworthy—or at least looks like it.
When two teams argue over whose data is right until they both give up.
A last-minute meeting because someone didn’t read the dashboard.
The frustrations of explaining, again, why two reports don’t match.
Guards their "secret metric" like it's launch codes when it's really just page views in a trench coat.
Data’s glow-up into something actually useful.
Wants to monitor every client blink without a clue what to do with it.
The law that keeps finance teams on their toes.
Teaching computers to recognize patterns so they can pretend to be smart—until they overfit and fail.
Rules about data that everyone agrees on but nobody follows.
Keeping secrets… until someone forgets to lock the database.
Keeping unauthorized users out - until someone shares a password.
Load first, transform later—modern data integration in action.
Transforms your bullet point into 40 slides featuring at least two mountain-climbing metaphors.
Deploying apps without touching infrastructure (until something breaks).
Ignoring that data quality issue until it causes real problems.
When processing big data was still cool.
DIY data anarchist whose unholy Excel concoctions somehow hypnotize executives despite breaking every statistical law.
Because someone needs to process transactions in real-time.
Keeping track of all the ways hackers can ruin your day.
Microsoft’s latest “one tool to rule them all” attempt—until the next one.
Organizing data at a scale where things will go wrong.
Tweaking a button color and calling it "strategy."
Fancy PowerPoint slides no one follows.
Turning raw data into fancy charts that people ignore.
Your code, but only when someone remembers it exists.
“This data connector technically works, but barely.”
Because well-managed data is the difference between insights and chaos.
Hoping two systems eventually agree on reality.
Like a Data Lake, but with regret control.
Checking if your security is solid—or just wishful thinking.
Because JSON wasn’t painful enough.
The reason your database admin hates you.
Keeping data safe from hackers, leaks, and bad employees.
Demands data-driven decisions then overrides everything because their morning shower had "different vibes."
Handpicking quality data like it’s fine wine.
The reason your reports make no sense.
The reason your computer fan sounds like a jet engine.
Nesting IF statements like Russian dolls and defending their desktop spreadsheet hoard like a caffeinated dragon.
Getting the most out of your budget before the CFO notices.
Learned SELECT * yesterday and now wants database admin privileges – what could go wrong?
This query better finish before the meeting, or I’m in trouble.
A corporate delusion tactic to feign control, optimism, or progress in the face of complete chaos.
Extract, transform, load—the classic data pipeline approach.
Teaching models with labeled data—kind of like school, but for algorithms.
Finding out where all the secrets are hiding before someone else does.
We built it for five people and are praying it doesn’t break at ten.
Grouping similar things together—useful for customer segmentation, but also how your closet naturally organizes itself into chaos.
Keeping multiple copies of your data in sync.
Feeding your data pipeline a never-ending buffet.
Keeping data within borders—because governments say so.
Making data look important in executive meetings.
That thing you forgot to set up before the system crashed.
Sorting data into neat categories, only for users to ignore them.
A central place for data that everyone fights over.
A vague, last-minute ask that will inevitably require multiple follow-ups and scope changes.
A free tool for tracking website traffic—until privacy laws step in.
Tracking data’s dramatic journey from birth to deletion
Fine-tunes LLMs like they’re sourdough starters. Has five GPU credits left and no intention of using them responsibly.
Doing more work with fewer complaints—on a good day.
The art of torturing data until it confesses something useful—or at least makes a nice chart.
The algorithm that helps machine learning models learn—think of it as slowly rolling downhill to the right answer.
Worships clean metadata and version control. Lives for data lineage and will fight you over naming conventions.
Transforming categorical data into numerical form—because computers just don’t get words.
500 commits in 3 hours. No documentation and no survivors.
Urban data dictionary powered by
