<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: comchangs</title><link>https://news.ycombinator.com/user?id=comchangs</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 16 Jul 2026 00:51:44 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=comchangs" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by comchangs in "Show HN: The Alphabetical Clock"]]></title><description><![CDATA[
<p>This is the kind of thing that's completely useless and I absolutely love it. Bookmarked.</p>
]]></description><pubDate>Mon, 30 Mar 2026 07:21:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=47571418</link><dc:creator>comchangs</dc:creator><comments>https://news.ycombinator.com/item?id=47571418</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47571418</guid></item><item><title><![CDATA[New comment by comchangs in "Show HN: Nanopm – PM automation for Claude Code (audit → strategy → roadmap)"]]></title><description><![CDATA[
<p>The persistent memory at ~/.nanopm/memory/ is clever. Having context survive across sessions is what makes this actually usable vs a one-shot prompt.<p>We did something similar with deployment presets in our CLI — saving frequently used server/module combinations so you don't re-specify them every time. The "memory layer" pattern seems to be emerging across all dev tooling.</p>
]]></description><pubDate>Mon, 30 Mar 2026 07:20:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=47571406</link><dc:creator>comchangs</dc:creator><comments>https://news.ycombinator.com/item?id=47571406</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47571406</guid></item><item><title><![CDATA[New comment by comchangs in "Show HN: DeepRepo – AI architecture diagrams from GitHub repos"]]></title><description><![CDATA[
<p>Tried it on a few repos — the file-tier prioritization is a nice touch. Skipping lockfiles and generated code saves a lot of noise.<p>Would be interesting to see this integrated into CI — auto-generate updated diagrams on each PR so architecture docs never go stale.</p>
]]></description><pubDate>Mon, 30 Mar 2026 07:18:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=47571389</link><dc:creator>comchangs</dc:creator><comments>https://news.ycombinator.com/item?id=47571389</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47571389</guid></item><item><title><![CDATA[New comment by comchangs in "Show HN: Email.md – Markdown to responsive, email-safe HTML"]]></title><description><![CDATA[
<p>Nice. The LLM authoring angle is underappreciated — getting an AI to write valid MJML is painful, but Markdown is trivial.<p>One thing I'd love: a CLI mode so I can pipe it into deployment notification hooks. Something like `echo "Deploy succeeded" | emailmd | sendmail` would be killer for DevOps workflows.</p>
]]></description><pubDate>Mon, 30 Mar 2026 07:10:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=47571329</link><dc:creator>comchangs</dc:creator><comments>https://news.ycombinator.com/item?id=47571329</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47571329</guid></item></channel></rss>