Last Saturday (February 21st, 2015), thirty-five Drupalers joined together at Classic Graphics for the sencond annual Charlotte Drupal Drive-in. The day was full of presentations, BOFs, and general chatting about Drupal and related web technologies.
The day-long, un-conference-style event was the brainchild of Thomas Lattimore. After CharDUG wasn't able to pull together the human resources to repeat the success of DrupalCamp Charlotte 2012, Thomas mentioned that he had an idea. Since he knew organizers had limited time to commit to planning and he wanted to host an un-conference-style event, allowing for simpler planning than a full-blown Drupal camp. You can learn more about his concept on the DruaplEasy Podcast.
I am amazed at the level of quality email newsletters that have hit the tech world in recent years. While, I spend a great deal of time filtering and pruning the emails I choose to receive, I have a few weekly tech newsletters, which I find valuable.
I thought it would be great to share the newsletters I have found interesting. Feel free to leave links to your favorite tech newsletters in the comments section.
I would like to introduce a new blog project, shelldevel.net. The blog was setup to allow a few friends to easily share tips they found while working on setting up a shell-based IDE (integrated development environment). Using VIM, tmux, and a number of other command line tools, very powerful and fast development can be accomplished.
The day Jeremy Edgell, a co-worker at Classic, mentioned it was possible to checkout pull requests, I knew that this trick would greatly increase my code review efficiency. Jeremy's solution involved adding an additional reference to the pull request location in an individual git repo's .git/config file. You can see a similar example to Jeremy's Stash solution in this gist.
Checking out a Github pull request (Note: The git alias, gpr-origin, indicates the remote to reference. I have one setup for origin and upstream.)