Academic Standards

Advice on writing standards from Kyle Coberly:

A trick I learned from Erin H is that your standards should never look like "Can you do this? Ok, but what about this? Nice, now what about this?" For example, you wouldn't have standards that are like "Demonstrate .push, Demonstrate .pop." No one talks about that shit that way. You might say "Demonstrate common array operations", and then enumerate each operation in the rubric. That gets to the heart of what you actually care about (doesn't change very often) while allowing some experimentation and evolution in how you measure it (can change rapidly).

I tend to go a step out from that and ask "What would a non-educator think is a discrete item?"

Literally no one would say "Ok, you know some basic JS- even arrays though?" So I scope stuff like under "basic programming proficiency" (doing basic operations with common data types). Someone very well might reasonably say something like "Ok, you've got some basic JS programming chops... have you heard of native JS array methods though?" and the answer could go either way that's a good candidate for a separate standard.