[AndyMcConachie]

It's not really any better outside of the humanities. Maybe the prospects are slightly better, but grad school is still a crappy choice.

I got a bachelors in Computer Science and then worked for 15 years before going back and getting a masters. While there I was asked to work for free on numerous occasions, we can call if different things, but that's how I saw it. Already knowing the value of my labour I finished my masters and then left. I definitely had the option to continue with a PhD, and I'm almost certain that had I applied I would have been accepted. But I just wasn't interested in being exploited.

I remember one class which I dropped in which the entire class was project based, and we were to work on projects that aligned with the research of the professor. On the first day there was no syllabus given, so I asked what the readings were and received a grumpy response basically saying, "Readings, yeah there will be some readings." Or something similar. It was incredibly clear the instructor just wanted grad slaves to advance their stuff. I dropped that class, but I could cite numerous other examples.

I paid for the privilege of working for free and learned some stuff along the way. Maybe I should have spent the two years and money on travelling and seeing the world instead. I likely would have learned more, but I wouldn't have this fancy grad degree.

[matthewdgreen]

Computer science professor here: I love to have students work on research in my courses, provided that they understand this is the point of the course and they choose to do it. Some of my best students (who went on to great careers in industry or academia) did terrific research projects of their own choosing.

I don’t ask students to do research projects because I expect “free labor” from them (unless they’re my PhD advisee, in which case it’s just poorly-paid labor.) In fact, most of the time I expect that undergraduate and MS projects will fail, or only be partially finished simply due to the schedule constraints those students have with other courses.

For students who are actually interested in conducting real research, the value to the student in being advised by me comes from the fact that they’re working on a research project that’s in my area of expertise and interest. The value to me is that sometimes I learn something new. There’s much less value in my advising students to do projects in areas that I wouldn’t be interested in researching myself, not because I’m looking to cash in on students’ labor, but because I won’t be able to offer them as much guidance.

[mnky9800n]

Yes I think what the person you replied to identified as work isn't really much work at all in the sense that you would find in a software dev job or something like that. You aren't asking your students to write another database interface or something. You are giving them projects to let them know what you do, what that part of the field is about, and to expose them to ideas that they might carry forward. The view presented is so cynical is hard to take serious tbh.

[toxik]

Counter anecdata: I am taking a CS doctorate degree, and have never been asked to work for free, and never been cheated out of course time to work on what the professor thinks is interesting.

[abnry]

I think the lab-heavy (i.e. non-digital) programs have this problem more. When I was in grad school, I knew plenty of chemistry students who were expected to work 6 days a week.

[aj7]

At Berkeley, the following phenomenon was well known. Towards the end of your program, you’d have to “fight” your advisor to finish. (You were trained, productive, and still earning the salary of a second-year grad student.) The “pets” didn’t have “fight.” It was adjudged that they could do more for the professor’s reputation on the outside.