Posts in category "Life"

A map of my year in Obsidian

2 min read; 15 GFI

Some time around late October or early November last year, around the time I started working at Textualize, I "discovered" Obsidian. While I didn't need another note-taking application (having gone through Evernote, trying to use Org, dabbling with a couple of other things and finally settling mainly on Apple Notes), I was quite taken by its style and ubiquity and the fact that it was, at heart, just a bunch of Markdown files.

So quite quickly I started using it; not to replace Apple Notes (which is still my general note-taking tool of choice), but to keep work notes and a daily coding journal, the latter coming in useful for the quick end-of-day meetings we normally have.

One of the things I was quite taken by was the graph. It was interesting and fun to see how each of my work days related to other work days, and what subjects kept getting pulled in, etc.

So come the start of this year I had an idea: what would it be like to keep a personal vault, but one where I track things I've done. Not a journal as such (I do keep one of those too, have done for many years now, but that's for other far more important reasons -- perhaps I'll write about that one day too), just a daily record of stuff I've achieved, stuff I've actually done, the routine things and the exceptional things?

What would that graph look like?

While it's not the end of this year yet, here's how that's shaping up:

The main graph

Each of the yellow circles is a day, each of the blue ones is a tag of some sort. As you'd imagine, the size of the circles relates to how often that item is tagged. So I can see what proportion of my days so far this year have been tagged with being heavily involved with work:

Work

Likewise, if I want to see how many days this year have involved a significant spot of gaming:

Gaming

Ditto for days where I've done some coding on pet projects, or even some personal-time coding relating to work projects (it might be work, but it's also Free Software and I do like to support FOSS!)

Coding

I sort of have a curated set of tags I apply, but I've not made it a strict set; if some new situation crops up that calls for a new tag I'll use it. Mostly though I try and keep the tags pretty general so lots of days can relate to the same general subject.

Another thing I've done is tag each and every day with the day of the week, so while it's not really surprising to find that Sunday doesn't dominate over other days, I can see which days are Sundays and perhaps wander along the connections and see what I get up to:

Sunday

I don't quite know what I hope to get out of this, I don't really know if there's anything useful to be had here at all, but it will be interesting to look back over it at the end of the year. It also means that I'll have a directory hierarchy full of Markdown files, all tagged and filled with information, which I'll be able to grep and slice and dice and count and perhaps pull into a database and cross-reference with stuff and things.

Or perhaps it's all just really me not having a good use for Obsidian but inventing one anyway. ;-)

Mythos: Ragnarok (plus Oppenheimer)

2 min read; 9 GFI

And I'm done! While it did only turn out to be one a week, I pulled it off, I managed to make it to at least one Fringe show per week!

View inside the Roxy

Yesterday was a full, busy, and hugely enjoyable day. While it could have just been a dash into town to see the show and back home again, in conjunction with Mariëlle (who first introduced me to the Mythos show) we arranged to go watch Oppenheimer first (amazing, easily the fastest any combined 3 hours have passed for me -- I'm not even going to try and write up anything about this, other than I was utterly enthralled by the movie from start to end), grab some dinner, then go and see Mythos: Ragnarok.

With a wee bit of shopping thrown in along the way.

As I've mentioned before, I first saw Ragnarok last year. Then they were in a fairly small venue, with a pretty full crowd. At the end they talked about how the first night they'd played the audience had been a single person; over the nights of the run it had slowly grown, and by the end of the run (we went on the last night) it was getting properly busy.

This year they were in a much bigger place, with a lot more seating, and the house was full. This did make it feel a little less intimate than last year, and also last year we were sat all around the stage, which worked well for the performance; this time around it was a more traditional stage at the front, seating all on one side thing. I was really pleased for them that they were in a much bigger place, but I did miss the layout from last year.

As for the show itself... just as fantastic. There seemed to have been some tweaks and changes to how the story was done over what I remember from last year, but mainly it was the same. The energy in the performance was incredible, and the comedy was spot on, with a lot of nods and winks to the audience. This is the part that I think I enjoy most: they know what they have, they know what they're doing, they know what they have on offer. It's a high-energy play performed by stunt people.

It's amazing.

As I write this there's one last show, I believe, tonight; so the chances of anyone reading this and getting to see it are very remote. But if they're back next year, and you're reading this near then and wondering about Fringe shows, do it! Really, do it. You won't regret it.

I'll be going again. No question.

Mythos: Ragnarok booked

1 min read; 7 GFI

That's a third show booked! This means that, as I hoped, I'm going to manage at least one show a week for the Fringe!

Now, this one could be seen as a cheat, sorta, kinda. I've seen this show before. But I liked it so much last year I have to see it again! The odd thing about it was it's not something I would have gone for on my own, it's technically not really my thing, but I got talked into it and I'm so glad I was!

So a year back Mariëlle told me about this wrestling show at the Fringe and how she wanted to go but nobody else was interested and I was all "yebbut wrestling though?" and didn't think much more about it. Eventually though, after some persuasion (I mean, an hour or so at a show and some beers afterwards, how bad could it be really?), I agreed to go. I expected to find it meh.

Cast of Mythos: Ragnarok 2022

Holy shit was it so much fun! Like, seriously so much fun. I'd never realised that wrestling was the best way to tell the tales from Norse mythology; turns out that wrestling is absolutely the best way to tell the tales from Norse mythology.

So we're off back again this year. All booked, not this weekend, the weekend after.

There might even be a beer afterwards. Perhaps not quite so many as last year though.

Encouragement, I guess?

1 min read; 12 GFI

Anyone who was (un)lucky enough to follow me on Twitter back in 2020 will know that, starting January 1st that year, I set about losing weight. At the time I was very overweight and wanted to get into some sort of healthy state. By August that year I'd managed to drop 30kg and hit and then went a wee way under my goal.

These days I'm back up a wee bit. Not much: generally about 5kg or so above that goal, most of that having turned up on the last 7 or 8 months (not exactly coincidental that it's happened in conjunction with the new job, the new work location, and the new commute). While it's no real cause for concern -- I'm still generally careful and still get plenty of exercise (normally walk around 35km a week, run 20km, get my 10k steps in every day)

