...inferences and recommendations as required Invest time in understanding customer and stakeholder expectations and priorities, developing services to meet those needs, including when they change Promote continuous development of performance...
...of technical skills to support their projects. The new matching process When designing the new process, which we first applied to the last accelerator programme cohort of 2020, we had...
...see all code open sourced, regardless of usefulness to a wider audience or not. The only exceptions are configuration management code, code that contain sensitive information (e.g. fraud detection components)...
...code, code that contains sensitive information (e.g. fraud detection components) or can pose a security risk if open. Publishing the source code will be a mandatory requirement when the service...
...to a relative newbie like me. But as I’m a keen data geek and can’t just take the figure that’s presented to me, I started digging into the metrics ‘Time...
...code from the Alpha so that other people could learn from it and that the team had a clear policy of open by default for the beta code, with a...
...the same question. I work for GDS assessing the benefits of new digital services. This involves a lot of financial modelling and working with number-crunching experts at HM Treasury. Andrew...
...was standardised (e.g. 'Epsom & Ewell' was always named 'Epsom and Ewell'), an 'ONS name' table was imported into the database too. This table contained local authority names, ONS codes...
...etc. Open Source Code The panel were encouraged to hear HMRC are making progress in this area, but we are still yet to see any service code published. Publishing source...
...source code to be made publicly available. Rather than making a judgement on what source code will be useful and reusable, the default approach should be to publish (sensitive information...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.