<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Principles on Tee Zhi Yao</title><link>https://teezhiyao.com/tags/principles/</link><description>Recent content in Principles on Tee Zhi Yao</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 30 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://teezhiyao.com/tags/principles/feed.xml" rel="self" type="application/rss+xml"/><item><title>Guiding Principles</title><link>https://teezhiyao.com/posts/guiding-principles/</link><pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate><guid>https://teezhiyao.com/posts/guiding-principles/</guid><description>&lt;p>Beliefs and principles developed over time that guide how I approach work, learning, and life.&lt;/p>
&lt;hr>
&lt;h2 id="when-you-fail-to-plan-you-plan-to-fail">When you fail to plan, you plan to fail&lt;/h2>
&lt;p>This is the principle I lean on most — across work, studies, and life. The idea is simple: a little forethought goes a long way in avoiding avoidable failure.&lt;/p>
&lt;p>At work, I see the consequences of insufficient planning regularly. Being in QA means I&amp;rsquo;m most often towards the end of the product or development cycle, making the ripple effects of poor planning particularly visible — edge cases missed, environments not ready, dependencies overlooked. This isn&amp;rsquo;t specific to QA; it&amp;rsquo;s an observation about work projects in general. But from where I sit, those gaps are harder to ignore.&lt;/p></description></item></channel></rss>