When you finish TeamTreehouse's entire Swift course, what skills can I put on resume my resume?

I wouldn't use the apps from the course as portfolio pieces either. All that proves is that you can follow instructions well. Take the principles from the videos and create your own apps.

After completing the entire Swift course, will I know enough and be able to say that when applying to Jr. iOS Developer positions in the future?

Not meaning to sound rude, but why have so many courses and quizzes on this site if all the people who complete the tutorials will not be able to get a job (skill competence wise)? By learning all the material on this site, what skills do I develop and what can I be confident to say to future employers after finishing this course?

Thank you for your great insight Dominic Bryan!

You will know many of the fundamental skills needed for a Jr. dev but that doesn't mean you have the experience necessary. You also need to consider that with Swift being brand new it would be hard to find someone willing to hire a person who only knows Swift unless you're looking for consulting jobs starting apps from scratch. Any other iOS job is going to rely heavily on knowledge of Objective-C. Most iOS jobs will mean inheriting a legacy code base full of Objective-C. The other thing that you didn't list which is more important than the tools is problem solving. Problem solving skills in the context of coding are something that take a while to develop (no pun intended). The more code you write the better you get at problem solving.

The courses and quizzes on this site aren't meant to be the end point. They are to teach you the basics so that you can apply them to your own apps and build experience from there. Come up with an app idea and build it. Then do it again and again. That said, if you have one killer app instead of several small apps, that might be enough to impress potential employers.

I agree with Patrick Cooney 's points, also when I say use your apps you build on the course in your portfolio try adapt them, change them, build something better with a base you built from this course. I also agree with Patrick's view on Jr.Dev position, at least for the next couple of years you are very unlikely to be hired with just Swift skills, learning Objective-C will be very helpful.

You don't sound rude, when you are committing time and money to learn from somewhere such as treehouse its final to get the details and be skeptical. As myself and patrick mentioned look at treehouse as laying down the basics with some certain difficult skills built in (i.e. Grand Central Dispatch, multi threading), and also remember treehouse's growing forum community and video library for new content to give you something else to work with.

Also its hard to really represent skills by jsut typing a list of them out, its all well and good writing down loads of skills but as mentioned before, building a few apps that use these skills is much more beneficial to you. What I did was take the apps I built from the Swift track and changed them and add new things to advance my skills and learn others. Then you can include them in your portfolio :)

Dom

Patrick Cooney and Dominic Bryan Thank you for your insight, I really appreciate it.

I know this question has been asked a trillion times and I might sound like a broken record at this point, but I have a year left of school and my brain is convinced that I should ignore Obj-C and go all in for Swift. My brain is convinced that Swift will have a job market in one year. I feel that if I learn Obj-C now, I will get a job, but the time will come where I have to dedicate time to learning Swift and I'll probably drop Obj-C after using it for a couple years.

Do you think it's naive to learn everything about Swift for about a year while ignoring Obj-C completely until I graduate (approx 1 year)? My brain thinks long term (probably need to work on more problem solving for long term..), but how do I decide that my thought process has any merit to it or if know if it's just wishful thinking? I've always had a great ability for making wrong decisions and I fear that this may be one of them.

Hope you understand my fear of trusting my self-judgement.

This may sound harsh but to be honest — yes 100% naive. See this answer I posted just yesterday. One of Apple's own Swift documentation engineers told myself and another guy at one of the WWDC labs that Objective-C will be around for a long, long time.

That said if you only ever plan to make your own apps for sale in the app store or you plan to freelance making apps for other non-technical people, you may be able to get away with Swift only.

Thank you Patrick Cooney, that is what my mind needed to hear in order to be convinced. If Apple's own Swift documentation engineer says so, I don't know who else who would have more credibility than him.

As a beginner in programming, is it harder to learn Obj-C than Swift? The pointers and brackets are very daunting and scary. Please let me know your thoughts! Thank you so much.