Symbolic Forest

It’s fair to say that I don’t always consciousnessly do the right thing in life. I’m getting better at that, and maybe there will be more posts to come on that at a future date, but historically I’ve always been either a wee bit too hesitant, or a wee bit too eager to not resist the wrong thing.

Still, it’s nice to know that this doesn’t always apply to my subconscious brain. Last night I was peacefully sleeping, going through a rather strange and incoherent dream when I suddenly became aware than one of my worst fears was on its way. I suddenly became aware, through a quick flash of an image, that a horde of zombies were on their way and were about to break into my dreamscape.

Zombies are one of my worst fears. Any dream with a substantial amount of them would quickly become a nightmare, and a bad one. My brain, though, knows this. And so at the first flash of them last night, I found myself suddenly hauled out of sleep and checking the time. It was just gone 3am: being awake just gone 3am isn’t ideal, and I knew I might not properly get back to sleep again, but it was better than than the alternative. Better than being stuck inside a nightmare still. I should, I think, be giving my brain a bit of a pat on the back.

Keyword noise: dreams, nightmares, instinct, subconscious, zombies.

A few weeks ago, I noted it was sixteen years since I first started writing this blog. Well, today, it’s a whole year since I relaunched it, as something of a lockdown exercise. It had taken most of my spare time in the summer, to go through all of the old posts, edit them, redesign the sight, and get the whole production pipeline up and running.

Since then there have been a hundred and forty-two posts, including this one; about mountains, beaches, trains, castles, cemeteries, trains, Lego, trains, computing, and trains. Have many people read them? No, probably not. That’s not really the point, though: not whether people read them, but whether I enjoy writing them. I have. So doing it has been worth it.

Despite it being the pandemic years, still, a lot has happened and a lot has changed over the past year. There will, I am sure, be more changes over the next year too. We won’t know, until they happen.

Keyword noise: blogging, anniversary.

Since changing jobs, I’ve been going for early morning walks most workdays. For about an hour or so, I’ve been walking up to the woods overlooking the village, or following the riverbank and canalbank, or walking across the fields to the next village and back. It’s a really good way to start the day. When I go to visit The Mother, though: well, there aren’t really any interesting places to walk and back in an hour. There aren’t actually very many public footpaths outside the village itself; there’s no river, and the woods are too far away. I was at a bit of a loss.

“Why don’t you drive down to the beach and go for a walk there?” suggested The Cute Accountant.^* It made complete sense. The beach is only 15 minutes drive away from The Mother’s house; I could easily stretch my morning walk to be 90 minutes without really having to rush. So, since starting the new job, when I’ve been at The Mother’s every morning I have gone down to the beach for a walk on the sand.

Cleethorpes Prom is your fairly standard seaside prom: pier, arcades, amusement rides and chip shops. All the signs of seaside civilisation, with the sand raked daily and the high concrete wall of the prom separating town and sea. If you head a couple of miles south, though, down past the leisure centre and the miniature railway to where the holiday parks start, then things feel much more remote. A broad band of salt marsh separates the dry land from the open water, and you can wander along the tideline or through the marshes feeling completely apart from the world, feeling as if it is some ancient unpopulated coastline. Look the other way, though, and behind the freewheeling seabirds, you can see the lighthouse on the far side of the river mouth, and always ship after ship standing at anchor and waiting for their upstream pilot.

At low tide, there is a vast expanse of rippled sand and mud, cut across by channels and with endless slight variations in height. When I was a kid, the dangers of the beach were always drummed into me heavily. Never go out too far. Never cross one of the channels. You’ll get cut off. The Mother would tell me lurid stories from her days as a 999 operator, of people finding bodies washed up on the shore after going out at low tide and getting confused by fast-descending fog. “The most dangerous beach in the country,” she’d said, which I’m not sure is the truth. Nevertheless, you have to be careful going down to the low tide line, always sure all the water you see is flowing out, not back behind you. If you do go all the way, you find the remains of shipwrecks, the gaunt ribcages of old wooden ships sticking stumpily out of the sand.

