Manda QoP

It's been a busy 2½ years helping out first with OSDC (Open Source Developers Conference) and then immediately jumping in to helping run lca2015 (Linux Conf Australia). Looks like another may be en route as well... watch this space... Whilst it's very rewarding helping to run a conference, there are also some traps for new players that I've learned about on the way. Luckily the first conference was a lot smaller than the second, so the lessons learned weren't quite so brutal as they could have been if they were discovered during lca2015. These pitfalls can be especially hard on those with certain mental illnesses and anxiety disorders, so I've come up with a top 10 list of how to protect your head space when helping to organise a conference. Make sure you have a 2IC/team for anything you're working on so that if you need to, you can take a month or two out without any feelings of worry or guilt. Remember to keep in touch with the team though so that ...

So far I'm impressed with Google Chrome.  I love simple designs and I'm particularly liking the garbage collection and process handling.  Very neat.  It harks back to the days when I was learning C & C++ and I remember these being standard requirements when writing code - tidy up after yourself, avoid creating memory leaks etc...  I take it that previous browser developers either forgot this or thought it didn't matter. I'm also wondering if they've read my TechEd talk on complexity where I talked about leaving cool stuff out so that the first iteration of your software is a workable, robust solution... maybe not, that was yesterday afternoon and I'm pretty sure the Google devs don't have a time machine. :-) I had a quick look at ESI as well and this is looking like an interesting thang that deserves a more in depth look.  More info on how that goes later on...