Week Nº 26

• Let’s look at our milestones: we should have a barebones-but-complete MVP today, moving into refinement next week.

• As we move more into design, let’s “put a pin” in any additional features and/​or “bells and whistles.” Come back to these after the flow/​look/​feel is where you want it to be.

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

• 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/​extension, using it, and then what its “end” state is. Does it feel resolved/​finished?

• Don’t show visitors/​us things we can’t yet do or use. If we have to do “step 1,” don’t show us “step 2” until we’ve done the first one. (Or show them differently, or disabled.)

  This is also a way to narrow your down your logic and edge-cases! And make the design less overwhelming.

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

• In code, if your JS includes element.style.property = someValue, this is just an inline style. Let’s mind our first-semester fundamentals about where our styles live (in our external stylesheets)⁠—you probably just want to add or remove a class.

  If you want to pass a dynamic value to your stylesheet, you can set a CSS variable with element.style.setProperty('--some-variable', someValue).

• When attributing “AI” questions, be sure to properly share the conversation thread (not just copy your session URL). You can test this in an incognito window!

  Some links are also just broken? Check your attributions⁠—a reminder:

  If you cannot furnish a link to your “conversation” and questions, you cannot use the tool nor its output.

• Some of these conversation attribution links are not showing the full chat history⁠—probably because the context window is limited. We need to see it from beginning to end! Start new, shorter, more specific conversations.

  This is also a good practice to prevent LLM feedback loops, dead-end paths, and “hallucinations.”

• Generally we want to see narrower, more focused questioning⁠—that does not cede your control/​understanding to the LLM.

  Less this:

  how use JS to filter json?

  More this:

  I’m trying to use Javascript filter() to look through an array in a JSON object, but am getting this error in my console: Uncaught SyntaxError: Unexpected token ')'. Can you explain this to me? Here is my function…

Devansh will be joining us again! We’ll break up into smaller groups today:

Structure for today

• Our goal today is for you to see both instructors and both one alumni! If we’re relatively quick about things.

• Have your MVP up on your phone (or your Chrome extension loaded), ready to tap tap tap.

• With your instructors: update us on your progress from last week and what you’ll be tackling next.

• Our goal is to help identify what you need to get across the finish line in two weeks. 😲

• With your alumn: give them a brief background to your problem/​concept and then just hand it over!

• This could be more about vibes, and just some fresh UX eyes.

• We’re heading into the closing phases of your projects. Next week, you should be shifting into design and testing/​QA:

  Project Nº 5: Refinement, Polish, and Testing

• Make sure we have your links/​progress:

  Submission Form