It is very, very high.
I’d have to dig to find the exact numbers but about 90 are directly involved in instruction, project management, etc. Not including student support.
> Do not make changes to ongoing cohorts
We really try to avoid doing so, but in some instances it is impossible.
> Isn't this something a school would be able to educate on? Why not introduce group projects (maybe you already have them)?
We do have group projects and do try to educate here. Students will come back a year after being hired and say, “Wow, I thought x was a waste of time but it was extraordinarily useful” all the time.
You sold students something you can't implement. Apologize and offer a full refund.
Students can be with Lambda for as long as 2+ years. Everything being frozen in time would be to their great detriment.
These are not the changes OP is complaining about. Your responses kind of strike me as misdirection.
Don't pull Bill Clinton [1].
When enough people complain you made changes that are material and detrimental.
[1] https://slate.com/news-and-politics/1998/09/bill-clinton-and...
The only times we can’t do that (and that’s happened maybe 1-2 times in the history of Lambda School) is when it’s a change to teams of students that run across multiple cohorts.
For what it’s worth, major changes in curriculum do lead to refunds at schools. There have been two examples in my education where mid-year I had a graduate level class need to be rescheduled from a night class due to a professor’s illness. Both were fully refunded when I couldn’t fit the class into my work schedule. That seems to be pretty analogous here, and I wasn’t charged a percent based on how many weeks I attended the class before the change. I was just refunded the total amount of the course because I wouldn’t be able to gain its value. It wasn’t even a difficult process to get the refund, unlike the weeks of trying to get support it seems like the person in this situation attempted.
I think I would place ‘elevated’ expectations for refunds on a founder due to the elevated risk of trying a Startup’s unproven, expensive, and risky education model. I don’t think the expectations are ‘elevated’ but I also think your baseline for doing good for students shouldn’t be ‘it’s only as bad as I perceive the alternatives.’ I think we should strive to do better.
But frankly, if the only thing you took out of this post is that the ISA structure is poor, without considering how you have all the power to set and enforce terms in your contract, I don't think I have much else I can say to try and help you. I think there are a lot of ways you can improve Lambda School to make it better for the people attending. And they don't involve deleting Reddit threads of criticism.
Edit: s/selling/securitizing
You are incorrect in your understanding of how ISA financing works. Our interests and incentives remain aligned.
Interesting, I didn't know this. I thought you just sold the ISA outright, which would retain some of the incentive but weaken it quite a bit. It's great to hear that that's not happening.
I found https://lambdaschool.com/the-commons/announcing-our-new-isa-... discussing this in more detail. Seems like everyone complaining about Lambda School ISA financing should just read that...
It's still completely aligned, we just fast-forward some of the cash so we don't have to raise endless amounts of VC.
As a student, I can confirm this is a lie. And you know it is because we have told you in Slack, we've told you on Twitter, we've told you on Reddit, and now you have to read about it on Hacker News.
> 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)?