Effective use of version control is an important and useful skill for any developer working on long-lived (or even medium-lived) projects, especially if more than one developer is involved.
Git is used by many tech companies, and a public GitHub profile serves as a great portfolio for any developer. But more than that, you’ll establish an efficient programming workflow that allows you to:
In this lesson, you’ll learn about a few different types of version control systems and discover what makes Git a great version control system for programmers. You’ll also get practice using Git to view the history of an existing project.
Effective use of version control is an important and useful skill for any developer working on long-lived (or even medium-lived) projects, especially if more than one developer is involved.
In this lesson, you’ll learn about a few different types of version control systems and discover what makes Git a great version control system for programmers. You’ll also get practice using Git to view the history of an existing project.
Caroline Buckey - Before joining Udacity, Caroline worked as a Software Engineer at Quixey, a startup building a search engine for apps. While receiving her undergraduate degree from Carnegie Mellon, she was a TA for six different courses, and that same love for teaching later led her to join Udacity.
Udacity is a for-profit educational organization founded by Sebastian Thrun, David Stavens, and Mike Sokolsky offering massive open online courses (MOOCs). According to Thrun, the origin of the name Udacity comes from the company's desire to be "audacious for you, the student".
Learning a little bit of code is probably better to start with.
I'd recommend it even if you don't know any version control system (just understand why you need version control at all). It teaches mental model of git, which is immensely helpful. Instead of learning few random commands and hoping for the best, you learn what is actually happening and what you need to do to get where you want to be.
tbh, all at once. Git is way complicated, and you need to know it at many levels. How to perform the commands, what stages you're in (visual guides help here), how the internals work... Typically any one guide will focus on one side, not all of them.
Absolutely. Git is a very complicated dev tool compared to most others (you can figure out the basics of vim after 30 minutes of vimtutor - not so much with Git). You should know how to code (and from that, figure out how to use dev tools, the terminal and so on) first. 4. level 2.