<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Posts on Keith Kee KW</title>
		<link>https://keithkeekw.github.io/posts/</link>
		<description>Recent content in Posts on Keith Kee KW</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 10 Jul 2026 12:00:00 +0800</lastBuildDate>
		
			<atom:link href="https://keithkeekw.github.io/posts/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Your Incident Response is Stuck on Observe</title>
				<link>https://keithkeekw.github.io/posts/2026-07-10-incident-response-ooda/</link>
				<pubDate>Fri, 10 Jul 2026 12:00:00 +0800</pubDate>
				<guid>https://keithkeekw.github.io/posts/2026-07-10-incident-response-ooda/</guid>
				<description>&lt;p&gt;&lt;em&gt;How I stopped running faster and started cycling smarter&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;I used to think a good incident response was about speed. Faster alerts. Faster diagnosis. Faster rollbacks. More dashboards. More eyes on the screen.&lt;/p&gt;&#xA;&lt;p&gt;I was wrong. &lt;strong&gt;Speed without shared Orientation isn&amp;rsquo;t speed — it&amp;rsquo;s organized chaos.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;The framework that changed how I run incident response came from a Korean War fighter pilot.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;the-ooda-loop-more-than-four-steps-in-a-circle&#34;&gt;The OODA Loop: More Than Four Steps in a Circle&lt;/h2&gt;&#xA;&lt;p&gt;John Boyd was a US Air Force colonel who noticed something strange. His F-86 Sabre pilots were consistently beating superior Soviet MiG-15s. The MiG was faster, could turn tighter, and climbed better. On paper, it should have won every engagement.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Occam&#39;s Razor: Why Simpler Explanations Usually Win</title>
				<link>https://keithkeekw.github.io/posts/2026-07-04-occam-razor/</link>
				<pubDate>Sat, 04 Jul 2026 20:08:00 +0800</pubDate>
				<guid>https://keithkeekw.github.io/posts/2026-07-04-occam-razor/</guid>
				<description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;You&amp;rsquo;re debugging a web application. The homepage loads slowly. Your first instinct is to blame the database query. But before you dive into query optimization, you check the network tab—and discover a 5MB uncompressed JavaScript bundle is the culprit.&lt;/p&gt;&#xA;&lt;p&gt;This is Occam&amp;rsquo;s Razor in action.&lt;/p&gt;&#xA;&lt;p&gt;The principle is simple: when multiple explanations fit the facts, the one requiring the fewest assumptions is usually correct. It&amp;rsquo;s not magic. It&amp;rsquo;s a practical heuristic that saves time, reduces overthinking, and points you toward the most likely answer first.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The 4D Framework of AI Fluency</title>
				<link>https://keithkeekw.github.io/posts/2026-06-27-ai-fluency/</link>
				<pubDate>Sat, 27 Jun 2026 23:33:03 +0800</pubDate>
				<guid>https://keithkeekw.github.io/posts/2026-06-27-ai-fluency/</guid>
				<description>&lt;h2 id=&#34;definition&#34;&gt;Definition&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;AI Fluency&lt;/strong&gt; is the ability to interact with AI effectively, efficiently, ethically, and safely. It&amp;rsquo;s not about memorising prompt tricks — it&amp;rsquo;s about developing a repeatable approach to working &lt;em&gt;with&lt;/em&gt; AI, rather than just throwing questions at it.&lt;/p&gt;&#xA;&lt;p&gt;Anthropic&amp;rsquo;s &lt;strong&gt;4D Framework&lt;/strong&gt; defines four core skills that make up that fluency: &lt;strong&gt;Delegation&lt;/strong&gt;, &lt;strong&gt;Description&lt;/strong&gt;, &lt;strong&gt;Discernment&lt;/strong&gt;, and &lt;strong&gt;Diligence&lt;/strong&gt;. Before applying any of the four Ds, it helps to recognise the three distinct modes you can engage AI in — because fluency also means knowing which mode fits the task.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Race Prompting Framework</title>
				<link>https://keithkeekw.github.io/posts/2026-06-26-race-prompt/</link>
				<pubDate>Fri, 26 Jun 2026 21:48:03 +0800</pubDate>
				<guid>https://keithkeekw.github.io/posts/2026-06-26-race-prompt/</guid>
				<description>&lt;h2 id=&#34;definition&#34;&gt;Definition&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;RACE&lt;/strong&gt; is a structured prompting framework designed to reduce ambiguity and improve the quality of AI outputs. It works by breaking a prompt into four deliberate components — &lt;strong&gt;Role&lt;/strong&gt;, &lt;strong&gt;Action&lt;/strong&gt;, &lt;strong&gt;Context&lt;/strong&gt;, and &lt;strong&gt;Execute/Expected Output&lt;/strong&gt; — ensuring the model has everything it needs to respond with precision. Rather than prompting by instinct, RACE makes prompt construction a repeatable, teachable process.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;the-four-components&#34;&gt;The Four Components&lt;/h2&gt;&#xA;&lt;h3 id=&#34;r--role&#34;&gt;R — Role&lt;/h3&gt;&#xA;&lt;p&gt;&lt;strong&gt;Who should the AI be?&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>What is Product Requirement Document (PRD)?</title>
				<link>https://keithkeekw.github.io/posts/2026-06-20---product-requirement-document/</link>
				<pubDate>Sat, 20 Jun 2026 22:44:03 +0800</pubDate>
				<guid>https://keithkeekw.github.io/posts/2026-06-20---product-requirement-document/</guid>
				<description>&lt;h2 id=&#34;what-is-product-requirements-document&#34;&gt;What is Product Requirements Document?&lt;/h2&gt;&#xA;&lt;p&gt;A &lt;strong&gt;Product Requirements Document (PRD)&lt;/strong&gt; is a foundational document in product management that defines what a team should build and why it matters. It acts as a &lt;strong&gt;single source of truth&lt;/strong&gt; for all stakeholders—including engineering, design, marketing, and sales—to ensure everyone remains aligned throughout the development process. By clearly outlining a product&amp;rsquo;s purpose, features, and behavior, the PRD serves as a roadmap for turning ideas into reality.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
