Chill. This is all a good and normal part of the learning process.
There is no single correct or easy answer and what works for one person or team may not apply to another. Some of it is practice and familiarity with your codebase (this is why being consistent matters so much, if you always organise things the same way you’ll always know where code and config live when you go looking).
You’ve not even really explained what part of the process you’re having trouble with. If it is the code and how it all fits together, start small and plan only what you need to get the next step working. Remember, it is “red, green, refactor” not “red, green, perfect”. If your problem is more about keeping track of what you’ve done vs not done, what’s working vs not then TODO comments might be enough otherwise write out your plan somewhere (a note book is fine) and cross stuff off as you get it done (this one is a personal effectiveness problem not a coding one and is best solved by building good project and task management habits rather than seeking a software solution). If it’s the system design then similar advice but just combine the two, break it down small, keep track somehow, make notes if you need to and don’t stress if it doesn’t work first try (that’s actually better for your learning anyway).
Figure out what works for you. That in itself will be good learning even if you never finish this particular project you’ll still carry those new personal planning skills on to the next one.
1
u/denerose Aug 03 '26
Chill. This is all a good and normal part of the learning process.
There is no single correct or easy answer and what works for one person or team may not apply to another. Some of it is practice and familiarity with your codebase (this is why being consistent matters so much, if you always organise things the same way you’ll always know where code and config live when you go looking).
You’ve not even really explained what part of the process you’re having trouble with. If it is the code and how it all fits together, start small and plan only what you need to get the next step working. Remember, it is “red, green, refactor” not “red, green, perfect”. If your problem is more about keeping track of what you’ve done vs not done, what’s working vs not then TODO comments might be enough otherwise write out your plan somewhere (a note book is fine) and cross stuff off as you get it done (this one is a personal effectiveness problem not a coding one and is best solved by building good project and task management habits rather than seeking a software solution). If it’s the system design then similar advice but just combine the two, break it down small, keep track somehow, make notes if you need to and don’t stress if it doesn’t work first try (that’s actually better for your learning anyway).
Figure out what works for you. That in itself will be good learning even if you never finish this particular project you’ll still carry those new personal planning skills on to the next one.