Teach unreachable code and scope in separate lessons for pyramid project about freecodecamp

[lasjorg]

I agree, it seems like an odd choice.

Unreachable code and variable scope should be taught separately.

[jdwilkin4]

@naomi-lgbt or @Ksound22 ?

Are either of you free to make these updates?

I don't want to open a PR right before I go on vacation.

Thanks 👍

[hbar1st]

ugh, I just saw step 52. I don't understand why step 51 would -implicitly- suggest that a person should create a new variable after the return only to point it out as wrong in the next step. step 51 should show us that a 'correct' declaration of the variable in a local scope will result in a ref. error when the variable is referenced beyond that scope.

As for teaching people not to put code after the return, that should be a -separate- and -unrelated- step in this case.

on the other hand, step 51 could -explicitly- tell people to put the new line of code after the return only to point out it is incorrect in step 52. At least this way, if a person knows enough to type it in correctly, step 51 could fail and make them type it into the wrong spot? (or just scratch this and take my original suggestion of fixing step 51 and teaching about not writing code after returns separately)

[Ksound22]

@naomi-lgbt or @Ksound22 ?

Are either of you free to make these updates?

I don't want to open a PR right before I go on vacation.

Thanks 👍

Can we open it up for contribution?

[naomi-lgbt]

I'd prefer to see the instructions updated to specify putting the variable after the return - I think it's valuable information to teach.

[lasjorg]

This is the first time campers will be taught about variable scope. They may have coded for less than half a day.

Adding unreachable code as part of teaching variable scope can muddy the water for the learner, where they may end up making a correlation between the two that doesn't exist.

I would suggest we split it up into separate steps that focus on each topic.

[naomi-lgbt]

I could work with that, yes