2 ms·
I think the ultimate problem here is lack of delivery. 6 years is a long time to work on something and not to get something done, delivered, completed and used.
by ensiferum 9y ago
I think the ultimate problem here is lack of delivery. 6 years is a long time to work on something and not to get something done, delivered, completed and used. If the author wants to continue on the product id recommend going backwards a bit and removing all the excessive features from the product. Define the smallest set of features that makes sense and then complete those. Get a release done and then take it from there in smaller increments. I have worked on a personal small project (60-70kloc) for over 12 years and imho the key is t o be able to.deliver something . I nearly killed my project when I did the classic mistake of doing a complete rewrite which took me over 1.5 years. It was very slow labouros unthankful job with no positive feedback. In retrospect I should have just carefully refactor my old code base to reach the same end result but with smaller increments.
- Etheryte 9y agoI don't think your point really applies here since as you can see on Github[1], the project has numerous releases, averaging at a release about every five months. Whether that's often or rarely is up for interpretation, but I'd hardly say the project is standing still. [1] https://github.com/FascinatedBox/lily/releases https://github.com/FascinatedBox/lily/releases
- ensiferum 9y agoOh, ok yeah. It just sounded like the had been grinding away for years without getting anything "out there".