Sprint Retrospective Term 1 - Week 8 Retrospective

[lilymaechling]

• members in attendance:

  • [x] Dylan
  • [x] Annie
  • [x] Abby
  • [x] Lily
  • [x] Melissa
  • [ ] Will

• what worked well

  • Downloading Python file from IDE
  • Uploading Python file to IDE, editing, and downloading file with changes
  • Rendering filename in Bracky panel
  • Getting open AI to run reliably for the majority of requests by tuning the parameters
  • Created collapsible sidepanel
  • Getting voice to code debugged
  • Reducing number of requests-now only one back and forth from frontend to backend
  • Start Coding: create + upload modals styled and functional
  • Cleaning up backend code and commenting it
  • Cleaning up frontend code

• what didn't

  • Getting open AI to run optimally wth complex/vague requests
  • Handling edge cases with voice to code
  • Figuring out where to keep code variable and where to update
    • currently migrating to redux

• self assessment on progress

  • Frontend styling almost complete. Only needs some finishing touches and inclusion of Convodex when written out
  • The backend is now running requests much faster and more reliable. There is still ample testing and research that needs to be done when using such a complex model but we are in a good place to demo simple voice to code

• lay out each of the following weeks till end of term with brief goals for each

  • week 9: working on convodex (ie. basic commands to run that are reliable)
  • week 10: finishing touches and identify use cases

• briefly summarize any other topics/discussions

  • talked about code insertion. We think it is a winter problem. Will require a whole rewrite of how we currently store code because code is currently stored as a contiguous string without notion of line numbers

[timofei7]

for code storage - i'm assuming newlines are in there? if so you can always reconstruct line numbers by splitting by newline into an array.