We’ve all been there at some point, the key to becoming a programmer is to keep learning and never give up!
Those that do give up, never become one.
The the rate of your learning will depend on your level of experience, and the level of the text you are studying from.
So the data needed to find that rate for you should be based on your current rate in iOS Apprentice.
I haven’t finished iOS Apprentice yet, I’m on the 4th (final) tutorial StoreSearch, Chapter 36: URL Session.
Keep in mind that I have some experience prior to iOS Apprentice
I have taken Stanford’s iTunes iOS course, completed Apple’s Everyone Can Code series, and read Ray Wenderlich books Swift Apprentice and Core Data by Tutorials (got half way through)
My iOS Apprentice rate of learning looks like
1 BullsEye, 2 Checklists, 4 StoreSearch
I averaged 1 chapter a day because these 3 tutorials were mostly review of previously learned concepts.
3 MyLocations This tutorial is probably the most challenging in the book.
I averaged .5 of a chapter a day. It took me 2 days to complete each chapter because the
CoreLocation framework was brand new for me. But, a good majority of this tutorial built upon my previous knowledge, so I was able to get through this one relatively fast considering the vast amount of info.
- This ends up being 45 days of study for 35 chapters (I still have 7 more to go).
- It’s taken me 55 days in real time with breaks and other life commitments.
- I’ve averaged .63 of a chapter a day.
Based on that rate I should expect to finish my last 7 chapters within 11 days.
But this data is only good based on my knowledge of iOS, and technically only good based on the content, the final tutorial has been primarily review, so I expect the last 7 chapters to take me 7 days or less to complete.
I’m assuming this is Swift Apprentice? Yes, this a must read!
My Swift Apprentice rate of learning:
For Swift Apprentice, a book with only 25 chapters, I would expect a faster completion time, but that wasn’t the case!
- It took me 35 days of study for 25 chapters
- Took me 46 days in real time.
- About .5 of a chapter a day.
For the majority of the book I averaged at 1.5 chapters a day, but then there were a couple chapters that took me 2 - 4 days to be able to grasp the concepts, and required a couple days break before returning to the challenging material.
.5 of a chapter a day is a good rate for me to shoot for based on my experience level and the beginner level 1 star books I’m learning from.
No doubt this will change when I start the intermediate level 2 star tutorial books.
I guess my advice to you is keep a daily journal tracking your progress. Use it to find a rate that makes logical sense and then use that to predict your course.
For me, the value of seeing my path laid out on a year calendar helps keep me focused & motivated on the present because I know that doing the now is just as important as the end, because I’m becoming more and more a programmer with every concept learned, and chapter - tutorial - book completed.
I can clearly see that if I continue on my path I’ll eventually reach my goal, upon which I will no doubt have new goals I will be aiming for.