About a week back I decided that it was time to give myself a bit of breathing room, to try and at least drop a couple or kg; so with that in mind I set a lower daily calorie goal in my tacking app.

When recording my weight first thing this morning (yes, I'm one of those people who records it every day and have for a few years -- it makes for interesting data!), this is what my calorie/stats tracker had to say:

Screenshot of my calorie and weight tracking app

I guess it's putting a positive spin in things? (for the record, I'm 5.3kg above my absolute goal).

New desk

2 min read; 9 GFI

I moved into my current place back in August 2019, bringing with me a fairly small desk. Originally, many years back, I'd had a pretty big office with lots of office space but, upon moving up to Scotland back in 2016, I needed to go with something a lot smaller.

Which was perfectly fine. Me and that desk wrote a lot of code. Me and that desk transitioned from one job to another, and then another. Me and that desk made it through the pandemic.

It's been a good desk.

But it was small. I'm in a place where I could spread out a fair bit again, but I also kept putting it off and putting it off.

Earlier this year I decided that it was high time I actually upgraded; I also promised the desk to someone else who I know will get a lot of good use out of it; so finally earlier this week I put in the order for something bigger and fancier.

Yesterday, with the help of a very good friend (thanks Mariëlle!), I got the desk built and roughly in place, and then today I've been putting the desktop back together and adding extra bits.

My new desk

It's so nice to have more space to spread out, it's also nice to have a black desk again! (the last one was white because... reasons) But what's really exciting is that it transforms into a standing desk at the touch of a button.

I've been trying it in the standing configuration today and, while I doubt I could do a whole day of coding with it like that, I'm already really liking it as a way of breaking up the time at the keyboard. On the days I work from home, or the days of my own where I get sucked into a personal project, I can absolutely see me swapping between the two states.

All that's left now is to get used to it. The screens are ever so slightly further away, the height is ever so slightly different (although I can adjust it, of course, but what I've done is adjust the sitting position to a nicer one and that's going to take some getting used to), my iPad and Stream Deck are in just a slightly different location, etc, etc... So I'm sure there'll be a few days of sitting here and making small tweaks to the spot where things live.

Before I know it I'll be used to it. It'll be "my spot".

On to something new (redux)

(Modified: 2026-04-28 11:25:08 UTC+01:00)
3 min read; 10 GFI

Just over five years ago I got a message from my then employer to say I was going to be made redundant after 21 years working for them. After the 3 month notice period the final day came. Meanwhile, I found something new that looked terrifying but interesting. In the end it was less terrifying and way more interesting than I imagined it would be. It was fun too.

But... (there's always a but isn't there?)

