Week 8 – Unusual Switch

Introduction:

The NYU library at peak hours , especially during the midterm week, turns into a Sunday bazaar with students pulling all nighters and some attending just for the vibes. It has been the case, that the number of students wanting to study always exceeds the number of study desks available. To address this, the library administration devised a policy – 25 minutes of unattended desk would result in transfer of that study place to another student. Many students toss in there belongings and go away. While the desk is not being used, it ends up not being utilized for studying. This way of booking and occupying places, is not only selfish but unethical. To address this issue, I wanted to resort to ‘out of the box thinking’. This is where I found a switch mechanism, apparently an usual one more befitting!

Working:

In order to be the switch to be unusual, it cannot be operated by hand. One of the indicators could have been the desk, but then I realized, that the chairs can be even more useful in the sense that it is definite that you have to sit down to work, compared to putting pressure over the desk with your items. Hence, as shown in the sketch, I utilized the pressure sensor, which has inverse relationship between its resistance and pressure applied onto its plate. Pressure decrease increases resistance. I added two leds, with one connected to pin-8 being red – indicating that the seat is occupied, and the other one connected to pin-12 indicating that the seat/workplace is free. The 10k resistors help prevent LEDs from burning and third resistor is connected to the pressure plate, to ground unnecessary voltage flux by the plate to 0V. This prevents anomaly and stops any non-necessary trigger sent over to A0 input. Since digitalRead had to be used, the simple ON or OFF state from the sensor was extracted and the state was sent over to the input ‘A0’. This input measures for 0s and 1s. When 1 detected, it triggers the logic inside the code.

Here is the schematic for the circuit:

Demo:

Code:

//alinoor

// declare variables
int sensorpin = A0;  // sensor pin
int sensor;   
// sensor readings
// LED pins
int led1 = 8;
int led2 = 12;
bool person_was_sitting; // to check if it is still in use while person away

void setup() {
  // set LED pins as outputs
  pinMode(led1,OUTPUT);
  pinMode(led2,OUTPUT);
 
  
  // initialize serial communication
  Serial.begin(9600);
}

void loop() {
  // read sensor value
  sensor = digitalRead(sensorpin);
  // print sensor value
  Serial.println(sensor);
  // turn on the red led and keep it on until the person is pressing against it
  // against it or its been 25 minutes since the last press.
  
  if(sensor>0){
    digitalWrite(led2,LOW);  //green led turns off
    digitalWrite(led1,HIGH); //red led turns on
    person_was_sitting = true;
  
  }
  else if(sensor < 1 && person_was_sitting == true){ //checks out only if now seat is idle and person is away for less than 25 min
  		digitalWrite(led1,HIGH);
    	delay (1500000); // delay for 25 minutes
        digitalWrite(led1,LOW); // red led turns off
    	digitalWrite(led2,HIGH); //green LED turns on
    	person_was_sitting = false;
    	

  }
 
}

The code is pretty much self-explanatory with the aid of the comments. To further explain the logic, the two LEDs are connected to pin 8 and 12. The sensor value store the digitalRead value measured for input to A0 pin. That value, either 0 or 1 (printed inside serial monitor as well for debugging), is used in if-else condition to perform certain task. The delay in else is in milliseconds equivalent of 25 minutes. For debugging 5000 millisecond was used which is equivalent to 5 seconds. If the sensor returns 1, bright red LED lights up to show ‘occupied’. It also sets the state of ‘person_was_sitting’ to true. When person no longer sitting, then else-if triggers and checks for both conditions. In the case that its been more than 25 minutes, and there hasn’t been any one sitting on the chair, then else-if isn’t checked for, and it continues to power the green LED. However, if a person just left, then a delay of 25 minutes is set in place, after which red light is turned off and the green one is toggled.

Future Improvements:

Potentially a brighter LED coupled with weight sensor to make it fool-proof. Students can swap chairs to prolong booking, which in my opinion would self-contradict their on idea of staying away from desk as they will have to comeback to swap again, but even then, adding in weight sensor can help monitor and record for previous weight. If someone else sits to prolong or to takeover someones space, an added buzzer can beep and notify the librarian of such act.

