<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: diogogberger</title><link>https://news.ycombinator.com/user?id=diogogberger</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 28 May 2026 19:18:17 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=diogogberger" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by diogogberger in "We built a B2B API infrastructure for resume parsing and tailoring"]]></title><description><![CDATA[
<p>Interesting space to build in. One thing I've found building developer APIs is that the first 20% of effort goes into the actual feature, and the other 80% goes into the reliability layer around it — rate limiting, key management, graceful error responses, usage tracking. Curious how you handle auth — API keys, JWTs, or OAuth? And are you targeting individual developers or teams/companies as the primary buyer?</p>
]]></description><pubDate>Thu, 28 May 2026 11:55:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=48307652</link><dc:creator>diogogberger</dc:creator><comments>https://news.ycombinator.com/item?id=48307652</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48307652</guid></item></channel></rss>