I'm not a fan of normal tutorials because they start from a point where everything is installed and running and the project already initialized and the file in your face ready to write on it. But how to get there? Magic.
Programming
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
I’ve had exactly the opposite thought - every tutorial or explanation I find starts from scratch with create-react-app or something when I already have a project and I just want to know how to use your library.
I was thinking about picking languages from scratch. If it's about libraries it is kinda expected to know some basics.
Yeah this gets to me as well. Worst of all is that I think these people are missing a trick. Create another article with the basic setup and link through to it instead and you get a free SEO win.
I have been through the same. I can find a lot of tutorials on the super easy stuff but more advanced or just a bit more advance stuff is up to me to figuring out. It is so bad that i start with documentations first then try it out myself, then google problems. I do not checkout tutorials anymore, only if i am super new on the subject. Chat gpt has been a lot more helpful, either it helps me with the problem or give me hints on what to google for or try out.
How far do you take that? I don't think tutorials should cover installing an operating system or the programming language being covered unless the tutorial is specifically about those topics. Having focus on the project itself rather than the prerequisites is generally a good approach unless there's something specific about the prerequisites that are unusual.
What I'm trying to say is that I have to drop a lot of tutorials because I can't even start running the code locally. If I don't know how to use the code I'm learning outside the browser is like I'm learning nothing.
What programming language? You might have to back to basics. I know what you mean though. That was my frustration as well. The basics aren't covered well enough on many courses, and learning in a browser IDE adds anxiety when following tutorials if you don't know how to set up your environment.
If it's with Python, maybe I can help. Getting your environment set up is the most important part. I like to use pycharm, it forces you into virtual environments but that's a good practice to follow and gives you plenty of practice with the basics since you'll have to install your dependencies for every project.
Sometimes the dependencies change, and it's nice to know what version you previously used vs how the new package version works.
Python was not such a problem because you can make a .py file and start doing things. More or less like a js. But when I want to make my own things with compiled programs like c++, rust, haskell... I get stuck.
When I first started learning how to code 9 months ago [...]
People who have most recently overcome a challenge have valuable perspective on facing that challenge.