Crawl, Walk, Run

TL;DR: I consolidate all of my thoughts on Twitter.

Oh, you want more? You got it.

Here’s a list of things that are different:

• Got a new job.
• Stopped writing JavaScript
• Started writing CoffeeScript
• Stopped working on my Backbone library
• Started working around Batman.js (and contributing to fix broken things)
• Became the most knowledgeable among my friends and coworkers about testing in JavaScript and associated environments
• Stopped working on front-end development
• Started working on iOS development again
• Became the most knowledgeable among my friends and coworkers about testing in iOS
• Fired up a personal project and got neck-deep in Angular.js and more familiar with Node.

That’s really all there is to say of interest. If that’s not enough, get in touch with me on Twitter. I’m still doing freelance work and I’m sure I can do something very helpful for your team.

Blog posts are such a huge investment for me.

If you want to see the day-to-day stuff I’m working on, come find me on my Twitter.

Side note: If you think something basic like natural date parsing in JavaScript is a) simple and b) not yet solved you are wrong on both counts.

Having great code but not being able to share it is rough.

For many years I’ve either been working on boring enterprise integration stuff or amazing tech that I’m not allowed to yet share with the world. That makes for a fairly silent blog and twitter feed. Unless, of course, you want me to talk about the sandwich I had for lunch and omigod how annoying are drivers in [your local commute path]?

But things have changed! I’ve been working on some awesome code, projects and platforms lately and I have some neat code that I think should be shared with the programming community.

Thankfully I’m seeing some progress here from management towards openness and embracing the community. That means not only do I get to talk about some of the crazy stuff I’ve done here but also start open sourcing our code!

Bam. It’s going to be cool. But hold on to your knickers cause enterprises are slow moving beasts. Patience, kids…

Just a quick tip on how to use the “Remote Disc” capabilities on any Mac that isn’t an Air. For some reason Apple will let you share a drive but not read it over the network unless you’re on an Air. Yet another quirk from Cupertino. In any case, the solution is easy.

Open up Terminal and run these two commands to update your settings. If you’re afraid of Terminal, just copy and paste these. Trust me, they’re harmless.

defaults write com.apple.NetworkBrowser EnableODiskBrowsing -bool true
defaults write com.apple.NetworkBrowser ODSSupported -bool true

Then open up Activity Monitor and force quit Finder. It will automatically restart. Open up a Finder window and marvel at the glory of sharing an OS X install disc over the network. Particularly handy when your MacBook Pro won’t read a disc.

I’m off to install Snow Leopard on my home/studio MacBook Pro. Over the wireless. Why does this sound like a bad idea? Hmm….

(or How I Learned To Loathe Independent Subsystem Settings)

For years I was a Winamp user. Man, I was downright ecstatic to use Winamp. Fast, feature-rich, lightweight…it was a dream. More importantly, it made my music sound great over my 5.1 speaker system. Then I got an iPod as a gift. In those days it was the dark ages of Winamp to iPod synchronization. It was a gamble; you could load more music or wipe the whole thing clean using the same button. And so, with a heavy heart, I made the painful switch to iTunes.

Like anything worth doing, I did it full-bore, diving into iTunes and never looking back to Winamp. As the years went by I kept the same speakers but iTunes grew, turning into the application it is today. Still, during every format I installed the latest copy of Winamp. Call it nostalgia but I just felt the need to have a copy around. Hardly ever used, Winamp was relegated to my defacto mp3 preview app as it started up instantly and was still relatively light on the resources consumed.

Not too long ago I downloaded a sample mp3 for a band (Genesis, by Justice) and by the time the main groove hit I was hooked. Shortly thereafter I had ripped the cd to my drive and tossed it into iTunes. But wait, something strange had happened in the transition from the sample mp3 to the full album. The song sounded flatter, weaker, missing in the upper and lower frequencies. I had followed my normal ripping procedure – EAC with LAME, using my custom configuration –  but I tried it again anyway, blaming folly. Still the same results. Out of curiosity I tried playing the song in Winamp and magically the fullness had returned!

Something was awry with iTunes. Following the tubes I found post after post blaming QuickTime for using wave out instead of DirectSound. However, inspecting my QuickTime settings showed that DirectSound was selected by default. Then, as I hopelessly clicked through the setting tabs, I saw something which defied logical explanation.

QuickTime was configured for a stereo speaker output despite Windows having a 5.1 configuration! Why Apple would choose to allow a secondary source of speaker setting, especially one which countered the Windows setting, was beyond me. With reserved hope I selected “5.1 (L R C LFE Ls Rs)” from the dropdown, stabbed the “Apply” button and waited for the configuration to save.

I tell you, I haven’t heard iTunes sound so sweet until that moment. My library felt alive again, full of verve and detail! Although the audiophile in me was saddened to realize I couldn’t notice a lack in quality all these years, this was quickly replaced with joy by my music’s new lease on life.

Lesson learned: Do not ever rely on third-party applications to obey the rules and settings of the host OS. Always explore all options. Ruthlessly configure and tune. Stock configurations are for people who don’t care. Option panels are for those who want to make their software work for them, not against.