3 ms·
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 oth
by 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 agoIn 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.