41–50 of 354 posts
Austen seems to finally have given up on trying spin every story about him that reaches HN, no posts in the last 9 months.[0] A sure sign of the dismal state of things at Lambda/Bloom. [0] https://news.ycombinator.com/threads?id=austenallred
Earlier quoted context omitted.
As a former instructor (not at Lambda), I'm kind of inclined to believe it has more to do with the fact that it takes a certain kind of person to put up with the demands of corporate software engineering. Getting both kids and adults (especially kids) to figure out how to program is easy if you understand that most of the concepts are better taught visually through p5js or what have you. Once they leave that sandbox,…
The frustration factor is a big deal. I took a bootcamp. One day and another student and I were working on something and a third member of our group (who had other issues) was really frustrated and took it out on us and then went to the teacher. She told the teacher "they just get it and I don't". But in truth the other student and I were not "just getting it", we were failing frequently, we had made no more progress…
I did teach a 6 week C++ course. Mostly attended by CS students at the local college. Back in the day we didn't teach kids how to code in a CS cirriculum. They were expected to just pick it up themselves. Six weeks really isn't enough to teach how to be good at C++.
I spent a fair amount of time reading Papert and Piaget, trying to develop a theory on how people learn and how to best teach "programming" concepts. I've yet to see ANYONE (myself included) do an excellent job teaching the kind of programming employers want. I saw another comment here about how "programming" is simple, but teaching architecture and putting things together is hard. I would mostly agree with that.
But... there are some techniques that are better than others.
My experience w/ Lambda School was they tried to hire me as an instructor way back when. I talked to them briefly about pedagogy and their approach to modeling learning and how they were going to measure improvements in their cirriculum. I got blank looks. They kept harping about how they were going to iterate, but without the slightest idea how they were going to improve between iterations.
I quietly walked out the door never to return (moving to Seattle to work for Amazon instead.) It looks like I made the right call.
Where are my people at these days?
Earlier quoted context omitted.
As a former instructor (not at Lambda), I'm kind of inclined to believe it has more to do with the fact that it takes a certain kind of person to put up with the demands of corporate software engineering. Getting both kids and adults (especially kids) to figure out how to program is easy if you understand that most of the concepts are better taught visually through p5js or what have you. Once they leave that sandbox,…
The frustration factor is a big deal. I took a bootcamp. One day and another student and I were working on something and a third member of our group (who had other issues) was really frustrated and took it out on us and then went to the teacher. She told the teacher "they just get it and I don't". But in truth the other student and I were not "just getting it", we were failing frequently, we had made no more progress…
There are tons of smart, hard-working people who have a mentality of "You should be able to do everything correctly and have it work correctly the first time, or maybe on the second try with some minor adjustments". And I think these people will find no joy in being a software developer and typically don't survive bootcamps.
Earlier quoted context omitted.
As a former instructor (not at Lambda), I'm kind of inclined to believe it has more to do with the fact that it takes a certain kind of person to put up with the demands of corporate software engineering. Getting both kids and adults (especially kids) to figure out how to program is easy if you understand that most of the concepts are better taught visually through p5js or what have you. Once they leave that sandbox,…
The frustration factor is a big deal. I took a bootcamp. One day and another student and I were working on something and a third member of our group (who had other issues) was really frustrated and took it out on us and then went to the teacher. She told the teacher "they just get it and I don't". But in truth the other student and I were not "just getting it", we were failing frequently, we had made no more progress…
Austen seems to finally have given up on trying spin every story about him that reaches HN, no posts in the last 9 months.[0] A sure sign of the dismal state of things at Lambda/Bloom. [0] https://news.ycombinator.com/threads?id=austenallred
or months and months of defending your reputation can wear you down. have a little empathy for the flawed human on the other side of the screen.
I'm convinced that Lambda School was shady, and I'm not debating that, but some of this seems over the top. ISAs as indentured servitude? The shadowy negotiating a company's validation "behind closed doors?" (Where else are you supposed to do it.) The criticism of Lambda School can stand on its own without wading into the extreme hyperbole.
Agreed, I gave real $ to the "Lambda Perpetual Access Fund" and now feel negative about the whole thing, but the sections where the author is talking about Austen's golf swing, bots, having written a paragraph conscious of clickbait? Not really necessary.
Earlier quoted context omitted.
As a former instructor (not at Lambda), I'm kind of inclined to believe it has more to do with the fact that it takes a certain kind of person to put up with the demands of corporate software engineering. Getting both kids and adults (especially kids) to figure out how to program is easy if you understand that most of the concepts are better taught visually through p5js or what have you. Once they leave that sandbox,…
The frustration factor is a big deal. I took a bootcamp. One day and another student and I were working on something and a third member of our group (who had other issues) was really frustrated and took it out on us and then went to the teacher. She told the teacher "they just get it and I don't". But in truth the other student and I were not "just getting it", we were failing frequently, we had made no more progress…
One of the projects I'm leading is a small R&D effort to see if a new technique will improve one of our core algorithms. And I have a very bright new junior programmer who has been with the company about 2 years and has a little post-college experience at another company, so he's not totally new.
When I give him work, he gets stuck (it's R&D after all), and blames the library or the API or things like that. It's like the "no there's not a bug in the compiler meme".
I'll take a good chunk of my day and pair with him to show him how to get around the problems, and it seems like he gets it, and then the next week when we sync up, he's back to blaming the tools.
My wife's opinion is that it just take a LONG time to learn that you're usually the one who's wrong, not the tools. And she pointed out that we both spent about 5 years in grad school. The biggest lesson of grad school is that you never know what's going on and that you need to figure out your tools, and that you're always the dumb one.
I've always been a little disappointed that I wasted so many prime earning years in grad school, but I think I agree with her here. Grad school is as close to the old "apprentice" model where you don't earn much (if any) money because you're primary goal is to learn the field and you really spend most of your time being in the way or annoying to your grad advisor. You don't bring much value in the time you're there. Much of that is learning how to deal with failure and working around that. (Edited to add: last week I found my archive of code that I wrote in grad school. I was surprised how little code I produced in those years and how I could now have solved the problem in about a week or so since I understand what tooling I now have at my disposal. But I did learn a ton in those years.)
I'm trying to figure out a way to get those lessons to my junior teammates (without making them feel as worthless as I did in grad school).
To bring this back to the topic, maybe Lamba school like boot camps are a problem just because the time is so compressed. You need time to keep learning the lesson that it's not the compiler, it's you. And then you can learn the problem solving of how do _I_ make this work.
Lots of self-taught from a young age people learn this, so it's not the grad school that's as important as the freedom to have time to learn (while not being on the hook to be providing value to someone who's paying you).
Not saying it's fair and I understand people need to support themselves, but I do think that the best problem solvers have put in the time and there's not real substitute for time.