3 ms·
README.md per project with a task per line, sorted by priority, is what worked for me. Example: # v1 MVP - skeleton project: with hello world. - database: ad
by hu3 2y ago
README.md per project with a task per line, sorted by priority, is what worked for me. Example:
# v1 MVP
- skeleton project: with hello world.
- database: add a database to the project and connect to it using code.
- login/logout: add users table and create a simple login/logout screen.
# v2
- reset password: allows user to click on forgot password and receive a new password link in their email.
- themes: tailwind or bootstrap.
And this is what I tried but failed:
GitHub Issues: not ergonomic enough. Requires many clicks and typing to search issues once you get past like 10 issues.
Trello: too simplistic and easy to desync with code.
Joplin: really nice but also easy to desync with code.
Google Docs: nice but also easy to desync with code.
- blablabla123 2y agoI also use a README.Md in a private repo plus I keep interesting ideas/links in it. Pretty messy at the beginning but works really well to get something off the ground. Once these things are done, things become more clear I think and I switch to implement what I feel like. And possibly open-sourcing it. (For more ambitious long-term efforts I guess some issue tracking makes sense though at that point)
- burgerrito 2y ago> GitHub Issues: not ergonomic enough. Requires many clicks and typing to search issues once you get past like 10 issues. I agree--Is it just me or GitHub's web is kinda slow to use? I wonder if it's my country's internet or just the website that is slow My solution is to use GitHub CLI tbh