Week 26, April 9

If All You Have Is a Hammer, Everything Looks Like a Nail

Special Guests! #

We’re joined today by two guests for our project check-ins:

Both are MPS alumni from last year!

Project Check-Ins, Part III #

…or is it four? Either way, same groups again!

Group 1

Mia, Amy, Hye Lynn, Jonathan, Shambhavi, Yuting, Bhakti

Group 2

Mika, Inji, Vee, Devansh, Jenny, Ziwei, Jolyn

Group 3

Rice, Rayana, Nadia, Huijie, Hannah, Irene, Jennifer

Group 4

Amely, Yaxuan, Ishani, Emma, Opal, Iris, Bee

More Overall Notes #

  • So we’ve noticed some continued, blanket/en-masse copy/pastin’—this despite our ongoing previous conversations around attribution.

    We don’t want grades to be why any of us does anything—but will say that ignoring our policies (and specific warnings) and plagiarizing your final project will result in a failing grade.

    When we open up your JS—do you understand what is going on? Are you demonstrating that, in your your use and comments? If the answer is no, don’t submit it until you do.

  • Consider the “storytelling” of your project—(good) stories have a start, middle, and an end. As we move more into your design, think of someone coming to your site, using it, and then what its “end” state is.

  • Don’t show us things we can’t yet do/use. If we have to do “step 1,” don’t show us “step 2” until I’ve done what we need to first. (Or show them diffferently, or disabled.) This is also a way to narrow your edge-cases! And make the design less overwhelming.

    Also affordances—what does this thing do? Make it obvious!

  • We need to move to visual design for next week—so let’s “put a pin” in any additional features and/or “bells and whistles.” Come back to these after the look/feel is where you want it to be.

    If your core functionality isn’t there yet, we’re behind—and that needs to come first to allow you to move to visuals! Two weeks!

For Next Week #