What to do with my plain code as a beginner?
Posted by ocarina_of_ami@reddit | learnprogramming | View on Reddit | 7 comments
I can write code, I‘m just starting to get really confused with git, github, docker, different environments such as VSCode, also extensions and writing tests for my Code, different compileres etc.
I watched some YouTube Videos but honestley they are too simple? Is there maybe a nice Book of how to do These things? I would especially like to know how to write good tests and how to actually run a program (I’ve heard of gui for C?).
For git, if you make lots of saved changes, isn‘t it inconvenient to see all of them in the terminal if you search for a specific one? And why would I put something in github publicly? I saw a video and the Person said that other people can change the main branch? Will all my projects be in VSCode forever? How do you organize your projects?
I just have so many questions
BeginningOne8195@reddit
Honestly this is a super normal stage, once you move beyond just writing code there’s suddenly a whole ecosystem around it and it feels overwhelming for basically everyone at first.
kennedy_gitahi@reddit
Let's start with the easiest to tackle: Your code doesn't live on Vs Code; it lives on your computer's hard drive. This means you can use any other code editor to write and edit the code as long as you open the same files and folders in it.
Think of it this way: if you have a text document, you can edit it in Word or Notepad; it's the same file on the computer, but the editor has changed.
As for Git, read the 'Pro Git' book at git-scm.com; it has everything you need to know. This also includes seeing individual changes for each of the commits you have made (meaning you do not see all saved changes in the terminal, just the ones tied to a specific commit).
And no, people cannot change your code on Github unless they fork it, at which point it will no longer be "your" code. For someone to change your code, you would have to merge their changes into your repo. Again, more on that inside the Pro Git book.
As for docker and tests, leave those alone until you have some coding experience and fully understand the basics. That includes learning how to structure your projects (lots of online tutorials can help with that).
If you have any more questions, feel free to ask below, and I will answer them as best as I can.
MartinEdge42@reddit
the tooling can feel overwhelming early on. quick orientation: git = save points, github = remote backup + sharing, docker = pretending all dev machines are identical (skip until you need it), vscode = the editor most beginners use. for git specifically just learn add/commit/push first, the rest can wait. tests: start with pytest or jest depending on language, just write 2-3 per function
MR_LAW11@reddit
Honestly this sounds very normal for where you’re at. Learning programming feels manageable until you realize there’s an entire ecosystem around coding 😅 Git, testing, environments, Docker, editors, deployment, all separate skills.
My biggest advice: don’t try learning everything at once. I’d focus on this order: VSCode + running programs → Git/GitHub basics → testing → environments → Docker later. Git especially felt confusing until I actually used it on a project. Also, GitHub can be private, people can’t just randomly edit your main branch unless you allow collaboration. Most beginner confusion comes from trying to understand tools before having a reason to use them.
deleted_by_reddit@reddit
[removed]
AutoModerator@reddit
Your post/comment was removed since we do not approve of going private.
There is zero benefit in going private as you lose the opportunity for getting peer reviews. Also we have had plenty of people return after going private (despite being warned) complaining about how they were ghosted after some time or being tricked into buying rubbish that didn't work and even if it did they didn't need.
Our Rule #11 demands that any and all communication happens in the open, public subreddit.
This is for the benefit of more against the benefit of one.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
ArchuFlutterBuilds@reddit
I understand , These are all very normal beginner questions. For Git and GitHub — 'Pro Git' book is free online at git-scm.com and covers everything you asked. For organizing projects, VS Code is fine forever — most professional developers use it daily. For GitHub public repos — other people cannot change your main branch unless you explicitly give them permission. Start with Git basics first — everything else will make more sense after that.