bobbyblackstone

You can copy the code.

But then you still have to host it secure it update it support it grow it

And then there’s the harder part: actually understanding the business it exists to serve.

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.

That doesn’t make you incapable. It just means you’re operating from the consumer side, not the builder side.

And that’s fine. Most people start there.

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.

That’s the part that’s easy to underestimate

whats your take hn.

I’ve been thinking about how often this happens to me.

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.

Then a few weeks later, I realize I have not opened it in a while.

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.

I am curious how common this is for other people here.

What is a piece of tech you were genuinely excited about, gave a real shot, and then quietly stopped using?

What made you stop?

I am especially interested in answers from people who wanted it to succeed.

bb.