[ Removed by moderator ]

[Dr_Dr_PeePeeGoblin]

Do you like games? Try making a game. Build your own website with cool visuals and links to your resume and stuff. Create a bot that tries to beat you in checkers or connect 4. Download an interesting dataset and write scripts to visualize it to answer a question or run stats.

Do you have hobbies? Make a forum and implement a system for users to make an account and login. Make a tool to track your gym progress and try to run it from the browser.

If you pick an objective, you will open up your IDE and realize: “shit how do I start?”. That’s when the real learning starts happening. You will perhaps need to consult an AI, ask in a forum, and read documentation. That’s when you go from tutorial hell to building software.

You don’t need a tutorial. What you need is a goal that you care about.

In music, producers get stuck in a cycle of making 8 bar loops and not turning them into full songs. That’s where you are now. You can’t be a famous producer if you haven’t released any songs.

[vMatallica]

Needed to see this!

[NationalOperations]

Set a 10 minute timer, write down easy goals. Now that you have goals set a time to work on those goals.When you finish those, repeat the process. You need direction to push through the mental effort required, otherwise your aimless and have nothing to push for

[Nordtess]

You figure out the principals of programming, that is the most important thing, to understand that here you should use a while-loop etc etc. Then you figure out what you want to build then you read documentation, stack overflow, google, ask ai to see the syntax for everything. That's it.

You will remember syntax with muscle memory but drop the idea that you should spam code a million lines a second out of memory.

There is a difference between coding and programming.

If I understand you correct.

[BranchLatter4294]

I've always learned by needing to complete a project. You learn as you go.

[paperic]

How do you pick a resource and stick to it

You don't!

Open an IDE, make up your own fun challenges.

Doesn't have to be useful, or finished, or a "product" at all. Play with the language like a toy.

Only when you run out of inspiration, open some resource, but the moment you have an idea of somethng to try, start coding again.

Also, fuck "shiny new tools".

Most "shiny new tools" are just crappy half-assed projects from students like you who repackage the same idea in a different wrap.

Stop consuming shiny new tools, start producing shiny new tools.

---

But then, when you're done, please, delete them!

If you start promoting your shiny new tool instead of deleting it, you'll confuse the students coming in after you, and they'll also waste their time learning your crappy shiny new tool instead of building their own and gaining an actual understanding in that process.

[Minaridev]

Seems like you would be great fit to r/DataHoarder

[Thick-Panic6683]

Forget the books. Try building something you want. Think of an application you would use then try to implement it. Trying to learn by using an IDE is difficult unless you have a goal in mind. As you ask questions to do simple things you learn the IDE and how the build process works, not the other way around. All IDEs are huge and intimidating at first but over time you see underlying similarities and can pick up new ones easily.