What is "crappy software"? Is it certain that hackers, per your lecturer's definition, produce no documentation? What is the criteria for ranking software produ

What is "crappy software"? Is it certain that hackers, per your lecturer's definition, produce no documentation? What is the criteria for ranking software produced by people following certain processes? How do you pretend to isolate those from other factors in the process of writing software? Software development methodologies are just processes, followed by people (yes, programmers are people too). You can't enforce them rigorously and you will deviate; dev teams under the milestone plan-driven model will produce some pretty horrible code (I wish I could showcase some), and hackers will in fact write some pretty neat documentation. I'd expect a lecturer to have the wisdom to stay away from blindly labeling and generalizing in such a crude fashion. Yeah, I'd tell him that as well. :-)