ipc_class-3:

notes:

• we spoke about all design (technically) excludes people, and tom reiterated that this class is about finding your way as a designer (by asking what is our philosophy). i think, owing to the absence of absolute-rights, it might be helpful to operate via principles (see inventing on principle, by bret victor).

  this makes me want to explore this for myself: my principles as a designer.

• discussed how the computer and microcontroller operate at a baud rate, which is the number of symbols (bits / pulses) passed every second. traditionally it’s kept at 9600 for the arduino.

• every electrical thing has some charge, even when not connected. important to account for that noise. i think this is something cody frost also told me.

• spoke about state change detection, which i stumbled opon myself in ipc_experiments_week-2.

• int rolls over after a maximum, but long is for a really long number (like time).

• when making physical devices, you should think about change(s) in time.

• saw plotclock, and learnt about servo motors. the pulse of the servo is 15-20ms, which is why you add a delay of 15-20ms before another pulse is sent out.

• tom & i also spoke after class, and we discussed about a change in my approach to itp.