...back together as a community. The event was a good opportunity to welcome newcomers, celebrate our successes as well as discuss the challenges faced across the community and share best...
...in the Challenge’s GitHub page. We would welcome your suggestions for others. Although they concern different use cases, all the user needs require the ability to connect a legal entity...
...and online communities concluded in a co-design session where participants developed their own algorithmic transparency measures. One of the key findings from the study was a recommendation to include two...
...maximise the benefits it delivers to the whole CJS. To support the delivery of this work, we welcome and value collaboration from data specialists across government. Are you a dynamic...
...& Tell focused this time around on Data Science Infrastructure. We were very pleased to welcome outside speakers Dr. Jagdev Panesar of British Telecommunications plc (BT) and data scientists setting...
...code available as open source. One recommendation for the future is to continue to clearly separate out secure code and patterns from the wider code base to allow more code...
...having been done, as well as reasons for the service not having published the code yet, and plans in place to publish code over the coming months. The service manager...
...source stuff. RAP is more than writing clean code To the person that wrote that RAP is a redefinition of documenting your code so that another person can read it,...
...checks within the code, but any sensitive code should be managed and kept private whilst all other code should, by default, be open source. We would particular urge the team...
...team to follow and for other teams to emulate. They explained how they now have a fully functioning development environment with integrated testing. Their process for getting code deployed is...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.