amoghs
Joined 7 years ago
Karma
434
Submissions
51
Member since
Jun 9
Joined 7 years ago
I felt that personally working on eesel [1]. We kept a tight focus on the problem (making it easier to refer back to your work more easily) and it's become far more than we could've expected. Ironically, the classic "is this a company or a feature" question might actually be a validation of keeping scope.
The only caveat I'd add to the post is that you should try to solve only one problem, but you should spend time exploring before hand to discover the broader set of problems and prioritise carefully.
This is so spot on! We're having similar learnings with eesel [1] too. Work is far too scattered across apps. Thanks for sharing your journey so far and congrats on the launch!
We've been in this space for a lil bit too with eesel (https://eesel.app) and it's really cool to see more people tackling these problems. It's about time we fix this.
Keen to be inspired and learn! :)