Follow Up: A more informed opinion on our community crisis

Posted on Thu, 03/23/2017 - 23:06

As I mentioned in my previous post, I was struggling to make sense of this situation. Was Crell treated fairly? Was he being discriminated for his beliefs? How is this possible in the confines of a community that supports diversity and inclusion? I spent parts of my day participating in discussions with team members, engaging community members, researching relevant topics, and reading responses of others that had their own questions and concerns. We are all still processing this and I ask you to please respect the diverse opinions from members in the community. In my post yesterday, I made it

drupal people

A Troubling Situation Indeed

Posted on Thu, 03/23/2017 - 09:17

When I was checking Twitter last night, a prominent community member posted a "TMI" message with a link to a blog post. This was totally off-character for a man regularly promoting thought leadership in technical capacities (why I was following him on Twitter). I was quite curious and I was immediately appalled by what I read. The post can be found here: This created widespread outrage on Twitter, Reddit, and much more. Inevitably it was followed up by a blog post from Dries: While totally uninformed and

drupal people

"First" based approaches need to die

Posted on Wed, 03/08/2017 - 14:59

Off the top of my head, I can name several "first"-based approaches. Do any of these ring a bell? Mobile first, content first, API first, user first, design first, experience first, modeling first, security first. For far too long, experts in these various realms have caught the attention of communities by coining these terms. They speak to the vulnerable: people who have ultimately been burned by not applying the best practices of whatever is being sold. But, that is an altogether different problem than what is ultimately being sold. What is being sold is the need to put something first. This

development people

Commits on

Posted on Fri, 12/09/2016 - 11:15

I'm a huge advocate for finding ways to encourage more Drupal participants. Due to the complexity, it's unreasonable to expect people to initially pick up programming-heavy issues. This is the motivation behind the "novice" label, providing a means for identifying potentially low-complex tasks new contributors could safely pick up. The end result is usually one or more commits which are credited to you and/or your organization on Commit BiasFor those looking to bolster their Drupal expertise, organizations will often look at who has "given back" to Drupal as a means of vetting. The

drupal people

Lessons Learned: The "Why" and "How" of Drupal Contributions

Posted on Fri, 10/21/2016 - 16:24

WhyI am ashamed to admit, for the longest time I used Drupal (heck, even complained about it) but contributed absolutely nothing back. It occurred to me that, not only did I learn technical and marketable skills thanks to Drupal, my Drupal experience directly corresponded to opportunities that supported my livelihood and viability for me and my family. And, all of this occurred without one line of code from me contributed back. A long while back, I decided to make an effort to solve a core issue. At that point, I had stronger SVN experience than Git. I had approximately eight years of

development drupal people

Balancing Theory and Practice

Posted on Fri, 09/23/2016 - 09:02

When you are building a tool, how do you measure the success of your efforts? There are data driven approaches around adoption, like number of times your tool has been downloaded or installed. Similarly, success could be defined as how effectively you solved the problem. This could be measured by the number of issues filed, the (hopefully) lack of vulnerabilities, or the number of feature requests created. But, in any measure, success is actually defined by other people. And, as an engineer, it's such a difficult task to put yourself in their shoes. How do you deal with that? Theory People are

development drupal people

The Technical Lift of Drupal 8

Posted on Wed, 07/27/2016 - 13:13

Drupal 8 has been widely praised for improving the developer experience (DX). The "best of breed" adoption of tools (see: Symfony, Guzzle, PHPUnit, Composer, etc) clearly positions Drupal to mature and evolve beyond that which one community is able to do alone. But, there are many different considerations of DX that need explored. And, what lift is required for the community to grasp this new version? And, what is the impact? DX ConsiderationsProbably the number one thing that is praised with Drupal 8 is the technical modernization. Drupal is already challenging to learn effectively. But, if

development drupal people

The office is dead

Posted on Mon, 04/11/2016 - 11:44

I recently made a pass through historic downtown Altoona and I noticed how many buildings appeared to be empty. It actually occurred to me that my definition of infrastructure has shifted radically from the conventional infrastructure companies have adopted. The "office" is hardly a requirement for a majority of jobs. I have now worked for two virtual companies for almost three years. Aside from the occasional happy hour, there is very little that I miss out on working virtually. Video conferencing software has been amazing (you can share your screen and co-work on items if needed). Slack has


Our fights are not your fights

Posted on Tue, 03/08/2016 - 18:05

I'm not one to really dig my heels into politics. I find it divisive and I recently had a clear example as to why. Earlier, I heard my doorbell ring. It was a Bill Shuster promoter walking door to door in my neighborhood. I have already grown tired of his campaign, seeing television commercials with scathing attacks on Democrats, his extreme views on health care, and the flashing images of Sarah Palin and other off-the-wall conservatives he self aligns with. I was handed a pamphlet of information and needed to look no further than the cover to set me off. Our fights are Bill's fights


"Just Enough" Planning - An Agile Concept

Posted on Wed, 12/02/2015 - 14:09

The Agile framework is all the rage. It aims to solve limitations introduced by waterfall. The framework is driven by value and priority, not fixed scope and heavy upfront planning. But, Agile and its Scrum variant is just a set of theories not intended to fully prescribe practice. There are many challenges that observing strict Agile/Scrum can present in practice, especially for agencies attempting to adopt it outside of a product development process. Background I believe the theory behind Agile and Scrum is sound. Where waterfall advocates for rigid planning first and foremost, Agile/Scrum

development people