Navigating all the way along the tideline, without heading back to the nearest concrete path, can be tricky. The outflow of one of the local becks cuts across the sand, in a surprisingly deep channel. At low tide it can be crossed with care, if you can find a shallow spot, if you don’t mind getting your feet a little wet and having to jump over the deeper parts. At higher tides, you have no chance, and have to find a way to cut back through the marshes, themselves riddled with deep, steep-sided channels of water with thick mud at the bottom. It’s far too easy to slip over at their edge and end up with a very wet and muddy arse. I hate to think what the marshes are like to navigate at the very highest tides: I suspect I’d have to sit on the thin line of dunes at the seaward edge of the marsh and wait the tide out a few hours. It wouldn’t be much of a hardship.

I could keep on here posting photos of the wilder parts of the beach, much as I could sit for hours on the dunes listening to the waves breaking. I’m going to pause this post here, though, before coming back again soon with more pictures and more to say. Think of it as the tide going out and returning again.

* For the really long-term readers: it’s career progression.

Keyword noise: Cleethorpes, beach, coast, river, estuary, Humber, Lincolnshire, North East Lincolnshire, The Cute Accountant, shore, shoreline.

Last January, I wrote about how I keep track of ideas for topics to write about. I said, when I have an idea, I create a “ticket” a bit like a “bug ticket” in a software development process, to keep track of it. What I didn’t say, though, is something that applies to writing ideas just as much as to bugs: it’s important to be descriptive. Things you think, now, are always going to be seared in your mind, will be over and gone in a few hours. Unfortunately, when I create a “writing ticket”, I will often only write down a few words and rely on my memory to know what the post was actually going to be about. When I come back to it later: baffled.

Take, for example, an idea I also wrote down back in January, a few weeks before writing that post. “Post about the fast-flowing waters of Stockholm.” Post what about them, exactly? I have no idea.

It’s true that the centre of Stockholm does have impressive fast-flowing water, a rushing, churning torrent that pours constantly in two streams, either side of Helgeandsholmen, the island taken up almost entirely by the Swedish parliament building. When I visited Stockholm, I walked through the old town and down to visit the museum of medieval Stockholm which lies underground, beneath the gardens in front of the parliament. When I reached the narrow channel of water separating the parliament building from Stockholm Palace, I was shocked and amazed by the speed and power of the water. It flowed from east to west in a solid, smooth-surfaced grey-green mass, as if it had an enormous weight behind it. It felt dangerous, unstoppable, and irresistable.

I already knew that Stockholm, and the Baltic in general, doesn’t really believe very much in having tides. Stockholm’s harbour is technically seawater, but there are many kilometres of archipelago between the city and the open sea, and to get to open ocean you have to go all the way around past Copenhagen and the tip of Jutland. Because of that, the Baltic isn’t particularly salty and doesn’t have very dramatic tides. This couldn’t, then, be a tidal flow. It took maps to show what it was.

The above extract from OpenStreetMap is © OpenStreetMap contributors and is licensed as CC BY-SA.

You can see how Stockholm is built around a relatively narrow point in the archipelago. What you can’t really see at this scale, though, is that all the channels of water to the right of the city centre are the main archipelago, leading out to see, but the channels of water to the left of the city centre are all part of Mälaren, a freshwater lake some 120km long and with an area of over a thousand square kilometres. Most significantly, its average altitude is about 70cm above sea level. That slight-sounding difference adds up to roughly 800 billion litres of water above sea level, all trying to flow downhill and restricted to the two channels, Norrström and Stallkanalen, the second narrow, the first wide, around Helgeandsholmen. Norrström, in particular, is a constant rush of choppy white water.

Why only those two channels? Although you can’t really see from the map, the other paths of blue that look like channels of open water, around Stadsholmen and Södermalm, were long ago canalised, blocked off with large locks. The two northernmost channels are the only free-flowing ones.

So, you might be wondering, what was the point of this post? Was there going to be some deeper meaning I had uncovered, some great symbolism or relevance to my everyday life? Frankly, it’s entirely possible, but I have no memory at all of what I was thinking when I wrote that note originally.

Right now, it’s tempting to say that sometimes, instead of trying to understand life and everything around you, instead of trying to predict what will happen and what the best course of action to take will be, it’s better just to sit back and ride the rollercoaster, and tht the sight of the massive onrush of water through the centre of Stockholm made me think of just jumping in a small boat and shooting the rapids without worrying about what happens next. Equally, I might have been thinking of how you can find such a powerful force of nature right in the heart of somewhere as civilised as a modern European capital city. For that matter, it could have been a contrast between how placid, still and mirrorlike the waters of Mälaren a few hundred metres away outside Stockholm City Hall are, compared with the loud, rushing, foaming rapids we’re talking about here.

