<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: yoaso</title><link>https://news.ycombinator.com/user?id=yoaso</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 12 Apr 2026 19:25:06 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=yoaso" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by yoaso in "I run multiple $10K MRR companies on a $20/month tech stack"]]></title><description><![CDATA[
<p>Fair point. Stack selection is mostly about what you already know. I chose managed services not because I optimized for it, but because that's the stack I'm comfortable with.
That said, my real point was simpler: whatever stack you pick, figure out who's going to pay for it before you spend time on infrastructure decisions.</p>
]]></description><pubDate>Sun, 12 Apr 2026 16:04:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=47741327</link><dc:creator>yoaso</dc:creator><comments>https://news.ycombinator.com/item?id=47741327</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47741327</guid></item><item><title><![CDATA[New comment by yoaso in "I run multiple $10K MRR companies on a $20/month tech stack"]]></title><description><![CDATA[
<p>I'm taking the opposite approach - managed services all the way, and my monthly infrastructure costs are higher than what's described here.<p>No regrets. Infrastructure isn't the problem I'm trying to solve. The problem is: who's actually going to pay for this?<p>Optimizing infrastructure before you have customers is like designing a kitchen before you've written the menu. I launched within 72 hours of starting development and went straight to customer validation. The market feedback started coming in immediately.<p>Infrastructure costs show up in your bill. The cost of slow customer validation doesn't show up anywhere - until it's too late. That's the number I watch.</p>
]]></description><pubDate>Sun, 12 Apr 2026 11:28:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=47738446</link><dc:creator>yoaso</dc:creator><comments>https://news.ycombinator.com/item?id=47738446</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47738446</guid></item><item><title><![CDATA[New comment by yoaso in "Ask HN: How do you get feedback for your products?"]]></title><description><![CDATA[
<p>Posting on Indie Hackers has worked best for me so far. Both positive and negative reactions are useful. That said, it's inconsistent - some posts get real discussion, others get nothing.
DMs are hard. X and LinkedIn both have weak response rates. The exception on X is when you catch someone tweeting about the exact problem at the right moment - then the conversation opens up naturally.
The surprise was the Stripe App review process. The back-and-forth with the reviewer surfaced gaps in my feature set I hadn't noticed. The application process basically became a product review.</p>
]]></description><pubDate>Tue, 07 Apr 2026 11:46:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=47673711</link><dc:creator>yoaso</dc:creator><comments>https://news.ycombinator.com/item?id=47673711</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47673711</guid></item><item><title><![CDATA[New comment by yoaso in "Emotion concepts and their function in a large language model"]]></title><description><![CDATA[
<p>Damasio is exactly what I had in mind. The somatic marker hypothesis basically says emotions are the brain's shortcut for decision-making. That's a mechanism, not a mystical experience.</p>
]]></description><pubDate>Tue, 07 Apr 2026 02:51:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=47670195</link><dc:creator>yoaso</dc:creator><comments>https://news.ycombinator.com/item?id=47670195</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47670195</guid></item></channel></rss>