correlation

NPS is first and foremost a marketing tool for Bain & Co to sell expensive consultants and def not "the one question to ask".

Several marketing scholars have pointed out the psychometrically undesirable properties of the metric and there is conflicting evidence on e.g. the metric's predictive validity, e.g. in relation to company success

(All in all that old HBR marketing article contains very little details to back up the claim that it is a good and valid metric.)

If you can go with behavioural outcomes for measuring success, e.g. purchases, I think that that will always be more powerful than what a user says in a survey.

And if you can then causally link (e.g. through experiment) something you can influence (e.g. some dimension of "UX) to that outcome you actually have a quite good decision tool too.

NPS does not provide that.

I have come up with a slogan for Jenkins: "Jenkins - The butler that does not hesitate to do a disservice".

It is currently the most brittle piece of infrastructure we run, with jobs spiralling out of control and slaves crashing with cryptic exceptions. Add to that a horrible plugin ecosystem (tried to install the Slack plugin, it crashed all builds and our webhook endpoint). Add to that groovy (I don't feel like becoming an archeologist).

Gosh, can't someone just build a lightweight ci/cd system ontop of e.g. k8s jobs?

Or should we just give up and do managed ci/cd?

Can someone please explain the psychology behind liking this kinda stuff? I've probably watched that Austrian Kowloon documentary a handful of times.

Martin Kleppmann's "Designing Data-Intensive Applications" is one of the best books in computing I've read in a very long time (and thus the best book of 2017).

It would be interesting to see how Tesseract holds up against this.