...The team co-locate (as far as is possible, given that the development of the service is already underway) The team look at how they will be making the source code...
...We recommend the iPython notebook and R Studio as good applications for writing code. A good text editor is also extremely helpful (we recommend Text Wrangler). If your work firewall...
...Analytics is now sent directly to the platform, reusing open source code from our team. Now HMRC controls all of its data and is able to quickly automate their integration....
...publishing platform, which concerned the panel before confirming that the team are capable of making their own amendments to the codebase should GOV.UK’s roadmap change. Security is being considered well...
...with them to ensure that their non-repudiation requirements will be met. Coding in the Open The team are committed to open sourcing the code for the service from the outset....
...new technology. This includes adding more data related content to the Technology Code of Practice, the Service Manual and the Design System. Supporting the government data communities by bringing the...
...is not available and confirm what the approach for this will be in public beta; ensure that they are evaluating code for sharing; implement Analytics and discuss (as already scheduled)...
...appropriate. A large proportion of the code is open source and being developed in the open. Some libraries are not yet open source but the team has a roadmap for...
...content, to multiple lines of code and incomprehensible combinations of characters. To extract insights, colleagues suddenly needed to manually filter out tens of thousands of unusable responses over the year....
...code. This will inspire future developments to the package, completing the development cycle. Aside from the accessibility legislation, the biggest feedback was the need for an R native solution. R...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.