Since we can only record in our spare time, we'll get into a recording and forget where we were from week to week and session to session. Things change with the band or with arrangements or with recording techniques. We'll come up with new ideas or new songs that we decide to tackle first. And sometimes that process is really, really long--we've been recording some of these songs through eight years and four different lineups!
Then it occurred to us: these are some of the same problems we frequently encounter in our day jobs as software engineers. And maybe, just maybe, we can apply some of the same solutions.
The software development world has been increasingly turning to a set of techniques known as Agile Development. In a nutshell, the process involves working iteratively, getting small, self-contained chunks done at once. This should limit the chance of losing our place or being thrown off course by inevitable changes. Agile projects try to release often, so that they can get continuous feedback - along with a constant sense of accomplishment. Along the way, we can take a teamwork approach involving our whole band, our close friends and our loyal fans, getting more feedback and producing a superior end product.
We highly recommend heading over to read the Agile Manifesto and reflect on those ideals, regardless of your discipline.
So here's the deal: as we record our next five-song project, Any Port in a Storm, we're going to take an agile approach. We'll update this blog after each recording session with session stories, engineering insights and, of course, sound files -- in high-quality, DRM-free format. For you, this is a chance to see the process unfold, get insight into how our songs grow and hear the different stages of recording unreleased songs. Read and listen along with us and let us know what you think in the comments.
The first installment in this series debuts tomorrow. See you then!
- E
No comments:
Post a Comment