<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>series on philliant</title><link>https://philliant.com/series/</link><description>Recent content in series on philliant</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 philip mathew hern</copyright><lastBuildDate>Thu, 02 Apr 2026 17:44:14 -0700</lastBuildDate><atom:link href="https://philliant.com/series/index.xml" rel="self" type="application/rss+xml"/><item><title>ai</title><link>https://philliant.com/series/ai/</link><pubDate>Thu, 02 Apr 2026 17:44:14 -0700</pubDate><guid>https://philliant.com/series/ai/</guid><description>&lt;p>this series is where i document how i use ai as a real work system, not as a novelty tool.&lt;/p>
&lt;p>i write these posts to make decision quality visible: when ai is helping, when it is creating hidden cost, and which workflow choices keep outcomes stable over time. the goal is to make ai usage more deliberate, measurable, and easier to hand off across sessions.&lt;/p></description></item><item><title>cursor</title><link>https://philliant.com/series/cursor/</link><pubDate>Thu, 02 Apr 2026 17:44:14 -0700</pubDate><guid>https://philliant.com/series/cursor/</guid><description>&lt;p>this series is my living documentation for using cursor as a daily driver.&lt;/p>
&lt;p>i built it because most setup guides stop at installation, while the real leverage comes from repeatable systems: workspace boundaries, reusable rules and skills, model-routing habits, and tight review loops. those are the parts that decide whether ai-assisted editing is useful.&lt;/p></description></item><item><title>commentary</title><link>https://philliant.com/series/commentary/</link><pubDate>Thu, 02 Apr 2026 05:11:05 -0700</pubDate><guid>https://philliant.com/series/commentary/</guid><description>&lt;p>this series is where i publish the looser essays that do not fit a strict tutorial format.&lt;/p></description></item><item><title>dbt</title><link>https://philliant.com/series/dbt/</link><pubDate>Mon, 30 Mar 2026 16:34:36 -0700</pubDate><guid>https://philliant.com/series/dbt/</guid><description>&lt;p>this series is my working notebook for dbt architecture and transformation workflows.&lt;/p>
&lt;p>i care less about one-off clever models and more about systems that are easy to understand, easy to test, and easy to change six months later. when i publish here, i focus on practical design decisions and why they hold up under change.&lt;/p></description></item><item><title>sql</title><link>https://philliant.com/series/sql/</link><pubDate>Sat, 28 Mar 2026 05:48:02 -0700</pubDate><guid>https://philliant.com/series/sql/</guid><description>&lt;p>this series is where i write about sql as a working craft: clear queries, reliable debugging, and practical performance habits.&lt;/p>
&lt;p>if a specific sql pain point keeps repeating in your work, send it to me and i will use it to shape upcoming entries in this series.&lt;/p></description></item><item><title>snowflake</title><link>https://philliant.com/series/snowflake/</link><pubDate>Sat, 28 Mar 2026 04:49:27 -0700</pubDate><guid>https://philliant.com/series/snowflake/</guid><description>&lt;p>this series is where i document practical snowflake decisions that affect speed, cost, and reliability in day-to-day data work.&lt;/p>
&lt;p>here, i consider the operating model: how to design warehouse layers, tune workloads, and keep teams moving without burning credits.&lt;/p></description></item><item><title>data vault 2.0</title><link>https://philliant.com/series/data-vault-2.0/</link><pubDate>Tue, 24 Mar 2026 07:00:00 -0700</pubDate><guid>https://philliant.com/series/data-vault-2.0/</guid><description>&lt;p>this series is where i break down data vault 2.0 decisions into practical implementation patterns.&lt;/p>
&lt;p>the focus here is concrete modeling choices: what to put in hubs, links, and satellites, how to handle change, and how to keep lineage understandable as the system grows.&lt;/p></description></item></channel></rss>