<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>philliant</title><link>https://philliant.com/</link><description>Recent content on philliant</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 philip mathew hern</copyright><lastBuildDate>Mon, 18 May 2026 05:56:15 -0700</lastBuildDate><atom:link href="https://philliant.com/index.xml" rel="self" type="application/rss+xml"/><item><title>again, adaptability for the win</title><link>https://philliant.com/posts/20260518-again-adaptability-for-the-win/</link><pubDate>Mon, 18 May 2026 05:56:15 -0700</pubDate><guid>https://philliant.com/posts/20260518-again-adaptability-for-the-win/</guid><description>i wrote earlier about a heavy lift, then a checkpoint where i thought i was through the worst of it. it turned out i was still on the wrong path, and the right move was to turn around. adapting to what was actually in front of me produced a much better solution than anything i was forcing, and reminded me that this so-called soft skill is one of the most valuable advantages anyone can develop.</description></item><item><title>working together or alone</title><link>https://philliant.com/posts/20260509-working-together-or-alone/</link><pubDate>Sat, 09 May 2026 05:22:03 -0700</pubDate><guid>https://philliant.com/posts/20260509-working-together-or-alone/</guid><description>working with colleagues costs more in coordination, but it pays back by catching blind spots, regulating emotions, planning realistic timelines, and reducing stress. working alone is faster on the surface, until it is not. this is a contrast of the two and how i decide between them.</description></item><item><title>keep your snapshots simple</title><link>https://philliant.com/posts/20260509-keep-your-snapshots-simple/</link><pubDate>Sat, 09 May 2026 05:05:27 -0700</pubDate><guid>https://philliant.com/posts/20260509-keep-your-snapshots-simple/</guid><description>dbt snapshots are useful when you genuinely need point-in-time history, but they introduce complexity, brittleness, and a heavy maintenance and backup tax. this post is a reminder that less is more, simple is better, and you should never build a snapshot on top of another snapshot.</description></item><item><title>on the plane, again</title><link>https://philliant.com/posts/20260426-on-the-plane-again/</link><pubDate>Sun, 26 Apr 2026 14:09:34 -0700</pubDate><guid>https://philliant.com/posts/20260426-on-the-plane-again/</guid><description>in-flight wifi is not for every traveler or every trip, but when i fly solo for work it turns dead time into a calm, contained place to think, build, and prepare. i am getting real work done up here, including this site and prep for meetings on the ground.</description></item><item><title>logic</title><link>https://philliant.com/posts/20260424-logic/</link><pubDate>Fri, 24 Apr 2026 17:37:10 -0700</pubDate><guid>https://philliant.com/posts/20260424-logic/</guid><description>logic is not just for code. learning to think in if/then/else terms helps with planning, troubleshooting, designing, and understanding people and systems. once you learn it, you keep it forever, and the compounding effect of better decisions over time is hard to overstate.</description></item><item><title>back at it</title><link>https://philliant.com/posts/20260422-back-at-it/</link><pubDate>Wed, 22 Apr 2026 16:45:35 -0700</pubDate><guid>https://philliant.com/posts/20260422-back-at-it/</guid><description>i am finally out of the weeds on a recent heavy lift. i stuck with it the way i wrote about in stick with it, then moved the way i should have from the start, in smaller pieces that add up to the larger change. there is still testing and user acceptance ahead, but a stable baseline gives me room to step back, reset, and continue with a clearer head.</description></item><item><title>stick with it</title><link>https://philliant.com/posts/20260416-stick-with-it/</link><pubDate>Thu, 16 Apr 2026 20:29:00 -0700</pubDate><guid>https://philliant.com/posts/20260416-stick-with-it/</guid><description>i am in the middle of a heavy lift that has grown bigger than i thought, and i want to remind myself that continuity over time is what produces long-term results. motivation comes in waves, but sticking with the problem is how the value actually shows up.</description></item><item><title>comfortable being uncomfortable</title><link>https://philliant.com/posts/20260410-comfortable-being-uncomfortable/</link><pubDate>Fri, 10 Apr 2026 12:22:41 -0700</pubDate><guid>https://philliant.com/posts/20260410-comfortable-being-uncomfortable/</guid><description>growth rarely happens where you already feel at ease. change is disruptive by design, and the uncomfortable stretch is where new skills, boundaries, and compassion tend to show up.</description></item><item><title>dbt snapshots: moving from merges to native history</title><link>https://philliant.com/posts/20260408-dbt-snapshots/</link><pubDate>Wed, 08 Apr 2026 15:20:37 -0700</pubDate><guid>https://philliant.com/posts/20260408-dbt-snapshots/</guid><description>a guide on using dbt snapshots to track slowly changing dimensions, including lessons learned from migrating away from custom merge strategies.</description></item><item><title>little by little, a little becomes a lot</title><link>https://philliant.com/posts/20260406-little-by-little-a-little-becomes-a-lot/</link><pubDate>Mon, 06 Apr 2026 16:03:29 -0700</pubDate><guid>https://philliant.com/posts/20260406-little-by-little-a-little-becomes-a-lot/</guid><description>habit forming seems like it takes forever to take hold, but it is easier when you understand you are working toward continuity and not perfection. little by little, experience adds up.</description></item><item><title>how i automated dev.to and linkedin publishing so visibility stops depending on memory</title><link>https://philliant.com/posts/20260405-automated-devto-linkedin-visibility/</link><pubDate>Sun, 05 Apr 2026 06:55:31 -0700</pubDate><guid>https://philliant.com/posts/20260405-automated-devto-linkedin-visibility/</guid><description>i now write once in my site workflow and let automation handle distribution to dev.to and linkedin, so each post reaches people consistently without manual copy and paste.</description></item><item><title>how i use cursor and ai agents to write dbt tests and documentation</title><link>https://philliant.com/posts/20260402-how-i-use-cursor-and-ai-agents-to-write-dbt-tests-and-documentation/</link><pubDate>Thu, 02 Apr 2026 17:44:14 -0700</pubDate><guid>https://philliant.com/posts/20260402-how-i-use-cursor-and-ai-agents-to-write-dbt-tests-and-documentation/</guid><description>writing dbt tests and documentation is often the most neglected part of data engineering. i will show you how i use cursor and ai agents to automate this process, ensuring high-quality data pipelines without the manual overhead.</description></item><item><title>the future of data engineering workflows with ai</title><link>https://philliant.com/posts/20260402-the-future-of-data-engineering-workflows-with-ai/</link><pubDate>Thu, 02 Apr 2026 17:44:14 -0700</pubDate><guid>https://philliant.com/posts/20260402-the-future-of-data-engineering-workflows-with-ai/</guid><description>data engineering is evolving rapidly with the integration of artificial intelligence. i will explore how ai agents, large language models, and automated workflows are transforming the way we build, maintain, and scale data platforms.</description></item><item><title>sharing is caring</title><link>https://philliant.com/posts/20260402-sharing-is-caring/</link><pubDate>Thu, 02 Apr 2026 05:11:05 -0700</pubDate><guid>https://philliant.com/posts/20260402-sharing-is-caring/</guid><description>mastering emerging tools like cursor and ai is only the first step. true value comes from becoming a point person for your team, sharing your voice, and mentoring others through the nuances of adoption.</description></item><item><title>what is art?</title><link>https://philliant.com/posts/20260330-what-is-art/</link><pubDate>Mon, 30 Mar 2026 16:38:30 -0700</pubDate><guid>https://philliant.com/posts/20260330-what-is-art/</guid><description>i do not have a clean answer. i am trying to understand why ai-assisted code can feel normal while ai-assisted painting or music can trigger backlash, and what that says about authorship, labor, and value.</description></item><item><title>dbt tests</title><link>https://philliant.com/posts/20260330-dbt-tests/</link><pubDate>Mon, 30 Mar 2026 16:34:36 -0700</pubDate><guid>https://philliant.com/posts/20260330-dbt-tests/</guid><description>dbt tests are one of the highest-leverage habits in analytics engineering, but they are often underfunded in real projects. this post explains how i use generic and singular tests, what to prioritize first, and a few practical examples you can copy today.</description></item><item><title>dbt docs</title><link>https://philliant.com/posts/20260330-dbt-docs/</link><pubDate>Mon, 30 Mar 2026 04:39:08 -0700</pubDate><guid>https://philliant.com/posts/20260330-dbt-docs/</guid><description>dbt docs are one of the most overlooked features in a dbt project, but they are one of the most valuable for teammates who consume data without building it. i walk through how they work, what options matter, and how to host them for free on github pages.</description></item><item><title>what is sql, and why it still works</title><link>https://philliant.com/posts/20260328-what-is-sql-and-why-it-still-works/</link><pubDate>Sat, 28 Mar 2026 05:48:02 -0700</pubDate><guid>https://philliant.com/posts/20260328-what-is-sql-and-why-it-still-works/</guid><description>i break down sql in plain language: what it is, how it evolved over five decades, which problems it solves best, and the core features that keep it relevant</description></item><item><title>the difference between snowflake and the "other" databases</title><link>https://philliant.com/posts/20260328-the-difference-between-snowflake-and-the-other-databases/</link><pubDate>Sat, 28 Mar 2026 04:49:27 -0700</pubDate><guid>https://philliant.com/posts/20260328-the-difference-between-snowflake-and-the-other-databases/</guid><description>when you first step into data engineering, the sheer number of database options can be overwhelming. i break down how snowflake compares to traditional relational databases like rds and nosql options like dynamodb, focusing on when to use each and how they scale.</description></item><item><title>adaptability</title><link>https://philliant.com/posts/20260327-adaptability/</link><pubDate>Fri, 27 Mar 2026 09:45:05 -0700</pubDate><guid>https://philliant.com/posts/20260327-adaptability/</guid><description>ai and agents are accelerating how quickly work changes, and that pressure is showing up far beyond tech. i am seeing it directly while working with almost no cell signal and shared low-bandwidth internet, and it keeps reminding me that adaptability is a compounding skill.</description></item><item><title>the danger of trusting the ai agent</title><link>https://philliant.com/posts/20260326-the-danger-of-trusting-the-ai-agent/</link><pubDate>Thu, 26 Mar 2026 06:31:57 -0700</pubDate><guid>https://philliant.com/posts/20260326-the-danger-of-trusting-the-ai-agent/</guid><description>i share a real failure mode where an ai agent created and then deleted files while debugging, leaving a clean git tree but low confidence. the lesson for me is simple: ai should accelerate the work i own and understand, while domain-specific decisions stay with the people accountable for that domain.</description></item><item><title>plane wifi: when the cabin forced disconnect</title><link>https://philliant.com/posts/20260324-wifi-on-planes/</link><pubDate>Tue, 24 Mar 2026 09:23:21 -0700</pubDate><guid>https://philliant.com/posts/20260324-wifi-on-planes/</guid><description>i used to want to protect disconnected travel time. now i am torn between relief from the message stream and the feeling that a long flight is wasted if i cannot sleep and i am not online. cabin class changes how real that tradeoff is, and i still do not have a clean verdict.</description></item><item><title>left join an effective satellite without duplicating rows (use a cte)</title><link>https://philliant.com/posts/20260324-left-join-effective-satellite-cte/</link><pubDate>Tue, 24 Mar 2026 07:00:00 -0700</pubDate><guid>https://philliant.com/posts/20260324-left-join-effective-satellite-cte/</guid><description>when an entity link to another hub is optional, a naive left join that pulls in an effective satellite in the same from list can explode or blur grain. i isolate the current effective row in a cte and left join that instead.</description></item><item><title>brain defrag: time away from screens (and from "one more" with ai)</title><link>https://philliant.com/posts/20260320-brain-defrag-time-away-from-screens/</link><pubDate>Fri, 20 Mar 2026 14:30:00 -0700</pubDate><guid>https://philliant.com/posts/20260320-brain-defrag-time-away-from-screens/</guid><description>i argue that constant production and always-on tools work against clarity. yard work, runs, and boredom give my thoughts room to float, and that is when problems unlock after long struggle.</description></item><item><title>deep dive: the ai models i use</title><link>https://philliant.com/posts/20260320-deep-dive-ai-models-i-use/</link><pubDate>Fri, 20 Mar 2026 10:45:00 -0700</pubDate><guid>https://philliant.com/posts/20260320-deep-dive-ai-models-i-use/</guid><description>i walk through composer-2, gpt-5.3-codex-xhigh, claude 4.6 opus, gemini 3.1 pro, grok-4-20, and kimi-k2.5 with a comparison table plus longer notes on how i actually use each one.</description></item><item><title>a practical ai workflow: jira, github, and mcp</title><link>https://philliant.com/posts/20260319-practical-ai-workflow-jira-github-mcp/</link><pubDate>Thu, 19 Mar 2026 11:30:00 -0700</pubDate><guid>https://philliant.com/posts/20260319-practical-ai-workflow-jira-github-mcp/</guid><description>i connect my editor to jira and github through mcp, create well-structured issues from templates before coding, and reuse that text in pull requests so every agent in the chain has the same ground truth.</description></item><item><title>from prototype to production: my early adopter view of ai</title><link>https://philliant.com/posts/20260318-from-prototype-to-production-ai/</link><pubDate>Wed, 18 Mar 2026 07:09:57 -0700</pubDate><guid>https://philliant.com/posts/20260318-from-prototype-to-production-ai/</guid><description>i have watched ai move from a prototype side assistant to an operational core system. this post shares that journey with time-stamped benchmark evidence and a practical view on where model usage is headed next.</description></item><item><title>starter templates for ai rules, skills, and commands</title><link>https://philliant.com/posts/20260315-starter-templates-for-ai-rules-skills-and-commands/</link><pubDate>Sun, 15 Mar 2026 04:00:00 -0700</pubDate><guid>https://philliant.com/posts/20260315-starter-templates-for-ai-rules-skills-and-commands/</guid><description>this follow-up post gives practical, generic templates you can adapt for rules, skills, and commands, plus side-by-side examples that show why tighter structure improves ai execution quality.</description></item><item><title>how to use ai to create ai rules, skills, and commands</title><link>https://philliant.com/posts/20260314-how-to-use-ai-to-create-ai-rules-skills-and-commands/</link><pubDate>Sat, 14 Mar 2026 11:15:00 -0700</pubDate><guid>https://philliant.com/posts/20260314-how-to-use-ai-to-create-ai-rules-skills-and-commands/</guid><description>this kickoff post explains why ai-authored rule, skill, and command scaffolds are often clearer for ai execution, and how to keep humans in control with constraints, reviews, and acceptance checks.</description></item><item><title>ai br-ai-n fr-ai</title><link>https://philliant.com/posts/20260314-ai-br-ai-n-fr-ai/</link><pubDate>Sat, 14 Mar 2026 10:30:00 -0700</pubDate><guid>https://philliant.com/posts/20260314-ai-br-ai-n-fr-ai/</guid><description>this post frames ai brain fry as a workflow design problem and gives a practical framework to reduce cognitive overload while keeping ai leverage high.</description></item><item><title>my cursor setup</title><link>https://philliant.com/posts/20260313-my-cursor-setup/</link><pubDate>Fri, 13 Mar 2026 10:30:00 -0700</pubDate><guid>https://philliant.com/posts/20260313-my-cursor-setup/</guid><description>this is my real cursor setup as of march 13, 2026, rewritten as a practical tutorial with settings explanations, mcp server breakdowns, and a replication checklist.</description></item><item><title>privacy policy</title><link>https://philliant.com/privacy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://philliant.com/privacy/</guid><description>&lt;p>this privacy policy explains how i handle data for philliant.com and the automation i use to publish my posts to social platforms, including linkedin and dev.to.&lt;/p>

&lt;h2 class="relative group">what this policy covers
 &lt;div id="what-this-policy-covers" class="anchor">&lt;/div>
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#what-this-policy-covers" aria-label="Anchor">#&lt;/a>
 &lt;/span>
 
&lt;/h2>
&lt;p>this policy covers:&lt;/p></description></item></channel></rss>