Weeknotes 08×09: Ping Pot Problems

  • Full speed ahead this week. The head is in full planning mode. No fancy Kerouacian prose this week, but I’ll keep the photos in…

  • My main achievement* this week was to establish a new game to pass the time. Inspired by various throwing games I saw in France recently, some ping-pong balls, flower pots and a low table were dutifully repurposed into a game I’ve come to call “Ping pot”. Bounce the balls off the table, into one of the pots. Simples.

  • not really my main one, but I like it.

Ping Pot: A table, surrounded by ping pong balls

  • (Ping Pot is definitely not just an executive version of Beer Pong.)

  • This is actually a serious exercise, DESPITE THE BALLS EVERYWHERE. I have a theory that problem-solving is – for me, at least – done best when the body and mind are both working together, without undue focus. Any gentle form of exercise is helpful to problem-solving, from going to the toilet, to going for a walk, to darts or tao chi. Firstly, screens are really, REALLY bad to have in front of you – they’re filled with information and all sorts of emotional routine attachments that distract you. And secondly, distracting the body with something simple somehow “greases” the mind – the semi-automated flow of physical energy also gets thoughts flowing better. As I said, it’s a theory.

  • As a result, these week’s photos are also all things from floor level?

  • An oddly unexpectedly “therapeutic” week. A few things I’ve not been so happy about have been playing on my mind, particularly at 11pm or 5am. Writing a draft email to the ether helped – like weeknotes, the act of getting things down clears things out of the brain.

  • I also read this short read on why we’re creative and problem-solving, and why that makes us grumpy, which definitely helped a lot this week. I’m often grumpy, and have written about trying to find the craft in my work some while ago. The article helped me realise that I do see the world as ‘problematic’ (or ‘puzzlematic’?), and I’m split between loving solving problems, and getting annoyed that others aren’t as ‘solvey’. So the perspective is a good one, and I can calm down.

  • Thursday afternoon, a quiet office and some decent work planning for the epic we’re currently on. We’re changing our underlying geographies, and I wonder if this is the most complex thing we’ve done in five years – it touches on all of our code, with no easy answers in some places. The team are doing a good job, up against annual leave, sickness, and Obi leaving.

  • My main aim now is to keep it on track, which means: Structuring the information learned so the work can continue to be distributed; Keeping an eye out for more detailed gotchas; Turning information into a plan with priorities and estimates (that hard part I’ve talked about before; and Keeping people interested in the work as the endurance test sets in.

  • Pace is everything in these things – pace and rhythm. A piece of work spanning multiple (2 week) sprints can feel like a never-ending slog if done badly. We’re over the big initial hurdle of facing an unknowable, chaotic mammoth, like those times you stomp up a huge hill at the start of a mountain walk. Feels like we need to enjoy the view and the refreshing meander now. I wonder how to build this in.

  • Should “pushing back against delivery pressures” be on the list of duties for a tech team lead? How can one value the longer term sustainability of slowing down? (This question of “undemonstrable value” seems to be a recurring theme at the moment.)

  • Behaviour management. This is something I really struggle with, because it’s rarely a clear line. Is there a difference between ‘rude’ behaviour, and ‘annoying’ behaviour? Not triggered by anything specific, other than looking through a feedback and suggestions form.

In links

  • gov.uk on roadmaps:

    ”But getting them right is hard. Roadmaps are born of all sorts of compromises: between committing to a plan while remaining agile; between giving product teams autonomy while aligning their work to business goals; and between improving existing software versus getting new stuff out the door.”

  • Warren Ellis again, in his Orbital Operations newsletter:

    ”I hope for, and fully expect, futures scenarios to get weirder and wilder, hyperlocal and supermodernglobal, very quickly. 2001 to 2018 has been the training ground for the New Next.”

  • Managed to post some minor internet postcards to Disposable Evidence – sign up, for something a little bit different.

In photos

A beer bottle on the street floor

A child's shoe on the street floor

A pink anarchy sign sprayed on the street floor

Weeknotes 08×08: Journeys, expeditions, exploration and navigation

A spiralled car park ramp

Following the same fragmentary nature as before.

  • I arrive in Manchester just as Pride is dying out, flickers of revelry still sparking behind closed doors in an effort to ride out the back holiday. Six hours of cattle-cage travel thanks to Euston unexisting, after two days of standalone parenting – driving drumming Buddha bowling chatting childing – and then the labyrinth of fresh streets, and the guesswork of solitude. I pick up a beer, check in, and crash out, all punctuated by the electric honk of trams outside. I sleep well, but it feels like a dream long before I sleep.

  • Manchester has back alleys, hidden places. The hidden places are filled with creativity – Street art, graffiti, throw-ups. Privacy is a place to experiment, to find out what works, to find out if you work.

'Motley' street art from Manchester

  • The data expedition is not quite what I expect, but these to is never are, which is a good thing. I go into it thinking through my skills – people management feels irrelevant here, but my “traditional” skill, coding, feels rusty. My laptop isn’t prepared. I feel like legacy…. I should have more confidence in myself – maybe it’s the dreaminess that’s throwing me. I can’t remember the last time I was alone in a strange place.

  • The expedition, run by an amalgamation of Open Data Manchester, Local Trust, and 360giving goes well. I feel a bit uncomfortable foisting our commercial product offering on to people by default in this non-commercial setting, so I disclaimer myself and allow the conversation to sway either towards exploring data from scratch, or to use our tool briefly to avoid the legwork and get on with other questions. We go for the latter, but I have a clean conscious. It’s helped that a bunch of people here already have access to it anyway, but one must always be sensitive to immediate aims.

My character sheet from a data expedition day

  • I spend most of the day actually looking up data and using our own tool, instead of coding – I have come out from behind the curtain. It’s weird and enlightening out here. Finding and understanding open data is a lot harder than it should be, given the effort and time that it’s had. So many interfaces, so little structure or user pathways. This is hard to say, but data.gov.uk feels actively unhelpful as I search. Hey weeknotes crowd, I’m happy to talk to anyone involved in it, if feedback is useful. (Did I read recently that someone new was taking it on?) That’s not to say its the only culprit though. I have many thoughts coming out of eating my own dog food.

  • Failed working experiments #1,652: Blocking out a regular morning every month to do planning (by myself) for upcoming tech work. Why didn’t this work when it does for blocking out time for work building up? Potential reasons:

    • Not enough interest (from me)
    • Aims and structure not clear (from me)
    • Lower priority (for me)
    • (My) Routine not established sufficiently

I think I will try an even smaller step by next week, of blocking out some just to get my head into it, by clearing out existing tech tickets in the system. One of the mental blockers to planning is that I don’t really know what’s in the system already and so adding new stuff makes me feel… dirty.

  • Returning to work, and agree to run a retrospective unexpectedly. I’m blurring the lines a little between Tech Lead (which I am) and Scrum Master (which I’m not) but there are many reasons, and one of them is that I sort of want to shake up the team processes a little, in light of developing the upcoming tech strategy. It’s always difficult to know quite when to step in and when to step back when the lines are blurred. I’m enthusiastic about the team growing, and it feels like there needs to be something different happening.

  • Secret bit: I actually quite enjoy running retro, but I also know how hard they are to get right. I don’t believe you can just assemble some “standard” discussion “tools” (although these can be useful) – the key is to explore the emotions in the room – usually the “negative” ones – but in a way that is productive. That’s a verrry fine line – I think a good facilitator opens up a lot of pain, but stops it – just – from becoming just a rant session. It’s a dangerous and risky process if done well – one that can go bad easily, either because it isn’t bold or vulnerable enough to be open and address real problems, or not channeled enough to come out of it with a sense of progress.

  • Something I always bring to any conversation I have seems to be a sense of mapping, mostly concept mapping, but any system of ideas being discussed. I tend to find myself jotting down what people say, then drawing lines between things. I hope it helps others. I’d love to be an “organisational cartographer”, now that I think about it.

  • Our last task of the day is to roll out some minor updates to our Australian site, which is getting a full on Aussie launch on Monday (when we’re all in bed). The launch comes amid a bit of political turmoil out there, so I hope it goes OK. It’s been a long time coming though, and while we have some internal tidy-up work still to do, it feels like another milestone.

I’m off to shift this cold and pick blackberries. Enjoy the week…


My name is Wil Wheaton. I Live With Chronic Depression and Generalized Anxiety. I Am Not Ashamed.”:

And as we were walking I just started to cry and she asked me, “what’s wrong?”

I said “I just realized that I don’t feel bad and I just realized that I’m not existing, I’m living.”

Warren Ellis’ Orbital operations, 19th August, on “graphical writing” and the story vs the author. I love this bit about consistent structures to let you get on with the real work:

Regular unbroken consistent grid paneling stops you looking at the structure and has you simply focus on the words and pictures.

A collection of thoughts on slowness:

  • How to be slow
  • Louise CatoWeeknotes s05 ep04: Wooden spoon on slowing down: “it does take energy to retain positivity when you’re not feeling it. It takes energy to re-word things, to consider, to be the best version of yourself
  • Is tai chi ‘slow thought practice’? By slowing down our movements, we get out of the habit of tensing in order to respond. Everything is considered and taken on board, but movement is constant. Direction is always flexible, never committed to. Things start and stop in their own time, never rigid nor panicked.

Frances Coppola on life after death and having only one life.

In Photos

Must turn these into a mini zine…

A bee statue outside Manchester Picadilly station

Two guys in Manchester holding hands in the night, reflected between pillars and glass

Fairly abstract shot of clouds reflected in a shiny glass building

A spiralled car park ramp

Abstract photo of lines and shadows

Weeknotes 08×07 :: Fragments

A dragonfly resting on a bus window

Naughty plug, but hey, we’re hiring for a data researcher!

Officially (by weeknotes law) I finished series 8 last week. I’m going to avoid assessing my serious aims from episode 1 like a cheeky bugger. Instead I’m trying out a new approach of jotting down a few random, disjointed fragments, Baudrillard style.

  • I’ve rewritten the whole damn tech strategy now, and re-formulated my initial aims and metrics into a set of parallel “phases”, each with their own timeline. Kim has also finished the marketing strategy for the year. I think maybe the key thing in writing it is not just to be a clear reference document, but to be useful to the person running the process, ie me for the document I’m writing. That’s essential, because it’s basically a user manual for myself. A standardised format just wouldn’t work. And if someone else took over, it would be best to rewrite it all again. Document structures need to match individual thought structures for maximum effect.

  • Heard about the passing of Hendrik Grothuis which was an unexpected and almost surreal thing to hear. I met Hendrik a few times, largely when I was younger and more… uncertain of myself, and he was someone who I always felt happy talking to, like he really knew his stuff but was so open and… warm? about it. It’s weird thinking back on that, and wondering about how influential certain people are on your life.

  • Andrew Sleigh on documentation, and the need to keep it frictionless. I’m still getting a lot of friction as part of my weeknotes flow – I like taking notes in the Diary app on my phone, which supports Markdown. And my self-hosted WordPress site supports Markdown and can then cross-post to Medium. But… Dunno, something. Maybe it’s the need to switch to a laptop for WordPress. Maybe it’s adding images is hard. Maybe it’s just the phone keyboard, give me a mechanical bash board any day. Or maybe it’s the need to summarise things into a week. Is an ongoing blog approach any better? Or just overkill for readers?

  • London on Thursday was really good, and I had trouble sleeping after it. I managed to understand the wider context about the Product Owner role I occupy currently, and why I’m frustrated about it. I’m not sure if it helps find a solution, but I like it when I get a better idea of the problem I’m facing

  • I also managed to pop into the Photographer’s Gallery near Oxford Circus and catch the amazing work of Tish Murtha documenting children and social deprivation in the 70s and 80s. Do go and see it if you can. I’m convinced photography has a massive, underestimated role to play in understanding our world. Data is great, but photography hits that emotional side of politics that we all deal in. If data visuals pull you in, documentary photography ducks you in, pummels you, and does a bloody dance around your body.

  • It was also great to meet up with a guy called Dan Barrett who is one of the world’s Heads of Search and Data, and has started weeknoting recently*. No, seriously though. I didn’t really know where the conversation would go, but we ended up comparing job notes and thoughts on democracy. It feels like we both had similar challenges, despite being in organisations of massively different size. It was also a great reminder that being a tech team lead isn’t about code, not in the slightest. But what is it then?

* weeknotes in-joke?

  • Relatedly, I started reading The Manager’s Path properly at last. The opening section of the book reminds us that tech leading is not about being a good coder, but a good leader, work/project manager, communicator, and systems thinker – how everything fits together, risks, and strengths. It’s more important to understand the people with in depth knowledge than to know the details of that knowledge itself. Change management. Curiosity. Confidence.

  • Relatedly, last week I also finished The Tao of Democracy by Tom Atlee. I’ve always tried to take something of a democratic, inclusive, consultative approach to my team. The book concluded with a quote from Lao Tzu which has also kept me inspired for many years: “When the best leader’s work is done the people say, We did it ourselves!”. I’ve been reassured by re-finding this – and have forgotten it at a conscious level for too long. As a result, I’ve been finding it difficult to demonstrate or explain the value of doing nothing, as a lead, and feeling like the team are getting credit for my doing nothing (which is all good, but doing nothing is a deliberate action in itself). If people feel the team are doing things themselves, then I think I’m following the path ok.

  • Friday afternoon – we’re re-establishing personal research time, so I started tidying up the spare office/table football room. OCSI now has a Memory Box.

In links

In photos

Dragonfly trapped on replacement bus

A dragonfly resting on a bus window

Till glitches

Till screen glitch at train station

Till screen glitch in bookshop

A marrow escape

Giant courgette, almost a marrow (and a curly carrot)

And an obligatory slice of London

Abstract photo of London pavement

Weeknotes 08×06: Make it all up then go away

Totorostreet art and graffiti

It’s a bit of a struggle to start writing these weeknotes this week, for two reasons. One I’ve been off for two weeks and am feeling relaxed. Two, a lot of my thoughts are fairly personal, and range long term over the next few years. It’s hard to turn that into something small and daily. But hey, maybe weeknotes is also a good excuse to get out of that a bit, get back to the practical stuff, and to think about just being open by default again.

So here’s a quick run-down of some thoughts on things that are happening. As this is traditionally the sixth and final “episode” in my series, I was going to look back at the aims I set out at the start. But I think I’ll save that for another time.

Three things that happened

(More than three things happened.)

1. Recapping on an ad-hoc strategy process

One of the key strands this series has been helping to draw out a coherent company strategy for the year ahead, including setting out my own directions for the tech team within that. My processes for this have been instinctual, rather than based on a known structure, partly because I didn’t have time to research ideas, and partly because I know the people involved, and it’s easier to design the process to fit their mindsets, working patterns, knowledge domains, styles, etc.

This week I wrote up the results from the process, in order to form my own strategy and see how well it aligns. I wish I could share all this more openly, but it would be remiss to do so. However, in a nice season of synchronicity, I’m also reading a book all about deliberation and decision-making (see “Culture” section, below), which helped put that recap of my own work into some perspective.

The key theme of all of my prices has been to try to gather inputs from a particular group of stakeholders first. This has happened a few times in different forms:

  • A group meeting, in person, to collate tech team pain points, and another meeting to summarise and confirm the ideas
  • A Google form survey to gather thoughts from the wider product team, on what they would like from the team
  • A few face-to-face sessions with the Management Team to draw out overall company aims over the next year

It’s not been the easiest thing to do in an experimental way – it’s not always clear what I’ve been asking for, or why, or what’s going to come out of it. But it does make a lot more sense than before, and I’m at a crux point with it.

The next step is to hammer out a clear and succinct write-up, and to base a final tech strategy on it. This should be fine – the key big challenge after that is to communicate it out to the team. I’ve agreed a date to go through it with the tech team, and would like to take the management team through it. This implies, though, that I should also go back to the other people I surveyed, to fill in the gaps and complete the circle.

2. Work happened while I was away

It’s always good to go away. I see it as a test of how well the team cope without me. 🙂 This time, there’s a particularly gnarly piece of work going on to migrate the geographies we use, and we’re slap-bang on the discovery and design stage.

Migration is one of the harder aspects of technical projects, I think, and I’m surprised there’s not more literature on blogs devoted to it, compared to sprint processes, testing, etc. Maybe I’m just looking in the wrong place, but I’ve done a fair bit of it over the last year, and seem to have an innate fear of doing it badly now.

Really pleased to see that the team had done a great job of planning it the work and looking into what’s required. The efforts we’ve put in over the last year seem to be paying off, and while I think I could do more to create a more ‘unified’ team (whatever that means), what I see, and the feedback I get (including from an annual review this week) is that things are running fairly smoothly.

It’s odd to reflect on that, and the effect I think I’ve had over the last 3 years. When you work with people on a personal and career development level, it’s not always easy to make the link between coaching/mentoring and the delivery of the work. How do people value that? How can that “experience” and “directioning” be taken account of within an organisation? Or is it something that people just “understand”? Sometimes I feel like it’s an intimate connection between myself and my charges, and I have no idea if anyone outside of those relationships sees or values that.

3. Somehow I am a research project advisor

On Friday I met up with Angie from Community Works, who’s running a project for local charities. There’s a survey and lots of data involved, lots of political implications, and some tough choices about how to design the work as a whole. The steering group that I’m on has a lot of great skills and experience shared across it, and I’m really enjoying seeing others jump into action. Just watching others work is so, so important, and sometimes I hit a mindset where I’m really happy to shut up, watch and learn, almost like I’m work-shadowing. It’s great to have that opportunity, and maybe that’s a big part of my weeknotes practice – to try to give something back in return for all the times I’ve learnt from others.

Anyway, we had a good chat, and afterwards I realised this is both what I do, and what I don’t do. I do project design all the time. I’m not considered a “researcher” though. The link between designing a project and designing a piece of code is real though. And between designing an approach to a task, or a strategy. This is all systems designs thinking. And a lot of it boils down to asking:

  • What needs to be done?
  • What order does it need to be done in?
  • Where should it be done? As in, which person, or what phase or component, or which object in your code?

Between these questions you basically get the outline of your system, and – more importantly – a way of dividing up chaos that lets you actually think about it in a simpler way. Scope, dependency, relationships. Everything else is detail.

It’s very rewarding being able to bring this kind of thinking to a fresh context and person. Like I’m testing my own design skills more.

Right, these notes are already well late. Catch you later.


  • Finished reading The Tao of Democracy by Tom Atlee. Got me thinking about what I do. What I like doing. A lot.
  • Finished watching West Side Story from 1961. Funny, I listened to the soundtrack a lot as a kid, and never realised how much of a social commentary it was 🤔 Some great sound and visual design though, worth a watch.

  • Writing: I finally started a new blog to keep track of my solar power adventures – https://6suns.exmosis.net/ – I’ve been running my phone and watch off solar power for 15 weeks now, and figured it was time to start being a bit open about it.

Weeknotes 08×05: Legacy is Productive. Agreement is Conflict. Slack is Usenet.

Abstract monochrome taken in London

What just happened?

(All photos from London on Thursday.)

Monday. Legacy Code is Productive Code (Sometimes).

Weekly sit-down. Various coalface deployments. Over the past few months, Emma and Obi (researchers) have been doing some great work to revamp the data delivery process for our US client. This has made some fundamental changes to the databases being used, which also means the tools that we use to manage the data need updating in turn.

The tools that we have are not what you might expect. In today’s modern world, mention ‘data management’ to people and they’d probably expect you to be talking about either a dozen crappy shared Excel files, or a giant database overseen by machine-learning overlords.

We have both – giant databases which are managed through a dozen Excel files. Why? Because it works. Usually. Just.

Sadly, because it just works and hasn’t needed changing, I’m the only person who really knows how it works currently. So I spent an hour taking Emma and Obi through the mechanisms. And by “mechanisms”, I mean “slightly-commented VisualBasic macros from 8 years ago.” Yeah, some things don’t get iterated and improved quickly and continually- but they do power projects and companies for years on end.

Looking back through the code, I was hit by two things:

  • Wow, how is this stuff still running? I mean, I know legacy code exists, but you’d expect a certain amount of … entropy that would force some sort of change to happen. I mean, it’s good it’s still relevant right?
  • But if we were to do things differently, what would we do better? It does work, it lets people manage data, and despite all the advances in data science, APIs and user research, managing data as a manual process is still one of the hardest things you can do.

So we have legacy code with a slightly shonky Excel interface, but is the lesson here that “legacy” isn’t always a dirty word, if the system is a) usable, b) understandable, and c) still fits the context?

