Author • 10 Posts

Pete Hodgson

Thumbnail for A Simple Guide to Chaos Engineering
Industry Trends

A Simple Guide to Chaos Engineering

Chaos engineering involves injecting failure into production systems, as a way to proactively validate that those systems handle a degraded environment.

Pete Hodgson
Thumbnail for Monitor Your Feature Flag Performance with New Relic
Code

Monitor Your Feature Flag Performance with New Relic

By pushing feature flagging metadata into New Relic, you can understand the impact of a feature change across any metric you care about, in real time.

Pete Hodgson
Thumbnail for Monitor Your Java Application with New Relic
Code

Monitor Your Java Application with New Relic

We’ll take a quick look at using New Relic to sleuth through a production incident, and then walk through setting it up for a Spring Boot web service.

Pete Hodgson
Thumbnail for You Might Not Need Continuous Deployment
Industry Trends

You Might Not Need Continuous Deployment

Of the teams I spoke with who are practicing Continuous Delivery, the vast majority were not practicing Continuous Deployment. Let’s explore why that might be.

Pete Hodgson
Thumbnail for Continuous Delivery in the Wild: 4 Successful Practices
Industry Trends

Continuous Delivery in the Wild: 4 Successful Practices

There’s more than one way to succeed with Continuous Delivery. In this article we summarize four of the common tactics various organizations employ.

Pete Hodgson
Thumbnail for Death of the Release
Code

Death of the Release

As our software development processes have evolved we’ve mostly said goodbye to the idea of defined product versions. Many modern product delivery teams are taking this a step further – even the concept of a “product release” is starting to fade. Instead our products are becoming a fluid, rapidly evolving set of features, assembled uniquely for any given user.

Pete Hodgson
Thumbnail for Managing Feature Flag Retirement and Technical Debt
Code

Managing Feature Flag Retirement and Technical Debt

Teams working with feature flags usually come to the conclusion that a large number of active flags isn’t necessarily a good thing. While each active feature flag in your system delivers some benefit, each flag also comes with a cost. I’m going to explain those costs, such as cognitive load and technical debt, and explain how to avoid them.

Pete Hodgson
Thumbnail for Management and Categorization of Feature Flags at Scale
Code

Management and Categorization of Feature Flags at Scale

Feature flagging systems can sometimes become victims of their own success. The benefits of feature flagging along with the broad applicability of the technique can lead to rapid adoption within an organization, and pretty soon the number of active flags can start to feel overwhelming. One way to keep your feature flags manageable is to introduce a categorization system.

Pete Hodgson
Thumbnail for Managing a Monolith Breakup – Stateful Services
Infra

Managing a Monolith Breakup – Stateful Services

This is one post in a series about managing the breakup of a monolithic architecture into a small service. In the first post of the series we looked at some fundamental techniques which allowed us to perform this sort of broad architectural shift as a series of small, safe steps. We started off…

Pete Hodgson

Stay up to date

Don’t miss out! Subscribe to our digest to get the latest about feature flags, continuous delivery, experimentation, and more.

Ready to get started?

Start using Split for free today. No credit card required.