Usually I take a week off every 6 episodes – this time round, it was two weeks. But it was a deliberate decision – I needed the rest, Feeling pretty tired in the run up to the end of the year, and trying to lift some of the pressure on myself. I’m going to go back to some fairly unstructured notes for a bit too; no season aims this time, and length/style of notes will be as needed.
I’ve also started using the open source Diary software on my phone, for no reason other than it’s open source? I like the Markdown approach too, and the way you can add in maps for where you are, but it’s so far looking harder to get the content out into other places. And TBH, it was pretty bloody hard with Evernote, anyway.
Monday: Communication as Curation
Trains. Times, routines, patterns, rhythms. All to get not somewhere, but anywhere. An infrastructure to allow flexibility, mobility. Go anywhere, do anything.
Tunneling through the boarded up walkways at London Bridge, I notice the signs and boards standing out. Travel disruptions, station constructions – everything is in flux and subject to change. When things change fast, clarity of information is key.
The structure for clarity needs to be in place before it’s needed. The process for feeding into that structure needs to be smart, and understood as an artisan aspect of communication.
Communication is about curation. Working it what not to say, as well as what to say.
So many plans today. It feels like we’ve gone from no plans to too many plans. What’s the best way of organising them, interleaving them like shuffled cards?
If I follow my thoughts on structure before process, should I establish a theoretical structure for priorities before going any further?
Wednesday/Thursday: Is Sychronicity a Job?
Flurries and fortitude. A scrabble to sprint, the scrum feels as organised as it could be.
It’s odd having a few days out of the office at this point. Everyone that’s been in is heads down in detail. Everyone else needs a higher level conversation. I don’t like to distract people from the details, but it’s a necessary evil. I spend a lot of my time working out who knows what, and who needs to talk to who.
I’ve come to conclusion that this is scary I bring to the job. Synchronicity.
The problem is, it’s not a formal skill. It doesn’t get recognised as a tech skill. Maybe it falls under “project manager” or “leader” or something, but it’s a strange and hard art and is more important than a lot of other things.
But as a result of it being an internal awareness, an instinct more than a role, I’m not really sure where to go with it next.
Friday: Flow Friday
Beta release day. Not enough closure focus? I can do context, planning and admin. I can do closure for myself. It’s a lot harder to clamp down across a team – so many people have been involved that disentangling them in order to close tasks is fairly complicated.
Hopefully I can learn from this for the next chunk of work. In fact, here’s a personal aim for the next 3 weeks: close as much as possible, as early as possible. Practice closure. Closure is agile.
Otherwise spent a lot of time today planning out code architecture on a giant white board.
Doing this, I realise how much I enjoy this – the sketching, the way it goes in with work planning. I’ve learned that the way code splits up (decouples) is directly related to the way the team splits up. And some people are driven by sticking headphones on and getting their mental teeth into a well-defined chunk of work, while others really appreciate shadowing and peer-working on a particular area.