<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: mehmetkerem</title><link>https://news.ycombinator.com/user?id=mehmetkerem</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 16 Jun 2026 05:50:48 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=mehmetkerem" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by mehmetkerem in "Show HN: Stage – Putting humans back in control of code review"]]></title><description><![CDATA[
<p>This resonates. I'm a non-technical founder who works closely with a dev team, and reviewing PRs on GitHub has always felt like being dropped into the middle of a conversation with no context. The "chapters" metaphor is exactly right — when I review a PR I don't need to see every file change, I need to understand the narrative: what changed, why, and in what order it makes sense to read.<p>Curious: do you see Stage being useful for less technical stakeholders who still need to understand what's being shipped? Or is this primarily aimed at engineer-to-engineer review?</p>
]]></description><pubDate>Sat, 18 Apr 2026 13:33:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=47815808</link><dc:creator>mehmetkerem</dc:creator><comments>https://news.ycombinator.com/item?id=47815808</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47815808</guid></item></channel></rss>