Welcome!

Automate the boring stuff. Simplify the tough stuff.

Pete Pickerill

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


Top Stories by Pete Pickerill

All too often, database development is an afterthought in Agile Development.  Developers perfect how best to implement a solution in code, but tend to spend too little time on representing that solution in the Database.  This is unfortunate, given that 65% of your change requests require changes to the application schema, according to independent research conducted by Simon Management Group.  This finding implies that Database changes are every bit as important as the Application Code, and should be treated as tier-one artifacts in your release process. At Datical, we typically find that development organizations process Database changes in one of two ways: Developers author Database changes, which must then be reviewed and approved by the DBA team, or Developers submit Database change requests to the DBA team, who then author changes. Either scenario would work fi... (more)

Mainframes, WebSphere Config and Databases, Oh My!

by Robert Reeves, Datical CTO: On August 14th at 1:00 PM EST, Eric Minick (IBM DevOps Evangelist) and I will be hosting a webinar on automating deployments beyond just copying files around your datacenter.  We’ll be discussing the intricacies of Mainframe, WebSphere Configuration, and Database Application Schema Migrations. There’s been a lot of talk about infrastructure as code and we agree!  The days of keeping environment information in a printed document and between one’s ears are over.  So, let’s do the same for our Mainframe, WebSphere, and Database automation! Pushing com... (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)

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)

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)