I consider Kinetic “an experiment” because:

One, I have *no clue* whether my half-baked ideas are even feasible (given my grasp of current technologies), and the only way to find out is to actually try them out.

http://www.flickr.com/photos/clivrow/2733115397/

And two: I continually tweak/mash/purge/brainstorm/test new ideas as I clumsily evolve the project towards something potentially useful.

Joel Spolsky calls this “Fire and Motion“:

When I was an Israeli paratrooper a general stopped by to give us a little speech about strategy. In infantry battles, he told us, there is only one strategy: Fire and Motion. You move towards the enemy while firing your weapon…It took me another fifteen years to realize that the principle of Fire and Motion is how you get things done in life. You have to move forward a little bit, every day. It doesn’t matter if your code is lame and buggy and nobody wants it. If you are moving forward, writing code and fixing bugs constantly, time is on your side.

Expect Kinetic to be under constant flux. I have a directory on my MacBook Pro desktop, named “Language syntax ideas.” I’ll try out the promising ideas, and discard those that make the product confusing.

Ready–fire–aim.