2009 300: Difference between revisions
No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
* [[Exercise in Post-fix vs. Pre-fix]] Scheme / LISP / Logo? | * [[Exercise in Post-fix vs. Pre-fix]] Scheme / LISP / Logo? | ||
* [[ Relational Databases ]] | * [[ Relational Databases ]] | ||
* Simple Web Servers | |||
== Technical Plan == | == Technical Plan == |
Revision as of 11:28, 14 April 2009
Basics as "études"
- Necessary Tools: sshfs (on Mac/Windows??)
- Physical Computing: Resistor sorting "party"?
- Networking
- Reich's Clapping Music as Distributed Arduino?
- Command-line Video Editing -- Variation movies
- Review Bits and Binary --> connect to arduino? switches?!, or to "magic" numbers like 4294967295, and the mysteries of two's complements?! bits to images
- Exercise in Post-fix vs. Pre-fix Scheme / LISP / Logo?
- Relational Databases
- Simple Web Servers
Technical Plan
Part of writing your technical plan is to select a day to present a topic. It could be a particular software package, a piece of code, or a technique. The key is that it should be something you would like to learn more about. You need to think of a small "proof of concept", an idea you would like to realize using the given tool. (Important to keep the scale realistic;) In the process of realizing this project, use the wiki page to document your progress. You should:
- Create a page on the TD wiki on your topic.
- Include links to the resources you used / found helpful in preparing your presentation.
- Create a small "proof of concept" demonstration of what you think you might be able to do / make with the given tool / software. As you go about.