Maybe there’s also a lesson here that says design for what makes sense, or something?

Smithfield Market roof, London
Smithfield market, Farringdon

Wednesday. Agreement == Conflict (Sometimes).

It’s the end of July and everyone – and I mean everyone – is on holiday recently or in the next month. So the ongoing aim to get a shared strategy together (see last week’s notes) before the end of August is looking … “tetchy”. Which is also what people become when they have to change from doing their own thing, to doing something in true collaboration.

This is also a theme that came up on Thursday, but at a global/democratic level rather than for a hot room with four people. But I think the gist is the same – most people hate giving up their well-cultivated mindset and opinions. And by “hate”, I mean “hate, detest, abhor, DESPISE”. If you’re in an organisation that has somehow managed to embed and stick to the idea of “strong opinions, weakly held”, LET’S TALK. Getting that mindset in place feels like 95% of the work, and I have no idea how it could scale to any 3 randomly-selected people.

So a bit up against both time and humanity on the day. We’d managed to agree a rough strategy overview previously, and this was a follow-on session to look at how to divide up our time among our workstreams. This was kind of where the conversation started, so we’d come full circle.

The circular route was intended, originally, to avoid discussion which went round in circles. My new motto, it turns out, is “THERE IS NO RIGHT ANSWER.” Reminding people of this – and that you are here to get an answer – is a good way to drive progress when any decision can be argued against, by opinion, or at a process level. I want to print out Winston’s quote on democracy. I want a trail of dead post-it notes to indicate when we get back to where we were half an hour ago. I want robotic meeting memories.

