It has been a dream of mine to have the option of developing on an iPad when my laptop is unavailable or when I just don't want to lug a full laptop around. Recently I have started developing apps in Meteor.js and I came across a web service and some techniques which allow me to develop Meteor apps on my iPad.
One thing that drives me crazy is a messy git log full of unimportant commits. While I subscribe to the commit often philosophy during development, it does lead to commits which have no historical significance to upstream project branches. Who needs a git history full of commit messages like corrected spelling and fixed a php notice. These commits are helpful during active development, but they just clutter up git history if pushed to an upstream repository. It doesn't have to be this way!
Sublime Text 3 has not been released yet, but I am using it for production work and have pruned my package list to include packages which I regularly use. I have included that list below. Note that most of these can now be installed with Package Control 2.0.
Well, you can certainly learn something new about Drupal everyday. I spent a good bit of time trying to figure out why I couldn't perform a simple field value update to a few nodes in an application. So, node_save() was running without error, and nothing I attempted to update in the node object or related fields would save.
I needed to test an older version of a file in a web app, but didn't want to checkout the entire codebase. The method below allowed me to easily checkout an older version of the file using the commit hash that I knew had the correct file. Other git object references such as tags, branches, and commits from HEAD can be used instead of the commit hash (full or short SHA). See details here.
$ git show [commit-hash]:/path/to/file/file.txt > file.txt