Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lesson 1 Feedback #1

Open
ibirnam opened this issue Nov 14, 2019 · 0 comments
Open

Lesson 1 Feedback #1

ibirnam opened this issue Nov 14, 2019 · 0 comments

Comments

@ibirnam
Copy link
Contributor

ibirnam commented Nov 14, 2019

@amelinagzz - feedback for Variables, Types & Functions

Swift Intro: Throw an image in here so it's not just text. Swift logo is fine

Playground Sections: Put screenshots of the different sections. Make one slide per section if you can't fit them all on one slide

Swap order of Variables and Constants slides. They know what variables are, so start them with something familiar and then show the new thing that's slightly different (constants)

Variable Naming: Show an example of camel case, don't just talk about it. Show the equivalent name in Python syntax (i.e. waterBottle vs. water_bottle)

Constants: explain what the let keyword means/what it's purpose is.

Variables - Swift Playground

  • Good to have a reminder of steps they need to take in order to properly open playgrounds (install xcode, install developer tools, how to "run" a playground, etc.)
  • for Crushing the block!, don't give them the code, just tell them what to do. Make them write the code themselves so they get practice
  • To me, this is really repetitive of the stuff you went over before. I like the practical aspect of it though, so this should either go before the TT, or interleave it with the TT (like do a chapter of the activity, brief TT, repeat). Can discuss this further if you'd like

Functions: Lots of text here, break it up with a basic function image. Something like this, or something a bit more creative

We can make it more readable if we use external names: need a better example, this one isn't distinct enough to make that big a difference to students

Return Values: good question here would be to ask them what the difference between print and return is.

Function Playground the first Experiment block is referring to something that doesn't exist, and the same with the paragraph after. Needs to be fixed.

Playground Activity: Similar to the above suggestion, instead of saving all the playgrounds until the end, I would interleave them. So for example, give your TT on tuples, then give them the Tuples playground to work through, then TT on type, playground on Type to follow, etc. Mix things up to keep engagement

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant