2020(S09) Lecture:week 1: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
No edit summary
 
(21 intermediate revisions by the same user not shown)
Line 21: Line 21:
Once "project runway" has launched and the winning design team has been recognized, we'll work as a class to add more ideas, questions and thoughts to this list.  
Once "project runway" has launched and the winning design team has been recognized, we'll work as a class to add more ideas, questions and thoughts to this list.  
* from 2008: ''"this was as an exercise in engineering.  We had to solve a given problem with limited time and resources, while working effectively as a team."''
* from 2008: ''"this was as an exercise in engineering.  We had to solve a given problem with limited time and resources, while working effectively as a team."''
* from 2008: ''"We ended up using my design choice because I am more stubborn. This is not a great success story in terms of teamwork, but it did produce the best plane in the class."  ''
* from 2008: ''"We ended up using my design choice because I am more stubborn. This is not a great success story in terms of teamwork, but it did produce the best plane in the class."   
*from 2009: "to give us a way to visualize a design that may seem unlikely and that may not seem like it would work''  
*from 2009: "to give us a problem we might feel is more approachable"
*from 2009: "the most complicated design isn't always the best. Simple works"
*from 2009: "how different all the plane designs are, even starting with the same materials."
*from 2009: " I think it was difficult to decide on rolls"
</div>
</div>
|}
|}


