Season's Savings | ₹5/mo for 3 months

₹199/month after first 3 months. Renews automatically. Terms apply.
My Data Guest Podcast cover art

My Data Guest Podcast

My Data Guest Podcast

Written by: Rosaria Silipo & Alessandro Romano
Listen for free

About this listen
This is your go-to podcast for exploring the world of artificial intelligence without the hype. Whether it's breakthroughs in Agentic AI, prompt engineering, AI tools, large language models, transformers, ethical dilemmas, startup stories, or just making sense of what AI might mean for your job, we are here to break it down, episode by episode.

mydataguest.substack.comMy Data Guest
Episodes
  • Ep. 23 - How AI is Rewriting Analytics
    Nov 18 2026

    AI is changing more than the tools people use to do their jobs. In Yuri Gubin’s experience, it is affecting both how his team develops solutions and what those solutions can make possible for clients.

    Gubin describes his team’s work as developing solutions that help clients innovate. AI is now part of that work: it supports code creation and architectural work, and it is influencing the kinds of solutions the team creates.

    The change, then, is not limited to using AI to complete familiar tasks differently. It also extends to how teams approach the work of building solutions.That same shift is visible in data.

    Gubin points out that working with data is not only about making information available for queries or creating dashboards. Those tools can help present and access information, but he sees a broader opportunity: enabling more people to work directly with data, explore ideas through faster experiments and make information more accessible to stakeholders who need it for decision-making.

    This broader access matters because experimentation can help teams learn and assess possibilities sooner. When more people can engage with data and test ideas, data work can support decision-making in new ways not only by presenting results, but by helping people explore what they might mean.

    For Gubin, AI’s potential lies in this combination: using it in the development process while also making data more accessible and useful across an organization. The aim is not simply to produce code or dashboards more quickly. It is to help teams and stakeholders do more with the information they have, experiment faster and create new possibilities for their work.



    Get full access to My Data Guest at mydataguest.substack.com/subscribe
    Show More Show Less
    34 mins
  • Ep. 24 - Navigating the Open Source Data Landscape
    Nov 11 2026
    Some guests need a long introduction. Marco Gorelli is one of them, so I’ll keep it short: mathematician, software engineer at Quansight Labs, former pandas maintainer, Polars contributor, and the creator of Narwhals, a library that gives you one API on top of the major dataframe libraries.We first met at PyCon Italy, when Narwhals was only a few months old, and we’ve run into each other at conferences since. This time we sat down properly and talked about the stuff that usually only comes up in a conference hallway: why some APIs win, how you get anyone to notice a new open source project, and what maintainers are dealing with now that coding agents can open pull requests.Here are the highlights.From pure maths to pandas maintainerMarco studied mathematics, followed by a master’s in maths and the foundations of computer science. Despite the name, it involved no programming at all, “much to some recruiters’ disappointment” when they tried to place him in very applied jobs.He went into data science around 2017–2018, when the field was booming. He pointed out that the way people talked about data science back then sounds a lot like the way people talk about AI today, which in turn sounds like how they talked about big data a few years earlier. (When was the last time you heard someone say “big data”?)The way into open source was very ordinary. He hit a bug in pandas at work and thought it might be fun to fix it. Then COVID hit, he had extra time, and he kept going. Eventually he became a pandas maintainer, and that led to a job at Quansight Labs working on open source full time.Why Polars won by not copying pandasAt Quansight, Marco got into Rust and Polars, a dataframe library written in Rust that avoids many of pandas’ historical design decisions.It’s easy to forget how recently people “would look at me as if I had three heads” if he mentioned Polars alongside pandas. Early on, the critics said nobody would use a dataframe library without the pandas index or the pandas API. Polars was adopted widely anyway. Meanwhile, several projects that copied pandas exactly, only faster, have mostly disappeared.Marco’s explanation: Ritchie Vink, the creator of Polars, treated not following the pandas API as a feature and not a limitation.> “Yes, there is a learning curve, but once you’re over that learning curve, everything is very consistent. Once you get used to the Polars way of thinking, it is a pleasure to work with.”His practical advice: the best time to try Polars is when you’re starting a new project. Don’t try to recreate your pandas habits. Learn the Polars way of thinking from the start and you get the benefits.Why pandas struggles to keep upI asked whether many of the complaints about pandas come from the fact that it has been around so long, through data mining, big data, machine learning, deep learning and now generative AI.Marco agreed and pointed to hardware. pandas was designed around 2008, when 16-core CPUs weren’t something everyone had. Today they’re common and cheap to rent. The problem is that the pandas API doesn’t make it obvious what can run in parallel. People say “pandas should just do things in parallel”, but the API doesn’t make clear how that would work.Polars makes it explicit. Each expression inside with_columns runs independently, so they can all run multi-threaded.> “The world has certainly changed around pandas, but it’s not easy for pandas to change itself at the same pace.”What you gain by going from user to contributorMarco named two things.1. You appreciate the invisible work. pandas is run entirely by volunteers, with the occasional grant. Polars has a company behind it, but much of what goes into the free tool isn’t driven by money. It’s driven by people who want to make data work better.2. You learn API design the hard way. Users often think there should be a built-in function for their use case. But if a library added a function for every use case, the API would become impossible to navigate, and every function would have 20 parameters. As the old pandas maintainer joke goes:> “There is no problem that cannot be solved by adding an extra keyword argument to read_csv.”(It’s probably past 50 by now.) A good tool has to be fairly minimal. It can’t solve everyone’s problem, but it can give you the building blocks to solve your own.Narwhals: copying Polars, not pandasI’ve always found it fascinating that something as simple as mean behaves differently across libraries. Marco gave an example right away: missing values. Most tools skip nulls by default, but the way you configure that differs between PyArrow, pandas, Polars and SQL.That’s the kind of problem Narwhals solves. Marco started it about two and a half years ago as a unified dataframe API, aimed mainly at library maintainers who want to accept different kinds of dataframe inputs.He had three options: copy pandas, copy another library, or invent a ...
    Show More Show Less
    41 mins
  • One year... And what's coming next!
    Oct 21 2026

    A year ago, Rosaria and I started My Data Guest with a simple goal: understand what was happening in AI by talking to the people building it. Most of that first season was about the how. How a transformer works, how a large language model actually processes context, how this new wave of tools was different from the data science we were used to.

    After a two-month break, we’re back. And the world we’re coming back to looks very different.

    My Data Guest is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

    The novelty wore off, and that’s a good thing

    Something changed in the last twelve months. New models still come out every few weeks, but the architecture underneath is mostly the same: bigger, faster, with a few more tricks. The excitement of discovery has quietly turned into something more practical. Rosaria called it a plumbing exercise, and I think she’s right.

    I noticed it in my own work. A year ago I was building an n8n workflow to post My Data Guest content on LinkedIn, and debugging it meant digging through logs. Today I don’t even open the logs. Claude Code is connected to n8n through an MCP server and looks into the problem for me. What surprised me wasn’t the capability itself, but how fast it started to feel normal.

    That’s the shift we want to follow this season.

    What we’re focusing on next

    When almost anything can be connected to anything, the question stops being can we build it and becomes what should we build, and how do we keep it under control once it’s running. We went from fear of missing out to being overwhelmed by options.

    Two themes keep coming up in conversations, posts, and articles:

    Production. How do you actually deploy an agentic system? I’ve come to see agents as distributed systems with an LLM in the middle, and that means a lot of what we already know from system design and cybersecurity still applies. The hard part is translating it.

    Legacy integration. Nobody gets to throw their existing stack away. Companies have years of systems in production, and now those systems have to talk to something completely new. It reminds me of the COBOL days. The old world doesn’t disappear; it has to coexist.

    And underneath both of these sits the topic I expect to dominate the year: security and control. LLMs aren’t just calling tools anymore, they’re writing their own and executing them. That only works safely inside a proper sandbox. We’ll talk about why, and we’ll dig into a recent story that shows what happens when a sandbox isn’t enough, trying to separate what actually happened from the marketing around it.

    What’s coming on the channel

    * Interviews stay free and open, as always. The first one of the season is with Marco Gorelli, and the story of how we met involves a Python package and a few pull requests.

    * New Learning Bytes, same format as before but more hands-on, built around deployment, safety, and what can go wrong before an agent hits production.

    * Courses and masterclasses for paying members: structured, multi-hour learning that takes you from zero to a working product, possibly at different levels, including for people coming from outside tech.

    * A Telegram group for AI news and channel updates. This one is happening for sure.

    There are a few more ideas in the episode, including a possible collaboration and a plan we’ve now announced twice (maybe this is the year).

    My Data Guest is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

    One more thing

    Last year we made a prediction: as more content becomes AI-generated, people would start valuing the human touch more. Real effort, real imperfection. Rosaria checked whether it came true, and the conversation took a turn I didn’t expect, from theatres to Hamburg’s new opera house to The Polar Express.

    You’ll have to watch for that one.

    If you want to be a guest, or you have a course you’d like us to build, reach out on LinkedIn or Substack. And thanks for staying with us for another year.



    Get full access to My Data Guest at mydataguest.substack.com/subscribe
    Show More Show Less
    33 mins
adbl_web_anon_alc_button_suppression_t1
No reviews yet