Week 8 – Reading Reflection

Her Code Got Humans On The Moon – And Invented Software Itself:

The story of Margaret Hamilton not only serves as great source of inspiration for woman in tech. but also to those who tend to walk a different path than the others. What was considered minute, soon ended up becoming center of attention as software oriented approach after the apparent success of Apollo launch, was placed emphasize on, and towards the implementation of  software centric system. A mother whose intention was to serve her family first, and make a difference is commendable; however in addition to the heart touching story, what caught my attention was the stubbornness. Sometimes its ok to believe in yourself and be stubborn. Had it not been for her toying around and discovering the potential problem with the simulator regarding the P01 switch control, maybe they wouldn’t have been able to find a fix within 9-hours. This taught me the importance of putting things to the test, and always opting for a back-up, rather than putting things to luck. A good system always has back-up incase of failure. In general, I found a confidence booster through this story of hers, and made me realize missed venues where I could have had been a trend setter instead of being a follower. This class allows me to build by will, and it is what I want to utilize to break and make just like Margaret!

Attractive things Work Better:

The reading discusses the universal cognitive bias where attractive items are interpreted as easy to use. Intelligently designed products allow producers to veil the flaws behind the curtain of attractiveness that products imposes onto its operators. In addition, that veil not only covers over the flaws, but also does the same to hide stressful, bottle-neck, and irritating situations as per what was described in the reading.  As mentioned in the reading,  ”pleasurable aspects of the design will make them more tolerant of difficulties and problems in the interface”. Come to think of it, I completely agree with this. Computers, despite complex algorithmic runtimes and clock-timings coupled with rising edges to get the minimal task carried out to a human mind may seem stressful. For those who develop, not so much so, but even then to process everything in our short term memory, can overwhelm any of the mind on the planet earth. Even its creator’s. Therefore we interact with what’s on the front-end. Even then, the interface differs. This is where I noticed contrast between iOS and Android operating systems. Both are very well capable, however, the minimalistic flat icon layout of iOS seems so clean and smooth, that we end up blaming android as a flawed system, even though both considerably have their own downsides. Moving away from non-tangible to tangible, the minimalistic aluminum body of Apple’s products make them pleasing to eyes and touch, despite the heaps missing array of sensors and functionalities that you can find on a 200$ android phone. To make my point clear, there is preference for both products, but Apple manages to hide its downsides with better design philosophy.  The reading does argue ‘Beyond Beauty’, and to that I think ‘reliability’ is the word I would reply back with. Not just the functionality, but a reliable functionality is also a core component, without which the age of product would short live, and its beauty would lead it to be decorated  on a shelf. Personally relating to it, my Parker ballpoint, after running out of ink, became of no such use. Nonetheless, I enjoyed the reading and believe, something reliable, functional, and soothing for the eye makes for a good product.

Week 8 – Reading Response

Attractive things work better.

I loved the article as it speaks on something very relatable and significant in the Design world and that is the intersection of design and beauty. I never really gave it much thought but after reading the article I now see this evident in my life too and that of friends around me. I appreciate how Norman categorised how affect impacts design and behaviour. In terms of behaviour, he explains how affect regulates how well we can solve problems and perform tasks. For instance, I find myself more motivated to handwrite when I have an aesthetically pleasing pen or pencil and the opposite is also true. In terms of design, affect impacts how easy it is to learn how to use an item. My takeaway from the reading is that designers should strive to strike a balance between optimum usability and also the appealing nature of their designs. 

Her code got humans on the moon

Such an amazing piece of writing highlighting the outstanding contribution of Margaret Hamilton in the development of software Engineering. There are so many lessons to learn from this writing but what stood out to me is the passion and sheer determination of Hamilton to push beyond the ordinary and uncover the complex technological milestones with so many odds stacked against her. I found it inspiring how she paid keen attention to the possible crash of code and was ready to solve it despite the skepticism she received from NASA. Had she not been that assertive, who knows what would have happened to the space explorers. On a broader scale I appreciate how the Apollo space program revolutionized both computing history and space exploration.So many insights to take on in life from the reading —encouraging me to push boundaries, embrace innovation, and persevere through challenges in any field.

 

