The Retro Problem

Retro Programming sucks?

Retro Programming sucks?

Derek Sivers writes about an idea for a creative computer: it would do nothing until you figet with it enough / learn about it enough to make it work. Kind of like the Radio Shack TRS-80 in 1978, which he grew up with.

I love this idea, but my no. 1 thought is that the context differed largely for him as a kid and for kids now. 1. there’s peer influences. I know that home schooling is a semi-big deal in the US (tried it once, it sucks) and that a large factor of that is keeping your kid isolated from bad influences.

In the scenario of CreatoComputer2009(TM), you would have to keep the “bad” influence of innovation and gadgetery around kids to a minimum, to allow your kid to use CreatoComp. Because as soon as that kid sees that all the other kids have to work nada to have a working computer, the whole experiment implodes.

Vs. 1978, where everyone had to work at making these wiry beasts, people dared calling a computer, work.

You can take this analogy to anything retro really: cars, movies, Asteroids the game. Compare that to any modern invention and people (except for the nostalgic crowd) quickly turn away.

I agree that to create creative & creating people, you have to confront them with difficult problems to solve at an early age (perhaps). I do think that it needs to be built upon the platform that we are now living with: super-connected graphical interfaces that operate in the digital realm mostly and involve minimal wiring or soldering. I also think that our understanding of education is evolving to the extent that even playing games can be considered a type of learning, which seems fairly compatible with being a child also.

You know there’s only one answer to this problem, right?

Vincent.
(P.S. I know, 2 posts in 2 days. Doesn’t mean that I’m back though, more confused about whether I want to come back. Gotta love the limbo that is August…).

Staypressed theme by Themocracy