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.
Where structured data goes to drown.
A fancy way of saying, “Re-use that old SQL query, but make it look fresh.”
Treats your dashboards like a digital coloring book.
A strategic delay tactic used to avoid commitment in meetings with more than three directors present.
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
When your company trends on Twitter for all the wrong reasons.
A group of overworked data engineers and analysts thrown together to fix a reporting disaster.
Holding onto data just long enough to avoid legal trouble.
When real-time isn’t worth the hassle.
The numbers that make up your analysis—sometimes useful, sometimes just noise.
Because raw data is just too ugly.
When bad data leads to even worse decisions.
The bare minimum dressed up like a competitive edge.
Predicting trends over time—useful for stocks, weather, and figuring out when your Wi-Fi will crash again.
Predicting all the ways data can ruin your day.
Keeps the data stack humming so analysts can pretend it’s “just a quick query.”
Guessing with data—because flipping a coin isn't "data-driven."
When two teams argue over whose data is right until they both give up.
Telling you whether your results matter or if they’re just a fluke—like winning the lottery.
Convincing everyone that my version of the dashboard is the truth.
The thing everyone blames but nobody fixes.
Because JSON wasn’t painful enough.
Nesting IF statements like Russian dolls and defending their desktop spreadsheet hoard like a caffeinated dragon.
Because manually checking your code is for the weak.
Keeping data safe from hackers, leaks, and bad employees.
The art of making sure analysts don’t work with garbage.
Teaching computers to recognize patterns so they can pretend to be smart—until they overfit and fail.
Because well-managed data is the difference between insights and chaos.
Getting access to the full raw data without documentation or guidance.
When your model is too smart for its own good and memorizes the training data instead of learning useful patterns.
“Yes, our data platform supports SQL. That’s not a selling point.”
A passive-aggressive way to say “this will be your problem soon.”
Like conducting a symphony, but with way more screaming.
Spotting the oddballs in your data, because sometimes anomalies are fraud, and sometimes they’re just mistakes.
Google’s way of making your SQL queries cost a small fortune.
Microsoft’s favorite way to make bar charts look really dramatic.
Creates JIRA tickets to track their JIRA tickets while drowning in chaos.
Because sometimes, you actually want long-winded responses.
Keeping track of all the ways hackers can ruin your day.
The fine art of deciding who gets in and who gets a "403 Forbidden."
A chaotic attempt to explain why the numbers don’t match across reports.
Because mistakes were made.
A 57-slide PowerPoint where 3 slides actually contain useful charts.
When your AI learns from biased data and makes unfair decisions—because garbage in = garbage out.
A fancy term for “don’t let hackers steal our stuff.”
Data’s glow-up into something actually useful.
Because finding the right dataset shouldn’t feel like a scavenger hunt.
Making sure your servers aren’t crying for no reason.
The difference between well-structured data and a digital black hole.
Because winging it with data governance isn’t a long-term strategy.
Learned SELECT * yesterday and now wants database admin privileges – what could go wrong?
Like a Data Lake, but with regret control.
“Will this dashboard break when more than 5 people refresh it at once?”
The secret sauce that makes data searchable, understandable, and actually useful.
Builds the data highways, then spends half the week fixing potholes caused by everyone else driving like maniacs.
The one number we stare at while ignoring the iceberg.
Extract, transform, load—the classic data pipeline approach.
Keeping data within borders—because governments say so.
This query better finish before the meeting, or I’m in trouble.
Cutting back on data storage costs until everything runs painfully slow.
The reason healthcare companies fear data leaks.
When leadership changes the KPI goal after you’ve already built the report.
Hacking yourself before someone else does.
Treats every email address like nuclear launch codes and speed-dials Legal when someone shares a first name.
Making sense of numbers so businesses can pretend to be data-driven.
Stripping personal details so data looks anonymous (but isn’t always).
The frustrations of explaining, again, why two reports don’t match.
The badge that says “We take security seriously” (but still have breaches).
Translating raw data into real-world meaning so it’s actually useful.
The magic behind neural networks—basically, trial and error on steroids until the model gets it right.
“Here’s what you should do, but no one actually follows.”
Shows up after work's done to sink regulatory fangs into your launch plans.
Because manually moving data is for people who hate themselves.
Making database queries run faster—because no one likes waiting 10 minutes for an SQL query to finish.
Letting a neural network go crazy with layers upon layers of computation—basically AI's version of overthinking.
Scrambling data so only the right people (hopefully) can read it.
Poking around in your data to find trends, outliers, and problems before they ruin your model.
The serial focus assassin. Everyone knows at least one.
Moving data from one mess to another.
Helping engineers understand how data flows, transforms, and actually works.
Human API who communicates in endpoints and considers UIs a moral weakness.
“We ran the same SQL query but indexed a column, so now it’s 2% faster.”
Rules everyone agrees on but nobody follows.
The law that keeps finance teams on their toes.
The Costco of structured data.
Brings structure to chaos with dbt and a folder hierarchy that could win awards.
Because not every department deserves full database access.
Workflow automation, so you don’t have to babysit data pipelines.
Fancy PowerPoint slides no one follows.
Teaching machines to "think" so they can replace humans (but mostly just generate weird chatbot responses).
“This report is valid until next quarter, when everything changes.”
The art of torturing data until it confesses something useful—or at least makes a nice chart.
Metrics that executives obsess over (but don’t always understand).
Talking to inanimate objects because humans are worse.
“Can you analyze all our data from the last 10 years for a report we’ll ignore?”
“This data connector technically works, but barely.”
We built it for five people and are praying it doesn’t break at ten.
Making sure your app doesn’t make users want to throw their devices.
A fragile house of cards filled with hidden errors, broken formulas, and misplaced decimal points.
Schedules pre-meetings for the pre-meeting's pre-brief because they couldn't read an email to save their life.
Urban data dictionary powered by
