Thats me in standing like an idiot at the Facebook office

Thats me in standing like an idiot at the Facebook office


Something for audiophiles (what sound engineers already know)

I’m no sound engineer which is why the graphic equalizer is a revelation to me. After many years of playing my tunes thru winamp and of late iTunes I forgot about the good ‘ol equalizer ie. the big device that once occupied a shelf in your vintage hi-fi setup. My dad still has a kickass 40-band eq. I loved that thing. They don’t make those thingems anymore. Or do they?

Ahem, yes I know, Hi-fi is old-hat. Today we have “home-theatre systems” and iTunes (mentioned already). We’re all aware what EQ does for us. At least we all use the presets on our various sound devices. Right? My iTunes and iPod EQ is almost always set to “Rock”

Handy. Someone already worked out which frequencies need to be boosted or reduced to compliment certain music styles. But EQs can do more than just that. EQ is also useful to get the right sound in the wrong room. And for aspiring musos they’re a handy way to highlight or reduce certain instruments (and their associated frequencies). For instance, I’m a guitar guy. Vocals can get in the way of figuring out which notes are played by the guitarist because guitar and vocal frequencies overlap somewhat. Using EQ I can boost the guitar’s EQ range and dim the higher end of vocals somewhat. Anyways. I found the following link very very useful.

http://www.methodshop.com/gadgets/tutorials/ituneseq/

Go Now. Create your own presets! 

Its a good starting point. Now I wish I’d done a sound engineering course. Maybe I still can :P

merge arrays and preserve numeric keys in php

weird. crazy. i had no idea you could do this

<?php $result = $array1 + $array2; // merges arrays and preserves keys! ?>

yay!

if you miss updating twitter status via IM you can do so via ping.fm’s gtalk and/or msn live bot

My first ping from pingdotfm :-)

Developer code reviews

Am about to write up a checklist for performing software code reviews. As lead dev I often find myself performing this task since Quality Assurance is one of my key job outputs. 

If I’m always performing the review then why document it? Well, for a number of reasons. First one being we’ve recently adopted SCRUM. SCRUM promotes cross-functional teams which means individually we should also be cross-functional, to some extent. Developers may never become designers but surely most developers can perform code reviews?

Its a given that performing code reviews requires a keen eye and attention to the details. It can require great skill when detecting XSS vulnerabilities or profiling issues but for the most part every developer can spot a boo-boo or coding horror. We all make mistakes from junior to senior. A peer review is an excellent tool to foster quality.

So once I have that documented checklist I can delegate! What a beautiful beautiful concept :-)

So, I’m still busy writing up that checklist! But in the meanwhile I’ve done a bit of research to ascertain whether my checklist is on par with the industry’s.

Some interesting links/articles I’ve stumbled upon:

The first one is a real gem