Bryan Cantrill has a great talk on software values. Lets go through all the values listed, to talk about which ones we care about.
A skateboard is approachable. You can see someone on it an instantly know how it's used. This doesn't mean you wont fall off the first time you try to ride.
This is not for production. Skate code is not "fire and forget". You should always be watching, to see if something's happeded. This massivly limits the areas you can skate, but if the ground isn't flat, you wount go their
This will break constantly. Not a value. Their should never be a specification for what is means to skate.
Yes, we want to be able to transition smothly from one trick to another.
Yes, this is a creative endevor. You shoud be able to tell who wrote some skate by their style, because this software doen't need to be maintained for decades to come, not every one needs to do it the same
Yes, we want users to do lisp-like macro things. Go Nuts. Their are no adults to stop you.
No, this makes debuging a pain.
No, not for production.
No, this is for short, one of scripts
No, this should not be perfomance intensive
No
No
No
Yes, but with human assistance
Punt to a human on tricky cases. This may involve "Time Travel"
No
NO
No
No
No
Yes, expecialy in the standard library
Yes, though the debuger
Yes, for developers