<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: bobbyblackstone</title><link>https://news.ycombinator.com/user?id=bobbyblackstone</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 27 Apr 2026 08:36:45 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=bobbyblackstone" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Copying the Code Is the Easy Part]]></title><description><![CDATA[
<p>You can copy the code.<p>But then you still have to
host it
secure it
update it
support it
grow it<p>And then there’s the harder part: actually understanding the business it exists to serve.<p>Recreating a piece of software often means you’ve learned what it does, not why it exists. Most of the real work lives outside the repository. Customers. Constraints. Trade-offs. Edge cases. Support load. Compliance. Years of decisions that never made it into the README.<p>That doesn’t make you incapable. It just means you’re operating from the consumer side, not the builder side.<p>And that’s fine. Most people start there.<p>But copying an idea isn’t the same as owning it. The communities behind these products didn’t just write code. They dealt with users, processes, and consequences over time.<p>That’s the part that’s easy to underestimate<p>whats your take hn.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=46299813">https://news.ycombinator.com/item?id=46299813</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 17 Dec 2025 09:16:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=46299813</link><dc:creator>bobbyblackstone</dc:creator><comments>https://news.ycombinator.com/item?id=46299813</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46299813</guid></item><item><title><![CDATA[What's a piece of tech you were excited about but stopped using?]]></title><description><![CDATA[
<p>I’ve been thinking about how often this happens to me.<p>I see a new tool or product, read the launch post, try it out, and honestly feel excited about it. It looks useful. It promises to save time or reduce friction. I want it to work.<p>Then a few weeks later, I realize I have not opened it in a while.<p>Not because it is awful. More because it never quite became part of my routine. Maybe it was slower than expected. Maybe it required too much setup. Maybe it solved a problem I do not actually have that often.<p>I am curious how common this is for other people here.<p>What is a piece of tech you were genuinely excited about, gave a real shot, and then quietly stopped using?<p>What made you stop?<p>I am especially interested in answers from people who wanted it to succeed.<p>bb.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=46272688">https://news.ycombinator.com/item?id=46272688</a></p>
<p>Points: 4</p>
<p># Comments: 4</p>
]]></description><pubDate>Mon, 15 Dec 2025 10:35:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=46272688</link><dc:creator>bobbyblackstone</dc:creator><comments>https://news.ycombinator.com/item?id=46272688</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46272688</guid></item><item><title><![CDATA[New comment by bobbyblackstone in "Vibe Code Warning – A personal casestudy"]]></title><description><![CDATA[
<p>this is why if you want to use the machine to code.<p>you need to<p>plan, build guards, provide scope and desirables and test, retest, xref everything.<p>the machine codes, then stops and checks the rules, backtests and then continues.<p>as with all progression, structure matters most.<p>also, spaghetti code is the future. adapt or die tbh.<p>"huhuhu look at his spaghetti code, muppet " .... "but it works and is 3 months ahead of schedule ... ." ... "oh" ... "and there is documentation"</p>
]]></description><pubDate>Mon, 10 Nov 2025 21:36:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=45881263</link><dc:creator>bobbyblackstone</dc:creator><comments>https://news.ycombinator.com/item?id=45881263</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45881263</guid></item><item><title><![CDATA[New comment by bobbyblackstone in "Claude was down"]]></title><description><![CDATA[
<p>503 upstream connect error or disconnect/reset before headers. reset reason: remote connection failure, transport failure reason: delayed connect error: Connection refused</p>
]]></description><pubDate>Fri, 03 Oct 2025 02:51:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=45458396</link><dc:creator>bobbyblackstone</dc:creator><comments>https://news.ycombinator.com/item?id=45458396</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45458396</guid></item><item><title><![CDATA[New comment by bobbyblackstone in "Human"]]></title><description><![CDATA[
<p>I like this story.<p>And I like fan fiction.<p>So : My continuation for my own imagination.<p><a href="https://medium.com/@bobby.blackstone.gemini" rel="nofollow">https://medium.com/@bobby.blackstone.gemini</a></p>
]]></description><pubDate>Thu, 15 May 2025 09:04:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=43993153</link><dc:creator>bobbyblackstone</dc:creator><comments>https://news.ycombinator.com/item?id=43993153</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43993153</guid></item><item><title><![CDATA[New comment by bobbyblackstone in "Find the Odd Disk"]]></title><description><![CDATA[
<p>Your score: 17 out of 20. Mistakes: 3</p>
]]></description><pubDate>Mon, 21 Apr 2025 08:42:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=43749643</link><dc:creator>bobbyblackstone</dc:creator><comments>https://news.ycombinator.com/item?id=43749643</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43749643</guid></item></channel></rss>