3 ms·
You just made the exact opposite argument of Paul Graham's "Blub" article: http://paulgraham.com/avg.html http://paulgraham.com/avg.html The "Blub Paradox" ar
by jimbokun 8y ago
You just made the exact opposite argument of Paul Graham's "Blub" article:
http://paulgraham.com/avg.html http://paulgraham.com/avg.html
The "Blub Paradox" argues you should hire developers using the most productive tools, even if those tools are unpopular, because that naturally selects for the best developers.
You are arguing that you should hire the developers using the least productive tools, because if they can get anything working at all with those tools, they must be pretty talented.
- zimablue 8y agoNo he didn't, because "productive" != "(not?) difficult", they're mostly orthogonal. LISP is productive according to PG because it has a kind of unlimited amount of abstraction, I don't think he would say that LISP is difficult. LISP/smalltalk: PG-productive, not difficult Java: PG-unproductive, not difficult C++: PG-unproductive, difficult (Forth? Haskell?): PG-prodictive, difficult So there are points in all 4 quadrants I think.
- QuercusMax 8y agoReformatted your list so it's easier to read: LISP/smalltalk: PG-productive, not difficult Java: PG-unproductive, not difficult C++: PG-unproductive, difficult (Forth? Haskell?): PG-prodictive, difficult
- jcranberry 8y agoThat's not what is says at all. The article claims that you should use the most 'powerful' language available when writing application software (that meets your performance requirements), and that doing so will result in the greatest productivity. The "Blub Paradox" is the claim that you can only understand how powerful languages are in terms of the powers the languages you know have. So if you understand Python and C++ and not Lisp, you are unable to estimate the power of Lisp.