Symphony.

This show is about a boy (Allen) who learns true magic (Symphony 2) and the challenges he and his friends faced against 3 evil entities: Bloat, Inefficiency and Learning Curve.

Allen talks about the challenges the team faced with the current state of Symphony and the solutions they've implemented for version 2; presented in a format known to the academics as "lectures I rather skip". Be warned, attendance will be marked against your final grade. Get the keynote presentation now or forever hold your peace with a B+ at best.

Our first Symphony Deve Chat was a good start but in this podcast, we've increased participants by 33%, length by 90% and on-tap beverage by a staggering 300%.

In this developer's chat podcast, we discussed the next version of Symphony; the potential of a version number change, making Symphony open source upon release and many other juicy tidbits. Don't miss it!

Hello and welcome to our first Symphony Dev Chat. This is your host, Allen Chang and with me is Symphony system engineer, Alistair Kearney.

The whole transcript below is only half of one-third of a quarter segment in the podcast, listen to the podcast for the whole full thing!

Hello and welcome to the Chaotic Pattern podcast, this is your host, Allen Chang. Today, I'm interviewing two very special guests. These guys are the only ones in the world that can pull off the title "Noob" in the coolest sense of the word, Brad Smith and Ryan Sims, the brains and brawn behind Virb.com and The Big Noob.

Remember to participate in our events to win a The Big Noob T-shirt. Find out more.

To celebrate the release of the iPhone, we are giving away free copies of Symphony! Incidentally, the Symphony blog is celebrating the release of the The Big Noob interview podcast by giving away 3 Noob T-shirts.

Symphony is soon reaching version 1.8. It’s over two years old and it’s been around its fair share of blocks. Symphonians now expect more features, greater stability and fewer bugs. The Symphony team is every bit as committed to these but because of it, we sometimes lose sight of existing features that need a little bit of tender, love and care. Each of the members in the Symphony development team have their own pet peeve with the system that we vow to one day fix. In this article, I will illustrate one of my pet peeves.

It's not everyday that you get a chance to speak to the guy who's written the mojo that lives in your servers, unless of course you work with the guy. Then again, I've never been in a position of a podcast journalist in this bizarre, yet refreshing role. You can either read the transcript below or alternatively, for the bandwidth-gifted, listen to the podcast.

Symphony certainly is a bit of a head scratcher. It’s difficult to really put your finger on it; “A ha, Symphony is [insert pre-existing definition]!”. It suffers from an identity crisis. Correction, Symphony knows very well who she is, the problem is people’s perception of her. Judging from the public’s opinion of Symphony and the type of support enquiries we receive, it’s obvious that many people have the wrong idea about Symphony. It’s our fault really, the product website fails to really define Symphony, who should use it and why it’s useful. Now that I’ve acknowledged it, I am going to address the problem right here.