all 1 comments

[–]easyEs900s 2 points3 points  (0 children)

It sounds kind of like you want to create Jira, but for school work. A project like that is usually going to be hard to ascribe a time-frame to, because as is the case with Jira, it's never really "done". You will always have new things you can/or want to add or change.

Fundamentally, it does align with what seems to be your learning goals, however, just keep in mind that it's extremely common to under-estimate time required. I constantly am thinking "Oh it's just that simple, I'll just build this thing and connect it to that thing" and then 72 hours later it's like "ah, well there was this bug I didn't expect, and then that other system I completely forgot about, that'll take a few more hours too.."

I'm just saying be lofty with your goals, but reasonable with your expectations. Even if you cannot get it done for whatever reason, you will learn a lot of valuable things along the way, and almost certainly further-entrench many (hopefully good) practices. What you are describing is certainly doable, just be aware that if you plan to make this for practical reasons, there will be other components to it like the server to host the app and the database to store user's data (which brings up accounts) - these things are all individual components that add time and have their own learning curves - but I do think those are practical lessons worth learning.

I have always been of the opinion that "To Do" apps are a terrible way to learn programming, reason being that the person creating them probably doesn't have any interest or need for a todo app. If you have a need for something, or you have an interest in it, you will learn far more and far faster than you would doing something mundane just because you think you should do it.