Now, if you don't know what the series is about, it's basically me going from zero toe app, and right now we're in the learning phase.

We're taking a course on you to me, and what we're about to do is discuss a little bit about the section I just went there, which is about Get and get Hub.

Get up is an open source community where people share ideas at it, other people's codes, but they're cut out there for other people to edit and collaborate in just an open source community.

It's very good community, and I'd recommend anyone who's getting into software development to check it out.

But before we go any further, I'd liketo just point this out.

Is X Code eight is no longer beta?

It's It's actual release just happened recently, and with that, normally what I refer to like the lecture about to get into his lecture.

Three.

It's a coating warm up in loops and that that's good.

Eight.

Release caused Deb slopes toe end Maur videos to this course.

They actually added at least two to ah, lecture or two, Section two.

Right now, this is section three and two videos to section two.

So that kind of messed up my lecture account.

Luckily, and normally read out the electric title.

So if you're watching any month passed videos or maybe even miss because in the future they may add more videos, you know, previous to this one right here or Thio what we're talking about right here, it might mess up my lecture account.

So focus on the title of the lecture, not the number.

So right now we're gonna do lecture 33 coating warmup loops.

So we're gonna go to the computer and do that.

So here we have Section three, lecture, 33 swift coding warmup alternating a raise.

So our Simon is to write a function that combines to raise by alternating Lee taking elements.

For example, given the to raise ABC and Bo Romi the function to return a bough b ro see me?

So in other words, we want our first array followed by a second array with 001 one to two because the race started zero and then we want that to translate into our third array which I mean, that's basically what this is.

So I knew where to start.

I know I had toe.

I knew I had to declare to a raise with the given information inside of them.

And after that, I needed to create a function.

I need this function combined because, you know, makes sense.

We had to combine these and followed by that with ah, with the first and the second string keeping thehe race and texts.

So it all works out and we're basically putting that into one array.

So we're combining both of those by a pending the zero from the first array than the zero from the second rate than the one from the first rate than the one from the second rains.

So one until we run out.

And I had a few syntax airs here.

I was trying to figure it out.

I realized I had a spelling error in the word combined in my function, as well as a space in between the lesser than sign and the second the words second in my four in loop.

I had to take that.

I didn't realize that until I read the error message and then I also had toe make sure a right one back under where I declared a ray three had the first Colin in front of it.

The thing with this is, if we were to have the array one have a, B, C, D and E break in, it wouldn't translate the last two letters in two or a three.

So for anyone who's up for the challenge, go ahead and try to get this working with two mismatching a race.

So one array with five strings and then one array with three.

So now that we got that out of the way, we're not really gonna be coating this section.

We're really just gonna be talking about setting up getting get.

Like I stated before, Lecture 34 is next about version control.

So we'll market.

So the courses I was 10 and swift three by death slips.

Mark Price is the person who created it.

He says Always use virtually troll versus control.

Is is basically say you have, like, a word document.

We're gonna dumb it down a little bit for anyone to understand.

You have a word document and you know you have version one.

You know how you can edit it and thats save over it instead of doing that.

What you do is you edit it, edit it and you save as and you make it version two.

And then what?

You edit that one making version three star able to refer back to your previous versions instead of just, you know, over overriding one version, never being able to access that exact thing again because you may take out and development.

You may take out a line of code and replaced with something else.

But maybe you needed that other line of code.

You forgot waas.

Now you can't refer back to it if you didn't, you know, make a new version and that's where get comes in.

Get allows you to have version control.

So basically, just like a small examples, let's say have get up here in the cloud.

So what you do is you can commit to get you can pull the code from commit, edit the code, and you can push it back when you pull that code.

That code.

So the file name merges with whatever file you already have.

If it's not in sync than you know, let you know But if you already have the basis of this code and someone else had edited it, then what will happen when you pull?

It isn't emerged together.

So you will have the updated version and this will make more sense.

This video goes on so toe lecture 35 it is.

Get basics.

We started off using get in the terminal window.

And when Mark used his command line or commands, he didn't explain some of them.

So I will explain some of them.

You know, he kind of went over and as you went through the video, you could understand.

But basically, l s allows you to see what is in your current directory.

So if you say just type and l s enter and you're in, you know, debt directory, Dex desktop.

You see whatever files are on your desktop or folders or whatever it may be, C D stands for change directory and you put CD and then you have to put a directory name after that, that is within the director.

You desist.

Let's say did l s.

And you see that directory?

I'd have journeys in that when you could.

D'oh is you can say CD.

I did journey and then I'll take you to that directory, and then you can click, or you can type in l s enter again and then you will see whatever is an idea Journey folder or director director is just folder, um, in k d.

I r is make directory.

It makes sense and that you type that in you type in whatever you want to name the director's.

That's just making a folder removed.

I don't know.

I don't even know if he went over this.

I don't think he did, but I'll let you all know our m d I ars removed directory and your director has to be empty in order to do this.

