State management explained

Wed, 24 Sep 2025 07:00:03 +0000

State causes a lot of complexity, is the main source of (weird) bugs and introduces high cognitive load to software engineers so it is important to handle it with care. In this article we go into the problems of (mutable) state, how and when to use mutable and immutable state, and how we can use our type system to prevent us from making mistakes.

Why State Management Matters

Most bugs out there are in one way related to state. Some examples are things like race conditions, null pointer exceptions and inconsistent behavior. And let’s not forget the famous quote “Have you tried turning it off and on again” that seems to fix most problems. This tends to work because resetting the device or software causes it to start with a new fresh state. Mutable state can also cause headaches when doing concurrent programming, but because most developers do not write multi-threaded software on a day to day basis, let’s focus for now on problems that are always present: complexity and high cognitive load.

Ties van de Ven on JAVAPRO International

State management explained

Why State Management Matters