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: https://www.garfieldtech.com/blog/tmi-outing This created widespread outrage on Twitter, Reddit, and much more. Inevitably it was followed up by a blog post from Dries: http://buytaert.net/tag/living-our-values 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

Not A Victim

Posted on Mon, 03/06/2017 - 09:55

The Trump team has been saying they are victims from attacks of those on the left that don't want them in office. While it is fair to say that those in the left indeed don't want them in office, this is a direct response to their policies. There has been a growing lack of confidence founded on the wrecklessness of the administration's words and actions. In response to the criticism they have received, members of the Trump team are claiming to be victims. This is one of many strategies the administration has used in deflection. An alternative strategy would be to engage with the public in


Commits on Drupal.org

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 Drupal.org. 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

Just Another Varnish and Drupal 8 Blog Post

Posted on Wed, 12/07/2016 - 16:17

Since both core caching continues to evolve in Drupal 8 and contrib modules are maturing, I wanted to capture my steps for configuring Varnish 4 to properly work with Drupal 8. Set up the VCLFirst, I am NOT a systems administrator. I rely heavily on the expertise of others in the community to steer my efforts. I set up Varnish to serve up content from the Drupal site, hoping that the VCL configuration I found from Jeff Geerling would do the trick. (Reference: https://raw.githubusercontent.com/geerlingguy/drupal-vm/master/provisio…). Under your acl purge IP settings

development drupal

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