Skip to content

Comment on Ask HN: Should I quit my project and move on?

Comments

There's two ways to look at it.

If the wind is out of your sails, and you've learned the "interesting" parts of the problem, then you may choose to move on to the next problem with "interesting" parts.

However, the other side of the coin is that you don't know what it takes to ship something until you ship it. And there's just a ton of detail that happens when shipping. It's one thing to build a table, it's another to level it, sand it, finish it, and wax it.

As they say 90% of the time of a project is developing it, the other 90% is getting it ready for production.

That final part is an important feather to have in your cap.

That doesn't mean this is the project for it, it could be another project. But just know that there's a gap between being "done", and "shipping".

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.