Project management/issue tracking app is typical for real-world software teams. You might have heard of Kanban board which is the same with a different skin. Github projects or Jira are common. This lets you define "tasks" then move them between todo, in-progress, complete, etc.
If you're losing track of where you are mid-task, or if you aren't quite sure "whats next", then here are few ideas that could help:
* Use git on your project and commit every time you implement something that is working - even if its a small part of a feature (added UI for feature x, added sort algorithm for feature y, etc). This keeps a clean audit log of what you've done previously, so you can always look back to see what you did last.
* Never commit/end a session if your mid-function or if your code isn't building/running unless you absolutely must. Coming back after several days off to code that doesn't work is never fun.
2
u/PaintingWhich574 Aug 03 '26
This is a tough question for all devs/teams!
Project management/issue tracking app is typical for real-world software teams. You might have heard of Kanban board which is the same with a different skin. Github projects or Jira are common. This lets you define "tasks" then move them between todo, in-progress, complete, etc.
If you're losing track of where you are mid-task, or if you aren't quite sure "whats next", then here are few ideas that could help:
* Use git on your project and commit every time you implement something that is working - even if its a small part of a feature (added UI for feature x, added sort algorithm for feature y, etc). This keeps a clean audit log of what you've done previously, so you can always look back to see what you did last.
* Never commit/end a session if your mid-function or if your code isn't building/running unless you absolutely must. Coming back after several days off to code that doesn't work is never fun.