<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>All Posts - piljoong.dev</title><link>https://piljoong.dev/posts/</link><description>All Posts | piljoong.dev</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>kpiljoong@gmail.com (piljoong)</managingEditor><webMaster>kpiljoong@gmail.com (piljoong)</webMaster><copyright>kpiljoong@gmail.com</copyright><lastBuildDate>Mon, 11 May 2026 02:55:00 +0900</lastBuildDate><atom:link href="https://piljoong.dev/posts/" rel="self" type="application/rss+xml"/><item><title>Turning Agent Work Into a System</title><link>https://piljoong.dev/posts/turning-agent-work-into-a-system/</link><pubDate>Mon, 11 May 2026 02:55:00 +0900</pubDate><author><name>piljoong</name></author><guid>https://piljoong.dev/posts/turning-agent-work-into-a-system/</guid><description>&lt;p>In the last post, I argued that prompting is not the system.&lt;/p>
&lt;p>The missing layer was the system that keeps work in a known, controlled state while it changes. That is what I started calling Ordo.&lt;/p></description></item><item><title>From Prompting to Context. Still Not the System.</title><link>https://piljoong.dev/posts/from-prompting-to-context-still-not-the-system/</link><pubDate>Sat, 18 Apr 2026 01:15:00 +0900</pubDate><author><name>piljoong</name></author><guid>https://piljoong.dev/posts/from-prompting-to-context-still-not-the-system/</guid><description>&lt;p>Early on, prompting felt like the core problem.&lt;/p>
&lt;p>If you wrote better prompts, you got better results. That framing made sense for a while.&lt;/p></description></item><item><title>AI Changed How We Build. It Did Not Change What Matters.</title><link>https://piljoong.dev/posts/ai-changed-how-we-build/</link><pubDate>Tue, 07 Apr 2026 21:07:53 +0900</pubDate><author><name>piljoong</name></author><guid>https://piljoong.dev/posts/ai-changed-how-we-build/</guid><description><![CDATA[<p><em>A view on engineering in the AI age</em></p>
<p>AI is powerful. That is no longer a theoretical point.</p>
<p>I spend far less time writing code from scratch than I used to. With a short prompt, I can generate something that would have taken hours or days before. I use that constantly now, and I don&rsquo;t think there is any serious way to deny that the economics of building software have changed.</p>]]></description></item><item><title>The 10-Join Query Nobody Wanted to Debug</title><link>https://piljoong.dev/posts/the-10-join-query-nobody-wanted-to-debug/</link><pubDate>Sun, 25 Jan 2026 02:46:20 +0900</pubDate><author><name>piljoong</name></author><guid>https://piljoong.dev/posts/the-10-join-query-nobody-wanted-to-debug/</guid><description><![CDATA[<p>The alert came in during business hours.</p>
<p>A seller-facing marketplace listing page was showing incorrect items. Products that should <em>never</em> appear in standard listings were suddenly visible. This wasn’t a cosmetic issue. It was a correctness problem in a read path users relied on.</p>]]></description></item><item><title>Distributed ID Formats Are Architectural Commitments, Not Just Data Types</title><link>https://piljoong.dev/posts/distributed-id-generation-complicated/</link><pubDate>Thu, 27 Nov 2025 11:16:56 +0900</pubDate><author><name>piljoong</name></author><guid>https://piljoong.dev/posts/distributed-id-generation-complicated/</guid><description><![CDATA[<p>Most systems start with auto-increment IDs because it&rsquo;s the easiest possible thing that works. The database hands you numbers, you store them, life is good. There&rsquo;s something comforting about watching IDs tick upward in perfect sequence—12345, 12346, 12347.</p>]]></description></item></channel></rss>