Doing to see

My sister and I just recorded a special episode for Driverlesscroc Podcast(‘Useful Things’), learnt a lot doing it, including:

  • That recording both ends of a skype call is a viable way to work over distance
  • The importance of triple-checking your mics after I made a schoolboy error and plugged my mic into a headphone jack. I could see that I was recording something, but it turned out to be my laptop’s built-in mic rather than my lapel mic, resulting in a voice-track that sounds like it was recorded in a bucket
  • That Kevin Kelly and Mark Frauenfelder do a really good job of keeping their Cool Tools show tight – we were trying hard to stay focused but easily racked up 40 minutes.
  • That Audacity projects are big (we hit a couple of gigabytes for all the uncompressed audio and project files).
  • That (I think) Audacity doesn’t play well with syncing to the cloud – some of the source-files for my project file somehow got corrupted and I almost lost it all – fortunately I’d made an almost-finished .wav of the whole thing so it was saveable.
  • That ‘ship the work’ sometimes means ‘finish the project’ – get it done, learn from it, move on. This project doesn’t exactly have a ‘client’, and its main audience is us – so we can say ‘not quite good enough – but finished’ with a clear conscience. I’ll post it to the podcast for completeness, and as a reference for anyone interested in the journey.

The idea that doing helps you see – that experience counts for a lot – is pretty obvious in lots of areas of life. You can’t understand being on stage, or driving a car, or playing in a sporting contest, until you’ve done them.

But we tend to forget how true this is for almost everything, and how context-specific our experience tends to be. By doing, we see.

I'd love to hear your thoughts and recommended resources...