To be honest, I really don’t know. I know which of those thoughts seems most apt right now, but it might not even have occurred to me in January. At least, now I’ve written this, I can close that ticket happy in the knowledge that something fitting, in one sense, has been written under that heading. Now I’ve done that, I can flow onwards to the sea.

Keyword noise: Sweden, Stockholm, Norrström, metaphor, Mälaren, water.

We had an unexpected visitor in late July. One morning, as I was heading out for my morning 6am walk, I noticed one of the neighbourhood cats lurking outside the house, asking for scratches and strokes. When I came back an hour or so later, it was in the back garden instead. I opened the back door, and it followed me inside. It prowled the kitchen, miaowing boldly, before deciding to lie down as Guardian Of The Recycling.

It came back again the following morning, and the morning after, and started to explore more of the house. Initially it refused to go upstairs, and if anyone went upstairs would sit at the bottom waiting for them to return; but after a week or two it was happy to roam the whole house and particularly liked lurking among the clutter in the office.

The Plain People Of The Internet: So is this one of those situations? The whole “this is your cat now” situation?

I doubt it is, somehow. It’s clearly a healthy, happy cat that has a home nearby. It doesn’t need food from us, and I haven’t given it any. Moreover, as one of the other regular correspondents has pointed out to me: if Random Cat is a much-loved household pet, tempting it away to another home is not exactly a very neighbourly thing to do, however friendly it seems to be and however much it stands by the kitchen cupboards miaowing at me.

Why has Random Cat been visiting, anyway? I realised its visits started in late July, at the same time as the school summer holidays. Maybe one local family’s routine changes so much in the school holidays that Random Cat can’t cope with not getting its breakfast early, and decided to scout around the rest of the neighbourhood instead. Possibly, then, now we’re into September and the schools are going back, its visits will start to dry up again.

Ever since moving house, we have said: we really should think about getting in touch with the local cat shelters and finding one to actually live here. That, in all likelihood, will stop it visiting, although it’s not guaranteed. My garden is already disputed territory between Random Cat and another neighbourhood cat, an all-black one which likes to sit on the roof of a nearby shed. They have face-offs balancing on top of our garden fence. A third cat thrown into the mix might not even change very much.

If we do get a cat to live here, no doubt this blog—and certainly the rest of my social media—will become rather heavily cat-centric, at least initially. For now, though, occasional Random Cat will have to do.

Keyword noise: cats, pets, feline, Random Cat, The Plain People Of The Internet.

Back in May, the latest post in the Books I Haven’t Read series was about The Hills Of Wales by Jim Perrin, a book which I felt had a somewhat exclusive and elitist approach to said hills. At the time I read it, or at least part of it, I was staying in a cottage under Moel y Gest, within sight of the Moelwynion, so the hills of Wales were very real and very much on the doorstep. For that matter, the hills of Wales are on the doorstep of my home, too, and the issue of why hills such as Yr Wyddfa, the Moelwynion and all the others of the Eryri massif are seen as valid and special in a way that the worn-out, lived-on hills of the south such as Mynydd Machen, Twmbarlwm and the Blorenge are not, is a whole ‘nother topic in itself. The hills of the North, after all, are almost as industrialised as the hills of the South, particularly in the case of places like Parys Mountain or Penmaenmawr which have been industrial sites for thousands of years. Putting that aside, my plan was always to come home and write about my own responses to the hills of North Wales and what they mean to me; but since May it has stayed on the to-do pile.

Last week, however, I was away again, this time to the area around Aberteifi/Cardigan in West Wales. Driving along the main road north from Aberteifi towards Aberaeron and Aberystwyth, I glanced to my left and saw the sparkling, shining seas of Cardigan Bay. The air was so clear I could see the mountains on the far side of the bay in the distance. I could only glance briefly—I was driving, after all—but there unmistakably in the distance was the lonely outline of Moel y Gest, and alongside it the double-peaked ridge of the Moelwynion. It filled me with a sudden thrill, spotting a skyline I recognised from the far side of the bay. As soon as I got out of the car, I was messaging one of the regular correspondants to tell them about it, to their undoubted bemusement. Later, when I was back home and back at a proper computer, I checked the distance: about sixty miles, pretty good seeing really. Even the sparkling sea was deceptive: although it looked close enough to touch, the shore must have been some five or six miles away. I was over 200 metres above it, not far off the altitude of Moel y Gest itself.

