Table of contents

Owning your development plan

Developers should take responsibility for their continued learning and development by forming a development plan.

Your role as a developer

Developers should identify areas they are interested in and areas where they have skill gaps and seek out suitable resources to help further their understanding. This might include books, courses, self-study, conferences, or mentoring.

Your development plan should be reflected in your objective (for example under the heading “What are you doing for personal development?”) and discussed with your line manager.

Junior level

You will probably have broad goals in your development plan as you become familiar with the large surface area of modern development and web/dev ops.

As a junior you have 20% time where you can focus on things that will help your development such as tutorials, books and projects.

You also have the opportunity to to work on a project that is non-delivery related but benefits GDS. A 20% project should have some specific learning outcomes and pairing with other juniors is encouraged to help you support and learn from each other.

There is a spreadsheet of suggested 20% time projects.

You should discuss the project with your line manager before starting on it.

Mid level

Your development plan may begin to focus more on higher level concepts, such as how to design maintainable and scalable solutions. You could focus on not only learning the intricacies of code, but also other skills that go into developing software like user research and writing good user stories. A mid level plan might also include some mentoring and presenting to help spread knowledge through the organisation.

Specific technology learning might be project based. For example, if you are working on search you might delve into Elasticsearch.

This page was last reviewed on 28 December 2018. It needs to be reviewed again on 28 March 2019 .
This page was set to be reviewed before 28 March 2019. This might mean the content is out of date.