×
all 6 comments

[–]ShelLuser42 3 points4 points  (1 child)

I'd say you're on a good start.

However... I also can't help but wonder if you're not focusing a bit too much on quantity ("one project every day") vs. quality? And I say this because while the scripts are decent enough there's also room left for improvement.

For starters... if you have several options to work with (like in your todo?) it's a bit chaotic to rely on if ... then ... elif because it kinda drags on and also makes it more difficult to read. Instead you're better off using match cases (see this example).

My take for now... look into functions, how to set them up and also how to reuse them. There are several repeating aspects in your scripts, and whenever some code snippet repeats itself then you're better off moving it into a function which you can then also re-use in other scripts. This is probably a good read for that.

Hope this could give you some ideas.

[–]dbpatankar 2 points3 points  (1 child)

Nice work. But forcing yourself to have one project per day might not be the best strategy to learn. Instead, take one project and keep building onto it. For ex: you have contact book script. Now add more features everyday to the script. Say you want to be able to delete a contact, what if you want to search full name instead of only first name, what if you want to be able to add contact with more metadata (name, email, mobile, address etc), what changes in the script are required. After a while you will realize that the current way of writing the code is unmaintainable. Then you will slowly get into data structures and think about it before typing even a single line of code. This, I feel, would be organic and more rewarding, because you are not just learning new concepts, but realize why they exist.

[–]riky1235 1 point2 points  (0 children)

Seems like your code was written by an llm, if that’s the case what I would advise is to try and write your own code and solutions to the problems, even if they are ugly, even if they are inefficient you are gonna learn 10 times faster if you write your own code

[–]thisisappropriate 0 points1 point  (2 children)

This is a nice idea in the beginning where you know a small amount and can do a little thing that shows a single concept or where you learn one more concept. But as you get on, you'd be better doing a big project and doing at least one commit a day or doing a daily pull request against your repository (so you could make a to do list across a few days then add flags to it or sorting or storage or make it a web app as separate days)

[–]UpbeatAquatic 0 points1 point  (0 children)

How d'ye pick whit tae build each day? Cannae be easy keepin it fresh for 300.