This collection of the blog is about the less technical stuff related to the work I do. You'll find less in the way of code fragments and geeky pedantry and more opinions about professional software development and IT related subjects.
I get a lot of questions about the fine details of what remote working actually involves for software development. So here's a few descriptions of how various activities play out when I'm working from home.
I've been remote working as a software developer for more than 12 years. That's full time remote, with occasional trips to "the office". Here's a few of the things I've learnt and passed on to other remoties as we've built a remote working team.
Remote development mainly involves the same tasks and challenges as when you're sat in the same office, except that any communication issues can't be fixed by physically standing/sitting next to someone. Instead the tools we use have to support us in making the sure communication works.
One of the concerns with remote working is how meetings work. I can't give a general answer, but over about 10 years remote working in software development team, I can talk about the regular meetings that pretty much work for us
While introducing agile development ideas, one of the things which went down really well with the project team was the process I used at the end of iterations. This was based around two simple, regular emails that followed the same pattern. I thought it might be useful to talk about them.