Week 8 – Reading Response

Attractive Design

I  found the example of the three teapots particularly interesting because it shows how different designs serve different purposes.  The author describes one of the teapots as being deliberately unusable, the other more aesthetically pleasing, and the last one being practical and well thought out. Yet, he uses all of them at different times, proving that design is situational. This made me reflect on my own experiences, there are times when I  am most liekly to prioritize efficiency, but other times I would like to appreciate beauty or novelty in design. Essentially,  it’s not about a single “best” design but rather the right design for the right moment.

Her Code Got Humans on the Moon

Reading about Margaret Hamilton’s contributions really gave me a new perspective on software design and reliability. I had never thought about how early software engineering had to account for human error in such high-stakes environments. This made me think about how much of today’s UI/UX design is centered around the same kind of principles and ideas Hamilton had. In interactive systems, we rely on clear, intuitive design to prevent mistakes, just like the Apollo software had to ensure astronauts couldn’t accidentally erase critical data. Her work really highlighted the idea that good software isn’t just about writing code but also  about anticipating how users will interact with it and designing systems that are both strong and intuitive to use.

week 8- reading response

Emotion and Design, by Don Norman:

This reading made me think about how emotions affect how we interact with objects. Norman explains that people don’t just want things to work, they want them to look and feel good too. I never realized how much my own emotions influence my experience with products. Even if something is not perfectly functional, I might still like it because it looks nice or makes me feel good. It shows that good design is about balance, not just usability but also beauty.

Her Code Got Humans on the Moon, by Robert McMillan:

Her story is inspiring because it highlights how crucial software is, even in something as big as landing on the moon. It’s interesting to see how her careful programming helped avoid disaster during Apollo 11. What stood out to me most was how she had to prove herself in a male-dominated field, yet her work shaped modern software engineering. It made me appreciate how much behind-the-scenes effort goes into technological breakthroughs

week 8- unusual switch

Concept:

I created this project because I often find myself unsure whether the fridge is fully closed. Sometimes, the door looks shut, but it’s actually slightly open. Other times, I forget if I closed it at all. To solve this, I designed a simple circuit using two pieces of foil as a switch. When the fridge door is completely closed, the foil pieces touch, completing the circuit and lighting up a bulb. If the door is open, the circuit breaks, and the bulb stays off. This way, I can quickly tell if the fridge is properly closed, preventing food from spoiling.

Code:

void setup() {
  pinMode(11, OUTPUT);
  pinMode(A2, INPUT);
}

void loop() {

  int switchPosition = digitalRead(A2);

  if (switchPosition == HIGH) {
    digitalWrite(11, HIGH);   // turn the LED on (HIGH is the voltage level)
  } else  {
    digitalWrite(11, LOW);    // turn the LED off by making the voltage LOW
  }
}

 

video: 

(I used my foot I promise)

video

Reflection and improvements:

Looking back at my project, I realize that while it works, it’s quite simple and could be improved. The basic foil switch effectively indicates whether the fridge is closed, but it doesn’t provide additional details, like how long the door has been open. I could have added more features, such as a timer that sounds an alarm if the fridge stays open too long or a small screen displaying a warning message. Adding these functions will make it more interactive.

Reading Reflection – Week#8

The first reading, “Attractive things work better” has changed one of the most important beliefs for me in the importance of beauty, as well as emphasized the importance of design for me. I don’t think I was fully convinced by previous readings that beauty was as important as utility. However,  it is through this reading that I had the thought that beauty could improve mood, and therefore, help people to be more relaxed and be in positive affect, which could be the type of affect needed at the time as it increases “the tolerance for minor difficulties and blockages.” I also felt an emphasis on the importance of design, through a very possible example whereby a person in anxiety, in flight mode, running away from danger as urgently as possible, could respond to a door that wouldn’t open after pushing. People could react by kicking harder and pushing harder, but this doesn’t solve the problem. However, if people were more relaxed, they may have slightly different though to pull the door instead. This example shows how design could be important to help save lives. Thus, a key takeaway for me is that the principles of human-centered design are especially important in stressful situations. The implication is that designs intended for stressful situations must pay attention to matching the needs of the users, to make actions salient and easy to apply.

