<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: silva97</title><link>https://news.ycombinator.com/user?id=silva97</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 02 Jul 2026 22:28:20 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=silva97" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by silva97 in "The primary purpose of code review is to find code that will be hard to maintain"]]></title><description><![CDATA[
<p>To criticize is, basically, to say what should have been different. It is in the past, yet it is still about what should be changed.<p>> making code more readable is a "change." I don't know what you're trying to say here.<p>Yes and this is exactly what I am trying to say. The author limited what is the purpose of a code review like it's has really this limitation but, in practice, the code review is widely about what you think it should changed on the code by multiple reasons: readability, manutenibility, performance, security, bugs, use cases, test coverage etc.<p>Making code more readable is just one of the reasons why you want the code to be changed on a pull request, it's not the primary purpose.</p>
]]></description><pubDate>Thu, 02 Jul 2026 19:24:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=48766173</link><dc:creator>silva97</dc:creator><comments>https://news.ycombinator.com/item?id=48766173</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48766173</guid></item><item><title><![CDATA[New comment by silva97 in "The primary purpose of code review is to find code that will be hard to maintain"]]></title><description><![CDATA[
<p>The author seens to misunderstand the purpose of code review. The purpose is, literally, review the code. Review means basically to think/talk about something again in order to make or not changes on it. When you review something (including code), you are basically asking for yourself: "Should it be changed or it's okay to stay like this?"<p>In order words, the purpose of code review is to or not ask for changes on the code.</p>
]]></description><pubDate>Thu, 02 Jul 2026 14:35:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=48762293</link><dc:creator>silva97</dc:creator><comments>https://news.ycombinator.com/item?id=48762293</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48762293</guid></item><item><title><![CDATA[Linux Kernel vulnerability research toolkit]]></title><description><![CDATA[
<p>Article URL: <a href="https://github.com/freedev-org/kernelvr">https://github.com/freedev-org/kernelvr</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48545506">https://news.ycombinator.com/item?id=48545506</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 15 Jun 2026 18:55:38 +0000</pubDate><link>https://github.com/freedev-org/kernelvr</link><dc:creator>silva97</dc:creator><comments>https://news.ycombinator.com/item?id=48545506</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48545506</guid></item></channel></rss>