5 ms·
Controversies like these make me glad I work in the field of programming...while arguments over what algorithm or frameworks work best are less sexy than what t
by danso 12y ago
Controversies like these make me glad I work in the field of programming...while arguments over what algorithm or frameworks work best are less sexy than what the sciences cover, at least with narrow claims, it's easier to concretely argue for one or the other...and then of course, if we're talking about open-source, then the errors of ambiguity are even scarcer.
It seems like a large part of the problem, at least in these psychological experiments, is that there isn't a structured/uniform way to describe preconditions, methodology, assumptions, and measurement practices...OK, so you used 40 undergraduate students for your original experiment...how did you pick them out? How were their characteristics accounted for (e.g. age/gender/major/health/etc)? Did any of them ever see the Trainspotting scene before? Have any of them ever seen a movie of equal grossness? How many minutes did you wait after showing them the Trainspotting scene? In what order did you hand out the questionnaire? How did you seat the students? etc. etc. etc. etc.
A totally honest researcher might have trouble enumerating and enforcing all of the different controls, never mind communicating them to other researchers. From the research papers I've read, the ability to communicate these facts doesn't seem to be of uniform quality.
- lliwta 12y agoCertain parts of software engineering research are moving in this direction, psychology as a the primary toolbox for research. Not sure how I feel about that. As far as science goes, Psychology isn't exactly the epitome of rigor. On the other hand, the problem really boils down to asking hard-to-investigate-scientifically questions, mostly about humans.
- agent00f 12y ago> Controversies like these make me glad I work in the field of programming...while arguments over what algorithm or frameworks work best are less sexy than what the sciences cover, at least with narrow claims, it's easier to concretely argue for one or the other Yeah, it's pretty ironic when the field with (Comp) Science in the name isn't really a science but math.
- gipp 12y agoIt is a science. A formal science. Same as math and logic, for example.
- kylebrown 12y agoHal Abelson disagrees with you. "Computer Science is a terrible name for this business. First of all, its not a science. It might engineering, or it might be art. But we'll actually see that computer -- so-called science -- actually has a lot in common with magic."[1] 1. https://www.youtube.com/watch?v=zQLUPjefuWA https://www.youtube.com/watch?v=zQLUPjefuWA
- cfallin 12y agoAdd to that list Fred Brooks (IBM System/360, Brooks' Law): http://www.cs.unc.edu/~brooks/Toolsmith-CACM.pdf http://www.cs.unc.edu/~brooks/Toolsmith-CACM.pdf Relevant quote: "... the scientist builds in order to study; the engineer studies in order to build. ... I submit that by any reasonable criterion the discipline we call 'computer science' is in fact not a science but a synthetic, an engineering, discipline. We are concerned with making things, be they computers, algorithms, or software systems."
- mikevm 12y agoRobert Sedgewick would disagree with Hal Abelson. Just because some people tend to use pure maths to analyze the run-time of algorithms, doesn't mean we can't apply the scientific method to the problem. Here's a nice presentation by Sedgewick where he shows how we can apply the scientific method to programming: http://www.cs.princeton.edu/~rs/talks/ScienceCS10.pdf http://www.cs.princeton.edu/~rs/talks/ScienceCS10.pdf And quote: > Algorithm designer who does not experiment gets lost in abstraction > Software developer who ignores cost risks catastrophic consequences
- jeffdavis 12y ago"...while arguments over what algorithm or frameworks work best are less sexy than what the sciences cover, at least with narrow claims, it's easier to concretely argue for one or the other..." Very few arguments related to programming are over algorithm choice, they are almost always over engineering concerns: readability, platform/language choice, frameworks, etc. Those, in turn, are often dependent on a mix of personal taste and predictions about the future (e.g. directions for the product architecture). So I don't think programmers are quite immune from non-scientific analysis. That's apparent from the longstanding programmer debates about basic things like compile-time type checking. Even narrowing the claims rarely seems to reach much consensus.