3 ms·
Ask HN: To delay or not delay, that is the question?
Been working on a big project since October, after building it originally it needed to be rehashed for usability. I'm still working on that now, but I'm frustrated with the way I programmed it. Should I stick it out and release, then rebuild if it proves to be worth while, or change it now and further delay release?
- thatusertwo 16y agoThe code is overly complicated and overly extensive, I could probably rebuild it with half the code and make it so much better. But I've been delaying as it is....
- matth 16y agoHaving faced the same situation in the past, I encourage you to simply release it. No need to spend months upon months improving the backend while no one is using the damn thing. How long has the refactor been on your mind? Has it been at least a month or two? Has your mental picture of the rebuild been consistent, or does it change week-to-week? Here's my advice to get you going: Write down your general refactor plan in detail. Next, create a todo list / timeline that gets you to production deployment as quickly as possible based on your current codebase. Focus on other things a bit. Launch, marketing, etc. Once this thing has been out in the wild for a bit, reassess that refactoring plan you wrote down and see if it still makes sense based on your application's performance - both as a product, and as a piece of software.