One of the many perks of working at Mediacurrent is the ability to work in the comfort of your own home or nearby coffee shop. With that being said, I was recently faced with a new task: increase recruitment and exposure for our growing team by adding Mediacurrent to the remote-jobs list in GitHub.
A Marketer Walks into GitHub...
In case you’re not familiar, GitHub is a community of more than 15 million people, where developers can discover, use, and contribute to millions of projects. To bridge the tech speak gap, think of it this way: GitHub is to developers as Pardot is to marketers, a central platform to house all of your code or content. Having no technical experience, I instantly felt like a fish out of water once my GitHub account was created. Lucky for me, I wasn’t braving the new terrain alone. Our Community Lead Damien McKenna generously helped walk me through the process.
Although Damien and I were communicating through our team’s messaging app and there was some lag time, the process took me upwards of two hours to complete:
1. Fork the Repository
2. Make the changes I wanted (which in this case was to add a new file)
3. Submit a Pull Request
Put in terms for non-technical folks like myself: the "fork" makes your own copy of the repository. You can then make changes (create files, rename files, delete files, change files, etc) in the form of a “commit,” usually with each change saved as its own commit. Once your changes have been made, you submit a pull request. A pull request is a request for the project’s owners or maintainers to “pull” in your suggested changes.
Lesson #1: Break out of that comfort zone
Although it’s not necessarily fun to feel lost and completely out of your element, it was even more refreshing to learn something new, and extremely rewarding once the Pull Request was submitted.
Lesson #2: Now, I ‘git’ it
Being a marketer in the Drupal space, I encounter unfamiliar terms on a regular basis. However, the silver lining at Mediacurrent is our team’s dedication to thought leadership and sharing what we know. If I ever have a question or want to learn more about a technical topic, there’s a good chance I can find what I’m looking for on our resources page. Mediacurrent’s blog post onGetting Git was a great starting point.
Lesson #3: Lean on your team
Even though Damien and I are in different departments and don’t work with each other frequently, he didn’t hesitate to walk me through something that he knew would be time consuming on his end. This is just one of the many instances where our team goes above and beyond to help each other grow at Mediacurrent.