<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>data warehousing on Naman&#39;s blog</title>
    <link>https://namang.me/data-warehousing/</link>
    <description>Recent content in data warehousing on Naman&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <copyright>Copyright © 2025, Naman</copyright>
    <lastBuildDate>Sun, 06 Sep 2026 10:11:29 +0530</lastBuildDate><atom:link href="https://namang.me/data-warehousing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Facts and Dimensions for Software Engineers</title>
      <link>https://namang.me/data-warehouse-basics/</link>
      <pubDate>Sun, 06 Sep 2026 10:11:29 +0530</pubDate>
      
      <guid>https://namang.me/data-warehouse-basics/</guid>
      <description>I&amp;rsquo;ve been using Google BigQuery at work and run into a few concepts I hadn&amp;rsquo;t come across as a software engineer. I figured I&amp;rsquo;d write this post for future reference and for anyone facing similar issues.
If you are a software engineer, you&amp;rsquo;re probably familiar with primary keys, foreign keys and joins. In a typical application data model, we have tables like user, role and user_role_association. We do this to isolate data into specialized tables and prevent data duplication.</description>
    </item>
    
  </channel>
</rss>
