Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Guilherme Kunzler
1,433 PointsThink we are going too fast
Way too many concepts going on at the same time. Should break this video in one module or introduce this concepts before trying to put them in practice.
Guilherme Kunzler
1,433 PointsI think it is more the way he is conducting the class. Not so much the subject. On Amit's classes I hardly get stuck cause he has a more paused and detailed way to explain things.
I went to youtube and found this little video. He goes a bit fast but it is easy to understand where he is picking the variables from and why he is doing it.
https://www.youtube.com/watch?v=Kpwrc1PRDsg
That is what I understood.
// override func prepareForSegue(segue: UIStoryboardSegue, sender: AnyObject?) This is standard function from swift. One of those things you don't have to understand, just remember.
// if segue.identifier == "showPlaylistDetailSegueIdentifier" This conditional is not fundamental to make the thing work. All it does is to detect if there a "segue" named "showPlaylistDetail" to execute the next line of code. As we are "pushing" just one segue we don't need that. If we have more than one segue going out of that view and we would like to send different data to each different segue that would make sense to have.
//var playlistDetailViewController (INSTANCE) = segue.destinationViewController as! PlaylistDetailViewController (OF TYPE) All it does is to create an instance "playlistDetailViewController" of type "PlaylistDetailViewController" and that gives you access to all properties and methods inside the "PlaylistDetailViewController" CLASS.
//playlistDetailViewController.buttonPressLabel.text = "" As we learned on classes and structs the "." after the name of the instance reveals you access to all these properties and methods that belong to the class "PlaylistDetailViewController"
Esteban Orozco
2,191 Points+1 Pasan knows his craft, but his pace is definitely not good. I think a teacher should stick to teach an entire track. When you're getting accustomed to someone's way of teaching and suddenly it's abruptly changed, most of the time it has a detrimental effect on the students, and I can see that.
Guilherme Kunzler
1,433 PointsDon't think that happened because I moved from Amit to Pasan.
I take classes on udemi, youtube, blogs and god knows where else with people with terrible accents , so teacher contrast is not a problem.
I will try to put it in clearer words. I liked Amit because his examples were very simple, were not mixed or complicated by extra concepts and his speaking pace was easy to understand. I expected the same same from Pasan. Unfortunately, for me, he has a different way to conduct classes.
6 Answers
Esteban Orozco
2,191 PointsI also believe Pasan has to slow the pace a little, specially after watching the Swift basics with Amit.
agreatdaytocode
24,757 PointsI'd like to make a suggestion that helped me when I first started out here at TreeHouse. I understand where Guilherme and SLC are coming from. I felt the same way for the first 6 months.
This really made a big impact on how I learned, it also helped me retain a lot more information and I became more efficient at learning. It sounds simple but it works.
The Suggestion: When watching the video for the first time. Close everything out, and I mean everything. Turn off the music, close twitter, and most importantly close Xcode. Sit back and watch. If you need to watch it 2-3 times to pick up on the concept do it. Then after you have a good idea of what the video is about open up Xcode and follow along.
You will notice that in some of the videos they go back an change some of the code at the end or refactor it. If you watch the video first you will save yourself the headache of writing out the long form of the code that gets refactored later.
I hope this helps. Good luck and Happy Coding!
Anthony Albertorio
22,624 PointsDid that and still nothing. The presenter is making assumptions that down casting and up casting has been present before. "as" has not been covered either. There are a lot of gaps and he is moving too fast to explain any of them.
Guilherme Kunzler
1,433 PointsI think it comes to what you think is useful while building something.
I am a designer and to every designer takes a while to understand what less-is more really means and why doing less does not actually mean you do not have the skills to do more if you want.
So when you think about UX design it is not different. Good UX is the craft of simplification to avoid deviating focus.
I guess, swift programming is already a very complicated thing. When tailoring a class for newbies focus deviation is everything. Less external concepts you mention, bigger are the chances we will learn what the class proposes to explain.
In my opinion this is a common problem I found after I moved from Amit initial classes. I pretty much stopped watching new classes here because I have to do a lot research outside in order to understand concepts and when I find the answers outside I pretty much do not come back.
I do not have any issue with Swift or TreeHouse tool experience. I think it is great. It is more about the decision of what would be a good example, or the most simplistic way to teach a specific subject or good introduction to subjects before bringing them into the mix.
This is a diagnostic of how the class content can affect the user experience and the user retention.
Robert Fiorendino
1,964 PointsI love the idea of watching the videos once before you type everything. This is very good advice.
One other thing I do is to watch them at 75% when I'm following along. (50% is too annoying to be useful for me.)
Good luck!
Raj Ku
Courses Plus Student 2,561 PointsHey dude, Believe me Pasan is taking steps as separate as he can.. these stuff seem to be too complicated in the beginning. Watch the whole section once without practicing then apply. It's definitely gonna take you sometime to get there, the course is quit organized yet the learning curve is very steep. Another advice is to keep watching as many tutorial as you can, either here, on youtube, or courses like the ones on Udemy. Just don't give up, you'll get there.
Guilherme Kunzler
1,433 PointsHi mate. Will never give up. As I don't think Treehouse should give up improving things as well.
As we students, teachers and lessons can improve.
I think Pasan knows a lot and I do not dare to question his knowledge, but he goes a bit too fast in his videos. Pauses between sentences and thoughts will give our brains time to absorb and compute.
David Park
Courses Plus Student 2,244 PointsI want Amit back...
Dan Hall
570 PointsI know this is an old thread but I just started the Java track ... Java basics and Java Objects and am fairly lost. Never coded before and wanted to learn from the ground up but so much stuff is flying by me. I do think the tracks move way too fast and don't explain things well some of the time. I know it's a lot to learn and a lot to take in but ultimately without any prior coding experience I would have thought it would have been much more basic, slow, and exhaustive.
shaunboleh
14,970 Pointsshaunboleh
14,970 PointsIt's the same with the Objective-C videos - hardly a moment to even let me pause, have to constantly "rewind" slightly. Need some space between steps, even if it's just silence. Longer videos? More videos? Probably. Because I eventually start thinking, you know, maybe a book is a better idea as my main resource.
Ah just frustration talking. Nothing is perfect, especially my work ethic. Have to try harder.