<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: overtaxed</title><link>https://news.ycombinator.com/user?id=overtaxed</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 17 Apr 2026 08:32:15 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=overtaxed" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by overtaxed in "From zero to a RAG system: successes and failures"]]></title><description><![CDATA[
<p>Sure - I neglected to include the pain point itself. Right now we spend a large amount of time during troubleshooting of a problem (incident) or when working features related to these two systems, and heavily rely on our existing internal documentation. Rather than combing through tons of those docs, a RAG chatbot made sense to me and the team seems to agree. Will move forward- thanks for the input.</p>
]]></description><pubDate>Fri, 27 Mar 2026 16:30:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=47544843</link><dc:creator>overtaxed</dc:creator><comments>https://news.ycombinator.com/item?id=47544843</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47544843</guid></item><item><title><![CDATA[New comment by overtaxed in "From zero to a RAG system: successes and failures"]]></title><description><![CDATA[
<p>Reading this blog post scared me a bit. The use case I proposed was building a "simple" RAG chatbot for some (~50 confluence docs and somewhat growing) on elasticsearch and another process that my team handles. I was just planning on using a stack like streamlit, text-embedding-3-small,FAISS for the vector store and it to be driven by a python script.<p>Didn't seem too expensive or too hard based on the handful of queries my team would be using it for, and it was a "low hanging fruit" pain point for my team that I thought could be improved by a RAG chatbot. That on top of the fact that Atlassian Rovo did not do a good job of not going to external sources when we had the answer in our existing internal docs.<p>Am I still on the right path?</p>
]]></description><pubDate>Thu, 26 Mar 2026 23:53:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=47537392</link><dc:creator>overtaxed</dc:creator><comments>https://news.ycombinator.com/item?id=47537392</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47537392</guid></item><item><title><![CDATA[New comment by overtaxed in "Ask HN: What Are You Working On? (March 2026)"]]></title><description><![CDATA[
<p>I'm working expanding upon one of the first web app projects I had on my resume when initially starting out in Software Engineering, HoopTime. It's an app for pick-up basketball players looking for a good park for games around your city. Right now focused on cities close to me, namely, Sacramento.<p>For this iteration of the project, I'm using Manus to build it. My first stab at using AI to build a web application, and the results have been interesting. Although I'm not debugging the code as much with this approach, I was surprised to still feel a similar level of 'fatigue' as I'm guiding the LLM along with the build. Check it out, would love your thoughts!<p><a href="https://hooptime-vbn5prc4.manus.space/" rel="nofollow">https://hooptime-vbn5prc4.manus.space/</a></p>
]]></description><pubDate>Mon, 09 Mar 2026 16:12:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=47310985</link><dc:creator>overtaxed</dc:creator><comments>https://news.ycombinator.com/item?id=47310985</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47310985</guid></item></channel></rss>