Monday 01st August, 2016
Changes to Benefit cap calculator
- PR #2477 - Spike: Allow user to choose between 2 versions of benefit-cap-calculator
- PR #2478 - Spike: Duplicate benefit-cap-calculator flow for 2016 changes
- PR #2480 - Spike: Duplicate benefit cap calculator flow for 2016 changes (with duplication then removed)
The changes to this Smart Answer ended up causing quite a few problems in the team and, in hindsight, I think it might’ve been better if we’d taken on the work ourselves.
Modelling Period of Incapacity for Work (PR #2479)
James built on his spike (PR #2280) to introduce this domain concept into the calculate-statutory-sick-pay Smart Answer. Domain modelling is something that’s sorely missing from Smart Answers so this is a great step in the right direction. We’re left with a Smart Answer that’s easier to test, reason about and discuss.
Fixing auto-correctable Rubocop violations (PR #2474)
James fixed a whole load of the auto-correctable Rubocop violations. This gets us much closer to our ultimate goal of having no violations.
Removing legacy code (PR #2476)
James removed support for an old name-based branching mechanism that was previously being used in Smart Answers.
Remove worldwide fixture data from regression test checksums (PR #2473)
This relatively small change means that we’re now consistently tracking worldwide fixture data in the regression test checksums.
Remove unnecessary explicit namespace qualifications (PR #2475)
The PR description says it all, really.
I continued to make progress with the backlog of week notes. Sadly, we seem to have fallen into the same trap again. I’m currently writing these about 3 months late!
We had some further discussion about what to do but are still yet to come to any conclusions.
Salary, dividend and pensions
I finished working on this task that I’d started last week. We agreed to reduce our salary and dividend amounts and to increase our pension payments.
We had an email from someone asking us about the Geohash explorer app hosted on our domain. James and I had completely forgotten about it but some investigation revealed that it was a project of Tom W’s. You can read more about it in notes for week 154 and Tom’s blog post, “A small toy to explore geohashes”
Show and Tell and Monthly Drinks
We resumed organising these tasks after a break at the beginning of the year. James got straight on the case and organised the monthly drinks for April.
Updating our cashflow forecast
We have a very basic spreadsheet that helps us forecast how long we can continue paying ourselves based on our current assets and liabilities. We noticed that some of the figures had been out of date for about a year, and that it didn’t take account of some additional monthly expenses. We updated the figures and also updated the instructions to try to make sure that we keep on top of these sort of changes in future.
Until next time.