Hacker News new | past | comments | ask | show | jobs | submit login

> I don't know whether it's intentional or not, but you continually, over and over, take two numbers that are not the same thing whatsoever and compare them or multiply them or whatever else and it simply makes no sense.

You keep running in circles around a very simple statement that was on the front page of your website: "86% of Lambda School graduates are hired within 6 months and make over $50k a year."

Just tell me how you got to 86%, because that's wildly inconsistent with years of outcomes data, in addition to the leaks.

> This is fair - there were students who just wanted experience even if unpaid, and the initial intent was to build it into the school itself literally with no pay. I changed my mind on that one after conversations with a few students, and we changed the design as you pointed out, but no student ever did any unpaid work, so it's also not accurate to say that we had a bunch of students doing unpaid work.

I'm sorry, did you just lie to my face, say, "This is fair" and try move on?

I'll be honest, I can't follow the story you're trying to tell. It sounds way more complex than what everyone watched unfold.

Your FAQ at launch clearly says it's unpaid. You had a product manager on Hacker News trying to defend the program while all the commenters explained, "This is an unpaid intern program and probably illegal." He even tried the same, "Well our lawyers said it was ok." After the Twitter backlash, you tweeted and deleted an apology, and then started acting like none of that stuff happened.

As for "no student ever did any unpaid work," didn't you pilot the program for months before publicly announcing it? (This is a rhetorical question. At this point I lack faith you'll tell the truth.)

>> > It was not a qualified educational loan. Section 523(a)(8) is all about how student loans are not dischargeable.

> Ironically other regulatory bodies disagree with the DFPI on this one, and part of the issue of ISAs is everyone wants to regulate it differently but there's no agreement

Let me get this straight. You're saying, "There's no legal precedent, but hey, it might be true? So we threw it in!"

> OK, I really am spending too much time here now. I remember distinctly when you told The Verge that our iOS curriculum didn't include things that would get a student through a phone screen, I offered a bounty to your favorite charity for you to point out any single thing that we were missing

You blocked me, making it impossible to reply.

> and you backtracked and said, "Well some of your students' code on github wasn't very good."

Despite the block, I said: "Your students publish their homework to GitHub. Half a cohort failed to grasp memory management, but you rubber stamped them through the program.

You even hired one of those students to be a section lead, to teach other students."

https://twitter.com/sandofsky/status/1270761157595262976

"I am not publicly linking to the students who struggled with it, because it’s not their fault. But I did share the GitHub projects with two senior iOS developers I trust, and they agreed these students didn’t get it."

https://twitter.com/sandofsky/status/1270761955976859650

So to answer your challenge: memory management. I have sign-off from two senior, ex-Apple iOS devs. Please wire that money to the National Student Legal Defense Network, who seems to be handling that lawsuit against you.

> I don't know why this has become such a personal grudge.

It's interesting that you think this is all about you.




Our iOS curriculum covered memory management extensively.


I said, "After looking through Lambda School’s curriculum, I’d say students are going to struggle with very basic questions you’ll get on first phone screens," and "Out of ten student projects available, five should have failed."

Yes, you had a page in the curriculum on memory management. You also rubber-stamped through people who didn't understand it, and even contracted one of those people to not-help other students on the topic.

Anyone can link someone to a page about a topic and say it's covered, but the difference between a Udemy course and $30k worth of training is the expectation that someone will actually look at homework.

Anyway, the reason you won't explain the 86% placement number claim is that it was true for one cohort in 2018. That's why you only submitted a single report to CIRR. At scale, the number has always been somewhere between 30% and 50%, but that's easier to obfuscate by coming up with your own methodology.

There's a strong parallel with the time you claimed 100% of your UX cohort was hired, without disclosing that only one student graduated. You said it's ok because you tweeted, "VERY SMALL SAMPLE SIZE."

https://news.ycombinator.com/item?id=26813371

And I'm sure you'll argue you didn't lie moments ago about the Fellows program due to what the word "launched" should mean. You have shown a pattern of deflecting the substance of criticism by focusing on technicalities.

Maybe this worked out for you in a different life. I suspect you've gathered so many critics, you're "attacked at all sides," because you're now among engineers. They just take your data, plug it into a spreadsheet, and let the facts speak for themselves.

https://applieddivinitystudies.com/lambda-lies/

But I don't think this had to be. There's an alternate timeline where you did a mea culpa, cut out the shenanigans, and the tech community washed the bad taste out of its mouth. This could have been an incredible reception arc. Instead, Paul Graham enabled you with that whole "haters" pep talk, and things went downhill from there. So it goes.


And what about the rest of the criticisms of your methodology?


Which ones?

The team that built our iOS curriculum is _literally_ the team that built the iOS curriculum at Apple. (https://www.linkedin.com/in/calebhicks).

Honestly at this point I’m getting back to work, I don’t think this conversation is fruitful.


It's been very fun watching this flailing get more and more desperate over the years on HN. Thank you for this!




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: