Plan and begin Code Insights backend work

Created by: slimsag

Felix, Jean, and Joel would like someone to step in to contribute to the code insights backend as the project is entirely blocked on that work and has not yet been able to hire a backend engineer. The aim is to unlock the rest of the team to begin showing code insights to prospective customers and set a good foundation for a backend engineer hire to start work from around Feb-ish.

• Discuss with Felix, Christina, and Jean about what high-impact low-cost wins exist with code insights backend work
  • Outcome: I will begin spending 60-70% of my time on the code insights backend starting after my current 3.23 work, ETA Dec 14th.
  • I will begin planning with Felix, Jean, and others immediately.
  • Stephen will ensure the work he does here is solely the high-impact work that will unlock the team to show this to prospective customers and act as a foundation for a new hire; will ensure the work he performs here is a good foundation for a new hire, etc.
• Felix put forward draft RFC with problem space etc. https://docs.google.com/document/d/1LX6Msbxnz_DRf6OItZLaX-vELfnHGKgODkb1bVauolk/edit
• Stephen review RFC and brainstorm with Felix about potential solutions and direction.
  • Call notes & next steps: https://docs.google.com/document/d/1LX6Msbxnz_DRf6OItZLaX-vELfnHGKgODkb1bVauolk/edit#heading=h.y5olw1fgpifr
• Solidify RFC
  • Stephen puts together "learn as we go" draft proposal
  • File GitHub issues for currently scoped work. Publish RFC and begin work, address feedback as it comes in and adapt
  • Get approval from Joel
  • Get approval from Felix (after he is back from holiday)
  • Run RFC by at least 1 other backend engineer (Eric expressed interest)
• Close this issue.