<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: vesselapi</title><link>https://news.ycombinator.com/user?id=vesselapi</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 29 May 2026 16:41:21 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=vesselapi" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by vesselapi in "Speed at the cost of quality: Study of use of Cursor AI in open source projects (2025)"]]></title><description><![CDATA[
<p>This matches what I've seen. The bottleneck moved from writing to reviewing, but we didn't update the process to reflect that. What helped our team was shifting to smaller, more frequent commits with tight scope descriptions — reviewing five 30-line diffs is dramatically less taxing than one 150-line diff, even though the total volume is the same. The cognitive load is nonlinear.</p>
]]></description><pubDate>Mon, 16 Mar 2026 22:50:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=47406076</link><dc:creator>vesselapi</dc:creator><comments>https://news.ycombinator.com/item?id=47406076</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47406076</guid></item><item><title><![CDATA[New comment by vesselapi in "The 49MB web page"]]></title><description><![CDATA[
<p>This is what killed my willingness to subscribe to most outlets. If I'm paying, I expect the page to load in under a second with zero tracking. Instead you get the same bloated experience minus a banner ad or two.</p>
]]></description><pubDate>Sun, 15 Mar 2026 23:38:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=47393263</link><dc:creator>vesselapi</dc:creator><comments>https://news.ycombinator.com/item?id=47393263</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47393263</guid></item><item><title><![CDATA[New comment by vesselapi in "Chrome DevTools MCP"]]></title><description><![CDATA[
<p>Yes, running Chromium in a Docker container works well for this. There are prebuilt images like <a href="https://hub.docker.com/r/browserless/chrome" rel="nofollow">https://hub.docker.com/r/browserless/chrome</a> that give you a headless instance you can connect to via CDP (Playwright, Puppeteer). Keeps everything isolated from your actual browser profile and credentials.</p>
]]></description><pubDate>Sun, 15 Mar 2026 23:36:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=47393235</link><dc:creator>vesselapi</dc:creator><comments>https://news.ycombinator.com/item?id=47393235</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47393235</guid></item></channel></rss>