+1 to this. There was a study IIRC that insider buys in open market were the only reliable signal from insider buys and sells -- especially if the insiders had been officers (directors/executives) for a while.
I beg to differ a little, Professors should be paid to do reviews, and not pay to have reviews done.
The companies that publish the journals don't take a cut, they take the lion's share basically, paying a professor to review would work better in having them take a share of the pie.
I've found Haskell to be much much 'cleaner' than OCaml (syntax wise) and intellectually more stimulating (probably because that is the first functional language I started learning).
My tilt towards OCaml these days is primarily due to it's reported speed (measured to be faster than GNU C on some benchmarks, I don't have the link handy, though Jane Street is using it for HFT, should be quick) and to a much lesser extent 'sacrificing' a little purity for getting the same constructs as Imperative languages.
That said, I'm an absolute beginner in both languages so take my views with more than a pinchful of salt, they are subject to change as I get to know both the languages better.
Wow thanks, I didn't know pyflakes. I knew pylint, but will make it more of a point to run it. I only occasionally need to code in Python, but when I have to, it is legacy code that I modify.
Yes, probably that is my confirmation-bias at talk. But more than anything it is the frustration that the whole make into a par file and deploy it on a production system, only to find just moments later that the binary isn't up because of a typo is frustrating in any language.
I remember writing in the description to the same effect that it was old, and may have been posted before. Although it served the purpose to bring it to other people's notice, you have have found it repetitive, for that I apologize.
The author really needs to be complemented on rewriting swathes of code from Python to Haskell.
In Google, in my project, we've had runtime errors in Python code, due to wrongly spelled variables(although that is a different problem), and type error, something a compiler would have caught.
Strong type checking is something that I truly like about Haskell and OCaml, I'm reasonably convinced that once my program has passed the typechecker, it is logically correct. Though debugging in Haskell is truly a different ballgame altogether (I'm a Haskell noob).