<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Writing | Dineshkarthik Raveendran</title>
  <subtitle>Practical notes on data engineering, platform strategy, and technology judgment.</subtitle>
  <link href="https://dineshkarthik.me/blog" rel="alternate" type="text/html"/>
  <link href="https://dineshkarthik.me/feed.xml" rel="self" type="application/atom+xml"/>
  <id>https://dineshkarthik.me/blog</id>
  <updated>2026-06-17T00:00:00+00:00</updated>
  <author>
    <name>Dineshkarthik Raveendran</name>
    <email>hello@dineshkarthik.me</email>
    <uri>https://dineshkarthik.me/</uri>
  </author>
  <entry>
    <title>Vibe coding vs agentic engineering: what the new SDLC means for leaders</title>
    <link href="https://dineshkarthik.me/blogs/vibe-coding-vs-agentic-engineering" rel="alternate" type="text/html"/>
    <id>https://dineshkarthik.me/blogs/vibe-coding-vs-agentic-engineering</id>
    <published>2026-06-17T00:00:00+00:00</published>
    <updated>2026-06-17T00:00:00+00:00</updated>
    <summary>AI makes generation cheap; verification, judgment, and direction are the new craft. A leader's synthesis of Google's new SDLC whitepaper on vibe coding and agentic engineering.</summary>
  </entry>
  <entry>
    <title>AI-native data teams: what drives success and what leads to failure</title>
    <link href="https://dineshkarthik.me/blogs/ai-native-data-teams-success-failure" rel="alternate" type="text/html"/>
    <id>https://dineshkarthik.me/blogs/ai-native-data-teams-success-failure</id>
    <published>2026-05-26T00:00:00+00:00</published>
    <updated>2026-05-26T00:00:00+00:00</updated>
    <summary>Most teams call themselves AI-native without changing how data, governance, or delivery actually work. Here's what actually separates the teams that deliver durable value from those stuck in demo mode.</summary>
  </entry>
  <entry>
    <title>What executives actually need from a data leader</title>
    <link href="https://dineshkarthik.me/blogs/what-executives-actually-need-from-a-data-leader" rel="alternate" type="text/html"/>
    <id>https://dineshkarthik.me/blogs/what-executives-actually-need-from-a-data-leader</id>
    <published>2026-05-08T00:00:00+00:00</published>
    <updated>2026-05-08T00:00:00+00:00</updated>
    <summary>Executives don't need more dashboards or a longer tool shopping list. They need a data leader who creates trust, improves decisions, and builds scalable organizational leverage.</summary>
  </entry>
  <entry>
    <title>Where AI fits in the modern data stack</title>
    <link href="https://dineshkarthik.me/blogs/where-ai-fits-in-the-modern-data-stack" rel="alternate" type="text/html"/>
    <id>https://dineshkarthik.me/blogs/where-ai-fits-in-the-modern-data-stack</id>
    <published>2026-01-14T00:00:00+00:00</published>
    <updated>2026-04-29T00:00:00+00:00</updated>
    <summary>AI doesn't sit outside your data stack. It works best where trust, governance, and reliable foundations already exist. Here's how to think about AI as an extension of modern data capabilities.</summary>
  </entry>
  <entry>
    <title>How to reduce data platform complexity without slowing teams down</title>
    <link href="https://dineshkarthik.me/blogs/reduce-data-platform-complexity" rel="alternate" type="text/html"/>
    <id>https://dineshkarthik.me/blogs/reduce-data-platform-complexity</id>
    <published>2025-11-28T00:00:00+00:00</published>
    <updated>2026-04-28T00:00:00+00:00</updated>
    <summary>A good data platform does not eliminate complexity entirely. It contains complexity in the right places and removes it from everyday delivery.</summary>
  </entry>
  <entry>
    <title>Why most data teams are busy but not effective</title>
    <link href="https://dineshkarthik.me/blogs/why-most-data-teams-are-busy-but-not-effective" rel="alternate" type="text/html"/>
    <id>https://dineshkarthik.me/blogs/why-most-data-teams-are-busy-but-not-effective</id>
    <published>2025-09-15T00:00:00+00:00</published>
    <updated>2026-04-28T00:00:00+00:00</updated>
    <summary>Data teams often appear highly productive—shipping dashboards, fixing pipelines, responding to requests—yet struggle to move the business forward. The problem isn't effort; it's a system designed for activity rather than leverage.</summary>
  </entry>
  <entry>
    <title>What I look for in a modern data platform</title>
    <link href="https://dineshkarthik.me/blogs/what-i-look-for-in-a-modern-data-platform" rel="alternate" type="text/html"/>
    <id>https://dineshkarthik.me/blogs/what-i-look-for-in-a-modern-data-platform</id>
    <published>2025-07-20T00:00:00+00:00</published>
    <updated>2026-04-27T00:00:00+00:00</updated>
    <summary>A practical framework for evaluating data platforms based on reliability, cost, developer experience, governance, and speed to insight.</summary>
  </entry>
  <entry>
    <title>Data Warehouse, Data Lake, or Lakehouse? A pragmatic guide</title>
    <link href="https://dineshkarthik.me/blogs/data-warehouse-data-lake-or-lakehouse" rel="alternate" type="text/html"/>
    <id>https://dineshkarthik.me/blogs/data-warehouse-data-lake-or-lakehouse</id>
    <published>2025-06-15T00:00:00+00:00</published>
    <updated>2026-04-26T00:00:00+00:00</updated>
    <summary>A practical decision framework for choosing data architecture based on workloads, governance needs, and team maturity.</summary>
  </entry>
  <entry>
    <title>Become a Data Engineer: Master the Fundamentals</title>
    <link href="https://dineshkarthik.me/blogs/master-the-fundamentals" rel="alternate" type="text/html"/>
    <id>https://dineshkarthik.me/blogs/master-the-fundamentals</id>
    <published>2025-01-25T00:00:00+00:00</published>
    <updated>2026-04-26T00:00:00+00:00</updated>
    <summary>A guide for building the core technical judgment behind data engineering, from systems thinking to the practical foundations that make teams effective.</summary>
  </entry>
  <entry>
    <title>Taming the Data Pipeline Beast: Best Practices for Robust Data Engineering</title>
    <link href="https://dineshkarthik.me/blogs/taming-data-pipeline-beast" rel="alternate" type="text/html"/>
    <id>https://dineshkarthik.me/blogs/taming-data-pipeline-beast</id>
    <published>2024-05-29T00:00:00+00:00</published>
    <updated>2026-04-26T00:00:00+00:00</updated>
    <summary>Design patterns for data pipelines that are observable, maintainable, resilient, and ready for real organizational scale.</summary>
  </entry>
  <entry>
    <title>Surfing the Technological Tidal Waves: Embracing the Hype and Conquering FOMO</title>
    <link href="https://dineshkarthik.me/blogs/surfing-technological-tidal-waves" rel="alternate" type="text/html"/>
    <id>https://dineshkarthik.me/blogs/surfing-technological-tidal-waves</id>
    <published>2023-07-15T00:00:00+00:00</published>
    <updated>2026-04-26T00:00:00+00:00</updated>
    <summary>A measured approach to new technology waves, experimentation, and separating durable value from noise.</summary>
  </entry>
</feed>