In the four and change years I've been there the company got bought out, and then the result of that got bought up. As I've mentioned before I'm generally not a "big company" kind of person; in all my years I've found that I'm happier working in a smaller place. After a couple of buyouts my employer had gone from being 10s of people in size to 100s of people in size (and technically 10s of 1,000s of people in size depending on how you look at it).

This change in ownership and size meant the culture became... well, let's just say not as friendly as you tend to enjoy when it's a smaller group of folk. On top of that I was starting to notice that my efforts were making less of an impact as things got bigger, and I started to feel like my contributions weren't really relevant any more. There were some problematic things happening too: undermining of efforts, removal of responsibilities without consultation or communication, that sort of thing. Plus worse. There's little point in going into the detail, but it's fair to say that work wasn't as fun as it used to be.

That felt like a good time to start to look around. If work makes you feel unhappy and you can look around... look around.

Thing is, I wasn't sure what to look for. I was in the comfortable position of, unlike last time, not needing to find something, so I could take my time at least. Over the course of the last year I've spoken to many different companies and organisations, some big (yes, I know, I said I don't like big places -- sometimes what's on offer deserves a fair hearing), some small, but none of them quite said "this feels like me". In some cases the whole thing didn't have the right vibe, in others the industry either didn't interest me, or felt uncomfortable given my personal values. In one particular case a place looked interesting until I checked the CTO's socials and OMG NO NO NO AVOID AVOID (that was a fun one).

Then I saw Will McGugan saying he was hiring to expand Textualize. This caught my interest right away for two reasons.

I can't remember how long I've been following Will on Twitter; I likely stumbled on him as I got back into Python in 2018 and I also remember noting that he was a Python hacker just up the road from me. We'd vaguely chatted on Twitter, briefly, in that "Twitter acquaintance" way we all often do (I remember one brief exchange about fungus on The Meadows). A small company run by someone I was acquainted with seemed like a safe bet.

The second reason was Textual itself. I'd been watching Will develop it, in open, with great interest. I had (and still have) a plan to write a brand new CHUI-based (okay fine TUI-based as the kids like to say these days!) Norton Guide reader1, all in Python, and Textual looked like the perfect framework to do the UI in. The chance to be involved with it sounded awesome.

Now, I said two reasons, but there's also a third I guess: Will's pitch for applying to Textualize felt so damn accessible! I'm on the older end of the age range of this industry; for much of my working life as a developer I've worked in isolation from other developers; while I first touched Python in the 90s, I've only been using it in anger since 2018 and still feel like I've got a lot to learn. Despite all these things, and more, saying "aye Dave this is beyond you" I felt comfortable dropping Will a line.

Which resulted in a chat.

Which resulted in some code tinkering and chatting.

Which resulted in...

Something new.

So, yeah, as of 2022-10-10 I'm on yet another new adventure. Time for me to really work on my Python coding as I work with Will and the rest of the team as part of Textualize.

Or, as I put it on Twitter a few days ago: "I'm going to be a Python impostor syndrome speedrunner".


  1. Future edit to add: it happened eventually

On to something new

2 min read; 9 GFI

Today is a fairly significant day for me. For the past 21 (and a bit) years I've worked for the same company. I know that, for lots of people in my industry, that's a hell of a long time to be in one position. It was a setup that served me pretty well; the company was small (I'm not much of a big company person), I generally got to dictate the development tools and direction, and I also got to work from home.

The working from home part was especially helpful as other life events involved me and happened around me. The job I've been in has seen a marriage come and go, and a move from Hampshire to Lincolnshire, and then from Lincolnshire to Midlothian. There's been a few adventures along the way.

But, three months ago, I got a call to say that I was to be made redundant. This sucked, obviously. It also appeared pretty stupid on the part of my employer: a company that is based around software had decided it no longer wanted an in-house software developer. A bold, and I think unwise, choice. From this point on they've decided to only go with contract developers and only contract developers from overseas (or so the story goes).

As it goes, things have turned out okay. Today is my last day with my old employer and, as I'm sat here typing this out while having some lunch, I'm actually glad that it's coming to a close and that I can get to move on.

I have a new employer, and will be starting in my new position during the first week of January. It'll be very different. It'll all be different. Not only will I be back working in an office (one where jeans and t-shirts are the norm, thankfully!), I'm also going to be working in an industry (as a developer still, of course) that I have no background in and no real knowledge of. It's going to be a seriously exciting challenge.

New book

Over the next couple of weeks I've got a fair amount of background reading (and video watching) to be doing. This isn't so much that I can get on with the job of development (although there will be a good bit of that to do too -- who doesn't want to be trying to understand new options for development?), it's more about understanding the language of the industry I'll be in and so that I can understand the needs of my users.

Goodbye fashion retail and all related things. Hello genetics and... well, I don't know, I'm going to find out. :)

Virgin East Coast 21

2 min read; 11 GFI

Yesterday I got the call about the Virgin East Coast Ticket Wallet app that I was promised last week (well, actually, promised a couple of months back). It didn't go well.

Well, I say "didn't go well", the conversation itself went very well, the chap I spoke to was polite and apologetic and helpful, but the outcome wasn't really very brilliant.

It didn't get off to a brilliant start when I was first told that the solution to my problem was that I needed to uninstall and then reinstall the app (something I've done more than once while trying to get to the bottom of the problem). I asked if that was really necessary and I was informed that it was the only way to fix the problem of the tickets not showing. Problem is... that wasn't my problem. So I then had to explain the exact nature of the fault I was experiencing (and also explained my guess as to what the cause of the problem was).

