<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Inês Garcia</title>
    <link>https://null-hypothesis.ines-garcia263.workers.dev/</link>
    <description>Recent content on Inês Garcia</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Inês Garcia</copyright>
    <lastBuildDate>Mon, 13 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://null-hypothesis.ines-garcia263.workers.dev/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Why I stopped using logistic regression for churn</title>
      <link>https://null-hypothesis.ines-garcia263.workers.dev/posts/survival-analysis-for-churn/</link>
      <pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://null-hypothesis.ines-garcia263.workers.dev/posts/survival-analysis-for-churn/</guid>
      <description>&lt;p&gt;A few years ago, I built a churn model for a B2B SaaS product. Logistic regression, binary label, 30-day prediction window. It performed fine. The business used it. I moved on.&lt;/p&gt;&#xA;&lt;p&gt;What bothered me was a question the model couldn&amp;rsquo;t answer: &lt;em&gt;how long does a customer actually stay?&lt;/em&gt;&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>The Data Analyst&#39;s Survival Guide to the Agentic Era</title>
      <link>https://null-hypothesis.ines-garcia263.workers.dev/posts/data-analyst-survival-guide-agentic-era/</link>
      <pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://null-hypothesis.ines-garcia263.workers.dev/posts/data-analyst-survival-guide-agentic-era/</guid>
      <description>&lt;p&gt;I need to say something that makes some data analysts uncomfortable: the job is changing. Not disappearing — changing. And the analysts who understand the change will thrive. The ones who don&amp;rsquo;t will spend the next five years fighting it.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>From Monolith to Modular: Rebuilding a Billing Data Pipeline From Scratch</title>
      <link>https://null-hypothesis.ines-garcia263.workers.dev/posts/modular-billing-pipeline-from-monolith-to-product-per-file/</link>
      <pubDate>Sun, 15 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://null-hypothesis.ines-garcia263.workers.dev/posts/modular-billing-pipeline-from-monolith-to-product-per-file/</guid>
      <description>&lt;p&gt;Earlier this year I shipped a pipeline rewrite I&amp;rsquo;m genuinely proud of. It replaced a 2,200-line SQL monolith — one of those files that everyone&amp;rsquo;s afraid to touch — with a clean layered architecture that handles 14 products, runs daily, and can be extended by adding a handful of config files.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Open Source Won the AI Agent War — Here&#39;s What That Means for Data Teams</title>
      <link>https://null-hypothesis.ines-garcia263.workers.dev/posts/open-source-won-the-ai-agent-war/</link>
      <pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://null-hypothesis.ines-garcia263.workers.dev/posts/open-source-won-the-ai-agent-war/</guid>
      <description>&lt;p&gt;In January 2024, Hugging Face published a benchmark that most people in the data world missed. They compared open-source LLMs against GPT-3.5 and GPT-4 on agent tasks — using a dataset that requires web search and calculator use, the fundamentals of any analytics agent.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>The Berkeley AI Lab Figured Out Why Analytics Agents Work (And It&#39;s Not About AI)</title>
      <link>https://null-hypothesis.ines-garcia263.workers.dev/posts/why-analytics-agents-work-berkeley/</link>
      <pubDate>Sun, 22 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://null-hypothesis.ines-garcia263.workers.dev/posts/why-analytics-agents-work-berkeley/</guid>
      <description>&lt;p&gt;In February 2024, the Berkeley AI Research Lab published a paper that quietly explained everything. Not &amp;ldquo;how to build AI&amp;rdquo; — but &lt;em&gt;why the move from single LLM calls to multi-component systems is inevitable&lt;/em&gt;. And once you read it, you see analytics differently.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>What Meta&#39;s Data Warehouse AI Taught Me About Building Analytics Agents</title>
      <link>https://null-hypothesis.ines-garcia263.workers.dev/posts/what-metas-data-warehouse-ai-taught-me/</link>
      <pubDate>Wed, 14 Jan 2026 00:00:00 +0000</pubDate>
      
      <guid>https://null-hypothesis.ines-garcia263.workers.dev/posts/what-metas-data-warehouse-ai-taught-me/</guid>
      <description>&lt;p&gt;In August 2025, Meta published an engineering blog post that changed how I think about analytics agents. It&amp;rsquo;s called &amp;ldquo;Creating AI Agent Solutions for Warehouse Data Access and Security,&amp;rdquo; and it describes a multi-agent system they built for their internal data warehouse.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Automatic Dip Detection in Time Series: A Statistical Approach</title>
      <link>https://null-hypothesis.ines-garcia263.workers.dev/posts/automatic-dip-detection-statistical-approach/</link>
      <pubDate>Thu, 11 Sep 2025 00:00:00 +0000</pubDate>
      
      <guid>https://null-hypothesis.ines-garcia263.workers.dev/posts/automatic-dip-detection-statistical-approach/</guid>
      <description>&lt;p&gt;Monitoring availability metrics at scale creates a familiar problem: you have a time series, you need to know when it drops, and you need to know this automatically — without someone staring at a dashboard.&lt;/p&gt;&#xA;&lt;p&gt;This post walks through a statistical algorithm I built to do exactly that. It detects dips in any continuous metric (availability, reachability, error rate) and returns precise start and end timestamps for each event. No ML required — just a modified z-score, two rolling windows, and a few transition rules.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Traffic-Based Customer Segmentation: A Practical Approach with Quantile Bucketing and k-NN Anomaly Detection</title>
      <link>https://null-hypothesis.ines-garcia263.workers.dev/posts/traffic-based-customer-segmentation/</link>
      <pubDate>Wed, 18 Jun 2025 00:00:00 +0000</pubDate>
      
      <guid>https://null-hypothesis.ines-garcia263.workers.dev/posts/traffic-based-customer-segmentation/</guid>
      <description>&lt;p&gt;Customer segmentation is one of those problems that sounds straightforward until you actually sit down with the data. In this post I&amp;rsquo;ll walk through an approach I built for segmenting customers based on their HTTP traffic patterns — the kind of traffic data that tells you not just how much a customer uses a service, but &lt;em&gt;how&lt;/em&gt; they use it.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>The Dashboard You Built That Nobody Opens</title>
      <link>https://null-hypothesis.ines-garcia263.workers.dev/posts/why-dashboards-are-read-once-and-never-opened-again/</link>
      <pubDate>Wed, 09 Apr 2025 00:00:00 +0000</pubDate>
      
      <guid>https://null-hypothesis.ines-garcia263.workers.dev/posts/why-dashboards-are-read-once-and-never-opened-again/</guid>
      <description>&lt;p&gt;&lt;em&gt;There&amp;rsquo;s a hard truth hiding in your analytics platform. Let me show you how to find it.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;Open your BI tool. Look at the list of dashboards. Find the one that took you — or someone on your team — two weeks to build. The one with the carefully color-coded KPI tiles, the year-over-year comparisons, the trend lines going back 18 months.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Why I Used Econometrics Instead of ML to Estimate Export Potential — And What I Learned Implementing It</title>
      <link>https://null-hypothesis.ines-garcia263.workers.dev/posts/export-potential-econometrics-vs-ml/</link>
      <pubDate>Mon, 10 Feb 2025 00:00:00 +0000</pubDate>
      
      <guid>https://null-hypothesis.ines-garcia263.workers.dev/posts/export-potential-econometrics-vs-ml/</guid>
      <description>&lt;p&gt;In 2020, I was handed a PDF — an ILO working paper titled &lt;em&gt;Spotting Export Potential and Implications for Employment in Developing Countries&lt;/em&gt; (Cheong, Decreux &amp;amp; Spies, 2018) — and asked to turn it into a working algorithm.&lt;/p&gt;&#xA;&lt;p&gt;The paper describes a methodology developed by the International Trade Centre to identify a country&amp;rsquo;s unrealized export opportunities, and then estimate how many jobs realizing those opportunities would create. Across six developing countries. At the product-market-sector level.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
