Those terrible video tutorial probably are made for getting ads revenue, where the presenter might not even know or good at what they want to teach, and those terrible video are probably similar because they might refer to the same material from invalid or bad source (that's why valid good sources and citations are so important).
@@LesterFD Reading the docs is no substitute for videos such as this, or other deliberately didactic material. Docs are useful for reference, but do not do a good job of explaining the bigger picture, or the right mental models to use. Learning new systems is hard, because everyone reaches this point with their own thoughts and expectations, and the docs may or may not align. (Look up the video where Linux evangelizes git to the Google crowd, I think in 2007. The introducer says "no-one understands this"). One cannot memorize the entire documentation set, make all the needed logical connections, fill out the missing details, etc. For creations like git, human instruction is a big time saver. I write my own notes as I learn, to steer my mental models in the right direction. Stackexchange has been incredibly valuable. Git has its own concept of "time", of what version control means, etc. These are explained to some degree in the documentation intros, but it can be a challenge to understand. The writer of the documentation always makes some assumptions about the audience, and cannot (or will not) explain everything to its last logical detail.
This is exactly the kind of lecture on Git that I was looking for. Too many of these "crash courses" just settle on teaching you the cmds and that's it. I think it's crucial to have an intuitive understanding of what's happening internally within git. The absolute best advice I could give someone trying to climb the otherwise steep initial learning curve, is to first fully comprehend the simple data/object model: how the repository tree is represented and versions of it are maintained; and the use of SHA-1 hashes to represent both file/object content, and most importantly how a hash (as a commit) handle uniquely defines a versioned state of the repo tree. I don't believe this point can be stressed enough: without an intuitive high-level understanding of what's going on internally, the task of learning GIT degenerates into a exercise of memorizing seemingly unrelated command invocations.
Although I would bash the git CLI api as much as the next person, I struggle to find a way to fundamentally improve it. I guess git is trying to give you really fine grained control over what happens with your repo, and it's hard to design a concise API to do that
Definitely one of the better introductions to git that I have seen. In one and a half hour, Anish succeeds in explaining the theoretical model behind git, and then goes from basic git usage over branching and merging to using remotes. And this all in 85 minutes. Well done!👍
This proves first "It's the teacher who teaches" and then "It's the student who learns ". The way the video is articulated shows how much effort the faculty has put in. Kudos to the teacher and to all the students you finally understood GIT from its core.
you probably dont give a damn but does someone know of a method to log back into an instagram account? I stupidly lost the password. I love any help you can give me!
@Gannon Graysen I really appreciate your reply. I got to the site through google and im trying it out now. Looks like it's gonna take quite some time so I will get back to you later when my account password hopefully is recovered.
This is the best Git Tutorial I've ever seen. And I've been using Git for more than a year with very little confidence. This gives me immense confidence in handling all the changes that my team does.
This is the best video for git. Totally worth it. Whenever I have to recommend someone for git,I'll recommend this and say don't watch any video from TH-cam until you finish this one
This is the best demonstration of git mostly people starts with commands and make some repos on github which is a very abstracted way of teaching git to anyone but in this demonstration they also explained the underlaying structure of git which makes it more intuitive to learn. I wonder why people start directly with commands. This is the perfect way to demonstrate the git to a beginner.
All i can say is wow. Wanted to skip over this as i know a little about git but the way you explained the inner workings i really don't see how i can go wrong ever. Great foundation to start with look forward to re watching and studying this video and going thru the notes. Thanks!!!
It was a unique lecture, you didn't just do commands like others but you explain the data model of git and things behind it. Thank you for this really missing things.
What are your favorite commands from this lecture? I found all the best stuff to be in the last 10 minutes. My favorites are: *git add -p * (interactively stage changed hunks of a file rather than the entire file) *git show * (shows commit message and changes) *git bisect* (binary search commit history to find where a bug or change happened)
At 13:35, it is said that the code of one branch could influence the behaviour of the code in another branch, and you wouldn't know before merging those branches. While this is very true, it is *not* necessarily a merge conflict. It could very well be fast-forwarded (ie. the 2 branches never changed the same line of code) and yet a new bug might occur. Only continuous automated tests can detect those defects, not merge conflicts.
11:08 I love how the arrows point in the correct way. Too many examples make the arrows point into the direction of the future. A new snapshot is based on an older one, thus the arrow should point towards the older snapshot!
Yeah, I learned that from git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell . Some things (like git log's output) make a lot more sense when you know that each commit has pointers to its parents, but not to its children.
I have been studying the pro git book but has been not efficient enough in learning. Following along the basic tasks of git with this video gives me a very speedy overview of the branching and merging. Now I feel confident to get back to the pro git book and learn the details. Thanks for the tutorial, Anish!
Git has never made sense to me like it does now (despite using for several years) thanks to this video. I plan to rewatch it without coding along just to further cement all this in me. Wonderful job.
I have been "using" Git for years. Struggling would be a better term. It's so bad that I'm considering getting out of software development. Had enough. Git is making my life hell. It's a massive time waster. It is completely unintuitive.
The lecture was informative with lots of repository in depth ways to grab data efficient time saving which I really like grab a certain command and everything's there at your disposal also ,this no where near what it's capable of man god stuff
Here's my explanation of a hash function: You input some data and the output is a hexadecimal number. If you change the input a little bit, the output will look wildly different. You can use this to confirm you have an unchanged file from a website. If I have program P and I say the hash is X, you can download it, recreate the hash and if you *don't* get X, you'll know it's an edited file. Well known algortihms are MD5 (outdated), SHA1 (outdated, though still often used), SHA-256 (current), though there are many more algorithms. An input/output example for SHA-256 is: input: Hello World! output: 7f83b1657ff1fc53b92dc18148a1d65dfc2d4b1fa3d677284addd200126d9069 input: Hello, World! output: dffd6021bb2bd5b0af676290809ec3a53191dd81c7f70a4b28688a362182986f As you can see, the hashes differ wildly, even though I only added a comma to the text!
Pretty much true but a hash function is defined as a function which take some data. Play with its bytes and returns a hash. Its not necessary to return a hexadecimal value. But a each input should have a unique and consistent hash.
@@ezio934 There are some relatively important details - The input data size to a hash function is arbitrary but the output size is a fixed number of bits. The algorithm should exhibit 1st preimage resistance (given y, it is difficult to find an x such that h(x) = y), 2nd preimage resistance (given x, it is difficult to find a second preimage x′ ≠ x such that h(x) = h(x′)) and collision resistance (it is computationally infeasible to find any two distinct inputs x, x′ that hash to the same output). Sadly SHA-1 Which is used by git does not have all these properties.
This is awesome. I've just cloned my GitHub repo of my Qt hobby project to my laptop and commited some test changes. I think using git with the command line is better than say the Qt Creator IDE integration since the former is universal. Great introduction that successfully got me started.
professional projects do not use the console, or command line. actually, in bigger projects, with pro teams, they will force you to use git tools that show you the git flow graph. only noobs work with the console. the console is great if something messes up, but otherwise you are prone to make mistakes, you do not see your whole project and team progress, where git flow issues might have happened in the mean time, and so on. so, if you can, grab sourcetree (not those awful gui tools from github), or any git tool with a graph, and learn to use it, or else your cto or tech lead will complain. git is not rocket science. also, in a real project with potentially dozens or hundreds devs, you will never be allowed to use many git features as described in this video, regardless of whether you are a junior or senior. for instance, in many projects rebase and revert are forbidden, etc.
@@misterbeach8826 Linux kernel devs are noobs because they use git console? I think it's just a matter of preference or a project mandates tools, as you said. No harm in trying it out for a hobby project though. Clicking buttons in a GUI doesn't really teach me anything about how things work.
@@godDIEmanLIVE How's pressing buttons any different though? If you press the "Pull" button, all it does is send a "git pull" command, so I don't see how one teaches you more than the other (unless you're talking about advanced stuff). There are two main differences (I can think of) between using the console or a GUI: 1. Like you've said, the console is universal. (Though you could argue that GUIs can also be universal, as long as they're 3rd party, such as Sourcetree.) 2. The console gives you more control. With a GUI you're basically stuck with whatever that GUI offers. Good ones, however, cover 95% of your needs (just throwing in some random number). Sometimes it doesn't cover a use case, and then you eventually want to use the console. The advantages of a GUI are self-explanatory ("visual"). I prefer to use a GUI (if Jetbrains IDE, the integrated one, otherwise Sourcetree). Others at my workplace mostly use the console, but they occassionally use GUI features, too (e.g. when viewing the commit history of a class or method). But yeah, I wouldn't call people who use the command line noobs. I'd argue the opposite tbh.
@@ThunderAppeal I would be very interested to see how your pedigree absolves you from recognizing that even very intelligent people can take a lot from these lectures.
You should review tags, signing and audits in the basic GIT lessons. It's REALLY important for developers to understand why they need to sign their code and sign their commits, not to mention carrying a proper audit across the GIT tree. Otherwise awesome GIT lecture.
![ILLSLICK - Homies Feat. LILY [Official Music Video]](http://i.ytimg.com/vi/r6jGK7MumF0/mqdefault.jpg)
31:42 git add . , git commit -m , git log , git cat-file -p
32:47 git commit -a , git add :/
35:23 git log --all --graph --decorate
36:12 git status (have staged or commited or not)
41:41 git-checkout -f (switch branch)
43:11 git diff hello.txt (show the changes in the file compared to the last commit)
43:28 git diff hello.txt (compared to the branch)
44:33 git diff HEAD hello.txt
46:22 git diff git commit -m / git commit
59:37 dog points to the branch you're trying to merge.
1:04:17 git init --bare (initiatialize empty git repo in current dir),
1:04:20 git remote add , git push :
1:07:54 git clone
1:10:33 git branch --set-upstream-to=origin/master
1:18:12 git blame .config.yml (who edit the file on which commit message by who, when) , git show (to get line changes like git diff)
1:19:22 git stash (changes saved somewhere) , git stash pop (get saved back)
1:20:46 git bisect
1:21:48 git ignore (put file name or *.extension)
This is by far the best video I've seen on git. There's so many terrible git videos on youtube 🤦🤦🤦
well, it is by MIT lecturers so no surprise there
Those terrible video tutorial probably are made for getting ads revenue, where the presenter might not even know or good at what they want to teach, and those terrible video are probably similar because they might refer to the same material from invalid or bad source (that's why valid good sources and citations are so important).
Yes but it implicitly requires that that you have previous knowledge of git.
instead of watching "so many terrible git videos" it's also possible to read the doc or do hands on tutorials
@@LesterFD Reading the docs is no substitute for videos such as this, or other deliberately didactic material. Docs are useful for reference, but do not do a good job of explaining the bigger picture, or the right mental models to use. Learning new systems is hard, because everyone reaches this point with their own thoughts and expectations, and the docs may or may not align. (Look up the video where Linux evangelizes git to the Google crowd, I think in 2007. The introducer says "no-one understands this"). One cannot memorize the entire documentation set, make all the needed logical connections, fill out the missing details, etc. For creations like git, human instruction is a big time saver. I write my own notes as I learn, to steer my mental models in the right direction. Stackexchange has been incredibly valuable. Git has its own concept of "time", of what version control means, etc. These are explained to some degree in the documentation intros, but it can be a challenge to understand. The writer of the documentation always makes some assumptions about the audience, and cannot (or will not) explain everything to its last logical detail.
This is exactly the kind of lecture on Git that I was looking for. Too many of these "crash courses" just settle on teaching you the cmds and that's it. I think it's crucial to have an intuitive understanding of what's happening internally within git. The absolute best advice I could give someone trying to climb the otherwise steep initial learning curve, is to first fully comprehend the simple data/object model: how the repository tree is represented and versions of it are maintained; and the use of SHA-1 hashes to represent both file/object content, and most importantly how a hash (as a commit) handle uniquely defines a versioned state of the repo tree. I don't believe this point can be stressed enough: without an intuitive high-level understanding of what's going on internally, the task of learning GIT degenerates into a exercise of memorizing seemingly unrelated command invocations.
agree.
this is exactly what happened with me and so I ended up, after more than 4 years in Tech, to re-learn git every month and feel the same stupidity😢
Although I would bash the git CLI api as much as the next person, I struggle to find a way to fundamentally improve it. I guess git is trying to give you really fine grained control over what happens with your repo, and it's hard to design a concise API to do that
spot on
Definitely one of the better introductions to git that I have seen. In one and a half hour, Anish succeeds in explaining the theoretical model behind git, and then goes from basic git usage over branching and merging to using remotes. And this all in 85 minutes. Well done!👍
This proves first "It's the teacher who teaches" and then "It's the student who learns ".
The way the video is articulated shows how much effort the faculty has put in. Kudos to the teacher and to all the students you finally understood GIT from its core.
you probably dont give a damn but does someone know of a method to log back into an instagram account?
I stupidly lost the password. I love any help you can give me!
@Lee Wesley instablaster =)
@Gannon Graysen I really appreciate your reply. I got to the site through google and im trying it out now.
Looks like it's gonna take quite some time so I will get back to you later when my account password hopefully is recovered.
@Gannon Graysen It did the trick and I actually got access to my account again. I'm so happy!
Thank you so much you really help me out :D
@Lee Wesley you are welcome :)
I just wanted to give a sincere thank you for uploading these lectures!
Learned many of those intricacies the hard way at work. It's really good to have someone pulling them together for you.
This really made me appreciate the genius of git and version control systems
Love the bottom to top approach of teaching this. Makes me more ready to deal with more complicated errors, and debugging
This is the best Git Tutorial I've ever seen. And I've been using Git for more than a year with very little confidence. This gives me immense confidence in handling all the changes that my team does.
One of the best Git tutorial available on YT.
These students actually ask questions I want to ask, it feels so good...
I’ve had just enough git skills to get by in the job and this video has helped fill in several missing gaps. Worth watching this video and thanks
This is the best video for git. Totally worth it. Whenever I have to recommend someone for git,I'll recommend this and say don't watch any video from TH-cam until you finish this one
have checked 10+ git tutorial on YT and this is by far the best one with no doubt
this is by far the best video on git.
I have been using Github for years but this was useful to actually know what's happening behind the commands, thank you so much!
No Joke, this is the best GIT-Video I have ever seen.
This is the best demonstration of git mostly people starts with commands and make some repos on github which is a very abstracted way of teaching git to anyone but in this demonstration they also explained the underlaying structure of git which makes it more intuitive to learn. I wonder why people start directly with commands. This is the perfect way to demonstrate the git to a beginner.
Very informative for someone who is just starting off with Git and GitHub. Thank you very much.
this video explains the core of git. it is really really good
All i can say is wow. Wanted to skip over this as i know a little about git but the way you explained the inner workings i really don't see how i can go wrong ever. Great foundation to start with look forward to re watching and studying this video and going thru the notes. Thanks!!!
I have been using git for a while, but I found this lecture to be very insightful about git internal data structure. That pseudocode was great.
thank you so much for upload this video, I just share it with my students and next time I will start to explain GIT from the model!
This long-time git user learned something new about git today. Kudos!
Great lecture. The first 25 minutes is an excellent example of a systems design interview question :')
The video suggested on my TH-cam and I wonder why but I ended up seeing it complete. First time I don't curse TH-cam for random recommendations.
I started getting agricultural automation, beginner rollerskating and "electro swing" dancers... go figure. Cool tho, watched a few
It was a unique lecture, you didn't just do commands like others but you explain the data model of git and things behind it.
Thank you for this really missing things.
Wish I could "like" this video several times... Thank you for this training!
What are your favorite commands from this lecture? I found all the best stuff to be in the last 10 minutes. My favorites are:
*git add -p * (interactively stage changed hunks of a file rather than the entire file)
*git show * (shows commit message and changes)
*git bisect* (binary search commit history to find where a bug or change happened)
At 13:35, it is said that the code of one branch could influence the behaviour of the code in another branch, and you wouldn't know before merging those branches. While this is very true, it is *not* necessarily a merge conflict. It could very well be fast-forwarded (ie. the 2 branches never changed the same line of code) and yet a new bug might occur. Only continuous automated tests can detect those defects, not merge conflicts.
Used git for years, interesting to learn about the data model and the pointers.
This is gold. Perfectly explained.
11:08 I love how the arrows point in the correct way. Too many examples make the arrows point into the direction of the future. A new snapshot is based on an older one, thus the arrow should point towards the older snapshot!
Yeah, I learned that from git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell .
Some things (like git log's output) make a lot more sense when you know that each commit has pointers to its parents, but not to its children.
Either way sounds logical to me. I mean, if you think of it as kind of a family tree, arrows in the other direction makes sense.
One of the best lectures on git, thanks for sharing
How come this is so fantastic ... I'm fully impressed.
An excellent lecture on git basics, I really liked it.
This has been extremely helpful to me as a beginner. I am grateful for having access to such a great resource.
Update? :)
Thanks for adding the lecture notes!
Very useful tutorial on git especially in terms of understanding the data model, and remote interacton. Thanks !
The demonstration of branching and merging was beautiful
This lecture is pure gold. Thank you so much!!
I have been studying the pro git book but has been not efficient enough in learning. Following along the basic tasks of git with this video gives me a very speedy overview of the branching and merging. Now I feel confident to get back to the pro git book and learn the details. Thanks for the tutorial, Anish!
Make sure to also practice using git in real projects. Reading and using git is very different.
Git has never made sense to me like it does now (despite using for several years) thanks to this video. I plan to rewatch it without coding along just to further cement all this in me. Wonderful job.
I have been "using" Git for years. Struggling would be a better term. It's so bad that I'm considering getting out of software development. Had enough. Git is making my life hell. It's a massive time waster. It is completely unintuitive.
"In pseudocode this looks like ..." and proceeds to write perfectly valid python code lol.
That's why Python is so powerful for newbies.
Wuuut? Lol.
Back in the day the "pseudocode" was BASIC.
Any pseudo code is basically python
@@spicybaguette7706 No, not all pseudocode. There is C like pseudocode also.
My sincere thank you for the lectures, this is so far the best material on git.
unbelievably useful lecture. 1,5h and I can rightly call myself a beginner :)
This is the best way to start learning git.
I don't think any tutorial on git is upto this level. Thanks for detailing the commands and their actual syntax with clear understanding.
Love this lecture, have been using Git/ GitHub for years but still don't know some of the basic idea.
Brilliant Lecture! This is the best lecture about Git I've learned :D
I almost lost hope in understanding version control through git. Until i found this! Thank you very much sir
Thankyou. I finally feel like I get what's going on in git
The lecture was informative with lots of repository in depth ways to grab data efficient time saving which I really like grab a certain command and everything's there at your disposal also ,this no where near what it's capable of man god stuff
Probably the 1st university to have a course on git and GitHub
Amazing.. thank you for the upload, this really helped me a lot
This lecture is a masterpiece.
Nice presentation. I'll definitely steal a few ideas next time I train someone on git.
This was really a big pleasure to watch this nice lecture. Thank you so much.
Very good lecture. The explanations are spot on!
I don't usually comment but I had to say it. This is good content. Very Helpful!
Here's my explanation of a hash function: You input some data and the output is a hexadecimal number. If you change the input a little bit, the output will look wildly different. You can use this to confirm you have an unchanged file from a website. If I have program P and I say the hash is X, you can download it, recreate the hash and if you *don't* get X, you'll know it's an edited file.
Well known algortihms are MD5 (outdated), SHA1 (outdated, though still often used), SHA-256 (current), though there are many more algorithms.
An input/output example for SHA-256 is:
input: Hello World!
output: 7f83b1657ff1fc53b92dc18148a1d65dfc2d4b1fa3d677284addd200126d9069
input: Hello, World!
output: dffd6021bb2bd5b0af676290809ec3a53191dd81c7f70a4b28688a362182986f
As you can see, the hashes differ wildly, even though I only added a comma to the text!
Pretty much true but a hash function is defined as a function which take some data. Play with its bytes and returns a hash. Its not necessary to return a hexadecimal value. But a each input should have a unique and consistent hash.
@@ezio934 There are some relatively important details - The input data size to a hash function is arbitrary but the output size is a fixed number of bits. The algorithm should exhibit 1st preimage resistance (given y, it is difficult to find an x such that h(x) = y), 2nd preimage resistance (given x, it is difficult to find a second preimage x′ ≠ x such that h(x) = h(x′)) and collision resistance (it is computationally infeasible to find any two distinct inputs x, x′ that hash to the same output). Sadly SHA-1 Which is used by git does not have all these properties.
best intro to git ever, love that guy c:
Great content git should be taught at every university!
marvelous lecture, was perfect for my commute just now.
my university doesn't teach git or vim and this git lecture has been really helpful. also loved the vim integration with git!
There are universities that team VIM and GIT ?
why on earth would u learn vim?
i LOVE vim and neovim its like my son
Such a nice video, learnt new things. Thanks a lot, totally deserve a +1.
This is gold. Learned a lot.
Thank you so much for this lecture!! The lecturer is so awesome!!
excellent, it helped me a lot as a newbie in Git
This is awesome. I've just cloned my GitHub repo of my Qt hobby project to my laptop and commited some test changes. I think using git with the command line is better than say the Qt Creator IDE integration since the former is universal. Great introduction that successfully got me started.
professional projects do not use the console, or command line. actually, in bigger projects, with pro teams, they will force you to use git tools that show you the git flow graph. only noobs work with the console. the console is great if something messes up, but otherwise you are prone to make mistakes, you do not see your whole project and team progress, where git flow issues might have happened in the mean time, and so on. so, if you can, grab sourcetree (not those awful gui tools from github), or any git tool with a graph, and learn to use it, or else your cto or tech lead will complain. git is not rocket science. also, in a real project with potentially dozens or hundreds devs, you will never be allowed to use many git features as described in this video, regardless of whether you are a junior or senior. for instance, in many projects rebase and revert are forbidden, etc.
@@misterbeach8826 Linux kernel devs are noobs because they use git console? I think it's just a matter of preference or a project mandates tools, as you said. No harm in trying it out for a hobby project though. Clicking buttons in a GUI doesn't really teach me anything about how things work.
@@godDIEmanLIVE How's pressing buttons any different though? If you press the "Pull" button, all it does is send a "git pull" command, so I don't see how one teaches you more than the other (unless you're talking about advanced stuff).
There are two main differences (I can think of) between using the console or a GUI:
1. Like you've said, the console is universal. (Though you could argue that GUIs can also be universal, as long as they're 3rd party, such as Sourcetree.)
2. The console gives you more control. With a GUI you're basically stuck with whatever that GUI offers. Good ones, however, cover 95% of your needs (just throwing in some random number). Sometimes it doesn't cover a use case, and then you eventually want to use the console.
The advantages of a GUI are self-explanatory ("visual").
I prefer to use a GUI (if Jetbrains IDE, the integrated one, otherwise Sourcetree). Others at my workplace mostly use the console, but they occassionally use GUI features, too (e.g. when viewing the commit history of a class or method).
But yeah, I wouldn't call people who use the command line noobs. I'd argue the opposite tbh.
It's amazing, thank you for the upload
best git tutorial ever！！
Thank u! Learned a lot. Whole different picture of git now
closed captions at 16:07: [Applause]
lol
This course needs to be in every university...
or just online for free oh wait
Probably, if the universities are populated by idiots like you.
@@ThunderAppeal These lectures are from MIT.
@@jakobwachter5181 I rest my case.
@@ThunderAppeal I would be very interested to see how your pedigree absolves you from recognizing that even very intelligent people can take a lot from these lectures.
I need to show my dev team this. Lordy, they need it.
I wish I had watched this before. Thank you!
keep up the good work, really good content
3:48 Git Bisect has saved me tons of time.
good video , helped me a lot for learning python and git
Thanks a lot for this rich lecture ❤
I dont know why this in my recommendation, but thanks you very much sir.
You should review tags, signing and audits in the basic GIT lessons. It's REALLY important for developers to understand why they need to sign their code and sign their commits, not to mention carrying a proper audit across the GIT tree.
Otherwise awesome GIT lecture.
The second part is the typical professor going at his owns speed without making eye contact. I was so hopeful.
For any one learning, use git graph extension in vs code that will give a intuitive graphical view of all git commands.
Thank you!
Really good tutorial
Thanks for the lecture.
This is so good!
Very good lecture, thanks a lot.
Outrageously espectacular video
quality content, thank you.
Great video thanks for sharing it with us.
Useful tutorial for git!!
quality lecturer
Excellent Lecture
A BIG THANKS!!!🙌🙌
you can also add title on
1:02:05 for remotes
Thank you anish!!!
Very well explained !