I agree 100%. It's important push yourself out the comfort zone and build something. It doesn't need to be perfect, bad code can be refactored, and bad design redesigned. The important thing is when we build something by ourselves the first time (unless some kind of genius which it's clearly not my case), we face problems and made mistakes, and those problems and mistakes help a lot in the learning process.
This is not related, but you have an unbelievable trust in humans not cheating (where you correct (y/n)) 😈
I was so excited when I started that I didn't think about how hard it would be to have the user type in the answer. Fuzzy matching is a little too complex for me at this point! That's why there's no high score, it's more for practice :)
I agree 100%. It's important push yourself out the comfort zone and build something. It doesn't need to be perfect, bad code can be refactored, and bad design redesigned. The important thing is when we build something by ourselves the first time (unless some kind of genius which it's clearly not my case), we face problems and made mistakes, and those problems and mistakes help a lot in the learning process.
This is not related, but you have an unbelievable trust in humans not cheating (where you correct (y/n)) 😈
I was so excited when I started that I didn't think about how hard it would be to have the user type in the answer. Fuzzy matching is a little too complex for me at this point! That's why there's no high score, it's more for practice :)
Another way to practice is adding those to a roadmap of future features / things to fix. Anyway, keep the good work!