4 ms·

What if your theoretical candidate on senior web Perl programming position knows about formlets, for example, and used them successfully? Formlets: http://hack

by thesz 16y ago

What if your theoretical candidate on senior web Perl programming position knows about formlets, for example, and used them successfully? Formlets: http://hackage.haskell.org/package/formlets http://hackage.haskell.org/package/formlets and then http://groups.inf.ed.ac.uk/links/formlets/ http://groups.inf.ed.ac.uk/links/formlets/ Does he still need to be proficient in OO? What if your candidate knows much about your current problem domain? Do you still prefer someone who doesn't know a bit but proficient in OO?

berntb 16y ago
The key word was "theoretical"; or are there really competent Haskell programmers that hasn't done OO? :-)
- thesz 16y ago
  When I started Haskell (early '99) I touched OO (C++) but wasn't like it much. Actually, I specifically searched for a language that wasn't OO but provide all the benefits of OO when I found Haskell. The standard library back then was about twenty or less modules. I don't really match against most of my colleagues right now, they done much more OO than me. So, until recently I was really competent programmer with Haskell experience in useful programs that hadn't done OO. ;)
ZeroMinx 16y ago
This discussion has focused on OO, but my point was that their general level was very low -- it wasn't just a lack of OO experience. Good knowledge in some other area would have made it a lesser issue that they didn't have OO experience, but they were generally lacking knowledge across the board.
- thesz 16y ago
  In the absence of information I can freely speculate about your job vacancy. Your proposed salary was low, your offering uninteresting, etc. Myself, I crossed Perl and Python (and Ruby, and Smalltalk, and Lisp and many others) from list of languages to discriminate good programmer from not so good one a long time ago. They just did not get used in anything I consider interesting or important (but I still prefer domain knowledge - so lisper with relevant past is still interesting). Right now I would use Haskell (or even stronger typed language like Coq or Agda) as a requirement, and my proposal would include DSeL for problem domain with Perl backend (if Perl is that necessary). I will get much less resumes initially, those resumes will be of higher quality and my employee will produce a tool that allow me (us as a team, actually) to retarget our product to another backend quickly if we need to do so.

by thesz 16y ago

berntb 16y ago

The key word was "theoretical"; or are there really competent Haskell programmers that hasn't done OO? :-)

thesz 16y ago
When I started Haskell (early '99) I touched OO (C++) but wasn't like it much. Actually, I specifically searched for a language that wasn't OO but provide all the benefits of OO when I found Haskell. The standard library back then was about twenty or less modules. I don't really match against most of my colleagues right now, they done much more OO than me. So, until recently I was really competent programmer with Haskell experience in useful programs that hadn't done OO. ;)

ZeroMinx 16y ago

This discussion has focused on OO, but my point was that their general level was very low -- it wasn't just a lack of OO experience. Good knowledge in some other area would have made it a lesser issue that they didn't have OO experience, but they were generally lacking knowledge across the board.

thesz 16y ago
In the absence of information I can freely speculate about your job vacancy. Your proposed salary was low, your offering uninteresting, etc. Myself, I crossed Perl and Python (and Ruby, and Smalltalk, and Lisp and many others) from list of languages to discriminate good programmer from not so good one a long time ago. They just did not get used in anything I consider interesting or important (but I still prefer domain knowledge - so lisper with relevant past is still interesting). Right now I would use Haskell (or even stronger typed language like Coq or Agda) as a requirement, and my proposal would include DSeL for problem domain with Perl backend (if Perl is that necessary). I will get much less resumes initially, those resumes will be of higher quality and my employee will produce a tool that allow me (us as a team, actually) to retarget our product to another backend quickly if we need to do so.