What stood out to me from second reading, “Her Code Got Humans to the Moon” are: first, the valuableness of code in allowing humans to go to the moon, or save lives, and much more; second, significance of not ignoring a danger as a possibility; third, the importance of an error detection and handling process. In particular, it was striking that when the Apollo software realized it didn’t have enough room to do all that it was doing, it went through its error detection process and simply focused on the highest priority. This was something I wanted to apply to my work as well.

Week 8 – Reading response

Attractive things work better

This reading talked about how people tend to ignore some usability flaws if the design of the object is visually appealing. I found this very interesting as I have never though of design to be such a powerful tool. And the craziest part about this reading was that it made me realize we all do it without thinking about it. For example, me personally, and I believe many of people reading this tend to grab an article which packaging looks better when buying stuff. For some reason, better looking packaging and elegant design is either associated with good quality or we just tend to look past quality flaws because of the nice design.  This opened my eyes on the world of design and made me realize its importance, in the future I will try to give more importance to good design into my projects.

Her code got humans on the moon

Reading about Margaret Hamilton’s contributions to the Apollo missions really opened my eyes to how fundamental her work was, not just for the success of the Moon landing, but for the very concept of software engineering as we know it today. I had heard her name before, but I didn’t realize the extent of her leadership or how groundbreaking her work was in an era when software development wasn’t even taken seriously as an engineering field. What especially struck me was how she was thinking ahead, not just about what the computer should do, but about how humans might make mistakes and how the system should respond. When the exact scenario she predicted actually happened, it was her forward-thinking code that saved the mission. That moment really highlighted how her ideas were undervalued, not because they were wrong, but because of assumptions about who gets to be “right” in technical spaces.

Week 8 – Unusual Switch

 

Week 8 – Unusual Switch

For this assignment, I had a hard time coming up with an unusual switch that didn’t require the use of hands. Eventually, I started thinking about switches that would actually be useful, something that I would genuinely want to use. That’s when I came up with the idea of creating a switch connected to a “shoe” that lights up an LED when you step on it or put it on, and turns off when you take it off. This idea came from the countless times I’ve woken up in the middle of the night or early in the morning and wished I had a light source that would guide me without stumbling around for a switch in the dark.

I started by gathering the materials I needed: 

  • Arduino 
  • Breadboard 
  • Wires 
  • Resistor 
  • LED 
  • Cardboard 
  • Aluminum
  • Sponge 
  • Tape 
  • Scissors  

I started by cutting out a piece of cardboard in the shape of a shoe, then cut two smaller cardboard pieces to act as the soles. I wrapped each sole in aluminum foil and built a sandwich-like structure. → Taped the first aluminum sole to the base of the shoe

→ Placed a sponge layer over it as a barrier

→ Placed the second foil-wrapped sole on top

 

The sponge was necessary as it acts like a spacer that keeps the two foil layers apart unless pressure is applied (someone steps on it). When someone steps on the shoe, the pressure compresses the sponge, which allows the two foil layers to touch and complete a circuit.

After that, I set up the arduino and breadboard by starting off with what we have done in class. First, I made sure that the LED is connected to a digital output pin (pin 13) instead of directly to 5V. Then I added a wire to the bottom foil and connected it to GND and added another wire to the top foil and connected it to Digital Pin 2. Lastly I updated my code, and made sure to print in order to test the output, (0 = foot pressed→LED ON, 1 = no contact → LED OFF). 

Link to photos of the process

Link to final video demonstration

 

 

 

Reading Response:

“Attractive Things Work Better” – Don Norman
Norman argues that attractive designs aren’t just superficial, but they actually improve usability. He mentions that when users find something aesthetically pleasing, they are a lot more likely to feel positive, be more creative, and continue problem-solving. However, he counters this emotional response with the logical-functional approach to usability, signifying that a good product needs to incorporate both usability and aesthetics.

