<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: caarmen</title><link>https://news.ycombinator.com/user?id=caarmen</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 21 Oct 2026 09:17:17 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=caarmen" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by caarmen in "I don't want to read what you didn't write"]]></title><description><![CDATA[
<p>To address the problem of symmetry, where the effort to generate a wall of LLM text is much lower than the effort to review it: if someone throws such a wall of text to me, I suggest we review it together. Same for huge PRs. When a coworker opens a PR with thousands of lines of non trivial code, I schedule a meet with them to do a pair review together. When doing this for a PR review, I found it much easier for me to review, and the other person also caught mistakes in their PR that I might have missed. This pair review (of PRs or LLM generated text) adds a tiny bit of humanity to the process.</p>
]]></description><pubDate>Wed, 23 Sep 2026 06:51:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=49812555</link><dc:creator>caarmen</dc:creator><comments>https://news.ycombinator.com/item?id=49812555</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49812555</guid></item><item><title><![CDATA[New comment by caarmen in "Perfection is not over-engineering"]]></title><description><![CDATA[
<p>> A team of three people maintains five microservices.<p>How about a team of 2 people maintaining 15+ microservices? :/<p>Add to this: at any given time, we have several features at different phases, so some microservices have multiple open PRs. And some features impact multiple microservices.<p>When we release a feature, we deploy all impacted microservices at the same time.</p>
]]></description><pubDate>Wed, 22 Jul 2026 06:27:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=49002591</link><dc:creator>caarmen</dc:creator><comments>https://news.ycombinator.com/item?id=49002591</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49002591</guid></item><item><title><![CDATA[New comment by caarmen in "Ask HN: What are you working on? (June 2026)"]]></title><description><![CDATA[
<p>A build of GnuCOBOL that can run in Android and iOS apps: <a href="https://github.com/caarmen/cobol-mobile" rel="nofollow">https://github.com/caarmen/cobol-mobile</a><p>No real use case in mind. Just a project that made me happy for a couple of weekends.</p>
]]></description><pubDate>Mon, 15 Jun 2026 20:47:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=48546835</link><dc:creator>caarmen</dc:creator><comments>https://news.ycombinator.com/item?id=48546835</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48546835</guid></item><item><title><![CDATA[New comment by caarmen in "I believe there are entire companies right now under AI psychosis"]]></title><description><![CDATA[
<p>Not OP, but a very simple example: I use AI to review my work before opening a PR for my colleagues to review. I ask it to review the commits in my branch. Instead of consuming tokens just to instruct it how to use git operations and other tools to find the commits since the base commit, I asked AI to create a little bash script to make patch files commit1.patch, commit2.patch, commit3.patch, etc, for all the commits in my branch since the base commit. Now I just use this script to prepare the context of commits to review.<p>I feel like an imposter here, I’m definitely not using AI as much as it seems everyone is :( I can’t imagine using hundreds of dollars of tokens a day. But maybe this little tip for reviews might be helpful to someone.</p>
]]></description><pubDate>Sun, 17 May 2026 02:05:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=48165459</link><dc:creator>caarmen</dc:creator><comments>https://news.ycombinator.com/item?id=48165459</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48165459</guid></item><item><title><![CDATA[New comment by caarmen in "Kagi Translate now supports LinkedIn Speak as an output language"]]></title><description><![CDATA[
<p>Input:<p>I'm getting burned out, feeling like I constantly have to be proving myself. It's exhausting. And the job market is terrible, so I can't just quit.  I want to cry.<p>Output:<p>I’m currently leaning into a season of intense growth and radical accountability. It’s a high-octane journey that truly tests your resilience!  While the current talent landscape is evolving, I’m choosing to stay committed to the grind and embrace the challenge. Grateful for the lessons that come with pushing your limits! #Resilience #GrowthMindset #HustleCulture #CareerJourney</p>
]]></description><pubDate>Tue, 17 Mar 2026 10:37:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=47410852</link><dc:creator>caarmen</dc:creator><comments>https://news.ycombinator.com/item?id=47410852</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47410852</guid></item></channel></rss>