So if you go and make one and right after you want to remove it, maybe you did a typo.

You didn't feel like going back and changing it.

So you just deleted it.

Make a new one.

You can do R N d I R.

And remove that director yet you have to put the directory name right after that.

Also, when you're typing in, let's say side of journey, you can type in I d E E and then hit tab, most likely as long as you don't have anything else named something similar, Uh, a little auto complete.

Whatever you're typing in and touch allows you to create a file you put touching in the filing and you want to create Instead of making a director, you're making a five.

So basically, this is just a bunch of get command.

So there's I'll put a put a list of it on the screen, you know?

So there's get in it, which is which initialize is.

You get status where when you're typing, get status.

And I say Get you see on the screen G i t.

It shows if your directory or files are tracked and get repo.

When you first make a directory, make a project that you want to push or commit to.

There we have to commit it.

You have to commit it before you're able to see the step.

Because if you type and get stabbed before you commit anything, it'll just be nothing.

You have nothing, and what you want to do is you do the get commit, uh, dash M and in whatever you want to name it.

So if you edited out a Alana code.

Just say, you know, cleared line 34 Whatever.

Whatever you want to put, I could just go over and read what each and every get command does that we went over.

But you could just pause this video in see the description.

So I just now decided that next to each of the of the git commands, I'm going to put descriptions so you can kind of see what each one does.

Lecture 36 is setting up.

Get up first, you want to sign up, forget hub and then generate an SS H key.

Basically an SS A ski allows your computer to access remote servers like get up.

So in this case, it is getting we just kind of go through the steps, Not not full on Steph.

Just kind of like we're pushing right direction because I'm getting they have a full on documentation guy documented guide where it takes you through the steps of setting up or generating your S h G.

So what you need to do is you need thio, generate your sshh key, copied the PB copy paste in terminal, and go to your get help account and add the SS H key you add, you enter the password appropriate password for it, and then you go.

So that probably wasn't very good explanation It It wasn't all that great of an explanation in the video, either.

You just have to go through the guide.

And one thing that he actually said in that he stressed before then I stressed to y'all, is that you need to learn how to read documentation.

If you're gonna be a software developer of any kind, you need to know how to go on to get hub.

Look at their clearly laid out documentation on how to do this and figure out how to do it.

You can't have someone holding your hand the whole way through.

It's just this is just not how the real world is.

Lecture 37 is get hub versus bit bucket.

So basically get hub is the open source community.

You put something on, get hub, anyone is able to see it, or you can pay, you know, X amount of dollars per month and allow up thio X amount of why amount of private repositories.

So I think if you spend like seven bucks a month you can get 55 or private repositories and pay more.

You get more, of course.

But that bucket, you're able to get up to what it was 85 I think you're able to get up to five private repositories on bit bucket.

So if you're creating that Mark said this is what he used for his professional quote.

Unquote.

What does he say?

Uh, I didn't write it down for his professional work.

So what do you know?

If you're creating something for yourself for a client, you can't just put it out or get out for anyone to see.

What you have to do is put it on a bit bucket or putting on get hub.

After paying seven bucks a month in order to keep it private, you put on that bucket and you're able to, I guess, basically do the same thing as you don't get up.

So I've never used that bucket.

He didn't really go over.

He just kind of said a bit bucket.

Use it for your private stuff because you could do a good amount for free and then get hub.

Uh, is for public lecture 38 local and remote get repose which repose the short for pa stores.

So in this lecture of what we did was we carried execute project and we created a get hub depository and pushed Argueta Project our escape project up in to get a gift.

And the way mark does it like towards beginning of the video?

He's like over here and he does this thing that I probably feels me about it Cut it out!

But it's not my course plane is a But after he does that, you know he goes a river.

After I had written it all down he goes over a way that takes like 10% of the time.

If that so, basically what you D'oh!

Let me let me see you create your ex Good project, you know?

So you already have everything set up.

You have your s s h g hooked up to your remote server on get hub which I already told you how you just go to the documentation.

You regenerate the key copy, pay all that good stuff and then what you do to create the next cut project.

Then create a repo without a read me file.

And when you don't do the read the file, they provide you steps, which it has, you know, get in it.

I think I think you know, has all those steps like you initialize it and you do all this other good stuff and then you're able to commit Pull, push.

Do whatever you need to do between your ex co project and get help.

Lecture 39.

Working through get merged conflicts and basically what it get merged.

Conflict is is where I say you have the cloud again Like we discussed earlier and coder a coder.

Excuse me, and we have could be over here.

Not really anyone, ever.

They just pretend.

And I you know, we have code up there.

I pull the curd, I end it Line 34 in this file of the code and then I push the coat back up there before I push the code back up there.

You know, editing it.

He pulled or he edited his his code on the same line 34 of the same file.

So he changed the same lines I did.

Wish in turn is really just bad communication.