8 ms·
TL;DR: Cut scope and call it done? These sound like you're trying to build something with professional polish when you wanted to have fun: > Part of it feels
by pushfoo 2y ago
TL;DR: Cut scope and call it done?
These sound like you're trying to build something with professional polish when you wanted to have fun:
> Part of it feels like I've tried to do too much at once instead of building piece by piece
> writing the tests for these and going back and forth on different decisions has killed all productivity and drive within me.
Why not build something awful and silly? Alternatively: add an awful plugin system and say it's left up to the user.
- slantyyz 2y agoAgree. Calling it done and using it might be the best approach. If this is truly a "small project for myself", start using it. If the app mostly does what you want, and you enjoy using the app, anything in the last 30% that you feel like you need - you'll be motivated to fix. Also, drop the tests. I'm not sure there's a lot of benefit in doing that for a web page editor you wrote for yourself.