State of JS @ The Guardian #426
SiAdcock
started this conversation in
Team Posts
Replies: 1 comment
8000
-
|
I've started a draft doc for this (in the CS Infra shared drive). Let's start filling out the "What do we want to know?" section! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In the CS Infra group I'm sure we're all interested in delivering real value to the department and the organisation. A common question that comes up is how you measure that.
I'd like to propose one source of metrics: a developer survey sent out to the entire department every 6 months. We assess the general level of knowledge of technologies, methodologies and resources that we care about. By analysing the results and tracking changes over time, we can ensure that our colleagues are spending their valuable time learning things that are important to Guardian engineering so that we are all pulling in the same direction. Examples include:
The State of JS survey could be a useful source of starter questions.
If we track the results (anonymised) over time, we might have some indication that our group is succeeding in improving the CS experience from the perspective of our engineering colleagues.
Beta Was this translation helpful? Give feedback.
All reactions