Category Archives: work

26 Apr
2021

Best Things About Developer Advocacy

There are some excellent articles around about what a Developer Advocate does, but have you ever wondered WHY we do what we do? I tried to articulate this when chatting with another developer lately, and I'm still thinking about it! So I thought I'd write it down to share a little more widely why I love this strange, misshapen career as much as I do. Continue reading →
31 Jan
2021

Lab Book Meets Bullet Journal

I enjoy a productivity hack as much as the next person, and I'm often asked about my setup. My background is in engineering (I hold an MEng in Electronic Engineering from York) and recognise the legacy of the lab book in much of what I do. If you're new to the lab book concept, check out this excellent article on how to maintain one properly. My practice breaks a LOT of the lab book rules and is also heavily influenced by the Bullet Journal trend (if you have time to spare, the instagram #bulletjournal hashtag gives a prettier introduction), which is a way to combine the benefits of productivity and processing information by writing it. Today's post gives a quick tour of my process. Continue reading →
23 Dec
2020

Digital Developer Relations: Past and Future

I work in Developer Relations, or "DevRel", and 2020 was a strange year with travel restrictions that meant that the entire industry did everything online, or digitally. I see this as a very positive progression of the way we work as DevRel professionals, and I understand that might be controversial, but I'd like to back up my position so hear me out (and then let me know what you think!). Continue reading →
26 Aug
2018

Support for Speakers

I've been a conference speaker for 10 years; I've given many talks, been to many events, organised a few events, and now have Opinions (TM) about conference speaking. This tweet showed up in my feed when someone tweeted at me to thank me for my support in their talks.

My approach to supporting other speakers is not really about the audience I would like (we're all different!), but more about making two things happen:

  • someone being the best they can be
  • them getting credit for that

In fact I've been a speaker coach and mentor for a few years and have variously watched rehearsals, suggested where to stand and not stand, walked nervous speakers around outside before their talk, fetched water ... all sorts of things. However this twitter thread (I got a bunch of tweets and the replies are also great) shows that _anyone_ can give great support to any speaker, whether you know them or not. Here are my favourite three things to do to support anyone giving a talk. Continue reading →

30 Jan
2018

What does a Developer Advocate do?

I'm a Developer Advocate (you might also hear job titles like Developer Relations, Developer Evangelist) and I'm constantly asked what that means. What do I do? The answer is different for every one of these jobs but there are some common themes. After 18 months of practice at answering this question, I think I'm ready to give it a go. Continue reading →
02 Dec
2016

Presentation Help Office Hours

When I joined IBM this summer, one of the things I was most looking forward to after years of being self-employed was having a team around me. Well, that team continues to meet my expectations on that front but there's one thing we do as a team which really stands out for me - and which I think others could replicate. Continue reading →
04 Jul
2016

Using OS X From The Keyboard

I have a new job (Developer Advocate with IBM Cloud Data Services) and subsequently a new work laptop. It's a mac and after almost 10 years as a linux-only user, that's rather a shock! Due to some nasty RSI issues, I don't use a mouse or any other pointing device*, so as well as learning a whole new operating system I also needed to learn its accessibility tools. I'm still at the swearing stage but mostly past the tears so I thought I would share what I've found - using a computer from the keyboard is fast and productive for everyone as well as less painful for me, so you may find some tools in here that you want to try yourself.

I collected all my tools, my own notes and scribbled cheatsheets and put them into this gist so that I could refer to them later; I also intend to keep updating this as a reference. Continue reading →

09 Feb
2016

Simple One-to-one Meetings

Recently I was giving some advice (that I was asked for, which is novel) regarding one-to-one meetings between developers and either team leads or management can be structured. My thoughts really boiled down to some very short points (this is why sometimes, those meetings take 15 minutes and other times they take 3 times that for a monthly update!). In case they're useful to anyone else, here's my meeting outline:

  • What's going well/what are you excited about?
  • What's tedious/annoying or actually a problem?
  • What could I be doing that I'm not?

Continue reading →

02 Jun
2015

Code Reviews: Before You Even Run The Code

I do a lot of code reviewing, both in my day job as principal developer and also as an open source maintainer. Sometimes it seems like I read more code than I write! Is that a problem? I'm tempted to say that it isn't. To be a good writer, you must be well-read; I believe that to be a good developer, you need to be code-omnivorous and read as much of other people's code as possible. Code reviews are like little chapters of someone else's code to dip into.

Over time I've developed some particular processes that I find helpful when reviewing code. In particular, I often surprise people at how much review I do before I run the code. Sometimes I grab the branch so that I can use my local diff tools, but I don't actually execute code until I've established some basic facts. This post is a little insight into what's happening in this not-running-the-code-yet zone. Continue reading →