The 2014 Digital PM Summit is here! I'm greatly looking forward to presenting on organizational growth from a PM perspective. I've arrived at the final post in this mega-series supporting the presentation, which focuses on planning (or not planning) for growth. It takes a look at examples where planning is called for, while in other cases making decisions based on growing pains is the most efficient route to success.
It's just over a week until the 2014 Digital PM Summit, where I'll present on organizational growth from a PM perspective. This post in my supporting series applies learnings from the world of digital project management to the need for managing company operations.
Meet the people behind the tool. For Toadcast 26 we are joined by members of the New Relic team to talk about Insights, domestic chore inventions, and the heirarchy of desserts/bands. Our guests include:
With my presentation at the Digital PM Summit coming up on October 7th, here is post number nine in my series on organizational growth. This post makes the case that if you want documentation that has a shelf life of more than 6-12 months while growing, you need to focus on the "why" and not the "what" when creating documentation.
With my presentation at this October's Digital PM Summit just a few weeks away, here is post number eight in my series that started after I first presented on the topic of growth at Drupalcon Austin. This post investigates how to create process frameworks that hold up throughout phases of organizational growth.
Like many Drupal developers, we have become big fans of decoupled front-ends using Drupal as a RESTful backend (a.k.a. "headless" Drupal). The myriad of authorization options can be confusing, however. We've settled on OAuth 2.0 for most situations. When OAuth is brought up, many people will think of the single-sign-on flow in a browser, with the associated redirects and permission dialogs. This flow is widely used, but not always a good fit for first-party applications, or machine-to-…
As we race towards the date of my presentation at this October's Digital PM Summit, I'm working to crank out the remaining posts in my series that started after I first presented on the topic of growth at Drupalcon Austin. This seventh post touches on one of the biggest debates of the last decade in digital and software project management: Agile versus Waterfall.
At Metal Toad we use Capistrano to deploy our projects to their respective servers. Normally this is done with a configuration file for each stage (Dev, Staging, QA, and Production) that contains a list of servers. Below is an example of one of those files.
Many years ago I got into skateboarding, soon after, that lead to hip hop. Something about the two seemed to be synonymous around that time, or perhaps it was just my area (Metro Detroit).
I am now within a couple days of having survived as a Junior Developer at Metal Toad for 10 whole months. To celebrate, I considered starting my first blog post with a well worn cliché about the passing of time and the having of fun. Fortunately I hold my literary career to a much higher standard. However in all honesty, if I had stooped to such a pathetic low, it would have been a completely accurate description of my time here. It has been an incredibly fun experience working at Metal Toad…