How To Learn Git In 2023
2024 ж. 22 Мам.
30 428 Рет қаралды
Do I need to know git? Is it different than GitHub? Git seems confusing and poorly made. Why would I need to know it? I know the basics of git. Is that enough? These are commonly asked questions. If you are a developer or an aspiring developer, you absolutely need to know git. If you want to get a job as a developer, you will almost certainly need to be skilled with git.
In this video, I will address why it is essential to know git or learn it in 2023. I will then walk you through the order to learn git in, how to learn it more effectively, and how to do so easily. I will also share with you a set of tips and tricks to learning git.
Full Training Courses: IAmTimCorey.com
Mailing List: signup.iamtimcorey.com/
This kind of roadmap/goals/advice videos are fantastic! Keep them up! Fantastic content! Looking forward to some Domain Driven Design content sometime in the future! Happy new year!
I am glad it was so helpful.
Really enjoying your "how to learn" set of videos. Gives a good overview of concepts that may have slipped through the cracks for folks who may even be already experienced with something.
Thank you!
Just completed your course git start to finish. Worth every penny! Still referring to it as a reference tool. We’ll done!
I am glad it was helpful.
Thanks Tim, one of your videos on git got me started with it, makes life so much easier. One more tip for the list - when learning git on command line, it's worth making a new repo as a sandbox each time you want to test a new command. It's hard to lose work once it's in git but a new repo gives you another safety net (and added practice of creating and initialising new repos).
I would definitely recommend working with sample code or something else that you don't worry about losing. I never recommend testing new things in production.
@@IAmTimCorey absolutely, this was mainly just me recalling the revelation my less experienced self had when he learned how easy it was to make new git repos for testing purposes - there's no excuse for not practicing.
Brilliant video, thanks very much Tim
You are welcome.
I (a paying member) had suggested, through your suggestion website, to make a video on how to use Git through Visual Studio (with best practices) - as opposed via command line. I feel like this would be very helpful.
Thanks for adding it to the suggestion site.
I have 20 years in too…sometimes I learn something new from your videos, sometimes I don’t. But I still watch. I also send a lot of your videos to junior devs that work with me. Thanks for everything.
I appreciate that!
Hi. Just wondering if there is a reason your course does not include Visual Studio as a client? Is it more difficult than the others? Also, When using TFS with git, can you still use a command line?
That’s very useful, thanks a lot. Any chance you are doing the same quick overview regarding every brick of c# development? Like docker, azure, asp etc?
More are coming.
I concur, you just have to learn it. I set up a gitea server on an old machine and am forcing myself to use Git for my projects so I have at least medium familiarity with it.
Excellent!
Love you Tim ❤️
Thanks!
Please forgive my measly donation. thank you and have a peaceful 2023.
Thank you! I really appreciate it.
I'm not a developer, but I'm curious: Can Git (or something like It) be applied to projects totally separate from coding? As an example, I sometimes create/develop song arrangements. In the process, I may try many different versions with different key signatures, different combinations of instruments, different rhythmic feels, etc. Basically, I'm wondering if the principles of versioning can be generalized for other, unrelated purposes, sort of the way generic methods in C# take specific algorithms, etc. and generalize them. Any thoughts?
Absolutely. Git is just a way to track changes in files. It does best with text-type files, but it can be used for change tracking on any files. Governments use Git to track changes in government documents.
I actually have a private git repo just for notes/resumes stuff like that makes it super easy if you get a new computer or what have you
I also would suggest you to study Git Internals. It would be so much easier for you to understand how Git works when you know the mechanism and the concepts behind it. The official Git documentation has a chapter called *Git Internals.* And there's also a great course on PluralSight called *How Git Works* by Paolo Perrotta P.S. If you think that Git commits contain code diffs, then the Git Internals chapter is for you. P.P.S. Thanks Tim for your work.
Thanks for sharing.
I use Fossil (SCM) instead of Git for my hobby projects. Fossil is developed by D. Richard Hipp and used for maintenance of SQLite. The best part is that wiki, forum, ticket as well as a GUI is included. Fossil is like Git + GitHub in that sense, but all in one single EXE-file. The (CLI) commands are very similar to Git but is intended to be used by teams that know each other and everything is stored for history (rebase is not an option...).
That's fine to do as long as you realize it isn't really preparing you to work at a job. If you aren't looking to get a job in software development, it isn't a problem.
I actually found if there are merge conflicts, then a person is forced to start over again unfortunately. I had cases where if I did not do old fashioned backups first, I would have been out of luck of being able to push any more changes. That is actually a bug of git.
I would HIGHLY recommend you learn how to resolve merge conflicts. If they cause you to start over, you are running away from the problem instead of learning how to solve it. That means you will run away for the rest of your life. That's not a healthy way to develop. And no, this is not a bug in Git. It is a bug in your understanding of how to use Git. Merge conflicts are going to happen. You can't be scared of them.
Merge conflicts are very normal specially in a large project. why would you think it's a bug lol.
I both use Git CLI(usually from VS Code) and GitKraken. and i don't single out one of them. next video opinion: versioning (minor, major)
👍
I hate tutorials with to much talking, but I found this soothing
Great!
Source Control and pinning versions is a life saver. Once you know, you know. 🤣
lol. I get that.
My biggest hurdle with git is the command structure. There is no logic to it. You just have to remember them. And the error messages are ____. And yes, git is a must have knowledge for sure.
Give it time and work through understanding what is happening. When you do, the command structures make much more sense, and the error messages start to make sense as well.
Should you do the Git course before the C# course?
Probably not, but it is ok either way. If you do C# first, you will have something to do with source control when you learn it.
Would you have suggested that for learning steps number 3 that a person actually create their own git app. In that case, you have the best of both worlds and you can do exactly what you want for the app.
U
If you want to try to create a little demo app to do that, that's fine. However, it isn't something I recommend because there will be a lot of wasted time fiddling with trying to get the UI right, etc. that won't be focused on learning Git.
Hello, dear tim, English subtitles are not active for me. English is not my native language, if you can enable it so that I can understand the video better . thanks and you are perfect !💯💯💯❤❤❤❤
Try refreshing the video. They are there and enabled. KZhead automatically adds English captions to all of my videos. I don't really have any control over them and I never turn them off. The only time they should be missing is if KZhead is having a problem.
@@IAmTimCorey ❤🔥❤🔥❤🔥❤🔥✌
I migrate from subversion (TortoiseSVN) to GIT (TortoiseGIT) years ago.
Sounds like you had a good plan. Keeping the same GUI vendor probably made it easier.
Hey 💪💪
👍
Short: practice with commands. Just do it!
Absolutely.
Git's one of those things that's technically supposed to be better but we've had so many issues with GIT that we never had with other Source Code Repositories. I think it's more of a Source Code Suppository 😂
It takes learning it to really understand how to use it. Otherwise, when you get into trouble, you feel overwhelmed.
@@IAmTimCorey I agree, it's extremely important to know the difference between, say, checkout, revert, and reset hard. It's dangerous to use without knowing how it works. I felt a lot more comfortable with Soucesafe, Vault, and Kiln.
"It seems poorly made." 😆 Understatement of 2023
The good news is that once you understand it, you will realize it is actually brilliant and incredibly well made.
Please make a .NET Maui Course :)
Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
Typically a "Tips & Tricks" video will include a walk-through, a demonstration of commands, and live examples that the viewer can emulate by typing along, not a pep talk about what and what not to do (although that's appreciated as well).
Not all tips and tricks are the same.
@@IAmTimCorey Still appreciate & love the content, thx. Keep it up..
a software company that does not use git is a gargantuan red flag.
In today's market? Definitely.