Datanamo

Everything is measured. Nothing is assumed.

Every system ships with counters, alerts and reports because decisions about data get made from data. Every claim in a status update is one of four things: known, estimated, unknown, or an opinion labelled as one. Watch a claim get sorted below, or step through the examples yourself.

A claim arrives

“The price floor raised order value.”

Is there evidence?checking

Average order value up 16 percent, 30 days before and after, from the settlement report.

  • I know.

    backed by a query, a log line or a test

  • I'm estimating.

    a range with its assumptions

  • I don't know.

    and what it takes to find out

  • I think.

    an opinion, labelled as one, with a way to test it

  1. I know.

    Backed by a query, a log line, a report or a test. The number and where it came from are in the message.

  2. I don't know.

    Said early, followed by what it would take to find out and how long that takes. Never papered over with confidence.

  3. I'm estimating.

    A range with the assumptions spelled out, replaced by a measurement as soon as one exists.

  4. I think.

    Welcome, as long as it is labelled as an opinion and comes with a way to test it. What is not allowed is an opinion dressed up as a fact.

What measured means in practice

These are habits, not a methodology. They are what lets one engineer run several production systems and still know which one earned what last month.

Every change ships with a baseline

Before a price rule, a feed change or a new channel goes live, the number it should move is written down with its current value. Thirty days later the same number is read again. That is the report, not a feeling about how it went.

Counters on everything that moves data

Every crawler, sync and import reports rows read, rows written and rows rejected on every run. A run that writes zero rows is not a quiet night, it is an alert.

Slow pages get a query plan, not a guess

When something is slow the first step is the database's own explanation of what it did. Indexes are chosen from that, and the before and after timing goes in the commit message.

Vendors and APIs are measured too

Error rates, quotas and spend per vendor are tracked per day. A vendor that degrades gets caught by the alert, not by the customer, and a budget that is about to overrun stops the pipeline before it does.

Reconciliation closes the month

Orders, settlements, invoices and e-invoicing are matched across every channel, so the margin figure is one that survives an accountant.

Reports are written for the owner

Monthly: what changed, what it earned or saved, what broke and how it was fixed, what is next. One page, numbers first, no adjectives.

Things I will not do

Each of these has cost someone money at some point. Saying no to them is part of the service.

  • Ship a pricing change without a before and after.
  • Call a migration done before every row is verified.
  • Give a date without a range and the assumption behind it.
  • Let a model send a customer message without a person approving it.
  • Report a number without saying where it came from.
  • Present an opinion as a fact.

Want a status update written this way about your own system?

Start a conversation