Name: Git and GitHub - CS50 Beyond 2019
Uploaded: 2020-04-04T05:38:49.000Z
Duration: 1 h 5 min 59 s
Description: Thousands of YouTube videos with English-Chinese subtitles! Now you can learn to understand native speakers, expand your vocabulary, and improve your pronunciation...

Feel free to help yourself to pizza now still, if you'd like,

A bit of a change of pace this afternoon.

So we spent the morning talking about HTML and CSS,

which you had seen in CS50, but we went a little bit beyond that,

looking at other features of HTML and CSS and more modern versions of both.

What we're going to do this afternoon is take a look at Git.

If you've used Git before and you feel comfortable with it, green smiley face.

If you've never used it before, red frowny face.

A bunch of people have never used it before.

So if you've never used it before, this will be a good introduction.

Even if you have used it before, hopefully you'll

get a bit more of an understanding of it here.

Git is what we call a piece of version control software.

It's software designed to help us manage and track

If you ever go on to take future computer science classes,

or you go and work for a computer science internship,

or work in computer science industry, you will almost definitely

be using Git as your means of keeping track

And so it's good to have an understanding of it and how it works.

So today is going to be a bit of an introduction to that,

give you an opportunity to see the various features of it,

get an opportunity to practice with it hands-on later on this afternoon.

And then in the latter part of the afternoon,

we'll also take a look at SaaS, which is a way

to generate CSS code, which we'll take a look at in a moment as well.

But questions before we begin on anything from this morning,

anything about the structure of the class

or, logistics of what's going to happen this afternoon?

So we're talking about Git today, and Git

is a piece of version control software, as I mentioned.

And it's good for a number of different things.

So the first thing that Git is particularly good for

is for keeping track of changes you make to your code.

I remember when I first took CS50, I would

be working on a problem in the problem set,

and I would work and get like part of it working, but not quite.

But I'd be afraid that if I added more, I would

So I'd save a duplicate copy of the code somewhere,

make changes to another copy, and pretty soon, you

have four or five different copies of the same program that

are all slightly different, and they just

become a little bit tough to keep track of.

Maybe some of you had similar experiences, definitely

This is before I learned how to use Git, which is primarily

designed for trying to deal with problems like this, keeping

track of changes you make to your code, such that you have a full revision

history, so to speak, of all the changes you make.

So you might have initially created a file, made some changes to the file,

added a line to the file, removed a line from the file.

And Git is going to help keep track of all of those different changes we

make to the code so that we have a record of all the changes we've made.

Another thing that Git is particularly good for

is for synchronizing code between different people.

So you might imagine that you have some file

that you and a collaborator, a partner, are working together on.

Maybe it's a partner you're working on in a problem set in a class together,

or a bunch of people that you're working with on the same software project,

if you're working for the same company, for instance,

and you're sharing some file that you're working on together.

And what Git makes it easy to do is to give both you and your partner

the same version of that file, such that you can both independently be making

modifications to that file, change different parts of that file,

and then eventually synchronize them back up

together in some sort of central server, such

that you can both then get that updated version of the file, where the idea is

you can both be independently making changes to the code,

synchronize them somewhere so that you both have access to the latest version.

No more emailing, like, this is the latest version, use that one.

And then there are conflicting versions being emailed around

Git helps to just simplify that process, keep track of everything

Another thing that Git is good for is it's

good at testing changes to your code without losing

So you might have something that's working,

and you might want to add a new feature to your website, for instance.

So you might want to tackle the next part of the problem set.

But doing so might involve breaking the stuff you've already made

So what git makes it very easy to do is say,

branch off, a term that we'll explore more in just a moment.

But say, try something else for a little bit while keeping the original.

And only when we've tried it and it works and we're feeling comfortable

Subtitles ListPlay Video

Git and GitHub - CS50 Beyond 2019

access

multiple

basically

conflict