@waleeddib7096
Btw in all honesty. If you start a for dummies series you’re going to blow up on YouTube. It takes skill to dumb down things.
@HeaBerty
"If you can't explain it simply, you don't understand it well enough."
@buildwithcode9743
To Nick: Can u please make this a series for other topics as well? To the others: Upvote this comment if you share the same thought ;)
@JasonBillingham
Two years later and this is still by far the best Git tutorial I've found on YouTube. Simple, easy to understand, and didn't want to make me tear my hair out. Thank you for de-mystifying Git and GitHub for me and showing me how simple the basics really are.
@vihrigapozax4592
"And then you make a repository. Repository means folder. Folder means repository. Same thing." Omg I love this approach. I have been stuck sooo many times in things like this. I am very bad at remembering names, addresses, etc, and it affects my studying because I have to google familiar terms all the time. It frustrates me so much and makes me feel so stupid, though I know I am not. And also, because I am smart in some ways, like logical thinking (maths, coding, algorithms...), people assume I know stuff, and are genuinely surprised if i ask help in "trivial" things. And then they explain them like I already knew it, so I learn nothing. Being smart and knowing facts and terms are two so different things. This video is gold. Thank you.
@sraynitjsr
This video is 1000000000000 times better than any 5, 10 Hour long playlist out there on Youtube, simply awesome
@JStephs1950
At 72 years old and more than one college degree, I've had my share of bad teachers, and good teachers, and so-so teachers. When @Nick started off saying he was going to teach Git like we were 5 years olds, I immediately "liked" this video and subscribed. That's my idea of the best way to teach. The worst teachers have always been those who forget what it was like to not know something; coincidentally, most of them were more interested in showing how much they knew instead of trying to impart their knowledge to students. That was a combination of faults deadly to an enjoyable, informative class. The only thing that will convince me to come back and remove my "like" is if he doesn't live up to the promise and starts getting all complicated and laden with detail. I look forward to finally being able to get something out of Git.
@ines226
Thank you, actually clear and useful! Put the summarized commands here for easy copy/paste: git init = initialize project to use git git add . = add all changes to be saved git add filename = add single file to be saved git commit -m "message" = save changes with message git push origin master = push changes to github new-branch git pull origin master = pull changes from github master git checkout -b new-branch = create a new branch git status = check status of changes git log = see all previous saved changes git checkout commit hash = travel back to old commit
@virx15
HTML just dropped a tear of happiness there mentioned together with "programming languages".
@yuji9774
I love how he seems impatient and drags his voice over every sentences. It cracks me up and keeps me interested. Thank you dude!!
@Jonathan_Strange
For people new to git, it may have become a little confusing at 14:30 where a similar word "pull" is mentioned. A "Pull Request" (essentially a request to merge) is not the same as the 'pull' command (which retrieves the latest version from the remote repository). A pull request is basically a note (request) to others (usually handled by the owner) to notify them that you have made changes on a branch and want (request) those changes to be merged into the main (usually 'main' or 'master', but may be another relevant branch, like 'UAT') branch. After a short discussion & quality check (or none at all) and a look at the changes (or not) a merge into the relevant branch is usually done. Please feel free to add any comments, corrections or clarifications.
@transcend8826
I like how he seem so frustrated while I'm understanding everything he said. Learning is so much fun
@Tinu921
3 years later, Just saw your video. You gain a new subscriber. This is by far the best video on youtube. Thank you!
@tyler7820
Fantastic work. No padding at the beginning, no pleading to Like and Subscribe, just good content for 19 minutes. Best I've seen about Git and Github. Respect!
@screaminscott
I like how you started with the concept of using Git to save your progress. Everyone else always starts with the concept of version control and repositories.
@dexterjonesibiza
I have watched sooooo many tutorials on Git, and I can honestly say, this is the best one. By far. Super easy to understand. Well done sir.
@mikeyserrano9748
Even as a 3rd year cs student, Git still confuses tf out of me, so this was VERY much appreciated
@LorenzoGuardati
I LOVE how your tone of voice perfectly reflects what's dumb and not relevant and what's really important. Videos with a flat tone of voice ends up confusing even more sometimes, because you can't isolate the most significant information
@minimon796
This one video taught me more than 10 previous git guide videos I have watched. I dont understand why other youtube videos dont actually teach beginners how to use git like this man does.
@ankushnothere