Category Archives: Culture

Church governance and cultural mismatch

About ten or twelve years ago, we used to go to a Baptist church (which, note well, indicates a very different denomination in the UK from what it is in the US). Unlike other churches we’d been members of, it had a rigidly democratic governance structure — something that had both pros and cons. Once a year, there would be a business meeting where members of the congregation would all come and hear proposals from the church leader and vote on them.

Continue reading

Advertisements

Here’s what post-truth politics looks like

I came across an extraordinary short (18 seconds) video, which I will transcribe:

Krishnan Guru-Murthy: The Conservative MP Ben Bradley is in the House of Commons. He voted to Remain, then became a Brexiteer, then voted against the deal, then voted for the Deal, then said he’d struggle to back the deal again, but now says he will back the deal. Ben Bradley, why do you get to change your mind?

Ben Bradley: I haven’t changed my mind.

Continue reading

A Thursday in December

Starring Gandalf the Grey.

It’s probably best thought of as a sound collage, and one that I find strangely relaxing.

Continue reading

Facebook’s and eBay’s monopolies are very different from, and scarier than, Google’s. But what about Amazon?

People talk a lot about “Internet monopolies like Google and Facebook”, as though they are the same kind of thing. Even as astute a commentator as Tim Harford (alias “The Undercover Economist”) lumps them together in statements like “Google dominates search; Facebook is the Goliath of social media; Amazon rules online retail”.

But these “Internet monopolies” actually fall into completely different categories.

Google dominates search because it offers the best general-purpose search engine currently on the market.

Continue reading

“What should I prioritise that ahead of?”

My colleague Jason Skomorowski and I (and many others) work together for Index Data on the FOLIO library services platform. There is a ton of work to do — fascinating work at that, so that I often find myself working on it in the evenings, not because of deadline panic but just because it’s fun to do.

Often when a request for a new feature comes in — whether it’s user-visible functionality, or more exhaustive test coverage, or better continuous integration support, or improvements to documentation — Jason often asks this key question:

“What should I prioritise that ahead of?”

Continue reading

Rebooting Linux with every new kernel

Back in the early 1990s, when I was working on Sun’s Unix boxes, it was routine for them to be up for multiple years at a time. A reboot was a big event.

Now here we are in 2017, and every single update to the Linux kernel — of which there are several every week — requests a reboot.

Continue reading

All you need to know about version numbers in one page

A colleague asked me a couple of days ago: “So we roll version numbers forward only with breaking changes, right?”

Well, the best approch for any sane project in 2017 is to follow Semantic Versioning. That is not a long document to read, but here is a summary. In a nutshell, version numbers have three facets, major.minor.patch.

  • If your new release breaks something that used to work, increment major.
  • If your release adds new functionality that clients might want to rely on, increment minor.
  • If your release only fixes a bug, increment patch.

Then dependencies of the form “^3.4.2” (for example, in package.json for a JavaScript project) mean “that version, or anything backwards-compatible with it”. Which means the same major version number (3 in this case) and the same or better minor number (4 or higher); or, if the minor version is the same, then the same or better patch level (2 or higher).

This is an excellent, simple and battle-proven system.

However. Continue reading