How can I find someone to explain, say, Git to a non-technical person
Where do I find that person? What am I paying them?
Where do I find that person? What am I paying them?
How complex do you want to go is always the question? What is a screwdriver? Its a tool that turns screws. What's a scew? A piece of metal that connects two thingsgs. OK I got one but its not turning? Oh yeah their are different screw types. .... And on and on for any seemingly simple subject.
What you need to know to use Git is variable and depends on what you want to do and how many people you want to collaborate with.
To me the situation you are setting up doesn't hang together well. Git isn't magic and if you are studying DL/ML/etc. Algorithms to understand them well enough to use them and write code or design an application with them, Git isn't hard to learn. Sure, Git can have deep details and capabilities but you don't need that to use them.
I would suggest you purchase a GitHub account or similar service and just start using Git. Get a paid account so that you have more control of the repo. Read the user agreement to make sure you agree with it. Setting up your own Git server usually isn't worth it.
Just like when one is hiring consultants. Don’t lie to yourself about the situation and there are cases where it can be useful. Treat it like a magic, expensive bullet that will somehow save time and money, and, well, you’ll put your eye out.
1. Imagine you have a folder with some important documents in it. You can think of the folder as a "repository" in git.
2. When you make a change to one of the documents, git helps you keep a record of that change. It does this by creating a "commit," which is like a snapshot of all the files in the repository at that moment in time.
3. Each commit has a special message that explains what changed in the files. For example, you might write a commit message like "added a new paragraph to the report" or "fixed a typo in the spreadsheet."
4. You can have many different commits in a repository, and they all form a timeline of changes. This is called the "history" of the repository.
5. If you ever need to go back to an earlier version of the repository, you can use git to find the commit you want and restore the files to that version.
Which part of this is "completely wrong?"
You say that you're only using Git as an example of something you'd like to learn. Are all these concepts that you'd like to learn technical/software related? If so, CodeMentor may be what you're looking for.
In a more general sense, it's a very interesting problem. How do you find personalized technical help online, with some assurance that the person helping you is actually competent in the field?
You’re asking for someone to care why you want to learn it, and tailor the instruction to you. To think about all the possibilities for you, and filter them down to a short list. To save you some time, or some effort. Hopefully both.
Consultants will cater to that style of interaction, and it will cost a lot. “A lot” is relative to the location of the consultant.
You can do 90% of the stuff with them. When you have an strange case use the command line.
What about Git do you want to know?