Writing from the work.

A metadata-driven internal dashboard that made report-parameter changes safer, more auditable, and easier to evolve across more than 150 reports.

An internal playground where analysts could test assessment-rule changes without production access or one-off engineer scripts.

A closer look at the KrakenD work: how gateway configuration and deployment were structured across environments, and the trade-offs involved in making those changes repeatable and reviewable.

Moving COBOL-era batch processing toward observable, idempotent ETL while keeping the remaining mainframe work in view.

Why a short system assessment helps before a team commits to a rewrite.

How to tell when repeated local fixes are no longer reducing the problem and a known-good rebuild deserves consideration.

A triage method for deciding which technical sources deserve deep reading, a summary, reference status, or release.

Chapter 1: Modern API Traffic Management

Originally published on Medium — Chapter 1: Modern API Traffic Management