The DevOps Database

Pete Pickerill

Subscribe to Pete Pickerill: eMailAlertsEmail Alerts
Get Pete Pickerill: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Pete Pickerill

Recently, the Agile Austin DevOps SIG invited Datical to talk about the impact of DevOps practices on database change management. This was a great opportunity for us to talk to folks about our approach to managing application schema change in IT organizations that have moved or are moving to more responsive and agile planning, development, and delivery processes.  It was a lively discussion with some great feedback from the audience. In framing the discussion, I relied heavily on "The Three Ways" of DevOps.  The Three Ways are the principles that underpin the DevOps patterns that Gene Kim discusses in detail in his novel "The Phoenix Project" and in the"The DevOps Cookbook", written by John Allspaw, Patrick Debois, Damon Ewards, Jez Humble, Kim, Mike Orzen, & John Willis.  Here's a quick summary of The Three Ways: The First Way: Systems Thinking - This Way stresses... (more)

The DevOps Database | Part 2

In my first post in this series, I discussed the underpinning principles of all DevOps patterns as eloquently stated by Gene Kim, author of "The Phoenix Project."  In this post I'd like to dig a little deeper into The First Way.  As a refresher: The First Way: Systems Thinking - This Way stresses the performance of the entire system of value delivery.  Instead of becoming laser focused on the part of the process for which an individual or team is responsible, the individual or team works to understand the entire process from requirements generation to customer delivery.  The goa... (more)

The DevOps Database | Part 4

In the final post in this series about bringing DevOps patterns to database change management, we’re going to discuss the Third Way.  Here’s a refresher on the Third Way from the introductory post in this series: The Third Way: Culture of Continual Experimentation & Learning – This way emphasizes the benefits that can be realized through embracing experimentation, risk-taking, and learning from failure.  By adopting this kind of attitude, experimentation and risk-taking lead to innovation and improvement while embracing failure allows the organization to produce more resilient p... (more)

DevOps and SQL Review By @Datical | @DevOpsSummit [#DevOps]

Automating SQL Review to Save Time and Money I’ve spent the majority of my tech career in startups.  I love the fast pace, the opportunity to learn new things, and the sense of accomplishment that comes from bringing a successful new product to market.  I began my career in Quality Assurance.  In startups, you rarely enjoy the low ratio of Developers to QA Engineers that you might in a large enterprise.  As a QA engineer in a startup, your inbox is always much more full than your outbox. You are the last gate before the next release so you’re always under the microscope. In an e... (more)

The DevOps Database | Part 3

In the third post in this series, I’d like to talk about the Second Way of DevOps: Amplifying Feedback Loops.  Here’s a refresher on The Second Way from my introductory post in this series: The Second Way: Amplify Feedback Loops – This Way deals primarily with facilitating easier and faster communication between all individuals in a DevOps organization.  The goals of this step are to foster better understanding of all internal and external customers in the process and to develop an accessible body of knowledge to replace the dependence on expertise scattered across individuals. ... (more)