<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: jbvlkt</title><link>https://news.ycombinator.com/user?id=jbvlkt</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 14 Apr 2026 22:28:43 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=jbvlkt" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by jbvlkt in "Servo is now available on crates.io"]]></title><description><![CDATA[
<p>Exactly. We do not have another artifact than code which can be deterministically converted to program. That is reason we have to still read the code. Prompt is not final product in development process.</p>
]]></description><pubDate>Mon, 13 Apr 2026 21:46:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=47758238</link><dc:creator>jbvlkt</dc:creator><comments>https://news.ycombinator.com/item?id=47758238</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47758238</guid></item><item><title><![CDATA[New comment by jbvlkt in "Servo is now available on crates.io"]]></title><description><![CDATA[
<p>I have been thinking about that lately and isn't testing and security evaluation way harder problem than designing and carefully implementing new features? I think that vibecoding automates easiest step in SW development while making more challenging/expensive steps harder. How are we suppose to debug complex problems in critical infrastructure if no one understands code? It is possible that in future agents will be able to do that but it feels to me that we are not there yet.</p>
]]></description><pubDate>Mon, 13 Apr 2026 21:09:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=47757841</link><dc:creator>jbvlkt</dc:creator><comments>https://news.ycombinator.com/item?id=47757841</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47757841</guid></item></channel></rss>