704
edits
Changes
Jump to navigation
Jump to search
mLine 41:
Line 41: − + + + + + + + + + Line 83:
Line 91: +
theory
i.e controlling physical robots with the code made by emulation.
i.e controlling physical robots with the code made by emulation.
The theory of this proposal are in one of Marvin Minsky's essays
The theory of this proposal are in one of Marvin Minsky's essays, specially this one
* http://wiki.laptop.org/go/Education_and_Psychology
''Teaching Cybernetics instead of Psychology''
'All this suggests that our ideas about psychology are still developing so rapidly that it wouldn’t make sense for us to select any current “theory of thinking” to teach. So instead, we’ll propose a different approach: to provide our children with ideas they could use to invent their own theories about themselves! The rest of this essay will suggest that such ideas could come from engaging children in projects that involve making machines that have ‘lifelike’ behaviors. Such projects would engage and integrate many concepts that we separately treat today, in Physics, Biology, and Mathematics—and in Social Studies, Psychology, and Economics—along with other important principles that don’t fit into any of those traditional subjects.
A flood of new concepts about what machines could do began to emerge in the 1940s, from research in the field called Cybernetics—which soon then led to other fields called Control Theory, Computer Science, Artificial Intelligence, and Cognitive Psychology. Each of those new sciences brought hosts of new ideas about how to build systems that actually do some of the things we use ‘thinking’ to do. So now, in the spirit of Seymour Papert’s “constructionism,” we can enable our children to experiment with networks composed of collections of parts that support many sorts of knowledge-based processes. 10 This is important because that’s what we are'
* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
* Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more
* Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more
There is an initial work on http://wiki.laptop.org/go/Peripherals/Robots