Why does spotting the Moelwynion give me a thrill like that? I don’t know, other than that I have been going back to that corner of the country on and off since I was a teenager. But spotting them like that did remind me to write this post, and it took me back to a day back in May when I was driving around almost in their shadow, hunting down some bottles of limited-edition beer (it’s a long story). The drive took me across the Traeth Mawr, then over the hill road from Garreg to Maentwrog, but it is the first part, from Prenteg to Garreg, that sticks in my mind. I really don’t expect you to know where these places are, by the way, but please do stop to look them up on a map. The Traeth Mawr is an ancient drowned valley, once a broad sandy silvery estuary, for the past two hundred years usually farmland.

The Romantics, Shelley in particular, thought it one of the finest sights in the world before it was reclaimed. Nowadays you can hike, drive, or catch the train across it. And even though the sea is no longer there to reflect them, the surrounding mountains are a mighty encounter. Driving across the Traeth in search of beer, I felt safe, warm and secure, cupped in a bowl, the grand bones of Eryri wrapping themselves around me and protecting me with their power. If you were to reach for your copy of the Mabinogion you might realise that Pryderi was buried just over the other side of the mountain ridge, with Lleu Llaw Gyffes living with his wife made of flowers just a short walk away too.

That, maybe, gives you some sense of the reaction that I have to the hills of Wales, or at least a small fraction of them. There are many more, of course, and I have much more to say. I have had half a post drafted about Mynydd Machen for a while, although I might need to go up there again in a better mood. I have complex feelings about the Rhinogydd even though I’ve never explored their dark, quiet and lurking shapes. I’ve promised to take one regular correspondant to Bryn Cader Faner to see its curious crown of thorns, and I will always remember a teenage walk up to Llandecwyn chapel at dusk, looking down on Harlech Bay as if it was in the palm of my hand. No doubt I will write more about Welsh hills over the coming months and years. The important thing, the thing to always remember, is that they belong to everyone. The people who live on them, the people who live around them, the people who walk up them and the people who work on them. They are too old and too powerful to ever be the property of just one.

Keyword noise: Cymru, Wales, mountains, mynyddoedd, outdoors.

It’s nearly a month now since I started the new job. It’s not been plain sailing all the way, of course, but it feels like it’s going reasonably well.

One aspect of coming in and taking over a team is that naturally I want to put my own flavour on things. I’m not saying I automatically think my ideas are always better than what the team already does, of course, but I do think firstly that new ideas can often trigger new thinking and give new energy to a team, and secondly, that some of the things are familiar to me are inevitably going to be new to my new colleagues, and things they might not have considered before. So, if I can bring in processes and practices that have worked well for me before, they may well work well in the new job too. If anything, as long as I can get the team behind them, they might be worth a try.

“As long as I can get the team behind them” is the key point there, of course; and it’s important to make sure we all feel we are a team and that we can all contribute to making change happen. I started writing down some Basic Good Principles along those lines. “We know we’re not perfect but we’re always improving,” for example. “We all review each other’s code, because everyone gets it wrong sometimes.” — I’m always surprised how many people don’t quite follow that one. “This document is not set in stone and is always changing, just as our processes are always changing and improving.” is another one, because when a particular practice or process turns into dogma is when it starts to impede you rather than work for you.

After a while brainstorming this stuff, writing down these sort of things, though, I started to get a bit of self-doubt. Is writing down these sort of principles really helpful, or were my notes just turning into meaningless platitudes in themselves? Was I at risk of accidentally coming up with the “Live, Laugh, Love” of software development?

Which of course, set me thinking. What is the “Live, Laugh, Love” of software development? Maybe if I deliberately came up with something quite so awful, quite so twee and nauseating, it would reduce the risk of ending up in that zone by accident?

I scribbled a few things down, crossed some out, shuffled some ideas around, and eventually came up with the following. I think it’s pretty good. By which I mean, I feel slightly disgusted with myself.

Code

Create

Care

One of our regular correspondents writes: Yeah, I think you might need a shower after that.

Most definitely. I felt dirty. If you ever find me giving that as advice to my team, please, tell me I need to take a holiday. All the same, if I was to pick a font and put it on a framed print, I wonder how many I could sell?

Keyword noise: work, coding, motivation.

