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.
Code reviews are a good idea for many reasons. They encourage people to share their opinions on how code should look at its prettiest and also what they like to see when they're called in to look at the ashes of a dead production app.
These are my opinions on reviewing code with a view to swearing as little as possible if I have to see it again when stressed.
In an ideal environment you're either already be using agile dev practices, or have enough support across the project team that trying it is considered a good thing. This post is about when we don't have that kind of environment.
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
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.