<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: jacarma</title><link>https://news.ycombinator.com/user?id=jacarma</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 15 Apr 2026 09:22:16 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=jacarma" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by jacarma in "Ask HN: What Are You Working On? (March 2026)"]]></title><description><![CDATA[
<p>- Ebook translation with AI <a href="https://polylexis.com/" rel="nofollow">https://polylexis.com/</a><p>- OSS - Stricture, a linter to prevent architecture drift <a href="https://github.com/stricture-dev/stricture" rel="nofollow">https://github.com/stricture-dev/stricture</a><p>- OSS - Enforma, super-productive react forms <a href="https://github.com/jacarma/enforma" rel="nofollow">https://github.com/jacarma/enforma</a></p>
]]></description><pubDate>Thu, 12 Mar 2026 20:19:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=47356471</link><dc:creator>jacarma</dc:creator><comments>https://news.ycombinator.com/item?id=47356471</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47356471</guid></item><item><title><![CDATA[New comment by jacarma in "Ask HN: Advice for a new Technical Architect?"]]></title><description><![CDATA[
<p>The bigger fails I've found in my dev career are over-architecture. Devs that though they were able to ideate quasi magical architectures that handle every single use case and adapt to any future changes. The result: very custom architectures that force devs to do things in weird and complex ways and get outdated as soon as the promoter leaves the company. Everything becomes slow and devs get frustrated. Many projects are already using the architecture and it turns very difficult to remove.<p>My advice: choose between the existing architecture options and stick to the standard as much as possible. Use existing tools and keep them up to date. Innovate in architecture only if your company has a specific interest in the architecture itself and they want to invest in maintaining it as one of their products (documentation, maintainers...)</p>
]]></description><pubDate>Fri, 15 Jul 2022 07:37:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=32105703</link><dc:creator>jacarma</dc:creator><comments>https://news.ycombinator.com/item?id=32105703</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=32105703</guid></item></channel></rss>