CQRSLaptopTablet
Allow me to wax philosphical for a moment with an observation about where computers and their operating systems are heading.

In the world of software development CQRS = Command Query Responsibility Segregation, which in its simplest sense recognises that it's sometimes better to use a different mechanism for reading data than it is for writing it. See Martin Fowler's exposition of the concept if you want to know more, but this post isn't actually about software development at all!

I reckon that we're at a critical juncture in the evolution of personal computing devices and that the CQRS principle is necessarily coming to the fore to save the human race.

Tablet computers are taking the world by storm, in case you hadn't noticed. Apple could barely make enough iPad Minis for me to be able to get my wife one for Xmas, though I did manage it at the very last minute, and shortly thereafter bagged one for myself too. Frankly it's bloody brilliant, but I use it predominantly for consuming rather than creating and I'm far from alone. This is partly because the human populace is inexorably dumbing down towards being fat blobs with brains wired directly into the 'net, consuming inane banter, amusing picture of cats and the latest celebrity news, 140 characters at a time. But that aside, it's just not very pleasant to write large quantities of text, manipulate images or perform other expansive creative works by prodding a tiny screen. Or even a big screen.

To write software, construct lengthy blog posts (ahem), edit movies, sequence the human genome or design great buildings requires a proper computer! On that basis I posit that there will always be a place for desktops and laptops, or indeed whatever replaces them but which necessarily has a non-trivial input mechanism. I genuinely worry that the market for serious computers will be increasingly neglected by the manufacturers, refocussing as they are on the mass consumer market, inevitably leading to the downfall of humankind. Perhaps I exaggerate – at least I hope so.

Now I've never used Windows 8, indeed I shudder at having to use Windows 7 on a daily basis at work, but I understand it represents something of a chimera. It is best known for its shiny, touchy, slidey 'Metro' UI, beckoning your greasy fingers to caress its tiles. However it also allows you to fall back into the more staid world of traditional Windows where presumably you can get some proper work done, as long as you have a keyboard and a pointing device other than your finger. I understand critics are conflicted about this hybrid approach, but it's CQRS writ large and may therefore be the way forwards. One way or another, at least some people will need to create great works. I do hope to be one of them, and to have the equipment to be able to do it.

BrickPath 2

I have a fair amount of lawn in my garden, which is looking pretty ropey right now, but I'm working on it! However I'm intending to convert a lot of it to more intriguing beds and paths. This project details one little part of that grand plan. In the picture above, I've removed the turf from a corner, which originally had just a narrow bed at the back against the trellis.

BrickPath 3

My plan was to put a curving brick path through this new area, leaving an eye-shaped island that will probably host a small tree and other planting high enough and rumbustious enough to make the path a little voyage of discovery. A very little voyage, but adding much-needed intrigue.

I started by using the garden hose to experiment with the shape of the path, using some bricks to get the width right. What a beautiful shape!

Those bricks, and indeed all the bricks I will use, are from the rear chimney on the house, which was removed in a recent loft conversion (the chimney, not the house). They are a mix of old handmade red clay bricks and nasty moulded modern things, but they have some character, including sooty marks, and I think mixed up they're going to look the part.

I'm not sure how well they will survive the harsh winters that seem to be the new normal. I strongly suspect they will suffer from frost damage and it will be interesting to find out whether it's the old or new that perform better. I have plenty left to repair the damage. For the record, ideally you'd use engineering bricks, but I don't have any and I feel it would lack the charm of a crumbling old brick path.

BrickPath 4

Having established the basic shape and scored a mark in the soil with the edge of a spade along the hosepipe, I dug it out about a brick deep plus a couple of centimetres for the sand. I also added 5cm or so on either side to give room for manoeuvre.

Theoretically I should use pegs in the ground, string and spirit levels to establish a perfectly level, flat path, but that's just not my style, and the two ends are not at the same level anyway. I used a couple of bits of straight wood and my eye to make sure that the soil bed was basically level with no major local bumps or hollows. Again I invoke 'rustic' as an excuse for my slapdashery.

BrickPath 5

Do you know why sharp sand is called sharp sand? Because the individual grains are all knobbly and 'sharp', compared to non-sharp sand which has smooth, rounded grains. This helps them to lock together and form a firm base. I've used four bags of sharp sand and with the aid of a rake and a piece of wood the width of the path dragged over it, I've turned it into a smooth base ready for my bricks. I spent quite a while trying to get this right, as it will be reflected in the final result.

By the way, I bought six bags of sand from Wickes for the grand total of £10.86, and that was my entire spend on this project. The rest is bricks and tools I already had, and my own labour.

BrickPath 1

I figured it was best to lay one whole run the length of the path, to establish and tweak the basic curve. Then of course the subsequent runs are a bit longer each time around the curve, so we need half-bricks here and there to keep a good pattern going.

I used a bolster chisel and club hammer to cut the bricks by hand, which takes a bit of technique, a certain amount of practise and a lot of patience, especially when it's raining and you can't see through your goggles (you don't want brick chips in your eye). I think most people would find this the most challenging part of the project if they haven't done it before. You can get machines to do it nicely and with no effort on your part, which would be worthwhile if doing anything much bigger. A straight path would only require half-bricks at the ends of course.

BrickPath 6

Once I'd got all the bricks down it looked pretty good, but only then did I fork over the beds either side, being very careful not to disturb my new path. I had been agonising over whether to do that first or last. I feared that if I did it first I might loosen the firm bed for my path, compacted nicely as it was under the old lawn. Also, it would have made working around the path and seeing the edges a lot harder, so I'm glad I did it this way around.

BrickPath 7

Finally, I did that digging of the compacted soil, and packed it up to the edge of my bricks, ready to receive plants. Then I brushed more sharp sand into all of the cracks to finish off the path itself. That took a surprisingly long time and a few goes as the bricks settled and new holes opened up. Using very dry sand really helps it to fall down those cracks so I dried mine out in the sun before using it.

I'm very pleased with the result, but time will tell whether it's really any good. Next project is the planting either side of it.