1. Homework should absolutely be graded to provide students with feedback, assess learning progress, and tailor instruction to strengths/weaknesses of students in the current iteration of the course. Once all the work goes into grading, it's hard for teachers to throw out that data when assigning grades.
2. It mimics the real world where sitting your butt in a chair and turning in useless reports is valued -- perhaps not as much as actual outcomes, but still valued. Perhaps that's stupid, but in most jobs it's a reality. IMO this isn't a great motivator, but it's one a lot of teachers cite.
3. Helps pad the grades of students who are terrible test takers / have anxiety issues.
4. Students are... students. They don't always know what's best for themselves. Making homework worth a portion of the grade communicates to students that they need to practice. Patronizing? Maybe. But also a reality.
5. It's the easiest way to inflate grades without explicitly lowering standards.
> It is not cheating. It is leveling the playing field.
This is not even remotely true. I think you seriously under-estimate the value of parents/tutors.
Students with tutors/parents will not just get the right answer. They will also be led to the right answer, over and over, and told what they need to practice in order to improve. Explanations will be tailored to their learning style. So they get direct help on assignments, but they also get regular indications about how to improve their performance in scenarios where they don't have that help.
Wolfram Alpha just gives the answer.
If homework in 90% of the grade, maybe it levels the playing field for letter grades in the course course... until a few years down the road when the student who didn't actually learn the material is screwed and has no way of catching up.
If homework is a more reasonable 20-50% of the grade, then the reckoning comes at midterm/final time.
> What this really show is that homework isn't the best tool for gauging student prowess
While W|A doesn't come close to making the field level, I think there's an argument to be made that it makes the field more level than it was. The perfect being the enemy of the good...
That's true. Especially the answers that tell you the process for deriving the solution instead of just giving the solution. Then you can see where you got stuck/went astray.
> it may help being able to just provide the answers, but homework made up a small percentage compared to the actual exams...
One of the easiest ways to inflate grades without explicitly lowering standards is to decrease the proportion of the final grade that depends on the midterm and final. Cut out the midterm for "more instruction time" and leave a 20% final. Homework is now worth an absurd 80% of the grade... that's no good. Throw in a project, participation, or auto-graded "e-labs" with infinite attempts. Suddenly it's really difficult to get anything less than a B unless you really just don't give a crap. But also kinda difficult to actually learn because So. Much. Busy. Work. And, on top of everything else, we're punishing the one student who's not cheating.
Any time I see a lower division syllabus where closed-book exams are worth less than 40% of the grade, I'm instantly suspicious.
> but ultimately they are failing themselves when it comes down to needing a fundamental understanding on the process itself.
Yup.
> It comes down to the students' willingness to learn, not how to thwart cheating on homework.
In fact, you can leverage the calculator or WA to teach the material at greater depth. No longer need lots of practice with trig identities or u substitution? Great. Maybe we can write a few proofs instead, or use the time to work through a large case study.
Believe me, very few grad students are writing code to "look smart".
First of all, coding isn't exactly a high class activity in most of academia. Any implementation that's not an uncommented mathematica notebook or matlab mess is in the top 1% of academic code.
Second of all, no one reads the code. So while there are incentives to intelli-obfuscate papers to trick naive reviewers, those incentives don't exist with code. (Oh, and it doesn't really work out well in papers either most of the time.)
Academics are not rewarded for good software engineering. The incentives are not properly aligned. And more-over, the that's not necessarily a bad thing! Research is research, not engineering.
Stop expecting production quality code out research groups. The purpose of research is to explore ideas, not implement some epsilon of your product.
If you want a perfect exposition in addition to a high quality implementation, there are ways to get it. Pay the consulting fees. Or pay the tuition. Or hire the students, Or if you can't afford that, wait for the thesis/book.
> Is pseudo-code a fucking premium?
In a paper? Well... yes. Categorically, emphatically, yes. If you want to read an exposition where space does not come at an extreme premium, you'll have to wait for the thesis/journal article.
Space comes at a premium for stupid reasons (artificial page limits) but also for good reasons (expositions cost time, which costs money and grad student time, and fuck if I'm doing a 10 year Ph.D. at $7/hr because you're irritated at some python code.
> Can you at least try to give some intuition before showering the reader with equations?
Either 1) no because you're not the intended audience, in which wait for the thesis/TR/dissemination blog post where I'll work every gory detail; or 2) no because the equations are hard for all of us to understand and no one has solved the exposition problem yet.
> How the fuck do you dare to release a paper without source code?
So all the products you work on all totally open source, eh? Either fully commit to Stallmanism while living off less than minimum hourly wage or get off your high horse.
> Why the fuck do you never ever add comments to you code When naming things, are you charged by the character? Do you get a bonus for acronyms?
Do you realize that OpenAI having needed to release a "baseline" TRPO implementation is a fucking disgrace to your profession?
Jesus christ, who decided to name a tensor concatenation function cat?
Because they're being paid 30k a year at best for 80 hour weeks under intense pressure to implement new ideas and the prop firms and Googles are knocking with 200k comp packages and honest to god 5 day work weeks. Time is (SERIOUS) money when you're slogging through grad school. Again, walk a mile.
And again, really, the point is to test ideas. For every publicly release line of code coming out a research group there's 5x or 10x unreleased code implementing dead ends.
If you want all this, stop bitching at over worked and absurdly under-paid grad students, and start calling your congressman to support higher NSF budgets so research groups can hire more permanent research support staff.
You might be conflating software graduate students with research developers. I have translated a lot of research code into production code; whether it be sourced in Matlab, incomprehensible C, confused C++, or convoluted Numpy.
Okay - so grad students have very little incentive to write readable code... fine, understandable. They are usually lucky if they can write an algorithm which isn't finely tuned to a very narrow dataset. In that sense, most Ph.D papers are outright fabrications lying about capabilities written by authors seeking paychecks. If people were able to investigate the underlying source code, that would be fairly apparent.
That said, why do so many professional research developers also suck as writing comprehensible code? They have fat paychecks, what's the problem now? There absolutely exist research developers who write very high quality software. They may still use very terse nomenclature (due to high cognitive load), but their code can be logically comprehended by those who do not understand the field. There are a lot of reasons (I think) for this; no incentive to improve, poor understanding of their own discipline, no acknowledgment of the problem, expectation that such work is for "engineers".
In reality - a lot of research developers are simply incompetent, but they find a way to regularly convince others they are not.. often through obfuscation. They're stringing together implementations from various publications (which themselves might be total fabricated lies) with relatively little comprehension.
That's okay, a lot of software engineers are incompetent too.
> You might be conflating software graduate students with research developers
I'm not conflating. The vast majority of research software is written by grad students.
> why do so many professional research developers also suck as writing comprehensible code?
Because incentives aren't aligned. And it's not even clear they should be aligned.
> There absolutely exist research developers who write very high quality software... In reality - a lot of research developers are simply incompetent
There absolutely exist software developers who write very high quality software... In reality - a lot of software developers are simply incompetent.
> If people were able to investigate the underlying source code, that would be fairly apparent... Own it
1. A huge amount of research software is open-sourced and does work as advertised.
2. You don't get it both ways. Either no open source demands, or no expectation that grad students should "own their work" -- and then making demands that they literally don't own their work.
I agree with you but I think this highlights a point. If academic articles are out of reach of people who work in the industries they're researching, doesn't something need to change? Shouldn't incentives be better aligned. Should this type of complaining be celebrated?
> Shouldn't incentives be better aligned. Should this type of complaining be celebrated?
IMO it's not as clear cut as some people think. Honestly, is the cost worth the cost to tax payers if the super high quality implementation is going to be out-of-date in 3 months?
It depends on the research project and how fast the field is moving.
At base, I wonder if the current system isn't reasonable. If research can't even stay fresh long enough to make it from conference paper to journal paper, maybe we shouldn't be throwing hundreds of thousands of engineering dollars at quality implementations.
I think you're building a straw man of "hundreds of thousands of engineering dollars" here
All we're talking about is better quality code. This isn't a huge cost. It's usually just a matter of a small change in mindset while coding, and a few minutes refactoring and commenting once the code is working. Those minutes are repaid (and more!) the very next time the author has to revisit that code again. Good quality code saves money, it doesn't cost it.
You can leave error conditions unmanaged, leave the UI as a complete mess, don't worry about internationalisation, none of the things that add serious cost to a commercial project. This is not that.
If research coders aren't aware of code quality currently, maybe it's time that they got taught it? Writing good code will help researchers who write code, not hinder them.
> I think you're building a straw man of "hundreds of thousands of engineering dollars" here
Been there, done that, no. Refactoring a crappy implementation into a high quality, documented code base takes an enormous amount of time. And literally no one in academia cares about it. Industry doesn't care about it either because there's a presumption that any software created while in academia is inferior quality.
If you advise students to do this type of work with the expectation of any type of personal reward, you're a liar. They're basically doing software engineering that academia won't reward them for, and their year of software engineering won't count as job experience if they go into industry. And they aren't being paid software engineering salaries. It's just exploitative.
> All we're talking about is better quality code. This isn't a huge cost
This flies in the face of what the market bears in tech salaries. But no matter; I'll just never pay my software devs more than 30k, and also only give them maybe 20% of their time for actual software development... I'm sure I'll get high quality code! /s
> Those minutes are repaid (and more!) the very next time the author has to revisit that code again.
Which for 99% of research code will literally never happen.
> If research coders aren't aware of code quality currently
Tons of grad students leave academia after their phd, take very high paying jobs in industry, and become valued members of software engineering teams.
Research jobs are not software jobs. The goals and incentives are different. Sometimes it makes sense to create a maintainable research software system, but usually it makes no sense because the code is throw-away for testing an idea. That's OK. No one owes you an epsilon of your product.
> I also have learned compsci with his similar methods of finding interesting areas and digging in
I don't think those things are similar. His method -- working backward for Wiles' proof of FLT to Linear Algebra -- is not really analogous to teaching yourself some undergrad CS. It'd be more analogous to deciding you want to understand Mulmuley's latest results from nothing and discovering while loops along the way.
There's a difference in kind. Maybe this is splitting hairs, and at some level they're both "self teaching", but the huge chasm in relative difficulty/impressiveness still irks me :)
> Frankly, professors would be more useful to me, if I could purchase their time by the hour over issues I don't understand
Find a decent university and go to office hours / ask for independent studies.
Paying tuition is quite literally purchasing their time. Only a small amount of official instructional time is spent in lecture halls. And most professors spend more time on teaching than they're technically required to. At decent universities that prioritize teaching, maybe 80%+ of teaching time is spend in one-on-one or small group interactions.
IME most people who dislike formal higher education never learned how to use it properly in the first place. Or attended undergraduate at colleges primarily known for the attached research institutes, not their undergraduate program.
> So this guys method is exactly what other mathematicians warn against? Trying to understand?
No, I don't think so.
The "there's no intuition" advice is really good advice for undergraduates or lay people first encountering abstract concepts in pure mathematics. In fact there is an intuition, but the intuition is usually sort of on its own terms -- not so much grounded in physical life experiences. In other words, you will get an intuitive grasp on the ideas but that intuition will probably not be an analogy to your previous experiences in everyday life. When mathematicians say "there's no intuition" they usually mean "there's no physical experience that corresponds to the underlying intuition, and it's not really like anything you've seen before. It's a new experience and you need to experience it on its own terms. Stop trying to ground yourself in classical mechanics or whatever."
But that's quite the mouthful, so better to just say "there's no intuition; just focus on working with the objects and you'll eventually get comfortable".
This quote from the article captures it well, I think:
> "Now I find real numbers much, much more confusing than p-adic numbers. I’ve gotten so used to them that now real numbers feel very strange."
> If you are a university in the "business of finding students a job" you are university'ing wrong.
Then everyone is university'ing wrong!
Universities spend an enormous amount of time and money getting students jobs. Maintaining relationships with recruiters, developing alumni networks, and entire departments of full time staff dedicated to "career services".
There's a solid critique of education programs that are overly sensitive to industry fads [1], but IMO universities and educators should definitely include "finding students a job" as an explicit curricular goal -- balanced, of course, with "ensuring students have a long and healthy career beyond that first job".
Finding students a job should be a secondary byproduct of first giving them a world class education where you prepare and enable the student for society through being able to learn. Universities are to teach students how to learn so they can learn and be more aware and active about what is happening around them in society. Universities gives you exposure to a wide array of subjects for a purpose. It isn't random, and if you are attending a university where it does feel random, then find a better university.
"The goal of university education is to help build a fairer, more just society" - Steven Schwartz. [0]
Indeed this aligns with Plato's view on education -- "Plato regards education as a means to achieve justice, both individual justice and social justice." [1]
But when I apply this philosophy to concrete curriculum design questions in CS, I end up caring about placing students at internships and jobs.
First, internships are a form of education, and I find that students who complete internships come back the next Fall as much more mature programmers. I can then leverage that maturity in programming to dig deeper into interesting theory. Because I'm not helping debug for loops, I can students debug proofs or design more complex algorithms. So I consider internship placement a major goal for the first two years of a CS curriculum, even when my goal is to teach pure theory.
Second, I have a hard time justifying the situation where students are debt slaves to banks. How does that achieve individual or social justice?
Third, your work output is an enormous aspect of your contribution to society. Someone who can build a software platform that helps rural poor in Nigeria get access to micro-loans under a fair terms is making a much greater impact on the world than a philosopher with a perfect understanding of what it means for the world to be just, but without the means to act on that knowledge.
The problem is that it is awfully hard to be a "life long learner" if you are unemployed, desperate, or working a shit job just trying to make ends meet.
Imagine all that extra time college graduates could spend learning if they were easily able to provide for themselves because college prepared them for the real world and they were able to get a good job.
Okay nice goals. But we face a problem today will a shortage of low skilled jobs. The few low skilled jobs that remain often still require university training. The rest offer terrible working conditions and pay.
It's nice to have a society that has people who are more aware and active about what is happening around them in society. But what about the average worker that's been unemployed for six months and just want's to be able to afford to raise a family?
We need to meet our basic needs first. Universities used to be for the upper few, but as they are required more and more for the majority of jobs, either the universities need to change or the job requirements need to change.
Well, the problem is that universities are being co-opted into job training programs, when they shouldn't be. The cost of training people for jobs is being passed on to them through the university, from corporations. It shouldn't be that way. Finding a job should never be the main, or even a large part of attending college. Now, naturally that's not what is currently happening, but we need to work to avoid this as a long-term solution to job training.
That seems unrealistic for the most part. No, most universities aren't optimized as trade schools focused on near-term employment prospects. And, you can certainly choose a university and major that, shall we say, sub-optimizes employment prospects.
However, it's certainly the expectation of most people that going to university for four years is going to improve their employment prospects--often in a field directly related to their undergraduate study. And as someone else noted, schools absolutely put effort into relationships and programs that improve their graduates' job prospects.
> And as someone else noted, schools absolutely put effort into relationships and programs that improve their graduates' job prospects.
They also put in efforts in a bunch of other places as well.
I will admit that, coming from a lower middle class background, university education to a 17 year old me was mostly a way to optimize my career prospects. But in hindsight, I would say it is a lot more than that. The two most important skills I learned were probably critical thinking and team work. There were also many side-benefits, that you get merely from being in close quarters with so many different kinds of people... to learn that diversity is important, that even people from different cultures are awesome etc. These soft skills are very important, and I don't see a way of acquiring them otherwise.
However, I think a way to remedy this would be to be very clear with what a university provides instead of being vague about it. e.g. if you pursue CS in Uof Something, you have x % chances of getting a job here right out of college. I agree Universities have been co-opted into being preparatory schools for the job market, but that is too narrow a purpose for them.
I don't really disagree with any of that. There are (mostly good) reasons why most universities look and act differently than they would were they solely constructed for learning some trade whether white collar or otherwise. Part of this is that the training part is mixed in, for many people, with moving out of the house for the first time, being self-directed to a greater degree, etc.
That said, there's also a general expectation that, barring graduate school, university grads will also go on to earning their own living. Some do so with just generalized university education--which is more or less what you have if you majored in medieval German literature. But it's easier with an engineering degree or something else that ties directly to what a company is specifically hiring for.
That's a good point. While they're definitely not the same thing, I wonder if the goal posts are just changing. So at first, it was: complete high school and you will def get a job! And then it was: get a univ education and then you will def get a job!
Maybe the economy is just changing so much that we simply don't have the capacity to absorb so many workers. Or maybe we need to direct more resources to create employment in those areas (i.e. more funding for arts, history, archaeology etc.). I don't know what the solution is.
Effort doesn't alway equal results and we shouldn't be praising them not attaining their stated goals. (or perhaps they are, and their goals don't matter to their customers -- students)
I'm just a single point of data, but none of my friends ever found the career services people to be helpful in any meaningful way. In my world, their success rate is 0%.
> and we shouldn't be praising them not attaining their stated goals
My post wasn't intended as praise for career services... it was intended as praise for departments and universities that prepare their students for internships and jobs.
> and their goals don't matter to their customers -- students
I don't know this, but I think a lot of the dedicated professionalized career services people are mostly there more to placate clueless parents. It's marketing, and it works.
> none of my friends ever found the career services people to be helpful in any meaningful way
Absolutely. The scare quotes in my original post are there fore a reason...
That said, good career services people are usually work closely with or are even embedded in the department -- not a separate service in the admin building. They ensure that there are regular talks from the alumni network or local community. That companies are invited to come in for an evening and talk about what they're working on / what skills they need. And then ensure those companies are invited back to job fairs etc. in the Fall, with companies who take it as a serious opportunity and who you think are most likely to fast track your students' resumes.
In fact, at smaller universities/departments, the best career services employees are typically professors who keep in contact with graduated students are former colleagues.
> Any reasonably intelligent and dedicated student can go to university and come out the other end with a well-paying job.
That's a pretty restrictive filter. Currently you have to be at least two of smart, goal-directed, and curious to make it through the university system with a decent education and good job prosepcts. Many other students make it through with good job prospects but no real education because they were able to bull their way through an in-demand major program. But a lot of them slip through the cracks and end up with neither job nor education.
I agree. Ideally, tuition would be extremely subsidized and higher ed wouldn't constitute an enormous financial gamble. But in the current US system, the restrictive filter really is in the students' best interest.
It's not self-serving to tell someone "really, no, you shouldn't take out a big loan to pay for this because you're probably unprepared and will fail".
On the contrary, taking literally every student who can get a federal student loan -- regardless of your faith in their ability to get something meaningful out of the degree -- is extremely selfish!
2. It mimics the real world where sitting your butt in a chair and turning in useless reports is valued -- perhaps not as much as actual outcomes, but still valued. Perhaps that's stupid, but in most jobs it's a reality. IMO this isn't a great motivator, but it's one a lot of teachers cite.
3. Helps pad the grades of students who are terrible test takers / have anxiety issues.
4. Students are... students. They don't always know what's best for themselves. Making homework worth a portion of the grade communicates to students that they need to practice. Patronizing? Maybe. But also a reality.
5. It's the easiest way to inflate grades without explicitly lowering standards.