iOS Development Guideline

[h1i2j3]

Steve

@sgerrard

The tutorial is also less about building apps, and more about adding transitions and other animations to a starter app. I liked 2D Animations because I was just pounding out more code and more apps and having fun with it.

Right, it sounds like I’d get more out of iOS Animations after having completed 2D & 3D books.
You’ve got me pumped for the 2D book!!

@sgerrard

iOS 11 and iOS Animations are both about learning iOS 11 as an OS, rather than learning Swift and how to design code. More like reference books, in a way.

Yeah, iOS 10 & 11 will be a mixed bag of review/solidifying learned concepts and gaining new experiences for me.
15 chapters per book means 30 apps!

@sgerrard

Core Data is good, but the subject is storing and retrieving data, which is not exactly exciting. It is a task you want to be able to do, but in my opinion only because you have to, not because you want to.

I dig Core Data, I got through half the Core Data by Tutorials book and stopped at Chapter 6: Versioning and Migration, because the second half was too advanced for me at that time.
Basically I was able to go through the motions of setting up the stack and fetching etc, but lacked understanding.

Now It’s a win because having read at least half of it prior to iOS Apprentice’s introduction of NSManagedObjectContext, NSFetchRequest<>() etc, bettered my understanding of what was going on in the iOS Apprentice chapters & Core Data in general.

Also, to be fair, this time around I had Swift Apprentice under my belt, so I instantly identified the GenericType of NSFetchRequest and plenty more.

Revisiting Core Data by Tutorials and finishing it this time around will be awesome.

@sgerrard

I do think getting brave and tinkering around on your own is crucial. You want to reach the point where if you have a good idea, you also feel like you know how to get that done.

Couldn’t agree with you more! I’ve built a few apps for myself for gaming (mainly tableViews) utilizing what I learned, and found out really quickly that following a tutorial vs making it myself was a whole different ball game.
You revisit the tutorial searching for a code example of what you want to do, and end up learning/understanding that concept & others.
Things that you thought you understood, now are understood on a new and more advanced level. You can’t get that kind of understanding by merely reading/following along, you have to experience it yourself, and figure it out for yourself to truly learn/master it.

@sgerrard

It takes a lot of practice to reach that point, so it’s good to get started on it. Even just changing little things can be satisfying.

I agree, and practicing coding is so enjoyable, I feel like I’m playing.

---

Off Topic

You helped me in functional programming before → Chapter 19 pg 415 Functional Programming (Thanks again!)
Did you master FP as you went through these books? or did you have experience with other languages centred around Functional Programming?
And what book/concept are you currently studying if you don’t mind my asking. (I’d like to follow your general path in hopes to become a better coder!)

I found this code you wrote to be beautiful!

@sgerrard

Here is my favorite version, because it comes closest to saying what you really mean:

if indexPath == nil || indexPath != IndexPath(row: 0, section: 0) {
  descriptionTextView.resignFirstResponder()
}

Cheers!
Rebecca