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.
The moment of truth when your model actually makes predictions—hopefully not embarrassingly bad ones.
The buzzword architects love, but engineers fear.
Proof that a company probably takes security seriously.
Slicing and dicing data until it fits your argument.
Deciding where to spend time, money, and energy—usually wrong.
Granting permissions based on job roles, not personal favorites.
Like a Data Lake, but with regret control.
Saving progress so your system can crash at a later, more inconvenient time.
A last-minute meeting because someone didn’t read the dashboard.
A group of overworked data engineers and analysts thrown together to fix a reporting disaster.
No one understands the report, but we’re pretending we do.
Keeping secrets… until someone forgets to lock the database.
Keeping multiple copies of your data in sync.
Stripping personal details so data looks anonymous (but isn’t always).
Because finding the right dataset shouldn’t feel like a scavenger hunt.
Making your inefficient queries slightly less embarrassing.
Running the same weekly report with slightly different date filters.
Poking around in your data to find trends, outliers, and problems before they ruin your model.
It’s not just a conference—it’s a group hug wrapped in YAML. No fluff, no gatekeeping—just real talk from data practitioners sharing their learnings and strategies.
The Costco of structured data.
When your system crashes but pretends it never happened.
Retiring an old dashboard but keeping the dataset running ‘just in case.’
“I don’t trust your analysis, so let’s keep poking at it until it fits my narrative.”
A central place for data that everyone fights over.
Digging through massive datasets, hoping to strike gold.
Following data laws just enough to avoid fines.
Extract, transform, load—the classic data pipeline approach.
Making complex queries expensive since forever.
Making data look important in executive meetings.
All the missing data that everyone pretends doesn’t exist.
When bad data leads to even worse decisions.
Workflow automation, so you don’t have to babysit data pipelines.
Turning monolithic problems into distributed chaos.
Organizing data at a scale where things will go wrong.
A 57-slide PowerPoint where 3 slides actually contain useful charts.
The science of making sense of data—assuming it’s not lying to you.
500 commits in 3 hours. No documentation and no survivors.
A digital breadcrumb trail for when things inevitably go wrong.
How much pain your system can handle before collapsing.
The reason healthcare companies fear data leaks.
For when the cloud is just too far away.
Because well-managed data is the difference between insights and chaos.
A gradient boosting algorithm that wins Kaggle competitions—because sometimes brute force just works.
Tweaking your dataset to improve model performance—because sometimes you need to cheat a little.
Scrambling data so only the right people (hopefully) can read it.
Europe’s way of reminding companies that data privacy matters.
A fancy term for “don’t let hackers steal our stuff.”
The easiest SQL query that someone still wants to call a "data-driven insight."
Like moving houses, but with more downtime and crying.
Predicting trends over time—useful for stocks, weather, and figuring out when your Wi-Fi will crash again.
The badge that says “We take security seriously” (but still have breaches).
The constant struggle to keep data clean, secure, and useful.
Load first, transform later—modern data integration in action.
The difference between well-structured data and a digital black hole.
When your model is too smart for its own good and memorizes the training data instead of learning useful patterns.
A passive-aggressive way to say “this will be your problem soon.”
When everyone agrees on what to pretend to care about.
Telling you whether your results matter or if they’re just a fluke—like winning the lottery.
Automating code merges so your team doesn’t go crazy.
That thing developers ignore until the database breaks.
Letting a neural network go crazy with layers upon layers of computation—basically AI's version of overthinking.
Because “I think this field means…” shouldn’t be part of data analysis.
Keeping data safe from hackers, leaks, and bad employees.
The stuff hackers (and marketers) dream about stealing.
Tweaking and creating data inputs so your model performs better—basically, data science alchemy.
SQL’s rebellious younger sibling.
Demands data-driven decisions then overrides everything because their morning shower had "different vibes."
Because bad data leads to bad decisions and lots of excuses.
Doing more work with fewer complaints—on a good day.
A strategic delay tactic used to avoid commitment in meetings with more than three directors present.
Because someone needs to process transactions in real-time.
Sorting stuff into categories, like whether an email is spam, a cat is a dog, or your AI is actually working.
Guessing with data—because flipping a coin isn't "data-driven."
Getting the most out of your budget before the CFO notices.
“Your data reports need to be better, but we won’t give you more resources.”
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
The magic that makes your slow queries slightly less slow.
Because just because you can collect data doesn’t mean you should.
A fragile house of cards filled with hidden errors, broken formulas, and misplaced decimal points.
Deploying apps without touching infrastructure (until something breaks).
Corporate deity whose random breakfast thoughts outrank your entire research department.
Where your data has commitment issues.
“I have 10 dashboards to fix and zero time for your ad-hoc request.”
A statistical method that updates what you believe based on new data—just like changing your opinion after checking Yelp reviews.
When your AI learns from biased data and makes unfair decisions—because garbage in = garbage out.
Preparing for disasters that will still somehow surprise you.
Shipping code faster than your team can fix bugs.
Making database queries run faster—because no one likes waiting 10 minutes for an SQL query to finish.
“Can you analyze all our data from the last 10 years for a report we’ll ignore?”
The algorithm that helps machine learning models learn—think of it as slowly rolling downhill to the right answer.
Absolute chaos agents.
Teaching machines to "think" so they can replace humans (but mostly just generate weird chatbot responses).
The frustrations of explaining, again, why two reports don’t match.
The law that keeps finance teams on their toes.
The reason your reports make no sense.
“This dashboard is broken, but let’s not discuss it in front of leadership.”
A job posting for a data analyst who can also engineer pipelines and train AI models.
The key metrics leadership suddenly decided to care about this quarter.
Where we test new models and hope no one deploys them to production by accident.
Data’s glow-up into something actually useful.
Urban data dictionary powered by
