Is this really a strict property of functional languages? :)
980 karma · joined June 16, 2011
Is this really a strict property of functional languages? :)
As a hiring manager, I've known a very few (but very good) contract recruiters who will actually do this. In short, most (contract) recruiters are sales people who are motivated to have a transaction occur.
As a hiring manager, I rarely find that there interests are aligned with mine.
Having said that, I am also not sure if this pricing works or not.
Am I the only person who feels that social media is a lot of work with little reward?
Hey! That's what I think, too!
Around 2007 when I'd had quite a bit of exposure to both Python and then Ruby I'd started to think the same thing. Although I didn't have the foresight to say it in a public essay I would tell my friends "In five years Javascript will start to become a popular general (i.e. non-web only) programming language and Lisp in 20."
I now think think the big Lisp (or Scheme) event will happen even sooner--say in 5 to 7 years. (Meaning you will see the kinds of articles you see around Node today on HN about Lisp.)
Seriously though, this article got me to thinking and I realized that why would one live with the smell of copy-and-paste when it's just so darn easy to write a singly reusable function?
I agree with what you in the sense that there's no need to go from what might be a few lines of copied code to a full-blown library or subsystem. But for a small bit of common code not refactoring that out immediately seems to me a really bad practice.
It will be interesting to see if their expenditures return to previous levels after the IPO or if their revenue will suffer from the cutback.
This is pretty awesome.
I've been using it outside of a web-based context to do some more computational intensive work and just get a little bummed when I need to re-implement something in C to get the performance I need. (I'm not a C hater either! I've just come to love Ruby.)
I just ported some code that performs probability computations from Ruby to C for performance reasons. While I'm really pleased with the runtime, I was pretty unhappy with the implementation time.
I need to extend this work for the next phase of the work I'm doing and have been contemplating moving to R, but have hesitated because I couldn't find any info on its performance.
Now I have!
http://en.wikipedia.org/wiki/Principality_of_Sealand
And the Freedom Ship: http://www.freedomship.com/+1 regarding the Google searches as well.