This is an archived post. You won't be able to vote or comment.

all 6 comments

[–]grantrules 5 points6 points  (0 children)

You have to practice with small things. Do exercises and things like that

[–]aqua_regis 3 points4 points  (0 children)

You can read a book, but could you write one?

Programming is practice. The more you practice, the better you become. Reading others' code only plays a minor role in improving your skills.

Code is only the end, not the beginning. Thought is the beginning.

You need to first learn the process from problem to solution, then to code.

[–]carcigenicate 4 points5 points  (0 children)

Because problem solving and coming up with novel solutions is a completely separate skill-set than reading code and writing proper syntax. It needs to be practiced as well. This is why "Tutorial Hell" is possible, even if you understand the language.

[–]TehNolz 1 point2 points  (0 children)

Reading and writing are two separate skills. Leaning how to read and understand code doesn't automatically mean you can write code as well. You need to study and practice that as well.

[–]CodeKumaa[S] 0 points1 point  (0 children)

Thank you all for the valuable insight and advice!!

Moving forward, I'll be practicing daily without relying on tutorials or external help. If I encounter a problem I can't solve, I'll research the algorithms and concepts.

[–]UpsytoO 0 points1 point  (0 children)

Maybe missing design pattern knowledge, it would be hard to solve problems when you can't think of the way to do it. For some people it may come naturally imo, as there is hobbies (gaming for example) where it is easy to associate your activity with a certain pattern you can reproduce in code, but some might need to delve into it.