After that, much of the content of the conversation involved vaguely confidential information (nothing too terrible or that big a secret -- just stuff that isn't generally known yet) which I'm not going to repeat here. The upshot of the chat though is this: they can't do anything for me.

Simply put: they acknowledge there's a problem with the app, the problem is at their end, it's a problem that needs to be fixed and there's nothing they can do to fix it any time soon.

The causes of this will sound familiar to anyone with experience of large companies who outsource much of their development and get involved in areas that they might not have much experience with.

I also found out the cause of some of the delay in actually getting back to me: the person who was supposed to originally call me went on maternity leave just after they'd first tried to call and, it seems, nobody thought to pick up their workload. This left me in the bizarre position of trying to call someone who was off work for an extended period of time, and whose phone wasn't being answered in any way.

Of course, it doesn't explain why that person's boss, who I was promised a call from a short while after, never bothered to call.

So, I think, to some degree, that's the end of this silly saga. Their software is buggy, they can't fix it any time soon, and I'm out of luck.

As for the extra free tickets I was promised a couple of weeks back now... they've still not appeared. Time for me to chase that up again.

Virgin East Coast 20

1 min read; 8 GFI

After my last post I sent off an email to chase up what was happening with the promised phone calls about the Ticket Wallet app and the general delays with getting things sorted. Here's what I wrote:

Hi again Mike.

It's now a week since you replied and, I think it's fair to note, it's no longer "early" this week. I've had no call -- neither form yourself nor from anyone related to the Ticket Wall App -- and I've not received the promised tickets either. While I do try to be patient I have to admit that it's starting to get very frustrating, being made lots of promises about progress that simply never happen. This has been going on for months now and I'm always having to chase things up.

I'd very much appreciate it if you could explain to me what's going on, and why.

A while later I got a reply. He said he'd be getting the tickets in the post the following day (so a Friday, which I think I can safely say isn't the start of the week) and would also phone me.

The following day he did keep his promise. He called (I managed to miss him the first time, but when I was finally free I called back and we got to chat). He promised I'd get some more tickets early next week and also that someone with technical knowledge would finally call about the app problem.

I have, of course, been here before. This is exactly the promise that was made a couple of months ago. It's easy to make the promise, apparently not so easy to deliver on it (or address the issue of not delivering on it).

So now I wait. Again. I'll be sure to update when something happens (or doesn't).

Virgin East Coast 19

1 min read; 9 GFI

I think I need to rethink the meaning of the word "certainly". Anyone still bothering to read this blog will recall that, last week, the Customer Relations Manager at Virgin East Coast said:

If you can leave this with me I will certainly be in contact early next week to try and get this resolved once and for all. In the meantime I will pop a further couple of tickets in the post for you, just so you have them incase you need to travel urgently.

That email was received last Thursday evening. It's now the following Thursday. Personally I'd take "certainly", in the above, to mean that there's little to no chance that I won't be contacted in the early part of this week, and that there's little to no chance that the tickets won't arrive in the early part of this week.

I'd have thought that "certainly" would be used to create a huge contrast between what has gone on before, and what will follow.

But, like I say, it's Thursday the following week and I've had no call from anyone about the Ticket Wallet app, I've had no call or email from Mike (the Customer Relations Manager) and the tickets haven't tumbled through the door.

I'm not surprised. I'm not in the least bit surprised. I am, however, rather disappointed.

And, of course, I'm now going to have to chase things up again.