Hi, I'm Mike. I'm a web developer. This is my story.

Simplifying the Front-end Build Process

CSS and JavaScript seems like it should be pretty simple. We have our site stylesheet, our site support scripts, and some dependencies like Twitter Bootstrap, JQuery, etc. And that's fine, until it gets to be a lot. Next thing we know we have 5 internal scripts, 10 dependencies, 3 internal stylesheets. Google PageSpeed is not happy with making 18 HTTP calls to load our front-end dependencies, which aren't gzipped, minified, or uglified. If you're like me, we tend to just write JQuery spaghetti code, too. No classes, no objects, just $('.thing').doSomething(); all strung together. Now we realize we have a mess on our hands. We work hard to organize our back-end code and keep it maintainable. Why not the same for front-end?


Automounting With Virtualbox

While I work on learning Vagrant and Puppet I am using a manually built VM for development. I thought it would be cool to just mount a directory from my mac to the Ubuntu /var/www. This way I can set my /etc/hosts file on my mac to point a domain to my VM, set up a vhost on that VM, ssh into the VM, and work and preview remotely. Doesn't sound too difficult right?



Teaching Laravel

I love to learn from other developers and share my knowledge. At work recently I needed to explain the Laravel 4 workflow. There are a variety of ways to go about this, and I thought about the pros and cons:


Vim - Down the Rabbit Hole

It's been a strange journey into the annals of Vim, but I'm now pretty comfortable using Vim as a PHP IDE. How did I get here?


Remote Config Files In CodeIgniter

I ran into a situation recently where I had multiple CodeIgniter apps which depended on the same config values. No problem, right? Just use a common third_party folder. That would work, except they were on different servers! My solution was to echo the config as JSON in one place, grab the JSON in other apps and load them as config values. Now you can do the same!