- ID
- 05b94011-4d9a-4b96-a434-afde3b24afb6
2020-04-23 - Thursday
Tasks
DONE [[id:1a25c7bf-7040-4905-9075-2b12948b128f][Admin Squad]] stand-up
CLOSED: SCHEDULED: <2020-04-23 Thu 9:00-9:10>
DONE Complete [[id:9a41e0e4-e656-4238-9c9b-2a62d9c7d465][15Five Report]]
CLOSED: SCHEDULED:
- LINK
- https://15five.15five.com/report/current/
DONE Improve efficiency of [[id:ca1d297e-764f-4c7d-90c7-93f448fee10b][People Attributes]] values API
CLOSED: SCHEDULED:
- Note taken on
This work has exposed a lot of funkiness in the current design. Turns out
ripping large chunks of functionality out can have repercussions for the
reliability of what’s left. Mostly it’s removing the two different value
types. I discovered that we still have a need to process the `value` field on
PeopleAttributeValue instances, because default values need to be loaded from
where they live on the User model.
General notes
- Note taken on
Github is averaging “two nines” here in April :/