<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Blog on Lightfactory</title>
		<link>https://lightfactory.app/blog/</link>
		<description>Recent content in Blog on Lightfactory</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://lightfactory.app/blog/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>What a review reads besides the diff</title>
				<link>https://lightfactory.app/blog/what-a-review-reads/</link>
				<pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate>
				<guid>https://lightfactory.app/blog/what-a-review-reads/</guid>
				<description>&lt;p&gt;A diff shows what changed. It rarely shows why the code was shaped the way it was. That knowledge usually lives in a module README or a decision record that the change never touches, so a reviewer who reads only the diff cannot tell when a change quietly breaks an agreement.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-diff-first-then-the-documents-behind-it&#34;&gt;The diff first, then the documents behind it&lt;/h2&gt;&#xA;&lt;p&gt;Lightfactory starts with the diff of the pull request. It then reads the README of each module the change touches and the decision records those READMEs link to. A finding cites the document it relies on, for example:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