Regular readers might have noticed that there haven’t been many posts on here lately: the pressure of various other things that come before this place. The new job, for example, is one. Going to visit The Mother and help her with various bits of paperwork, another. I was up visiting The Mother the other day, as it happens. Not only did I also fit in a few nice long walks on her local beach, which will be the subject of another post another day, but I went down the pub and met up with this chap for lunch.

In the post about the new job, I mentioned how I used at one time to write lots of posts about my colleagues, giving them all false names and talking about some of the less controversial things some of them got up to. The chap in the picture is the guy referred to on this site as Wee Dave—not his real name of course. I called him Wee Dave because he succeeded Big Dave, although of course that wasn’t Big Dave’s real name either.

I hadn’t seen him for, ooh, it must be thirteen years nearly. We caught up, on and off, about various things that had happened through the intervening time: him on how strange it was, after I left that job, to stay on for a few more years in a business that was slowly shrinking as its owner wound down towards retirement, selling off a department here and shutting down one there, until in the end only Wee Dave and a couple of other people were left rattling around inside an empty warehouse. For my side, I told him all about some of the things I’ve worked on since, some of them interesting and some of them less so.

Naturally, we also reminisced about the people we worked with and that I wrote about here. “Say hi from me!” messages were passed over, and we talked about how few of the people there we actually kept in touch with, and quite what a strange place it was to work. Wee Dave ended up working with someone else from that place at his next job; unlike me, of course, disappearing to the far end of the country. Like me, though, he’s moved from general IT work into software development, partly because it’s far more interesting and challenging than setting up servers, rotating backup tapes and generally being a systems dogsbody. We shared the usual gripes that all software developers have, such as nobody really agreeing on what Agile is supposed to mean even though everyone claims they do it. That, indeed, is something I might have a long ramble about on here some time.

Thirteen years is a long time, from one meeting to the next. Of course, as I have to go up there and visit The Mother fairly regularly nowadays, I’m going to be in the area much more often in the future. Hopefully the gap until we next have a drink together won’t be quite so long.

Keyword noise: Wee Dave, work.

I passed a very minor milestone yesterday. Duolingo, the language-learning app, informed me that I had a “streak” of 1,000 days. In other words, for the past not-quite-three-years, most days, I have fired up the Duolingo app or website and done some sort of language lesson. I say “most days”: in theory the “streak” is supposed to mean I did it every single day, but in practice you can skip days here and there if you know what you’re doing. I’ve mostly been learning Welsh, with a smattering of Dutch, and occasionally revising my tourist-level German.

My Welsh isn’t, I have to admit, at any sort of level where I can actually hold a conversation. I barely dare say “Ga i psygod a sglodion bach, plîs,” in the chip shop when visiting I’m Welsh-speaking Wales, because although I can say that I am wary I wouldn’t be any use at comprehending the response, if they need to ask, for example, exactly what type of fish I want. To be honest, I see this as a big drawback to the whole Duolingo-style learning experience, which seems essentially focused around rote learning of a small number of set phrases in the hope that a broader understanding of grammar and vocabulary will follow. I’ve been using Duolingo much longer than three years—I first used it to start revising my knowledge of German back in 2015. When I last visited Germany, though, I was slightly confused to find that after over a year of Duolingo, if anything, I felt less secure in my command of German, less confident in my ability to use it day-to-day. Exactly why I don’t now, but it helped me realise that I can’t just delegate that sort of learning to a question-and-answer app. If I want to progress with my Welsh, I know I’m going to have to find some sort of conversational class.

Passing the 1,000 days milestone made me start wondering if anyone has produced something along the same lines as Duolingo but for computer languages. In some ways it should be a less difficult problem than for natural language learning, because, after all, any nuances of meaning are less ambiguous. I lose track of the number of times Duolingo marks me down because I enter an English answer which means the same as the accepted answer but uses some other synonym or has a slightly different word order. With a coding language, if you have your requirements and the output meets them, your answer is definitely right. In theory it shouldn’t be too hard to create a Duolingo-alike thing but with this sort of question:

Given a List<Uri> called uris, return a list of the Uris whose hostnames end in .com in alphabetical order.

1. uris.Select(u => u.Host).Where(h => h.EndsWith(".com")).OrderBy();
2. uris.Where(u => u != null && u.Host.EndsWith(".com")).OrderBy(u => u.AbsoluteUri).ToList();
3. uris.SelectMany(u => u.Where(Host.EndsWith(".com"))).ToList().Sort();