=='''Homework''' for tomorrow's studio session==
=='''Homework''' for tomorrow's studio session==
Line 39: Line 43:
=<center>Week 1 Studio</center>=
=<center>Week 1 Studio</center>=
==Part 1: <font color = blue>Wednesday matinee</font color>==
==Part 1: <font color = blue>Wednesday matinee</font color>==
'''Instructions:''' Today you will have the opportunity to watch two videos showcasing completed [http://ung.igem.org/Results iGEM projects]. "iGEM" stands for the "international Genetically Engineered Machines" competition. It is a summer-long opportunity for teams of students working at colleges and universities around the world to design and build genetically engineered machines, many of which use standard biological parts from the [http://parts.mit.edu Registry of Standard Biological Parts.] The videos will orient you to the kinds of accomplishments realized in a summer by teams of undergraduates and their advisers. <br>
'''Instructions:''' Today you will have the opportunity to watch two videos showcasing completed [http://ung.igem.org/Results iGEM projects]. "iGEM" stands for the "international Genetically Engineered Machines" competition. It is a summer-long opportunity for teams of students working at colleges and universities around the world to design and build genetically engineered machines, many of which use standard biological parts from the [http://parts.mit.edu Registry of Standard Biological Parts.] The videos will orient you to the kinds of accomplishments realized in a summer by teams of undergraduates and their advisers.  
<br>Our first featured presentation will emphasize some of the "biology" that's often present in "synthetic biology." As a class we'll watch:
===Our first feature presentation===
* the 2008 iGEM team from Heidelberg describing a genetically-engineered bacteria that will find, and kill pathogenic bacteria [http://2008.igem.org/files/video/Heidelberg.mp4 presentation video] [[Media:Heidelberg.pdf| presentation ppt]]
Our first featured presentation will emphasize some of the "biology" that's often present in "synthetic biology." As a class we'll watch:
'''Note''' that this team developed a tremendously useful website that describes both their project, their human practice work and the basic background a person might need to understand the work. If your molecular biology is rusty, you can refresh your memory [http://2008.igem.org/Team:Heidelberg/Human_Practice/Phips_the_Phage/General_Backround| here]  
* the 2008 iGEM team from Heidelberg describing a genetically-engineered bacteria that will find, and kill pathogenic bacteria [http://2008.igem.org/files/video/Heidelberg.mp4 presentation video] [[Media:Heidelberg.pdf| presentation ppt]]  
<br>In watching their project we can focus on  
<br>In watching their project we can focus on  
[[Image:Sensing.png|thumb|left| sensing]]
[[Image:Sensing.png|thumb|left| sensing]][[Image:LyticPhage.png|thumb|right| lytic phage]]
**'''cell-cell communication, sensing and chemotaxis'''
**'''cell-cell communication, sensing and chemotaxis'''
***our ppt review of these processes is [[Media:20.20(S09) review Sensing&Chemotaxis.ppt| here]]
***our ppt review of these processes is [[Media:20.20(S09) review Sensing&Chemotaxis.ppt| here]]
[[Image:LyticPhage.png|thumb|left| lytic phage]]
**'''phage life cycles, DNA transfer mechanisms and "parts"'''
**'''phage life cycles, DNA transfer mechanisms and "parts"'''
***our ppt review of these processes is [[ here]]
***our ppt review of these processes is [[Media:20.20(S09) review lambda.ppt| here]]
 
'''Note''' that this team developed a tremendously useful website that describes both their project, their human practice work and the basic background a person might need to understand the work. If your molecular biology is rusty, you can refresh your memory [http://2008.igem.org/Team:Heidelberg/Human_Practice/Phips_the_Phage/General_Backround| here]
[[Image:Collicin.png|thumb|left| colicin killing]]
===Our second feature presentation===
 
[[Image:EauD'coli.jpg|thumb|left| Eau D'coli]] Our second featured presentation will emphasize some of the "engineering" that can be accomplished in a summer by a talented group of undergrads much like yourselves. We'll listen to
<br> Our second featured presentation will emphasize some of the "engineering" that can be accomplished in
* the 2006 iGEM team from MIT describing a neat project for fine chemical synthesis [http://www.igem2006.com/presentations.htm presentation video] [[Media:IGEM2006-MIT-Powerpoint.ppt| presentation ppt]] <br>
* the 2006 iGEM team from MIT describing fine chemical synthesis [http://www.igem2006.com/presentations.htm presentation video] [[Media:IGEM2006-MIT-Powerpoint.ppt| presentation ppt]] <br>
Their project will allow us to focus on
Their project will allow us to focus on
** programming genetic logic
** '''programming genetic logic, growth phases of bacterial cultures, ethical questions of human experimentation'''
** growth phases of bacterial cultures
***our ppt review of these processes is [[Media:20.20(S09) review EauD'coli.ppt| here]]<br><br>
** ethical questions of human experimentation


'''After''' each presentation, you will have 10 minutes to gather with your fellow moviegoers and discuss what you saw, using these "iGEM review questions" as a guide for your conversations:
===After each presentation===
You will have 10 minutes to gather with your fellow moviegoers and discuss what you saw, using these "iGEM review questions" as a guide for your conversations:
# what was the problem this team chose to address and why?
# what was the problem this team chose to address and why?
# is this an important problem and why or why not?
# is this an important problem and why or why not?
Line 67: Line 68:
# are there aspects of the work that are unclear to you?
# are there aspects of the work that are unclear to you?
# if you could ask this team one question what would it be?
# if you could ask this team one question what would it be?
{| cellspacing="2"
|- valign="top"
|width="670px" class="MainPageBG" style="border: 1px solid #336600; color: #000; background-color: #FFFFFF"|
<div style="padding: .4em .9em .9em">
<center>'''Why are we doing this??'''</center>
Most of our studio session today was spent considering two projects carried out by undergraduates not unlike yourself. The iGEMers worked in teams (as you will) to figure out what they wanted to build (as you will) and then spent some time in the lab realizing their project (not possible in this class but you could join the iGEM program this summer, as three of the 20.020 students from Spring 2008 did!). Remember that these are just two projects of many and you should feel motivated by them to work this term on a project that's important to you. The projects also highlight a few of the many widgets in the toolbox for biological engineers. You might want to revisit these projects as the details of your project becomes clearer. 
</div>
|}


==Part 2: <font color = blue>Dear John </font color>==
==Part 2: <font color = blue>Dear John </font color>==
Line 74: Line 83:
*what areas were tackled?
*what areas were tackled?
*how many also proposed solutions to these problems?
*how many also proposed solutions to these problems?
Take notes on your letter about any new ideas, clarifications, or thoughts you have from the discussion and turn them in
After about an hour of discussion at your tables, you'll have a chance to hear from the other groups. Be sure to take notes on your letter about any new ideas, clarifications, or thoughts you have from the discussion. You will turn in a revised letter before tomorrow. (and note that if you've finished your discussion about the letters early you can get to work on the homework below). 


=='''Homework''' for tomorrow's challenge session==
=='''Homework''' for tomorrow's challenge session==
#To solidify the biology and engineering that's associated with the two projects we studied today, please look at the documentation of their project ([http://2008.igem.org/Team:Heidelberg here for Heidelberg 2008] and [http://openwetware.org/wiki/IGEM:MIT/2006 here for MIT 2006]) and answer the following questions:
1. To solidify the biology and engineering that's associated with the two projects we studied today, please look at the documentation of their project ([http://2008.igem.org/Team:Heidelberg here for Heidelberg 2008] and [http://openwetware.org/wiki/IGEM:MIT/2006 here for MIT 2006]) and answer the following questions:
#*The Heidelberg team built two chimeric receptors to drive chemotaxis in response to AI-2. What successes did they realize? What experiment didn't work? What will they try next?
*The Heidelberg team built two chimeric receptors to drive chemotaxis in response to AI-2. What successes did they realize? What experiment didn't work? What will they try next?
#*The lambda phage built by the Heidelberg team had both a selectable drug marker (CamR) and an origin to enable the phage to transfer via the F pilus (oriT). However the phage wasn't able to lyse either the predator strain it resided in, or the prey strains it infected. Why (you'll have 2 different answers here)?  
*The lambda phage built by the Heidelberg team had both a selectable drug marker (CamR) and an origin to enable the phage to transfer via the F pilus (oriT). However the phage wasn't able to lyse either the predator strain it resided in, or the prey strains it infected. Why (you'll have 2 different answers here)?  
#You should revise your letter based on any feedback you received from your classmates today. <br>
*We didn't spend a great deal of time in class discussing the Colicin experiments that the Heidelburg team worked out. In your own words, please describe this component of their work: what was their "prey"? what was their "killer"? How did they expect this system to work? Did they build and test this?
'''Time to complete this letter revision and answer these questions: 1 hour MAX.'''<br>When you are finished, please upload both to [http://openwetware.org/wiki/Special:DropBox the homework dropbox.]
*Do you believe, as this team does, that "science communication" is the basis for the formation of public opinion and acceptance of new technologies? Give an example of an effective and an  ineffective approach to scientific communication.
{| cellspacing="2"
*The MIT team made some "on the fly" adjustments to their project based on early data collected. For instance they decided to control the banana smell for expression in stationary phase since the smell overwhelmed the wintergreen. Could they have used a computer simulation of their system to make this decision? Why or why not?
|- valign="top"
When you are finished, please upload your assignment to your "Personal Design Portfolio" in the [https://stellar.mit.edu/S/course/20/sp09/20.020/homework/index.html homework dropbox.], calling your assignment: FirstInitial_LastName_PDP_1.doc, for example: <font color = red> B_Obama_PDP_1.doc </font color><br>
|width="670px" class="MainPageBG" style="border: 1px solid #336600; color: #000; background-color: #FFFFFF"|
2. You should revise your letter based on any feedback you received from your classmates today. When you are finished, please upload your letter to your "Personal Design Portfolio" in the [https://stellar.mit.edu/S/course/20/sp09/20.020/homework/index.html homework dropbox.], calling your assignment: FirstInitial_LastName_PDP_2.doc, for example: <font color = red>J_McCain_PDP_2.doc</font color> <br><center>
<div style="padding: .4em .9em .9em">
'''Time to complete this letter revision and answer these questions: 1 hour MAX.'''</center>
<center>'''Why are we doing this??'''</center>
Most of our studio session today was spent considering two projects carried out by undergraduates not unlike yourself. They worked in teams (as you will) to figure out what they wanted to build (as you will) and then spent some time in the lab realizing their project (not possible in this class but you could join the iGEM program this summer, as three of the 20.020 students from Spring 2008 did!). Remember that these are just two projects of many and you should feel motivated by them to work this term on a project that's important to you. 
</div>
|}
 


=<center>Week 1 Thursday</center>=
=<center>Week 1 Thursday</center>=
Line 96: Line 100:
# Watch [http://www.ted.com/index.php/talks/view/id/202 this video] in which Gever Tulley talks about learning by doing.
# Watch [http://www.ted.com/index.php/talks/view/id/202 this video] in which Gever Tulley talks about learning by doing.
# Watch [http://gizmodo.com/348769/macbook-air-tear-down-sexy-on-the-inside-too this video] of a person taking apart a MacBook Air
# Watch [http://gizmodo.com/348769/macbook-air-tear-down-sexy-on-the-inside-too this video] of a person taking apart a MacBook Air
# Working in groups of 4, you will take apart a tape recorder. One person should work the tools, another should record the process (e.g. "began by taking off back panel), another should keep a parts list (e.g. "4 Phillips-screws 3 mm long from back panel"), and the last person should record the purpose of each component (e.g. "Phillips screws held back panel in place). '''Your team's goal is to disassemble the tape recorder into the greatest number of re-usable parts'''... note of the word '''"reusable"''' since next time we meet, the goal will be to reassemble your tape recorder into a working machine. As you work, you may find it helpful to describe what you think each component does and if it's made of sub-components that can be separated further without forever destroying the component's function.
# Working in groups of 3, you will take apart a tape recorder. One person should work the tools, another should record the process (e.g. "began by taking off back panel), another should keep a parts list (e.g. "4 Phillips-screws 3 mm long from back panel") and should record the purpose of each component (e.g. "Phillips screws held back panel in place). '''Your team's goal is to disassemble the tape recorder into the greatest number of re-usable parts'''... note of the word '''"reusable"''' since next time we meet, the goal will be to reassemble your tape recorder into a working machine. As you work, you may find it helpful to describe what you think each component does and if it's made of sub-components that can be separated further without forever destroying the component's function.
#*"One of the problems of taking things apart and seeing how they work--supposing you're trying to find out how a cat works--you take that cat apart to see how it works, what you've got in your hands is a non-working cat," Douglas Adams
#*"One of the problems of taking things apart and seeing how they work--supposing you're trying to find out how a cat works--you take that cat apart to see how it works, what you've got in your hands is a non-working cat," Douglas Adams
# If there's time, watch [http://www.studiodaily.com/main/technique/tprojects/6850.html this video] showing the inner life of the cell, an understanding largely achieved by scientific "take apart" techniques.
# If there's time, watch [http://www.studiodaily.com/main/technique/tprojects/6850.html this video] showing the inner life of the cell, an understanding largely achieved by scientific "take apart" techniques.
Line 107: Line 111:
* from 2008: ''by taking the tape player apart, we learned in great detail how it worked.''
* from 2008: ''by taking the tape player apart, we learned in great detail how it worked.''
* from 2008: ''I think this activity was useful because it showed us that we needed to be really diligent about keeping track of each and everything we did.''
* from 2008: ''I think this activity was useful because it showed us that we needed to be really diligent about keeping track of each and everything we did.''
* from 2009: advice: ''"draw pictures, taking pictures would be even better"''
* from 2009: what would have helped? ''"more time, not having to reassemble, knowing which parts can be broken, if the tape player was build for human understanding and use"''
* from 2009: thoughts for next time: ''"I hope not every part is needed""it would have been easier if we could re-assemble it right away rather than wait until Tuesday"''
* from 2009: what were these built for: ''"these are battery eaters, optimized for disposable, cheap economy"''
* from 2009: woulda-shoulda-coulda: ''"we should have tested it before we took it apart"''
* from 2009: If the tape player had been built to take apart, thered probably be...''"fewer parts esp if not all parts are needed" "easier open/close, no hidden clips" "documentation" "higher quality parts"''
</div>
</div>
|}
|}


=='''Homework''' for next week's challenge session==
=='''Homework''' for next week's challenge session==
#Read [http://www.nature.com/nature/comics/syntheticbiologycomic/index.html Adventures in SB]. Using the problem or opportunity you described in your letter, draft a two chapter script for a comic book using characters from your imagination. In chapter 1, have the characters talk about the problem or opportunity. In chapter 2, have the characters brainstorm a way to solve the issue. Print these out to bring to the 20.020 challenge time next Tuesday.  '''Time to complete this script: 1 hour MAX.'''
#Over the next week we'll be turning the letter you wrote into a script and then a story board. The script should be fun to write and doesn't have to win you a Pulitzer Prize since you'll be turning it into a comic book. For inspiration, look through [http://www.nature.com/nature/comics/syntheticbiologycomic/index.html Adventures in SB]. Then, using the problem or opportunity you described in your letter, draft a two chapter script for a comic book using characters from your imagination. In chapter 1, have the characters talk about the problem or opportunity. In chapter 2, have the characters brainstorm a way to solve the issue. Before next Tuesday's challenge session, please upload your letter to your "Personal Design Portfolio" in the [https://stellar.mit.edu/S/course/20/sp09/20.020/homework/index.html homework dropbox.], calling your assignment: FirstInitial_LastName_PDP_3.doc, for example: <font color = red>H_Clinton_PDP_3.doc</font color><br><center> You should also print out a copy to bring to the 20.020 studio time next Wednesday<br>'''Time to complete this script: 1 hour MAX.'''
#*For an example script, and making a comic background, check [[Adventure_Background | this]] out.
#Complete survey. [http://www.surveymonkey.com/s.aspx?sm=tG9ERe3RBwAmFFS1DG5BQw_3d_3d Click here to start] It should only take ~10 minutes. Please note that this is NOT the same survey that the Project-Based Learning Center might have asked you to complete.
#Complete survey. [http://www.surveymonkey.com/s.aspx?sm=jEDG6UoQRvqu9P4YX7IkSQ_3d_3d Click here to start] It should only take ~10 minutes. Please note that this is NOT the same survey that the Project-Based Learning Center might have asked you to complete.

Latest revision as of 09:18, 10 February 2009

<html> <style>#en2020 a {color:black;}</style> </html>

Week 1 Tuesday

Challenge: Project Runway

Instructions: Today you will design, build (i.e. fold) and launch a paper airplane. Your goal is to make a plane that flies further than anyones. Working in teams of 3, choose one person to be the designer, one to be the builder, and one to be the launcher. You can talk to each other at all stages but be sure each person does the assigned job and that someone takes notes of your work together (decisions, uncertainties, disagreements, expertise etc). Your team may use the internet if you want. The designer has one dollar to spend and your team must keep track of costs. No refunds will be issued for parts you do not use. In the event of a tie, cost and aesthetics will serve as the tie breaker. Relevant materials cost:

  • paper is 30 cents a sheet
  • paper clips are 10 cents each
  • scotch tape is 5 cents per 1 inch strip
  • pennies cost 20 cents each
  • a pencil costs 10 cents
  • scissors are unavailable
  • a test flight before the competition costs 30 cents.

Your team has 20 minutes to design and build a plane for the competition. If you are not ready to launch at this time, you will forfeit.

Why are we doing this??

Once "project runway" has launched and the winning design team has been recognized, we'll work as a class to add more ideas, questions and thoughts to this list.

  • from 2008: "this was as an exercise in engineering. We had to solve a given problem with limited time and resources, while working effectively as a team."
  • from 2008: "We ended up using my design choice because I am more stubborn. This is not a great success story in terms of teamwork, but it did produce the best plane in the class."
  • from 2009: "to give us a way to visualize a design that may seem unlikely and that may not seem like it would work
  • from 2009: "to give us a problem we might feel is more approachable"
  • from 2009: "the most complicated design isn't always the best. Simple works"
  • from 2009: "how different all the plane designs are, even starting with the same materials."
  • from 2009: " I think it was difficult to decide on rolls"

Homework for tomorrow's studio session

Draft a letter. Address this letter to someone(s) you care about. Your letter should introduce and describe a real world problem or opportunity, one that you have inherited, identified, dreamed about, or otherwise encountered, and that you would like to solve or realize. Your letter should explain why you feel the problem or opportunity is important, and what the consequences of success might be. You can focus on more than one issue, but each issue needs to be explained. Please print and bring your letter to the studio tomorrow. Time to complete this letter: 1 hour MAX.

Why are we doing this??

We're looking ahead to the project you and your team will design this term...the first step is for you to decide what you'd like to work on. This letter should start you thinking about your areas of interest. The letter will also be a way to talk with others about things that interest them. Maybe you'll hear an idea you never considered and want to investigate it further. Maybe you'll find someone with very similar concerns.

Week 1 Studio

Part 1: Wednesday matinee

Instructions: Today you will have the opportunity to watch two videos showcasing completed iGEM projects. "iGEM" stands for the "international Genetically Engineered Machines" competition. It is a summer-long opportunity for teams of students working at colleges and universities around the world to design and build genetically engineered machines, many of which use standard biological parts from the Registry of Standard Biological Parts. The videos will orient you to the kinds of accomplishments realized in a summer by teams of undergraduates and their advisers.

Our first feature presentation

Our first featured presentation will emphasize some of the "biology" that's often present in "synthetic biology." As a class we'll watch:


In watching their project we can focus on

sensing
lytic phage
    • cell-cell communication, sensing and chemotaxis
      • our ppt review of these processes is here
    • phage life cycles, DNA transfer mechanisms and "parts"
      • our ppt review of these processes is here

Note that this team developed a tremendously useful website that describes both their project, their human practice work and the basic background a person might need to understand the work. If your molecular biology is rusty, you can refresh your memory here

Our second feature presentation

Eau D'coli
Our second featured presentation will emphasize some of the "engineering" that can be accomplished in a summer by a talented group of undergrads much like yourselves. We'll listen to

Their project will allow us to focus on

    • programming genetic logic, growth phases of bacterial cultures, ethical questions of human experimentation
      • our ppt review of these processes is here

After each presentation

You will have 10 minutes to gather with your fellow moviegoers and discuss what you saw, using these "iGEM review questions" as a guide for your conversations:

  1. what was the problem this team chose to address and why?
  2. is this an important problem and why or why not?
  3. did they succeed in part or in total?
  4. are there aspects of the work that are unclear to you?
  5. if you could ask this team one question what would it be?
Why are we doing this??

Most of our studio session today was spent considering two projects carried out by undergraduates not unlike yourself. The iGEMers worked in teams (as you will) to figure out what they wanted to build (as you will) and then spent some time in the lab realizing their project (not possible in this class but you could join the iGEM program this summer, as three of the 20.020 students from Spring 2008 did!). Remember that these are just two projects of many and you should feel motivated by them to work this term on a project that's important to you. The projects also highlight a few of the many widgets in the toolbox for biological engineers. You might want to revisit these projects as the details of your project becomes clearer.

Part 2: Dear John

As homework you were asked to draft a letter describing a real world problem or opportunity you have inherited that could be addressed in the near term. You should discuss these letters at your team tables and make some notes about them on the white boards. For example,

  • who were they addressed to?
  • how many problems/opportunities did each letter address?
  • what areas were tackled?
  • how many also proposed solutions to these problems?

After about an hour of discussion at your tables, you'll have a chance to hear from the other groups. Be sure to take notes on your letter about any new ideas, clarifications, or thoughts you have from the discussion. You will turn in a revised letter before tomorrow. (and note that if you've finished your discussion about the letters early you can get to work on the homework below).

Homework for tomorrow's challenge session

1. To solidify the biology and engineering that's associated with the two projects we studied today, please look at the documentation of their project (here for Heidelberg 2008 and here for MIT 2006) and answer the following questions:

  • The Heidelberg team built two chimeric receptors to drive chemotaxis in response to AI-2. What successes did they realize? What experiment didn't work? What will they try next?
  • The lambda phage built by the Heidelberg team had both a selectable drug marker (CamR) and an origin to enable the phage to transfer via the F pilus (oriT). However the phage wasn't able to lyse either the predator strain it resided in, or the prey strains it infected. Why (you'll have 2 different answers here)?
  • We didn't spend a great deal of time in class discussing the Colicin experiments that the Heidelburg team worked out. In your own words, please describe this component of their work: what was their "prey"? what was their "killer"? How did they expect this system to work? Did they build and test this?
  • Do you believe, as this team does, that "science communication" is the basis for the formation of public opinion and acceptance of new technologies? Give an example of an effective and an ineffective approach to scientific communication.
  • The MIT team made some "on the fly" adjustments to their project based on early data collected. For instance they decided to control the banana smell for expression in stationary phase since the smell overwhelmed the wintergreen. Could they have used a computer simulation of their system to make this decision? Why or why not?

When you are finished, please upload your assignment to your "Personal Design Portfolio" in the homework dropbox., calling your assignment: FirstInitial_LastName_PDP_1.doc, for example: B_Obama_PDP_1.doc

2. You should revise your letter based on any feedback you received from your classmates today. When you are finished, please upload your letter to your "Personal Design Portfolio" in the homework dropbox., calling your assignment: FirstInitial_LastName_PDP_2.doc, for example: J_McCain_PDP_2.doc
Time to complete this letter revision and answer these questions: 1 hour MAX.

Week 1 Thursday

Challenge: Sexy on the inside 2

  1. Watch this video in which Gever Tulley talks about learning by doing.
  2. Watch this video of a person taking apart a MacBook Air
  3. Working in groups of 3, you will take apart a tape recorder. One person should work the tools, another should record the process (e.g. "began by taking off back panel), another should keep a parts list (e.g. "4 Phillips-screws 3 mm long from back panel") and should record the purpose of each component (e.g. "Phillips screws held back panel in place). Your team's goal is to disassemble the tape recorder into the greatest number of re-usable parts... note of the word "reusable" since next time we meet, the goal will be to reassemble your tape recorder into a working machine. As you work, you may find it helpful to describe what you think each component does and if it's made of sub-components that can be separated further without forever destroying the component's function.
    • "One of the problems of taking things apart and seeing how they work--supposing you're trying to find out how a cat works--you take that cat apart to see how it works, what you've got in your hands is a non-working cat," Douglas Adams
  4. If there's time, watch this video showing the inner life of the cell, an understanding largely achieved by scientific "take apart" techniques.
Why are we doing this??

Taking something apart is one way to understand how it works. Having disassembled a simple machine, you should consider what you've gained from the process. What did you learn? What about this challenge resembled science and what did or didn't feel like engineering? Was the tape player build to enable this sort of work? What (else) has the tape player been built for/ optimized for? What are the chances you'll be able to re-assemble this machine next week? Before leaving class today we'll add ideas/questions/thoughts to this list.

  • from 2008: by taking the tape player apart, we learned in great detail how it worked.
  • from 2008: I think this activity was useful because it showed us that we needed to be really diligent about keeping track of each and everything we did.
  • from 2009: advice: "draw pictures, taking pictures would be even better"
  • from 2009: what would have helped? "more time, not having to reassemble, knowing which parts can be broken, if the tape player was build for human understanding and use"
  • from 2009: thoughts for next time: "I hope not every part is needed""it would have been easier if we could re-assemble it right away rather than wait until Tuesday"
  • from 2009: what were these built for: "these are battery eaters, optimized for disposable, cheap economy"
  • from 2009: woulda-shoulda-coulda: "we should have tested it before we took it apart"
  • from 2009: If the tape player had been built to take apart, thered probably be..."fewer parts esp if not all parts are needed" "easier open/close, no hidden clips" "documentation" "higher quality parts"

Homework for next week's challenge session

  1. Over the next week we'll be turning the letter you wrote into a script and then a story board. The script should be fun to write and doesn't have to win you a Pulitzer Prize since you'll be turning it into a comic book. For inspiration, look through Adventures in SB. Then, using the problem or opportunity you described in your letter, draft a two chapter script for a comic book using characters from your imagination. In chapter 1, have the characters talk about the problem or opportunity. In chapter 2, have the characters brainstorm a way to solve the issue. Before next Tuesday's challenge session, please upload your letter to your "Personal Design Portfolio" in the homework dropbox., calling your assignment: FirstInitial_LastName_PDP_3.doc, for example: H_Clinton_PDP_3.doc
    You should also print out a copy to bring to the 20.020 studio time next Wednesday.
    Time to complete this script: 1 hour MAX.
  2. Complete survey. Click here to start It should only take ~10 minutes. Please note that this is NOT the same survey that the Project-Based Learning Center might have asked you to complete.