Name: 如何重回iOS開發 - iDev Journey² 4 (How to Get Back Into iOS Development - iDev Journey² 4)
Uploaded: 2021-01-14T10:24:29.000Z
Duration: 10 min 3 s
Description: 【看影片學英語】數萬部 YouTube 影片，搭配英漢字典即點即查，輕鬆掌握單字發音與用法，長久累積看電影不必再看字幕。

過去簡單式

I told you guys, this video is going to be about Iowa's development.

Episode four season to now I almost restarted Season two because I've been away from it for so long.

But I think it's only right toe have a continuation of the previous episodes in season two of Mind a journey because that's what we're getting back into the development of that application I've been knows deep, refreshing myself with Iowa's development in the current state of the APP, which really brings me around to the main point of this video.

And that is how to get back into Iose development after being months away.

I'm going to give you my first hand experience and doing that as well as discussed the current state of the application that I'm building in the Siri's.

But first let me address the elephant in the room, and that is why am I wearing snowboarding bibs?

It rarely snow, so when it does, we take advantage of man.

All right, So now playtime is over, the sun has set and it's time to get back to work.

And let's talk about the two simple steps that I used to refresh myself with Iowa's development.

Step one, I added, Read me files to any of my existing Iowa's projects on my get up account if they already had read me files.

Then I edited the Those read me files to match the format of all the new read me files that I'm creating, and it's really better for you to see firsthand of what I actually did.

So let's go ahead and jump to get home before we dive into the depository.

I want to have a shameless plug for myself and that is Go follow me on get hub google dot com slash first night.

Same spelling as the title of my channel, or go ahead in the Lincoln description.

It'll take you two there, make sure you open it in a new tab so you don't leave this video.

But this is where I keep all of my OS projects for you guys to check out.

You can see my code kind of download it, edit it, or you can forget, recommend a fork to me and I can integrate that into my repositories.

So that's a whole another story for another day.

Let's get into the retro calculator depository and look at my read me file.

So, as you can see in my Read me file, I have the title of my application, which is essentially the title.

I have a brief description off that application.

This is a retro themed, simple calculator IOS application, and then I state what I learned.

I learned how to write simple math operations with Swift integrate you my buttons and sounds, designed a U IE using image assets with us stack view in practice, using I'd be actions and Ivey Alice.

That's because, as you can see up here, I built this application about a year ago, but about a year ago, but uploaded this read me file about four days ago.

So you're wondering how in the world did you remember what you did in this app?

Fervor, You know, over a year being away from it?

This was a huge help refreshing myself on what I did on all of my other applications.

All these like how many applications I have here?

I can't remember what I did in all those after a year of being away from them.

I worked with core data, affection, display images and information.

What this did, it allowed me to dive back into my Iowa's applications and refresh myself, remind myself what I did in that app.

And I had a lot of Oh yeah, moments like Oh, yeah, that's what I was doing in that application or oh, yeah, that's how you use Ivy actions and Ivy outlets.

Oh, yeah, that's how you integrate sound into an application because I've already learned it.

I just need to find it in my brain and refresh myself of what I've learned previously.

All of those Oh yeah, moments is just me remembering knowledge that I previously forgot in another huge plus is having these need to read me files allow future employers or potential clients to see what the APP is all about, as well as what I learned about building the up so they know I know how to do that.

So if it's a potential employer, they see that I know how to use NS fetched results controller and I know how to use core data.

Or I know how to use how to integrate a P I with in my application like it did in my weather app or how to learn or how to use coca posit Alamo Fire.

So, basically, to recap, step one, go back into your old ass year old extra projects.

Read your code within those applications.

Look at the main dot storyboard, see how everything works and refresh yourself on that application, and I'm sure you'll have many Oh yeah, moments like I did.

I broke down my current project, the stock trading application I've been building in Season two, into smaller chunks.

I saw that I had log in authentication, for example, I found logging off the authentication within my code, saw how that worked, what else that affected with in my application and then continue to do that with other aspects of my current application.

So I had many Oh yeah, moments as well, because it's not like I'm diving into somebody else's code base, where I not really sure what's going on.

I remember integrating logging, authentication and Google authentication and trying to get Facebook authentication to work.

I remember all that now that I went back to my code, broke things down into smaller chunks and found the code and realized how it worked.

So it's essentially how you go back and work into somebody else's software.

It's basically getting hired by any existing software company in order to integrate any useful code into their code base.

You kind of have to understand that code base and a good way to do that from my experience and from others.

Experience that I've spoken with is you go back, you bring things into smaller chunks, see how they work, see what else is affected by it and then go into the next thing.

This is affected by that and kind of see how that works and what else is effect by that.

And it's just a chain reaction and you just kind of get familiar with the code base.

In my opinion, that's the easiest way I found.

But as I mentioned, it's much easier to get back into your original could base than somebody else's.

Code based because you're code base is going to remind you of how you built it, and someone else's code base is all new to you.

So basically, you're just trying to have many Oh yeah, moments as possible with Step one and Step two because all this code has been yours, you created it.

You're just going back in reminding yourself what you previously created.

And that's basically it for Step one and Step two.

That's how I got back into I was development After being away for many months, more months, then I prefer.

But luckily, I have committed myself into getting back and ties development, obviously, so I could make many more.

I did journey Season two videos to come an end season two as soon as possible because many of you know ending Season two is finishing up this application that building in season two.

So the sooner I finish up this application, the sooner Season two ends And then we can get into Season three, which is launching that on the APP store, putting my marketing plan into place and then kind of growing that into the business that I hope for it to be.

And yes, I will be doing this alongside a very busy final semester as a computer science student.

But I promise I'm going to get a CZ much.

I was development fit into this upcoming semester as possible in hopes to have a final product at most by summer.

But that's it for I don't journey Episode four If you made it this far into the video, I'm assuming you enjoyed it.

So be sure to show me that hit the like button right down there and if you really enjoyed it and hope to see future content like this, hit the subscribe button right down there.