The answer, by the way, is 2. Please do write in if I’ve made any mistakes by being brave enough to write this off the top of my head; writing wrong-but-plausible-looking code is harder than you think. Moreover, I know the other two answers contain a host of errors and wouldn’t even compile, just as the wrong answers in Duolingo often contain major errors in grammar and vocabulary.

Clearly, you could do something like this, and you could memorise a whole set of “cheat sheets” of different coding fragments that fit various different circumstances. Would you, though, be able to write decent, efficient, and most importantly well-understood code this way? Would you understand exactly the difference between the OrderBy() call in the correct answer, and the Sort() call in answer three?^* I suspect the answer to these questions is probably no.

Is that necessarily a bad thing, though? It’s possibly the level that junior developers often work at, and we accept that that’s just a necessary phrase of their career. Most developers start their careers knowing a small range of things, and they start out by plugging those things together and then sorting the bugs out. As they learn and grow they learn more, they fit things together better, they start writing more original code and slowly they become fluent in writing efficient, clean and idiomatic code from scratch. It’s a good parallel to the learner of a natural language, learning how to put phrases together, learning the grammar for doing so and the idioms of casual conversation, until finally they are fluent.

I realise Duolingo is only an early low-level step in my language-learning. It’s never going to be the whole thing; I doubt it would even get you to GCSE level on its own. As a foundational step, though, it might be a very helpful one. One day maybe I’ll be fluent in Welsh or German just as it’s taken me a few years to become fully fluent in C#. I know, though, it’s going to take much more than Duolingo to get me there.

* The call in answer 2 is a LINQ method which does not modify its source but instead returns a new enumeration containing the sorted data. The call in answer 3 modifies the list in-place.

Keyword noise: Duolingo, learning, languages, coding, Welsh, Cymraeg.

What do you do on a random Saturday with zero plans? Walk up a mountain? What an excellent suggestion, thank you! So yesterday morning I headed off for a gentle amble up to the summit of the Blorenge, the mountain that stands over the valley of the River Usk opposite the Sugar Loaf, and separates the urban environs of Blaenafon from the rural tranquility of Abergavenny and Crickhowell.

I say “a gentle amble” because it’s not a particularly strenous walk. It’s not like the sort of mountain where you park your car at the bottom and hike up a path so steep you’re almost too scared to come down again. The road over the mountains north from Blaenafon isn’t that much lower than the summit, only about eighty metres or so. The walk, therefore, is essentially a cross-moorland ramble more than anything else. Still, it’s definitely a good way to spend a morning.

When I thought of posting this, I was intending to turn it into something hugely informative: a long story full of history, geology, packed with information about the mountain. Unfortunately, I couldn’t quite work out how to get into it. It turned into something dry and meaningless, without flavour, when I wanted to write something evocative, something that would make you really feel you were on the mountain alongside me. What I do have, though, are pictures.

I started here at Keepers Pond; at least, that’s what it’s called on the signs. The Ordnance Survey map calls it Pen-ffordd-goch Pond—the head of the red path. Older, Victorian-era maps call it Forge Pond. The whole area around the Blorenge is filled with ancient industry: pits, hollows, old quarries and old mining tips, joined up by tracks that were once horse-drawn railways. Nowadays Keepers Pond is busy with wild swimmers, canoers and paddleboarders. The only ancient industry I found was one length of Victorian railway rail.

Despite all its ancient industry, the Blorenge now is a quiet place, a place where the loudest sounds are of songbirds. There are many hikers, but they walk silently, conversations blown away by the wind. In the distance you can see all the way to the Severn Sea, in the far distance the coast of Somerset, but on Saturday the skies were grey, the clouds low, and sea, sky and distant land all merged into one continuous blue-grey palette.

At the summit, naturally, there’s a trig point. On the ground, though, unmarked, a second benchmark was carved. An old one, by the look of its shape. Possibly, it is the benchmark labelled on an 1880s map as 1,832 feet.

To the north, at first, the view was lost in cloud, leaving just impressions of a valley. Then, slowly, as I returned back to the car, it started to open up again. The valley of the Usk, the Black Mountains and the Sugar Loaf. The grand vista stretched before me, before the cloud came back down again once more.

Keyword noise: Cymru, Wales, hiking, Blaenafon, The Blorenge.