Field notes

Written on the floor, between pages.

No thought leadership, no predictions for next year. Things we got wrong, things we fixed, and the occasional piece of regulation explained in words a person can act on.

Everything so far

Three articles, and no schedule for the next one

We publish when there is something worth writing down. A blog that posts weekly whether or not anything happened is just another channel nobody reads.

The alert nobody reads is worse than no alert at all

A channel with four hundred notifications a day is not monitoring, it is wallpaper. How we cut one client from 380 alerts a day to 6, why their outage count went down rather than up, and the four rules we now apply everywhere.

Synthetic checks vs real user monitoring: use both, page on one

RUM tells you what happened to people who were already there. Synthetics tell you what will happen to the next one. At three in the morning that difference decides whether anyone finds out — and only one of them should ever ring a phone.

NIS2: what actually changes for a 60-person company

Most of what has been written is aimed at enterprises with a compliance department. Here is the short version for a mid-sized company, including the reporting clock that starts running 24 hours after you notice.

Demo note: Nightshift is an invented company. These articles were written for the demo to show how a content-heavy B2B site holds together — the client anecdotes are illustrative, though the technical and regulatory substance is not made up.

Or skip the reading and look at the timeline

Sixty seconds with a slider will tell you more about why this matters than any of the articles above.

Open the timeline