Friday 16th March, 2018
We’ve spent the week working from Space4, TOG Bloomsbury and home.
We paired more this week than we have for a while. It’s reminded me how much I enjoy it, and how effective it can be. Although we communicate regularly throughout the day, that’s still not quite the same as having two people working through a single problem.
We’re continuing to focus on the GDS Asset Manager work. It feels as though we’re really not too far from being able to serve the Whitehall attachments from Asset Manager (although it’s felt like that for a while).
We’ve been improving the Whitehall code by pulling apart some unwieldy logic into more expressive methods. This makes the code easier to understand and helps give us confidence that we’re correctly updating the assets in Asset Manager.
We’ve also been improving the Whitehall Sidekiq workers that communicate with Asset Manager. They’d grown somewhat organically and we’d ended up storing a fair amount of state on the queue. Not only can this state be out of date by the time the job is processed, but storing lots of data on the queue can eat into the memory available to Redis (as we discovered in week 473!) The workers now take a single database ID which minimises the memory use and allows us to retrieve the state at job process time.
We’ve added code and a Rake task in preparation for updating the metadata of all Whitehall attachments in Asset Manager. This is the final step before we can switch serving these assets from Asset Manager!
We received some more detailed feedback about why we were rejected for the coaching opportunity we mentioned in week 475. I’ve not read through it in detail yet but hopefully it’ll help us understand what we can do to improve.
Cat and Annie of The Dot Project continue to do a great job of working with a subset of CoTech members to produce something that can be used to sell CoTech services to larger organisations.
James has archived some of our older repositories after we received vulnerability warnings from GitHub, including the fondly remembered Freerange Beards.
We’ve accepted the GDPR variations to the Digital Outcomes and Specialists Framework. The more I read about GDPR the more impressed I am by its intent. I look forward to seeing the back of some of the more underhand practices that certain services employ.
Until next time.
If you have any feedback on this article, please get in touch!
Historical comments can be found here.