He notes the psychological perspective, where he mentions the connection between emotional design and better problem-solving. This supports the idea that positive emotions lead to better cognitive performance. Additionally, his perspective encourages a switch from function-first design to a more holistic perspective where aesthetics and usability are interdependent. This idea has a significant influence on product design, branding, and architecture, proposing that the way something looks may influence not simply preference, but also performance and satisfaction.

“Her Code Got Humans On The Moon — And Invented Software Itself” – Robert McMillan

This article highlights Margaret Hamilton, a pioneering software engineer with her work at NASA during the Apollo missions in the 1960s being necessary to landing humans on the moon. She was the main developer of on-board flight software for the Apollo program at MIT’s Instrumentation Laboratory. She not only created the term “software engineering”,  but also helped set it up as a well-respected discipline. One of her most memorable moments was during Apollo 11 because her code was able to prevent a mission abort due to an overload in the spacecraft’s computer system. Due to her team’s powerful software design, she was able to ensure mission success regardless of unexpected errors.

Hamilton’s story is extremely impactful because her exceptional contributions were taking place during a time when both women in STEM and the concept of “software” were still unexplored. Her work was able to set the basis of modern software engineering as well as challenge gender norms. She was an extremely innovative individual who introduced various new ideas including prioritising tasks within software, which assisted in managing the Apollo computer’s limited memory. While her work was initially under appreciated, it is now commemorated as being crucial to not only the space race but also the evolution of computing. Her story highlights the significance of resilience and acknowledging the “what ifs” in technology.

Week 8 – Creative Switch

1. Concept

I was inspired by the reading on switches and pushbuttons to get creative with switches. I was especially inspired by the part about several custom switches that, when combined, turn on a light. I wanted to have a fun kind of switch, and integrating a game into the project was a good choice for that.

While I’ve been involved in constructing a circuit to play tetris a long time ago, I had the idea of adapting it so that instead of using hands to press buttons to rotate a shape, move a shape left, move a shape right, or move a shape down, the user could use their feet. It may bring an interesting experience in the way of bringing a bigger challenge for playing tetris. It could also be a fun way that engages users in the process of switching on a light through a game. It could be used in a scenario, where, for example, the light has automatically turned off after undetected vigorous motion in the room, as someone has been studying for an extended period of time, and to take a break, the person could play the tetris game using feet (while resting hands).

The switch is in the form of a pushbutton, with two shoe holders (containing aluminum foil on one side of its surface) with four ground boards (containing aluminum foil on one side of its surface). When a shoe holder comes into contact with a ground board, the switch is closed, otherwise, it should remain open.

2. Highlights

I encountered two major obstacles in the attempt to set the switches/pushbuttons to work:

  1. Initially, I planned to use copper wires to extend the connection between the alligator wires connected to the breadboard, alligator wires connected to the ground boards, and alligator wires connected to the shoe sholders. However, I realized that uncovered copper wires can come into contact with each other and disrupt the ideal circuit flow I had in mind. I decided to extend the connection with just alligator wires.
  2. Initially, I had just two shoe holders with four ground boards. I planned to have each shoe holder used for contact with a pair of ground boards. However, this posed the problem where both ground boards associated with the left shoe holder could incorrectly perform the same action on the shape (go down). Thinking that the functional, original circuit had four independent pushbuttons, I cut out the 2 shoe holders to make 4 shoe holders. I tested this and it was solved the issue!

3. Video

4. Reflection and ideas for future work or improvements

Overall, all my goals were achieved through this project: integrating a game into the switch, having several custom switches that combine to turn on a light, as well as functional switch, buzzer, potentiometer, etc. I definitely gained valuable experience in learning how to use the LCD and how to adapt circuits for purposes I would like.

I would love to integrate ideas for a switch that would involve two people and teamwork. This could be done by directly extending the current project, so that one person has the options to rotate a shape or move a shape left, while the other person has the options to move a shape right, or move a shape down. This could be a great way to help foster cooperation and further engagement with the hopefully creative switch.