Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
Agenda
- Definition of Done (5mns)
- Consensus on long-term goal
- Today's Problems/Observations
- Developer Velocity
- Pull request complexity
- i.e., over interdependencies
- Pull request wall time for tests
- Developer onboarding
- Disorganization
- Quality
- Clear seams and contracts for tests
- APIs
- Brittleness
- Extensibility/Modularity
- Incremental Upgrades (Python/Django) - Future
- Question:
- Will a containerized/modularized monolith within the same repo give us the benefits we're looking for?
- Yes, with the exception of:
- incremental upgrades
- test time - unless we come up with a smarter test-runner
- independent scalability/failure-recovery
- Metrics (30mns)
- Before embarking on this project, what metrics can we use to validate our progress and success?
- Collect metrics from the field
- That extended around the monolith
- Enterprise projects
- Learner projects
- That needed to deal with the monolith
- That tried to modularize before working
- Which metrics?
- Extensible Modularity - Repo lines touched (how many lines within the monolith needed to be changed for new features)
- "Good metric"
- Easy to measure
- Actionable: validates/invalidates
- Hotspots within the codebase
- Which modules of the code have a lot of contention?
- Number of commits touching the same file
- EdwardF (Deactivated) to share Hotspot presentation
- Code reviews (measuring modularity)
- PRs that needed cross-team reviews
- Number of reviewers that needed to be tagged
- Number of comments
- Pull Requests
- Number of files touched
- PRs that touched multiple modules
- Time-to-value
- Review proposed Epics (15mns)
- Next Steps (10mns)
- Swarm or Divide-n-Conquer?