Skip to content
Aniefiok Akpan

A problem I struggled with

Two weeks on a deadlock that turned out to be a lock-ordering mistake in code I had reviewed twice.

, 6 min read

Two weeks on a deadlock that turned out to be a lock-ordering mistake in code I had reviewed twice.

Filed under

  • Concurrency
  • Debugging

Related

  1. Journal, , 5 min read

    The bug that only appeared on Fridays

    A cache warm-up running on a schedule nobody remembered setting. A short story about assumptions hidden in configuration.

    • Debugging
    • Redis

  2. Article, , 12 min read

    Java concurrency, the parts I keep relearning

    Executors, CompletableFuture and virtual threads — written down so I stop rediscovering the same three pitfalls.

    • Java
    • Concurrency

Next

Have a system worth arguing about?

If this note raised a question, or you would have designed it differently, I would like to hear it.

Start a conversation