P2 Ideas
This form is due at 2:30pm before class on Tues, Feb 27.

First, include a reflection of the tools we've already used in class (see the lecture PDF for background context). Then, type in and rank 3 ideas in the order of how excited you would be for them. Your email is collected so you have the option to edit your responses any time. (Sometimes the best ideas come from ignoring them for a while!)
Iniciar sesión en Google para guardar lo que llevas hecho. Más información
Correo *
Name *
Tool reflection from in class
*
Think about all the tools (analog + digital) you’ve used so far in this course. Which ones were (1) most interactive, (2) made you feel like you had agency, (3) best at complimenting your existing skills, and (4) best at helping you achieve your goals? Why?
When tools worked well, why? (Familiarity? Mental models?) When tools were challenging to use, why?
Computational design tool ideas
For each idea, copy/paste and fill out the below template:
---
Tool title:
User:
Domain of use:
Problem:
Proposed computational solution:
1-5 how enthusiastic you are about doing this project idea (1 least, 5 most):
1-5 technical feasibility of this project (1 IDK how to do this at all, 5 confident I can code this):
(Optional) Other comments, insecurities, or emotions on this idea:
---

Note that the solution does not have to be fully fleshed out at all. How would you begin to approach solving this problem? What are some rough strokes of what the tool would do? Remember for technical feasibility, we'll have about 4 weeks to code the tool (from when the system diagram is due).
Idea #1
*
Idea #2
*
Idea #3
*
That's it!
We'll form groups in class on Tuesday. By the end of the day on Feb 27, you should have a group of 3-4 students, a way of contact, and a set 1 hour weekly time to meet for the rest of the semester.
Enviar
Borrar formulario
Nunca envíes contraseñas a través de Formularios de Google.
Este formulario se creó en Stanford CS & EE Departments. Denunciar abuso