01Performance / Kraken Technologies
Make the database do less work.
63 s → 16.5 msRecorded SQL execution benchmark
- The problem
- An operational message view combined and sorted every matching record before taking a single page of results.
- What I changed
- I bounded each ordered input before combining the results, and avoided the union when only one message direction was needed.
- Unbounded inputs
- Limit before combining
- Read one page
The engineering principle
Find the unnecessary work before adding more infrastructure. For data-heavy systems, the shape of a query can matter more than the size of a server.
These are SQL execution timings, not whole-page latency. Separately, I removed 11 redundant indexes and reclaimed approximately 1.43 TB across two production estates.
Read the full case study ↗
02Correctness / Kraken Technologies
Keep bad data out of settlement.
≈483k / monthInvalid updates blocked across two clients
- The problem
- Billing validation and industry submission run asynchronously. A reading could leave the system before a separate process quarantined it.
- What I changed
- I added reading-validation safeguards and persisted suspect-reading state so a separate submission worker could see it. A configurable delay also gives asynchronous billing time to run.
- Validate the reading
- Persist shared state
- Gate submission
The engineering principle
Correctness has to survive the boundary between processes. A local flag is not enough when another worker makes the next decision.
The monthly count is the validation result recorded in my CV. It does not measure the separate submission-delay or migration-repair changes.
Read the full case study ↗
03Controlled operations / Kraken Technologies
Give production work a visible lifecycle.
Request → resultPermissioned execution with captured output
- The problem
- Launching a background command is only part of the job. Competing requests must not run equivalent work concurrently, and failed work must not stay marked as running.
- What I changed
- I built the Django models, execution logic, Kubernetes integration and UI: explicit permissions, ordered row locks, captured output and reconciliation with the actual Job state.
- Permissioned request
- Claim + Kubernetes Job
- Output + reconciliation
The engineering principle
Make it possible to explain who can run work, what happened and how failures are recovered. Operational control belongs in the system itself.
Delivered across four implementation stages. The source supports the workflow and concurrency safeguards; it does not quantify adoption or time saved.
Read the full case study ↗