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

General Comments #195

Open
2 of 7 tasks
ibirnam opened this issue Jan 29, 2014 · 7 comments
Open
2 of 7 tasks

General Comments #195

ibirnam opened this issue Jan 29, 2014 · 7 comments

Comments

@ibirnam
Copy link
Contributor

ibirnam commented Jan 29, 2014

I just emailed these to Peter, but comments 1 and 4 were based off of a previous version of the lab. Though why did we scrap the variables section? They need to know it before HW1, and this lab is their only chance to learn it.

  1. We should probably define (or remind them) what a script is, as its used a lot in the first page. This can be something that is added to the lab, or gone over by the TA beforehand, but just wanted to bring it up.
  2. on the If and If Else page, it would good to clarify what you mean by "temporarily". For example, you could say that a value that is stored in the "answer" variable is kept there only until the next time the ask block is called.
  3. LOVE the page on and, or, not, especially the truth tables, I'm glad they're learning this early on.
  4. This is more a suggestion, but perhaps add quiz question that has both global and script variables involved? A basic scope question would be pretty beneficial
  5. On the Practice With Complex Booleans page the 2nd bullet point I think could be reworded for clarity to say "You could write this without using your <weekend?()> block, but it would be much easier if you use it"
  6. On the same page, bullet 3 asks them to write a block we just showed them how to do on the previous page. Seems a bit redundant.
  7. This link for predicate solutions leads to a 405 page: http://peterasujan.github.io/bjc-r/cur/programming/functions/predicates/ge-soln.html
@ghost ghost assigned peterasujan Jan 29, 2014
@xtitter
Copy link
Contributor

xtitter commented Jan 29, 2014

Good comments. A few thoughts:

  1. we shouldn't call (answer) a variable, but a reporter, since it can't be set. Brian Harvey is ... adamant about this.
  2. no global variables please! Not until lab 4.

@ibirnam
Copy link
Contributor Author

ibirnam commented Jan 29, 2014

Is there a reason though that the page on variables was taken out? They need to be taught what a script variable is, at least.

@ibirnam
Copy link
Contributor Author

ibirnam commented Jan 29, 2014

also i realized my link for number 7 didnt go through, i updated it accordingly

@peterasujan
Copy link
Contributor

Is there a reason though that the page on variables was taken out? They need to be taught what a script variable is, at least.

Yeah, we're planning on teaching them when they're needed (a bit later in the lab).

@xtitter
Copy link
Contributor

xtitter commented Jan 29, 2014

Peter is going to add script variables for sure, and set. Supposed to be in lab 3. But, it seemed tacked on at the front; we wanted it integrated for students when they needed it, which is in custom-block predicates I think.

@ibirnam
Copy link
Contributor Author

ibirnam commented Jan 29, 2014

Ah ok got it, I was just confused because it jumped from the "More Complex Boolean Expressions" page right into the quiz abut script variables, but if the page explaining variables is gonna be added in, then that works out

@cycomachead
Copy link
Member

Anything left to be resolved here?

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

No branches or pull requests

4 participants