Last year's Dev WorkFlow

1. Feature provided from the product team
2. Prototype
3. Develop
4. Unit Test
5. Work with Infra and QA to release

Current Dev WorkFlow (With Diff)

1. Feature provided from the product team
2. Describe tasks (in Jira, agile)
3. Prototype
4. Develop
5. Implement text into Contentful
6. Unit Test
7. Write End-to-end Tests
8. Write Monitors
9. Work with Infra and QA to release
10. Integrate automatically

This Is Costing Lots of Money

• This is costing lots of money in losses that are not directly related to engineering
• How?
  • Pixel outages
  • Analytics outages
  • Integration across apps and repos outages (somewhat engineering related)
• Reference Link

Dots are not connecting between departments and

engineering teams 

• With feature building, engineers miss important changes when working across many apps and repos
  • End-to-end tests are only covering what is written in Jira; leaving small gaps that get compounded
  • Monitors deal with the same issue

IDEA

• Use Contentful to define business needs
  • Each Feature could can have a corresponding JSON object generated by Contentful
  • This JSON object could provide
    • The feature name
    • A/B Tests
    • Child Components
    • Pixels
    • Analytics
  • This JSON object would be consumed by
    • Face-e2es (end-to-end tests)
    • Face-monitors (monitors)
    • Apps
  • This JSON object could act as contract defined by product and QA
  • Each engineer would then build features, write tests and monitors and not have to be aware of the small knowledge gaps that grow when many features are built and maintained for all of the company by many engineers