...team – in opposition to our RAP principles. The more you invest in developing these skills in your teams the less likely it is you invent a black box. But...
...service is not currently at a standard to move into public beta, there is a longer term vision, sustainable team and infrastructure in place to be able to quickly build...
...to source systems data, to untapped sources like PDFs, free text, voice and others. We should invest in APIs over large systems, in better tagging and metadata, in the basics...
...available to view on GitHub. If you'd like to know more about how we productionise related links and what we're doing next, please get in touch in the comments below...
...departments and users to determine whether the code is useful. We recommend confirming the availability of and adding a GitHub plugin to the existing source code repository early in beta...
...general introduction to data science, we recommend Wikipedia, the Data Scientist’s Toolbox and Data Science Central. Drew Conway's diagram is an introduction in itself... Choose a project This is perhaps...
...code will lead to other services learning how to expose similar functionality in that manner. It should also provide working code for ideas that could potentially be taken to the...
...to remove unnecessary risks and issues from the service. The service is unable to perform end-to-end testing in an environment identical to live due to the numerous integrations with legacy...
...to better understand how well their content work is performing. The team uses agile methodology to deliver our work, which involves daily stand-ups to provide updates, fortnightly sprint planning, retrospective...
...started by looking for ways to visualise the data in the Google Analytics interface, as I wanted to be able to break it down into individual visits. This is where...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.