/
Operation Tame: Proposed Epics

Operation Tame: Proposed Epics

Brian Beggs and I came up with the following epics:

  • Document Best Practices and Architecture Decisions
    1. Code Structure: Python modules/django app, Tests, Assets, urls.py, settings.py
    2. Assets: JS, Pattern Library, Sass, etc.
    3. Interfaces:
      1. api.py
      2. REST
      3. Messaging (async versus sync)
    4. Tests: Thoughts on Tests
    5. Repos vs django-apps vs IDAs
    6. xBlocks can use django!
  • Validate the Seams
  • Discovery
    • Can we co-locate assets?
    • Find/create automated tools for refactoring
    • Metrics
      • Complexity analysis tool
      • Dependency analysis tool
  • Dependency Graph
    • Use as ongoing metric to validate progress
    • Use as input for organizing folders and extracting components
  • Organize
    • Group by functionality using automated tool(s)
    • Validate progress using metrics

Related content

Arch Tea Time: 2020-04-30 (Configs, OEPs, CookieCutter, Shared Slack)
Arch Tea Time: 2020-04-30 (Configs, OEPs, CookieCutter, Shared Slack)
More like this
Arch Lunch: 2019-09-26
Arch Lunch: 2019-09-26
More like this
Arch Lunch: 2019-06-20
Arch Lunch: 2019-06-20
More like this
Book Club: Boost Your Django DX
Book Club: Boost Your Django DX
More like this
2021-05-03 Python Study Group Retrospective
2021-05-03 Python Study Group Retrospective
More like this
Architecture Challenges (2017-2018)
Architecture Challenges (2017-2018)
More like this