🔒 Am i learning the right way?

[rotund wing]

i have a basic foundation of python where i know the syntax and basic programs.
now i m trying to build projects from the book big books of small python projects daily for 2-2.5 hours
firstly i see the problem and code the working project for the given problem
then i read the book's code and just write it as it is from the book.. is this the correct way to learn from the book's code? if not then what's the correct way?

for reference,
this is what i do, for 6th project
i firstly made a working project by myself, then i copied the book's code whilst understanding it side by side,
my first try without book: https://github.com/BadDreams34/python-small-projects/blob/main/caesar_cipher.py
book's code : https://inventwithpython.com/bigbookpython/project6.html
my book's copied code: https://github.com/BadDreams34/python-small-projects/blob/main/caesar_cipher_third.py

[tiny comet]

@rotund wing

Python help channel opened

Remember to:

• Ask your Python question, not if you can ask or if there's an expert who can help.
• Show a code sample as text (rather than a screenshot) and the error message, if you've got one.
• Explain what you expect to happen and what actually happens.

:warning: Do not pip install anything that isn't related to your question, especially if asked to over DMs.

Closes after a period of inactivity, or when you send !close.

[hollow whale]

That's honestly the perfect approach

[jagged berry]

that sounds like a pretty good way of doing things

[rotund wing]

tyyy

[jagged berry]

ah, got sniped :/

[rotund wing]

aight tysm

[hollow whale]

Always make an attempt first before trying to find out other ways of doing things

then, compare your solution to others to see what you could do differently

[rotund wing]

yeahh... but i think i m not comparing it like when i see the book's solution i try to write it from scratch instead of comparing with my first code

and when i m writing i m mostly copying pasting

only thing is i try to understand what i m copying

[hollow whale]

This is fine, but what you should then do later on is open a blank file, and see if you can code it using the book's solution, but this time on your own

that way you can see how much of the book's solution you actually learned and understood

this is actually how I approach learning new things

[rotund wing]

yeah i dont think i will be able to rewrite on my own, in that case i will just firstly observe the books code with more focus and give it more time ig

[hollow whale]

just make sure you understand the purpose of every line. It's important to understand syntax, but it's also important to understand why each line is there

I'm pretty sure the projects in that book are well commented at least

[rotund wing]

yeah i understand that in that case i think i m doing good

but i just can't write the book's code in a blank file on my own

[hollow whale]

you should try and see how far you can get though

then again, and again

until you can

get a little further each time. It's ok to peek at the original code if you get stuck

[rotund wing]

tyyy

i will try

[hollow whale]

it can be intimidating looking at a lot of code like that

but every project is written one line of code at a time

[rotund wing]

thats true

thanks again

[hollow whale]

np!

[tacit hill]

you don't need to produce a verbatim copy of the code from the book on your own, it's the general idea of the solutions that is the important part

[rotund wing]

tyy

[tiny comet]

Python help channel closed for inactivity

This help channel has been closed. Feel free to create a new post in #1035199133436354600. To maximize your chances of getting a response, check out this guide on asking good questions.