You're free to come up with a better example. The point is that dependencies have behavioral properties that software depends upon. We can write tests for those behaviors. Mocks that are correct and remain so should implement those same behaviors we expect from the prod implementations of those dependencies.
This sounds more like metrics than a log statement.
For me logs should complement metrics, and can in many instances be replaced by tracing if the spans are annotated sufficiently. But making metrics out of logs is both costly and a bit brittle.
> Even if nothing changes, you can run into trouble. Norwegian PNs have your birth date (in DDMMYY format) as the first six digits. Surely that doesn't change, right?
I guess that Norway has solved it in the same or similar way as Sweden? So a person is identified by the PNR and for those systems that need to track a person over several PNR (government agencies) use PRI. And a PRI is just the first PNR assigned to a person with a 1 inserted in the middle. If that PRI is occupied, use a 2,and so on.
It seems like they have reliability issues; if I read their status page correctly, they have incidents every few minutes. Or how should one read their all green page?
I was a little taken by the state of American trains if this was true. Two days would mean at least 36h for me and that in turn would mean that the trains would have an average speed of 20mph.
But it turns out that it takes 20h, so twice that speed. Still not fast but better. With that duration it also seems unlikely that the speed is kept artificially low to allow some sleep on the train, as is very common in Europe.
> Overall: maybe this wasn’t the right way to engage
Lex Livingroom. If you are among friends you can surly criticize a sweater, but if you come barging in uninvited and criticize the same sweater, you're in for a bad time.
This excludes a lot of cases, like just a simple postgres where reads are done from a replica.