If the goal is for you to learn, then I don't think it much matters. It seems the point of the post you linked is mostly that the 20th todo-list app you build will likely bore you. That's a valid point - if you're trying to learn, it's a little counter-productive to build something that wont hold your interest.
However, like you say, it still covers the surface you're looking for. If you can build a todo list end-to-end, not get bored by it, and learn everything about the new framework that you intended to understand, what's the problem? It may, in fact, be even better to stick to well-worn territory - you don't want to split your focus by also wrapping your head around a new problem. It will be easier to fit a new tool to an already-solved problem.
What concerned me are the responses like "Add it to the mile high pile over there..." when I shared it and was being proud I could finish it within 2 weeks.
So, who are you doing it for? If the purpose of the project is to teach yourself a thing, and you succeed, who cares how high the pile is. Compare yourself to yourself, be proud it!
The aim was to learn the framework. I was super excited about the end result and just wanted to share with others, thinking that it could be useful for others also.
I guess that's a choice you'll have to make - thing is, with a TODO list app, it may be exciting to you but it might not necessarily be exciting to others, simply because there are so many already. I kinda split my own side projects into two categories: there's things I build to increase my own understanding, and then there's things I build because I think the world needs one. For me, a TODO list app is totally worthwhile, but I'd only put it in the first category.
If the goal is for you to learn, then I don't think it much matters. It seems the point of the post you linked is mostly that the 20th todo-list app you build will likely bore you. That's a valid point - if you're trying to learn, it's a little counter-productive to build something that wont hold your interest.
However, like you say, it still covers the surface you're looking for. If you can build a todo list end-to-end, not get bored by it, and learn everything about the new framework that you intended to understand, what's the problem? It may, in fact, be even better to stick to well-worn territory - you don't want to split your focus by also wrapping your head around a new problem. It will be easier to fit a new tool to an already-solved problem.
What concerned me are the responses like "Add it to the mile high pile over there..." when I shared it and was being proud I could finish it within 2 weeks.
So, who are you doing it for? If the purpose of the project is to teach yourself a thing, and you succeed, who cares how high the pile is. Compare yourself to yourself, be proud it!
The aim was to learn the framework. I was super excited about the end result and just wanted to share with others, thinking that it could be useful for others also.
I guess that's a choice you'll have to make - thing is, with a TODO list app, it may be exciting to you but it might not necessarily be exciting to others, simply because there are so many already. I kinda split my own side projects into two categories: there's things I build to increase my own understanding, and then there's things I build because I think the world needs one. For me, a TODO list app is totally worthwhile, but I'd only put it in the first category.
That said, every domain has room to innovate.
Well said, thanks for the help.
Implementing it in a new way can be appealing to others also, not just me.
I agree with all this.
Go ahead and build the TODO. I think it's actually pretty cool that there is a sort of standard for this sort of thing
These are the comments why I stick to Dev.to instead of Medium, thank you guys ;)