Podcast
Questions and Answers
What is the main issue with the current backend design?
What is the main issue with the current backend design?
- Guesses made during 'session continue' do not impact any program-run
- Programs (program-runs) statistics are not effectively captured
- A guess is linked only to a single ProgramRunQuestion (correct)
- User engagement and interaction on Slack remains empty
What is the reason for planning to remove the 'session continue' feature?
What is the reason for planning to remove the 'session continue' feature?
- To increase user engagement on Slack
- To improve statistics for programs (program-runs) (correct)
- To limit the impact of guesses on program-runs
- To reduce the number of user interactions
What is the impact of the current design on guesses made during 'session continue'?
What is the impact of the current design on guesses made during 'session continue'?
- They are considered 'training' guesses that do not impact any program-run (correct)
- They are not captured in the statistics
- They impact all ongoing program-runs
- They link to multiple ProgramRunQuestions
What is the proposed solution to allow every guess to impact all ongoing program-runs?
What is the proposed solution to allow every guess to impact all ongoing program-runs?
What is a key functional problem that needs to be addressed in the system design?
What is a key functional problem that needs to be addressed in the system design?
What potential problem does the 'program retry' feature pose for user statistics and overall completion rates?
What potential problem does the 'program retry' feature pose for user statistics and overall completion rates?
What issue can arise if a lead modifies a program while a user's program run is in progress?
What issue can arise if a lead modifies a program while a user's program run is in progress?
What is the proposed solution to address the issues related to program completion and user progress tracking?
What is the proposed solution to address the issues related to program completion and user progress tracking?
What is a trade-off of replacing the program-run model with a more straightforward scoring approach?
What is a trade-off of replacing the program-run model with a more straightforward scoring approach?
What is the main issue with the current design in terms of user engagement and program completion?
What is the main issue with the current design in terms of user engagement and program completion?