News for hackers. Stuff that matters.
Re:Reasons to use Haskell as a Mathematician (2006) by gone35 on Saturday June 14, 2014 @04:47PM (#7893655)
Shamelessly off-topic, but I can tell the author is a legit pure mathematician:

(1) Haskell is Functional

(2) Haskell Insulates You

(3) Haskell Performs Well

[...]

(3) Haskell is Declarative

Not being ironic, by the way. From experience, often I can tell pure vs applied mathematicians by how hilariously bad/absent-minded they can be at basic arithmetic/algebraic manipulations.

Same for theoretical- vs systems-oriented CS people, I've found --almost as if being a horrible programmer somehow gives you academic hipster cred.

(EDIT - To clarify: I mean CS academics in grad school, not CS professionals in industry. Also it's just a silly anecdote only marginally correlated with reality: no offense intended to anyone.)

Re:Reasons to use Haskell as a Mathematician (2006) by nostrademons on Saturday June 14, 2014 @07:21PM (#7893956)
He was a pure mathematician at the time this was written. Now he works for Google, IIRC on self-driving cars:

http://www.knowthecosmos.com/destember/destember-experiment-...

He also won an Oscar this year, his second total:

http://www.imdb.com/name/nm0685004/awards

Re:Reasons to use Haskell as a Mathematician (2006) by JoeAcchino on Sunday June 15, 2014 @09:36AM (#7895201)
Nice to know, if an oscar-winning pure mathematician working on science-fiction projects found difficult to learn Haskell, I can save myself the trouble.
Re:Reasons to use Haskell as a Mathematician (2006) by nostrademons on Sunday June 15, 2014 @12:03PM (#7895516)
If that's your goal. There are some people who do things because they are difficult, because whatever activity is most difficult is probably the most mind-expanding.
Re:Reasons to use Haskell as a Mathematician (2006) by moab on Saturday June 14, 2014 @05:18PM (#7893725)
Inheriting off-topicness, while that stereotype does apply to most mathematicians, a large number of the CS theory people I've worked/TA'd with were actually pretty good programmers, and a few had even taught multiple years of our intro systems course. Of course this is just one school, but I think computer science as a field is still young enough that someone can be an expert in one area and still be reasonably fluent in other areas.

Don't think the last point is particularly true either: being a good programmer is valuable even for theoretical CS. Point in case, recently saw the work leading to a paper on SDD solvers: there was a ton of programming and exploration (albeit in Mathematica/Matlab) that led to the final paper. Also, people working on parallel stuff these days (even the theory guys) usually publish CILK/MPI along with the paper. It's great when you can do both :)

Re:Reasons to use Haskell as a Mathematician (2006) by gone35 on Saturday June 14, 2014 @07:12PM (#7893948)
Yes: That's definitely the way it should be! I agree 100% that CS is still young and cohesive enough for dedicated people to achieve both breadth and depth, which perhaps means "grand" single-person revolutionary breakthroughs can still be achieved: Karp made a similar point during one of the Turing centenary talks (*An Algorithmic View of the Universe [1,2]), positing that the field is not yet specialized enough to prevent an Alan Turing-like figure today to have a comprehensive view of the state-of-art of the discipline (!).

[1] http://dl.acm.org/citation.cfm?id=2322176.2322189

[2] http://www.youtube.com/watch?v=f6df3s3x3zo#t=56m25s

Re:Reasons to use Haskell as a Mathematician (2006) by StandardFuture on Saturday June 14, 2014 @05:35PM (#7893765)
It is technically impossible to be a good 'CS People' and simultaneously be a 'horrible programmer'. It seems that what you are referring to are people who know basic CS concepts and even know the basic features of a language or two but do not have a 'Hacker' mindset. This does not make them a 'horrible programmer' -- just as a hacker who comes up with 'tricks', without actually understanding that the things he 'created' were already discovered in some 70s CS paper, is not a 'horrible Computer Scientist'. It's not a sufficient method to describe a person's strengths and weaknesses.
Re:Reasons to use Haskell as a Mathematician (2006) by gone35 on Saturday June 14, 2014 @06:39PM (#7893896)
Sorry I wasn't clear: by 'CS people' I meant to refer to CS academics in graduate school (professors, post-docs, grad students), not CS professionals in industry --admittedly a sign of insularity, I recognize.

And what I meant is that, anecdotally, academics working on CS theory (eg theory of computation, computational learning theory) are more likely than not to unmistakeably be what I think everyone on HN would agree to call point-blank "horrible programmers": no use of version control, no tests, little concern for organization/modularity/maintainability, etc. And in part it makes sense since they don't have to hack nearly as much as systems-type CS academics --in many ways their work is closer to pure mathematics than engineering/applied math. That's all.

In all just a silly anecdote, although with a kernel of truth. See for instance Scott Aaronson's joke comments about his programming abilities [1]:

On the spectrum of computer science, I'm about as theoretical as you can get. One way to put it is that I got through CS grad school at Berkeley without really learning any programming language other than QBASIC (!).

[1] http://www.scottaaronson.com/blog/?p=266

Re:Reasons to use Haskell as a Mathematician (2006) by cottonseed on Saturday June 14, 2014 @06:57PM (#7893930)
This wouldn't be at all surprising if people realized that the job of academic computer scientists is not to program (just like the job of an academic mathematician is not to perform basic arithmetic.)
Re:Reasons to use Haskell as a Mathematician (2006) by nmrm on Sunday June 15, 2014 @09:38AM (#7895205)
First -- I don't think it's wise or useful to judge Ph.D.'s by the same standards as industrial developers. Or vice versa. Consider the corresponding criticism of industry: "have you meet some of these jokers in industry? Most of them couldn't pass the qualifiers even after like 5 years doing CS full time. WTH?! It's almost like like haven't learned much new theory or math since graduating from undergrad or something...")

Second -- and this is purely based upon my personal experience (perhaps we have worked with people in radically different departments or research areas) -- what you say is simply not true in most cases.

I've worked with a lot of theory people, and did not encounter any really bad programmers.

Your specific criticisms:

1. version control. Everyone uses it for everything. Even and especially paper writing. If your experience is that theory phds don't use version control, then I would say your department is/was abnormal (or else we've observed people in very different parts of theory, I suppose).

But also, in many cases, using VCS is more religious than practical. Academic projects are often <10kloc single dev projects. It's more of a useful additional backup mechanism than actually necessary.

2. Testing. If the paper contains a full spec and correctness proof for the implementation (e.g. inference rules, automata, algorithm in terms of some mathematical object) then the point of the implementation is really just transliteration. The space for potential bugs is still there, but the bugs are very different from typical bugs (which, imho, are most often due to poor/vague or even completely absent specification). You simply need fewer unit tests when you know that precisely the thing you are implementing is correct, and just want to make sure you copied things down correctly.

3. The code is often well-written. When it is not, two problems are most common:

a. no comments! Okay, but of course there is a 20 page paper explaining the core idea. And also it's a protoype.

b. Bad structure/poor abstractions. Again, most prototypes don't need to be maintainable. If the core idea gets big and important, it probably makes sense to reimplement as part of a new research agenda anyways (e.g. for performance reasons, or because of unforeseen extensions due to scientific advances, etc). Also, in some cases, the correct way to organize a piece of academic software is highly non-obvious. Organizing your code is much easier when it's a completely solved technical problem in search for new social applications (yet another web app) than when it's a completely new technical idea.

Re:Reasons to use Haskell as a Mathematician (2006) by elliptic on Saturday June 14, 2014 @05:51PM (#7893805)
So, basically, you think that there are exactly 0 CS professors who are horrible programmers?
Re:Reasons to use Haskell as a Mathematician (2006) by StandardFuture on Saturday June 14, 2014 @06:00PM (#7893827)
How can your comment completely disregard the entirety of my actual conclusion?

>It's not a sufficient method to describe a person's strengths and weaknesses.

So, there should be if your classifications are correct. You are assuming that 'CS Professor' is equatable to 'good CS People'. But, my classification may not be so rigid.

EDIT: You also still have not defined what it means to be a 'Good Programmer' vs. a 'Horrible' one.

Re:Reasons to use Haskell as a Mathematician (2006) by Bahamut on Saturday June 14, 2014 @10:30PM (#7894188)
I don't think you know enough pure mathematicians.
Re:Reasons to use Haskell as a Mathematician (2006) by gone35 on Sunday June 15, 2014 @01:10AM (#7894476)
You are probably right --I haven't been spending much time of late with people from my own department. :)