<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: kadhirvelm</title><link>https://news.ycombinator.com/user?id=kadhirvelm</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 06 May 2026 20:49:44 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=kadhirvelm" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by kadhirvelm in "The bottleneck was never the code"]]></title><description><![CDATA[
<p>Totally agree, we wrote our own piece similar to this: <a href="https://productnow.ai/blogs/teams-that-coordinate" rel="nofollow">https://productnow.ai/blogs/teams-that-coordinate</a><p>I really think as code becomes cheap, misalignment between people, teams, and organizations is going to hurt a lot more, especially when everyone is trying to move at break neck speeds.<p>I also think a big piece of this is human attention and inertia. Aka, why bother doing the hard work to coordinate with others when you can just ship whatever you’re thinking. I think whichever organizations can figure out the human and cultural aspects to this will do phenomenally</p>
]]></description><pubDate>Wed, 06 May 2026 15:01:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=48037065</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=48037065</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48037065</guid></item><item><title><![CDATA[New comment by kadhirvelm in "Incident with Actions"]]></title><description><![CDATA[
<p>Honestly I kind of feel for them - their traffic must be spiking like no tomorrow. Though still annoying when the team takes down time because GitHub is down...has anyone transitioned to something else successfully?</p>
]]></description><pubDate>Tue, 05 May 2026 16:13:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=48024522</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=48024522</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48024522</guid></item><item><title><![CDATA[New comment by kadhirvelm in "[dead]"]]></title><description><![CDATA[
<p>We don’t think AI vs human authorship is as much of a problem at slop vs not slop is. To break through the noise, we’ve started optimizing our docs on human download time</p>
]]></description><pubDate>Tue, 05 May 2026 15:19:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=48023736</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=48023736</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48023736</guid></item><item><title><![CDATA[New comment by kadhirvelm in "Bun is being ported from Zig to Rust"]]></title><description><![CDATA[
<p>I can't imagine going from reviewing code in Zig to letting Claude code handle it in Rust. Seems like a lot of change to deal with in a short amount of time. Wonder how much the bun team culture will change? We've been really liking bun so far</p>
]]></description><pubDate>Tue, 05 May 2026 07:14:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=48019075</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=48019075</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48019075</guid></item><item><title><![CDATA[New comment by kadhirvelm in "Doc driven engineering prioritizes team coordination"]]></title><description><![CDATA[
<p>As AI wrote more and more of our code, we found the speed came at a steep cost: we were constantly misaligned even as a small team. It was just too much to keep track of. So we switched to a doc driven development culture and found a lot more success in keeping the stack stable and maintaining feature velocity.</p>
]]></description><pubDate>Thu, 30 Apr 2026 13:31:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=47962169</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=47962169</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47962169</guid></item><item><title><![CDATA[Doc driven engineering prioritizes team coordination]]></title><description><![CDATA[
<p>Article URL: <a href="https://productnow.ai/blogs/engineering-playbook">https://productnow.ai/blogs/engineering-playbook</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47962168">https://news.ycombinator.com/item?id=47962168</a></p>
<p>Points: 1</p>
<p># Comments: 1</p>
]]></description><pubDate>Thu, 30 Apr 2026 13:31:29 +0000</pubDate><link>https://productnow.ai/blogs/engineering-playbook</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=47962168</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47962168</guid></item><item><title><![CDATA[New comment by kadhirvelm in "Our doc-driven engineering playbook"]]></title><description><![CDATA[
<p>We are a doc-driven development team. No major feature ships without a clean RFC attached to it. It sounds like overhead, but in practice it's been one of the highest-leverage investments we've made.</p>
]]></description><pubDate>Wed, 29 Apr 2026 22:47:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=47955724</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=47955724</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47955724</guid></item><item><title><![CDATA[Our doc-driven engineering playbook]]></title><description><![CDATA[
<p>Article URL: <a href="https://productnow.ai/blogs/engineering-playbook">https://productnow.ai/blogs/engineering-playbook</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47955723">https://news.ycombinator.com/item?id=47955723</a></p>
<p>Points: 5</p>
<p># Comments: 1</p>
]]></description><pubDate>Wed, 29 Apr 2026 22:47:55 +0000</pubDate><link>https://productnow.ai/blogs/engineering-playbook</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=47955723</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47955723</guid></item><item><title><![CDATA[New comment by kadhirvelm in "The Cognitive Dark Forest"]]></title><description><![CDATA[
<p>Honestly my hope is the arbitrage that allowed big tech to make the kind of margins it does on software starts to go away because it’s sooo cheap to build software. In other words, defending the technical moats that we rely on today doesn’t make sense in the future because it’s not a reliable way to make money. Aka no need to protect your technical secrets because there’s no capitalist reason to lol. Taken further, my naive hope is societal attention moves away from this layer and onto whatever becomes the new way to make money and the people left paying attention to software are big on sharing</p>
]]></description><pubDate>Sun, 29 Mar 2026 20:24:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=47566900</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=47566900</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47566900</guid></item><item><title><![CDATA[New comment by kadhirvelm in "Next.js is infuriating"]]></title><description><![CDATA[
<p>Well the thing that’s infuriating for me is feeling like there isn’t a good, well supported alternative for writing an enterprise grade React app that will be continue to be around. I used to rely on create-react-app, but now that that’s deprecated, I often find myself asking what else can I actually rely on? I don’t want to spend eng cycles dealing with webpack and stuff, this seems to be what the React team is endorsing so I guess I’m stuck?<p>Another thing I don’t know how to think about is the target market for nextjs seems to overlap with Ruby on Rails, a lot of e-commerce, media, etc. And most of these B2B apps I write are certainly not that…</p>
]]></description><pubDate>Tue, 02 Sep 2025 16:13:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=45105049</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=45105049</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45105049</guid></item><item><title><![CDATA[New comment by kadhirvelm in "Jujutsu for busy devs"]]></title><description><![CDATA[
<p>Sounds like your opinion is jj is easier and faster? Would you say that’s true for new developer onboarding too?</p>
]]></description><pubDate>Tue, 22 Jul 2025 14:20:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=44647234</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=44647234</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44647234</guid></item><item><title><![CDATA[New comment by kadhirvelm in "Jujutsu for busy devs"]]></title><description><![CDATA[
<p>I’ve had a lot of success using <a href="https://graphite.dev/" rel="nofollow">https://graphite.dev/</a>. Been pretty easy to pick up and slots right into our usual GitHub workflow. I end up using the vscode extension to manage it. Anyone have opinions how jujutsu compares?</p>
]]></description><pubDate>Tue, 22 Jul 2025 05:29:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=44643513</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=44643513</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44643513</guid></item><item><title><![CDATA[New comment by kadhirvelm in "Reflections from Toxic Engineering Teams"]]></title><description><![CDATA[
<p>Some thoughts on the causes of toxic engineering teams I've been on and some potential fixes.</p>
]]></description><pubDate>Thu, 17 Jul 2025 23:10:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=44599337</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=44599337</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44599337</guid></item><item><title><![CDATA[Reflections from Toxic Engineering Teams]]></title><description><![CDATA[
<p>Article URL: <a href="https://resync-games.com/blog/engineering/toxic-teams">https://resync-games.com/blog/engineering/toxic-teams</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44599336">https://news.ycombinator.com/item?id=44599336</a></p>
<p>Points: 5</p>
<p># Comments: 1</p>
]]></description><pubDate>Thu, 17 Jul 2025 23:10:44 +0000</pubDate><link>https://resync-games.com/blog/engineering/toxic-teams</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=44599336</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44599336</guid></item><item><title><![CDATA[New comment by kadhirvelm in "LLMs as Compilers"]]></title><description><![CDATA[
<p>Totally agree - I'd bet there will be a bigger emphasis on functional testing to prevent degradation of previously added features. And I'd bet the scope of tests we'll need to write will also go up. For example, I'd bet we'll need to add latency based unit tests to make sure as the LLM compiler is iterating, it doesn't make the user perceived performance worse</p>
]]></description><pubDate>Thu, 03 Jul 2025 06:06:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=44452104</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=44452104</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44452104</guid></item><item><title><![CDATA[New comment by kadhirvelm in "LLMs as Compilers"]]></title><description><![CDATA[
<p>Interesting, I'd hypothesize something slightly different, that we'll see a much more efficient language come out. Something humans don't need to read that can then get compiled to machine code super efficiently. Basically optimizing the output tokens to machine work done as much as possible</p>
]]></description><pubDate>Thu, 03 Jul 2025 06:03:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=44452092</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=44452092</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44452092</guid></item><item><title><![CDATA[New comment by kadhirvelm in "I'm dialing back my LLM usage"]]></title><description><![CDATA[
<p>Wrote more thoughts here: <a href="https://resync-games.com/blog/engineering/llms-as-compiler" rel="nofollow">https://resync-games.com/blog/engineering/llms-as-compiler</a></p>
]]></description><pubDate>Thu, 03 Jul 2025 02:09:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=44450957</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=44450957</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44450957</guid></item><item><title><![CDATA[LLMs as Compilers]]></title><description><![CDATA[
<p>Article URL: <a href="https://resync-games.com/blog/engineering/llms-as-compiler">https://resync-games.com/blog/engineering/llms-as-compiler</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44450937">https://news.ycombinator.com/item?id=44450937</a></p>
<p>Points: 35</p>
<p># Comments: 55</p>
]]></description><pubDate>Thu, 03 Jul 2025 02:05:23 +0000</pubDate><link>https://resync-games.com/blog/engineering/llms-as-compiler</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=44450937</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44450937</guid></item><item><title><![CDATA[New comment by kadhirvelm in "I'm dialing back my LLM usage"]]></title><description><![CDATA[
<p>I don’t doubt LLMs will become better assistants over time, as you said every few weeks. I more mean if LLMs will cross the assistant to compiler chasm where we don’t have to think about the code anymore and can focus on just the features</p>
]]></description><pubDate>Wed, 02 Jul 2025 17:09:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=44446211</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=44446211</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44446211</guid></item><item><title><![CDATA[New comment by kadhirvelm in "I'm dialing back my LLM usage"]]></title><description><![CDATA[
<p>I wonder if this is as good as LLMs can get, or if this is a transition period between LLM as an assistant, and LLM as a compiler. Where in the latter world we don’t need to care about the code because we just care about the features. We let the LLM deal with the code and we deal with the context, treating code more like a binary. In that world, I’d bet code gets the same treatment as memory management today, where only a small percent of people need to manage it directly and most of us assume it happens correctly enough to not worry about it.</p>
]]></description><pubDate>Wed, 02 Jul 2025 15:45:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=44445153</link><dc:creator>kadhirvelm</dc:creator><comments>https://news.ycombinator.com/item?id=44445153</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44445153</guid></item></channel></rss>