Anyway, we went round a few circles, but the work last week did help restrict the overall scope of the conversation. I felt like a frustrated facilitator/nasty negotiator at times, but I also felt like it was needed at those times. Progress requires being bold, most of all. I think there’s a lot that engineering brings to this art, oddly. A timescale to build something gets you creative and, ultimately, harsh because non-delivery isn’t an option. I love being an engineer. Is “decision engineering” a thing?

Also plusgood – aim 2 this series was to “set the course of work and of the team for the next six months” – this is a huge step to being able to set it for the next year.

Abstract of bicycles at Barbican, London
Slice of London, Barbican

Thursday. Exmosis is real. Realer than the people themselves.

London, wooo! In the searing heat! And with delayed trains! There, that’s the negatives out of the way, cloaked in exclamations to scatter their power. !

The third aim this series was to “get out of the office and go and talk to people” – Thursday was the day for this. I’d arranged to meet Louise as she was in town, which meant I also ended up getting to see Steph and Sam from Free Ice Cream, as well as Laura from our partner organisation (who’s moving on and we chatted about weddings), and Giuseppe over a beer near Victoria later on. Thanks to everyone I met, I needed it 🙂

Some great catch-up and conversation on consultation processes, democratic engagement, scopes of understanding, remote working, company strategy, blockchain politics, and emotional mapping. I felt slightly “odd” going up, because I wasn’t meeting anyone for anything “specific” – not a project, or a planning session. I described it to myself as a “semi work jolly” and wasn’t sure whether to really expense stuff.

