Skip to content Skip to navigation

Reflections on BADCamp 2015

Over four days in October, I found myself once again, wandering the campus of UC Berkeley and attending BADCamp. I've lost count of how many times I've attended BADCamp. I think I attended the first camp and have just kept coming. 

What keeps me coming? I suppose it's to connect with the Drupal community, learn how to do something, and find out what's up and coming.

Connect with community

Sure, you can watch their presentations on YouTube, but there's nothing like meeting the people responsible for building the module or developing the technology that you're using. 
On Friday I attended Jesus Manuel Olivas' training on how to build a module in Drupal 8.  After an introduction to Drupal 8, Composer, and the The Request/Response Flow with Symfony2, we jumped into Drupal Console. This tool developed in large part by Jesus, helps to automate module development for Drupal 8. Not only will it download and install a Drupal site, i.e., $ drupal site:new and $ drupal site:install, it will create, install, and generate many parts of a Drupal module , i.e., $ drupal generate:module, $ drupal module:install my_module, and more! As we explored using Drupal Console, Jesus listened to our comments and suggestions, promising to consider them for the next version of Drupal Console. Check out his slides! Just participating in this training provided a great opportunity to connect with the Drupal Community.

Learn how to do something

BADCamp is a great place to learn how to do something else. Git is a tool I use on a daily basis. Frequently, you can find me cloning a repository, pulling the latest changes, or committing my changes back to a repository. Presented by Mark Ferree and Brad Erickson, the session on Next Level Git highlighted some unfamiliar and new commands in Git. I was reminded for example, that when have a small mistake like a spelling error that doesn't really need to be a separate commit, using $ git commit --amend allows you to tack that change on to that last commit.  I also learned more about using $ git rebase. With this command I can package all my little commits into one big commit with a succinct message describing the real purpose for all the changes. 

Find out what's up and coming 

The Drupal world is constantly changing and growing to meet the needs of our community. For example, there were many sessions referencing REST and "Headless Drupal." One way Drupal is growing is that people in the community are beginning to view a Drupal site as a way to provide content for other services. That is, rather than going directly to a website for information, you  use an external application to get the content from the website. Then your application can use that information in new ways. Your application circumvents the user interface on the Drupal site and accesses the content typically through a REST API. When bypassing the front end we get the name "Headless Drupal." 
Once again, I had a chance to learn and grow at BADCamp, and  I'm already looking forward to next year when I can again rekindle my connections, learn, and grow with the Drupal community.