Something to help us getting back to old projects
Hey everybody! I've been here for about a year already and never posted anything other than some comments here and there, but now I finally have something that could be useful for the community somehow.
I have a lot of unfinished projects that I've started and for wherever reason abandoned it for another idea.
I think a lot of people here can relate to that, and if you ever took some time to get back to your side project you know that it doesn't make much sense after a while, you don't even know why you did that or why you needed this, etc.
This happened to me with a project I've took months to get back to (because reasons 🙃), so I decided that I should build something to help me (and hopefully others) with that.
And for my surprise I actually finished it this time! Go figure! 🤷♂️
It's open source so I not planning to make any money off that, but hey, I finished something!
Here you go, hope it proves itself useful for someone else too (feedbacks very welcome of course):
https://github.com/schiehll/kerbs
The tagline says "Onboard new devs into your project" but I guess future and past me counts as different devs.
Congrats on your first post!
This is a cool project. It definitely solves a problem I've had. I've got a folder of dozens of old projects that, quite frankly, I'd have no idea how to jump back into even if I really wanted to.
Here's some feedback: Your demo is a little bit confusing at first. That's because it's on the Kerbs project itself, so it's hard to know if I'm looking at a demo of a product or a marketing page. It may be helpful to have a blurb at the top explaining that this is a demo, or perhaps changing your demo to use Kerbs on a project other than itself so it's less meta.
Also, it'd be great somewhere if you explained your philosophy. What are your opinions here? What are your beliefs? Why do you think your way of solving this problem is the best compared to alternatives? There are already numerous different ways to document a project, which is fine, but it'd be great to get your take on why we should use Kerbs. When you sell users on why your project exists and why you made the decisions you made, it helps instill confidence that this is a thoughtful project that can improve our lives.
Overall, looks great, and congrats again on getting this out the door!
Thanks, @csallen! That's great feedback!
I didn't thought of the possibility of it being too meta, will try to think in a better example to use.
About the philosophy, I believe that doesn't really matter how you organize your project or which technology you chose to use, as long as you document it to make intent clear to other people that may join your project or even yourself in the future.
Maybe I should add that somewhere in the github README 🤔