>be me
>been wanting to learn programming since ages
>keep hearing people say "skip tutorial hell" "just start working on a project" "tutorials are useless"
>don't know what sort of project to do
>don't know how im supposed to build a project if i don't know how to write code
>but people say i need to do a project to learn programming
i don't understand it, am i really meant to go in blind and just do like a shitty weather app or something similar? how do you even build a weather app? if i can't watch tutorials how will i know what to do? how are babies made?

>>105939287 (OP)
>"skip tutorial hell" "just start working on a project"
What? Usually tutorials are just walkthroughs for trivial projects. A tutorial is exactly what you should do if you know literally nothing. It's the only way to get dragged through the basic ideas and vocabulary.

The people who told you tutorials are useless were sabotaging you. You can't start with nothing. Learn the basica and then start a project. Make a calculator or something.

>>105939287 (OP)
>>105939305
>>105939306
Tutorial hell is when all you do is watch tutorials of the most random basic bullshit and never actually do anything on your own
You keep on watching tutorials on python and Django and vscode and then java and then some JavaScript and all you've done is hello world in them

Get a book, learn the basics, do shit, if you don't know how to do shit you investigate (which doesn't mean get aislop) and learn how to do it

just ask AI honestly, tell it to handhold you, its easier and faster than trying to find a good tutorial out of all the shit google results, this applies for everything

>>105939347
>Tutorial hell is when all you do is watch tutorials
Oh well yeah no shit.

My advice is don't watch videos at all ever for anything that isn't either high level math or a mechanical problem.

The videos are the hell, not the tutorials.

>>105939287 (OP)
Do this book. It will teach you how programming works and some useful projects. Then learn html/css/javascript and how to host on aws

I've learned many languages and techs. My typical process is like this:

1. learn an overview and the basics on like w3schools or something
2. build something with it

First you need broad exposure then you need detailed work on something practical to tie it all together

>>105939305
>>105939306
>>105939347
>>105939463
>>105939500
thanks anons atleast now i know the whole tutorials are le bad thing is just bs advice, i started reading the automate the boring stuff book and found it pretty good i'll probably read it and afterwards try to do a shitty little project to get started (though i still can't think of one)

>>105940925
Automate the boring stuff has plenty in it. You'll think of something to make based on the projects included. Try making a webscraper to add thumbnails to your movie file folders or something

>>105939287 (OP)
Try to create a small idea with python, Use gemini aistudio pro api with roo code in vscode to build it, you will learn by editing the code to your liking

>>105939287 (OP)
Here’s a project. A program that tells you what kind of project to do next.
Could be random selection from a list.
Could be a database search based on keywords, filters, and tags.
Could be a random project generator by chaining random nouns and adjectives.

>>105942568
Do this but with a webscraper

>>105939463
Second.

>>105939287 (OP)
no c

what languages have you tried?

>>105939287 (OP)
mine was a script to convert a defunct, proprietary midi-esque file format into standard midi
I had no idea what I was doing, but I knew what the input and output were supposed to look like, I just had to fill in the gaps. Hard to comprehensively list the concepts it helped me understand, but I learned basic i/o, types, functions, loops, libraries

>wanting to learn programming
that's your problem. Learning for its own sake is doomed to fail, as you well know

>>105939287 (OP)
Any good book will have exercises for you try out to apply what you learned and remember it better.

Read a book. Don't read online "tutorials."

I don't know why people don't read books anymore. What is happening?

>C Programming A Modern Approach - K. N. King

>>105939430
Exactly this. READ and DO, don't watch. If you want to do web stuff, the Open Full Stack Helsinki was really helpful to me a few years back.

In terms of "wat do", maybe someone can post that list of a 100 projects for "roll your project". Don't roll on it, pick whatever is easiest - you'll struggle with the infrastructure enough at first.

>>105939287 (OP)

My fist project was a videogame in Java.
Obviously I never finished much of it. Didn't even understand much of it...
Made a lot of retard mistakes... Didnt know how to use loops, so hardcoded repeating events, figurd for loops are difficult and redundant so I can just lean while and never use for statements... Spent an awful lot of time on switch statements for some bizzar reason.

But it was a productive waste of time. Programing and learning is knownig how not to do things just as much as knowing how to do things

>>105944200
Books are important, always be reading -- but you should always be building too. Hence you need a project and you need a book to read.

Also it's useful re-read a book you've already read and think you've understood. You'd be surprised at how much you can learn the 2nd and 3rd time you've gone through a book.

>>105939287 (OP)
ask deepseek to make a daily coding routine for you, project ideas and long-term study plan