<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>The Yenpo Journal</title><description>Notes on reading code, asking better questions, and understanding what we build.</description><link>https://yenpo.app/</link><language>en</language><item><title>A thoughtful guide to reviewing AI-generated code</title><link>https://yenpo.app/blog/review-ai-generated-code/</link><guid isPermaLink="true">https://yenpo.app/blog/review-ai-generated-code/</guid><description>Move beyond a plausible-looking patch. Check the behavior, the boundaries, and the evidence.</description><pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Follow a function call without losing the plot</title><link>https://yenpo.app/blog/trace-a-function-call/</link><guid isPermaLink="true">https://yenpo.app/blog/trace-a-function-call/</guid><description>A practical way to trace execution across files while keeping the original question in view.</description><pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate></item><item><title>How to understand an unfamiliar codebase</title><link>https://yenpo.app/blog/understand-an-unfamiliar-codebase/</link><guid isPermaLink="true">https://yenpo.app/blog/understand-an-unfamiliar-codebase/</guid><description>Start with one behavior, follow its path, and build a map you can actually use.</description><pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate></item></channel></rss>