We've been doing a lot of work around career paths at GDS, and I wrote a post on the GDS blog about the work I lead around career paths for developers and web ops.
In the last few years I've been more involved in recruitment and seeing a lot of CVs for developer roles has given me some thoughts on what makes a good technical CV. Here are some tips to improve yours.
On our team we always commit code using pull requests, for review by someone who hasn't worked on that code. Here are my guidelines on how to raise a good pull request.
A few weeks ago I wrote a post about being a technical architect, and one of my main conclusions was that you need to stay technical. But how?
I have wanted to be a technical architect since I started out in IT, and last September I was delighted to achieve this long-held goal. But very quickly I realised that, while it was clear to me that the role of a technical architect is overseeing the technical aspects of large software projects, I really wasn't sure what that meant I should be focusing on day-to-day. So I turned to some of the brilliant technical architects I know, both colleagues and elsewhere in the industry, for their advice.
I've written a post on the GDS Technology blog about moving a project from 'coded in the open' to true Open Source. How we moved vCloud Tools from Coding in the Open to Open Source.