> We have just north of 2,000 students and ~180 full-time staff members, the majority of which are student-facing.
2000/180 = 12 students per staff member. This seems high and "student-facing" is padding the numbers. "Customer Success" people are technically student-facing but not instructors, and number of instructors per student is the most important number that matters for quality
> This student’s frustration comes from a series of changes we made simultaneously
Do not make changes to ongoing cohorts
> Some students see it as one more thing distracting them from writing more code, and believe the only thing that will determine their career success is ability to write code
Isn't this something a school would be able to educate on? Why not introduce group projects (maybe you already have them)?