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.
Moving data from one mess to another.
The unlucky souls tasked with keeping data under control.
A central place for data that everyone fights over.
How much pain your system can handle before collapsing.
Deciding where to spend time, money, and energy—usually wrong.
Making sure standard data values stay standard—good luck with that.
Turning data into a fixed-size mess—useful for passwords, not so great if you ever need to reverse it.
When bad data leads to even worse decisions.
A job posting for a data analyst who can also engineer pipelines and train AI models.
Ignoring that data quality issue until it causes real problems.
The difference between well-structured data and a digital black hole.
A vague, last-minute ask that will inevitably require multiple follow-ups and scope changes.
The fine art of deciding who gets in and who gets a "403 Forbidden."
Digging through massive datasets, hoping to strike gold.
The illusion of structure in your chaotic data world.
A table that tells you how often your model gets things right (or, more realistically, how often it screws up).
Saving progress so your system can crash at a later, more inconvenient time.
A corporate delusion tactic to feign control, optimism, or progress in the face of complete chaos.
“Will this dashboard break when more than 5 people refresh it at once?”
The legal hoops companies jump through to keep your data kinda safe.
Where your data has commitment issues.
Because “whatever naming convention feels right” is not a strategy.
Double-checking data before it makes a fool of you.
When talking about talking becomes your main deliverable. Bonus points if you can turn it into a self-congratulatory Linkedin post.
The dashboard everyone ignores until an executive asks for it.
Fixing data mistakes before they embarrass you.
“We made a pretty chart—please pretend it changed your decision-making.”
Because reading rows one at a time is for chumps.
The buzzword architects love, but engineers fear.
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
“We need to filter this data in every way possible until it agrees with us.”
Turning monolithic problems into distributed chaos.
Code for “this could’ve been a Slack message.”
Data about your data—because keeping track of what your numbers mean is harder than it should be.
A structured way to describe data relationships (or overcomplicate things).
We built it for five people and are praying it doesn’t break at ten.
Corporate deity whose random breakfast thoughts outrank your entire research department.
Rules everyone agrees on but nobody follows.
Google's open-source machine learning library—great for deep learning, if you don’t mind the steep learning curve.
Bridging the gap between development and IT operations.
Getting machines to do the boring stuff for you.
Because not every department deserves full database access.
The behind-the-scenes details of how data was collected.
Finding insights in data—or just realizing what’s missing.
Proof that a company probably takes security seriously.
“Your data reports need to be better, but we won’t give you more resources.”
Metadata management to keep track of your ever-growing data jungle.
A flowchart-like model that makes decisions—think "choose your own adventure" but with math.
Shows up after work's done to sink regulatory fangs into your launch plans.
Moving data to the cloud—hopefully without breaking everything.
Europe’s way of reminding companies that data privacy matters.
When a relational database is too much effort.
When your system crashes but pretends it never happened.
Poking around in your data to find trends, outliers, and problems before they ruin your model.
Organizing data at a scale where things will go wrong.
A gradient boosting algorithm that wins Kaggle competitions—because sometimes brute force just works.
The art of making sure analysts don’t work with garbage.
Guessing with data—because flipping a coin isn't "data-driven."
Predicting trends over time—useful for stocks, weather, and figuring out when your Wi-Fi will crash again.
The secret sauce behind databases that actually perform.
Making sure your servers aren’t crying for no reason.
Copying data from one mistake to another.
When you can’t commit to a single cloud provider.
Tweaking a button color and calling it "strategy."
Grouping similar things together—useful for customer segmentation, but also how your closet naturally organizes itself into chaos.
“Here’s what you should do, but no one actually follows.”
When your data is so bloated no one knows what to do with it, but it sounds impressive.
Checking your data before it embarrasses you.
The mess left behind when shortcuts meet data analytics.
Finding out where all the secrets are hiding before someone else does.
Shipping code faster than your team can fix bugs.
SQL’s rebellious younger sibling.
Checking if your security is solid—or just wishful thinking.
Microsoft’s favorite way to make bar charts look really dramatic.
Proof that "we'll fix it later" never actually means later.
Where your data goes to sleep.
Protecting user info while secretly monetizing it.
A data point that’s way off from the rest—could be an error, or could be the next big discovery.
The thing everyone builds but nobody documents.
Creates JIRA tickets to track their JIRA tickets while drowning in chaos.
The theoretical version of your data that reality refuses to match.
The Costco of structured data.
Shoving a half-baked feature into the project at the last minute.
Telling you whether your results matter or if they’re just a fluke—like winning the lottery.
The delicate art of begging people to care.
Like conducting a symphony, but with way more screaming.
Making database queries run faster—because no one likes waiting 10 minutes for an SQL query to finish.
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 well-managed data is the difference between insights and chaos.
What you just got assigned because you asked a question in the meeting.
Because just because you can collect data doesn’t mean you should.
“This data connector technically works, but barely.”
A last-minute meeting because someone didn’t read the dashboard.
Someone else’s computer, but shinier.
Making sure your app doesn’t make users want to throw their devices.
The behind-the-scenes data that keeps everything (barely) organized.
Teaching machines to "think" so they can replace humans (but mostly just generate weird chatbot responses).
Teaching computers to recognize patterns so they can pretend to be smart—until they overfit and fail.
Sharing resources and pretending everything is fine.
Like moving houses, but with more downtime and crying.
Urban data dictionary powered by
