Self Expression

 I must, at some deep cognitive level, be a product of my environment. I have no family history here, but I was born and raised in Devon and I've lived here for most of my life. The hedge that I'm looking after had been right here for about 400 years. As part of looking after the hedge I've bought myself a billhook. I chose the one that seemed most practical. It's not too big. It's only sharp on one side so that you could hit the back of it, and the handle can be shaped to only be held one way round. It also has a sort of exaggerated choil so that you could tie a lanyard around the blade.

I found out after I'd bought it that this is the "DEVON" pattern of billhook. At some stage, my thinking must have become Devonish enough that I can pick the billhook out of a lineup despite never having seen one before.

Richard "Nature or Nurture" B

Til Daddy Takes the T-Bird Away

 Type 1 fun is something that you do voluntarily and it's enjoyable in the moment. My best example would probably be playing on stage when you're not nervous, you're playing well, the rest of the band is playing well and the crowd is dancing. I have type 1 fun at track days after all the preparation is done and nerves have subsided. There is also plenty of type 1 fun available at rock climbing.

Type 2 fun is something that you did voluntarily, that you didn't enjoy it while it was happening, but that you're happy with after it's finished. I can think of some motorcycle and car journeys that were horrible in the moment, but I was delighted to have done them. I did a climb recently that was fun in the first half, but the rest was so difficult and frightening that it was deeply unpleasant. I actually got down from having done it and said "that stopped being fun half way up" however I was really pleased with myself for having done it.

And then there's the much more esoteric Type 3 fun, which is neither enjoyable in the moment nor in retrospect.

Richard "something that everybody wants to have read and nobody wants to read" B

makefile.sh

Let me tell you about my deep, pure and abiding hatred for the Apache Maven build tool.

There is machine code, which tells a microprocessor exactly what to do in terms of bits and addresses.

There are procedural languages in which you tell the computer what to do. You have useful constructs like loops and logic, and named variables to store values.

There are functional languages. I'm oversimplifying it, but generally you tell the computer what value you want and it calculates it for you without any of the grubby details of explaining how it should calculate it. I class SQL as a functional language. In its purest form it has no looping structures and no variables. You tell it what you'd like to know and it decides how to get the relevant data from the disc and how to combine and process it for you. Many are the times that the query planner has come up with a deeply suboptimal order of operations and I've been powerless to persuade it to do it better. You get the right answer, but very slowly.

And then there's Apache Maven, which is supposed to make working on large software projects easier. You tell it where some things are and what you'd like to achieve. It then does what IT THINKS YOU SHOULD HAVE WANTED to do. I've spent far to long this week trying to control what an artifact was called, with persistence and the help of google, Stack Overflow, a very skilled senior engineer and an AI, we've come to the conclusion that no, you just can't do that.

Richard "And the Docs Are Terrible" B