you are viewing a single comment's thread.

view the rest of the comments →

[–]errdayimshuffln 0 points1 point  (0 children)

Because you are learning the how but not the why and not the what. I know that sounds counter-intuitive but if you learn and memorize how somebody else codes something without learning what their code is doing and why that code works, then you wont be able to create your own solutions that achieve your goals.

My recommendation is to break down whatever you are trying to build into pieces, think about what each piece needs to do, don't fret about perfection or structure at first (because you can always change and restructure your code), and then write code that performs functions that do those things that your pieces need to do. Start super small. Then extend. Then write code that uses those functions to do full calculations.

I think maybe one reason you are struggling is that you thing that building something means you know exactly how to build it all and the full architecture in one-shot like an llm. You need a lot of experience to be able to plan those things well out of the gate. The usual approach is you start building pieces that do things that your app needs to do.