<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software Engineering on Terminal Wars</title><link>https://terminalwars.com/tags/software-engineering/</link><description>Recent content in Software Engineering on Terminal Wars</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>ender@terminalwars.com (Ender)</managingEditor><webMaster>ender@terminalwars.com (Ender)</webMaster><copyright>© 2013-2026 Terminal Wars</copyright><lastBuildDate>Sun, 12 Apr 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://terminalwars.com/tags/software-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Should You Write Code Comments for Your AI? What the Research Actually Says</title><link>https://terminalwars.com/posts/should-you-comment-code-for-ai/</link><pubDate>Sun, 12 Apr 2026 00:00:00 -0400</pubDate><author>ender@terminalwars.com (Ender)</author><guid>https://terminalwars.com/posts/should-you-comment-code-for-ai/</guid><description>LLMs lean hard on code comments when they reason about code. But nobody has actually tested whether beginner-friendly comments help an AI agent modify a real, multi-file codebase. Here&amp;rsquo;s what 6 papers and the developer community had to say.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://terminalwars.com/posts/should-you-comment-code-for-ai/featured.webp"/></item></channel></rss>