Task Splitting and Circular Dependency Resolution (146)

Total hours: 261.367

Top three:

1) Documenting Security Protocol

This is complicated because it depends on the level and the level also depends on other factors which I haven’t yet figured out. However I managed to sidestep most of the circular dependencies and concepts by ensuring that all accounts start at lax and can be upgraded or downgraded in the future.

2) Collapsing and pushing key management to a later task

Key management and deployment is a very complex issue which is completely separate from the current security task of designing the initial keying and deployment of the software. Unfortunately since the applications need to be in the respective stores, I can’t have each one custom keyed like Backblaze does with their applications. Therefore there’s an important linking step that I need to have succeed without being overly intrusive or annoying.

3) Adding in important and complicated tasks for later use.

There’s alot of task and work that’s codependent. The hardest part is modelling and at the same time not getting into the weeds in one part and loosing the forest for the tree.

But at the same time I can’t be at the forest level all the time. I’m really really good at forest level thinking but not really good at tree level thinking. I need to get better at tree level thinking.