But after the day, I was reminded of really just how important this kind of conversation is. It goes back to the made-up definition of exmosis, the made-up word I used as my permanent domain: “exmosis” is the learning we naturally absorb from each other purely by being around each other. The learning, and the transfer of it around our network, is more important than us as individuals. Humans are just a learning network, and nodes within it would be nothing without that.

This ‘existential’ learning is not something that has business value. Economics likes things to be structured, directed, clear and concise. Training courses and productivity metrics. Business deals and yadda yadda. It’s not until you piece together a situation, a puzzle, a conversation, and an ‘a-ha’ moment, that you really appreciate the value of learning from each other.

I also did over 14,000 steps apparently, which put my sandals into shock.

"Accurcy is Appreciated" sign
Notice found in cafe loo, but felt appropriate for global democracy too

Friday. Slack is the new Usenet.

I started out by sorting through my Slack channel list on the train. After hearing how others use IRC instead of Slack, I couldn’t help think about the difference. I miss the “nowness” of IRC – the sense of presence and attention. Slack is great and useful, but to have it as another background tool that you can catch up on? That risks just becoming yet another source of information overload. In addition to going through emails, I end up going through Slack as well these days.

I spent a little while Friday morning trying to recapture this sense of “social focus” by leaving a whole bunch of low-priority slack channels. In doing so, it makes me realise that Slack is more akin to Usenet/forum message boards than to IRC – topics are a good way to turn “Noise” into “Signal”, but that advantage is totally lost if everyone has to be in all channels to know what’s going on.

This does, though, break the use of the “@channel” notification route, which highlights a conflict in the Slack experience – is it a mode of communication, or a mode of broadcast? By joining a channel, am I there because I want to talk, or because I want to know what’s going on?

My current solution is to be picky about my channels, but also mute as many channels as I can – it turns out you do see an indication of whether you’ve been mentioned or @channeled. I’m not sure if it mutes emails though.

Friday was otherwise half spent initially planning out a large task for the next few months with Stefan, Obi and Alex, which has given us a good start. And half tidying up stuff before heading off. I’m off for two weeks, so definitely no weeknotes, only wine. Winenotes? Is that a thing? I’d like to do a series recap when I get back, to remind and reflect on what happened recently, and get my head in pace for the Autumn.

Also, it rained today, so I’m taking that as a good omen, and a symbol of washing away the work mindset. Enjoy yourselves. Be nice. Smile. Over and out.

A giant concrete tower
Remember, concrete did shards before glass ever did


  • Not been consuming too much recently, but have now watch all of the first series of Our Country on iPlayer. It’s funny, and also slightly sweet and/or inapproriate.


  • Levels are low after the lack of rain – so low that the pond liner is showing through. I’m hoping the fish are OK.