4 ms·
Not that I don't agree with some of the points raised, but the article's purpose is to be a refutation to this claim: There are genius programmers who wri
by bad_user 16y ago
Not that I don't agree with some of the points raised, but the article's purpose is to be a refutation to this claim:
There are genius programmers who write Lisp,
and Lisp may suit them well. But these same folks
would also be able to accomplish amazing things in
other languages.
Languages and tools are not created equal, but the author assumes he's one of those geniuses, which may not be the case.
Extraordinary developers do extraordinary things, regardless of the tools used. Here's an example, using as reference http://en.wikipedia.org/wiki/Git_(software)#Early_history http://en.wikipedia.org/wiki/Git_(software)#Early_history
The development of Git began on April 3, 2005. The project was announced on April 6, and became self-hosting as of April 7. The first merge of multiple branches was done on April 18. Torvalds achieved his performance goals; on April 29, the nascent Git was benchmarked recording patches to the Linux kernel tree at the rate of 6.7 per second.
And here's the kicker: Linus would probably be more productive in LISP, but would he bring more value to the world? Probably not, as churning out code is not Linus' strength -- he outcompetes everyone by superior design, by pragmatism and by being a good team-leader.
That's the type of developer I admire -- people that kick-ass in bringing value and making sacrifices is part of that. Sometimes you have the luxury of picking up a new language (Ruby) and invent a new web framework with it (Rails), sometimes you don't. Either way, code talks bullshit walks (so to speak).
- lisper 16y ago> the author assumes he's one of those geniuses Exactly the opposite actually. Not only do I not assume that, I specifically deny it.
- SeanDav 16y agoActually, even though you deny that you are a genius I think you are. I don't think your article refutes the original article by John Cook at all as you are one of the very small percentage of people that can "make things happen" in Lisp or any other language. I would suggest you are too much of an engineer to use an "inferior" tool like C++ or Java because you know there is something "better" otherwise I am sure you would achieve equally spectacular results in other languages.
- lisper 16y ago> you are one of the very small percentage of people that can "make things happen" in Lisp or any other language Although I'm flattered, I have to ask: what possible basis could you have for making that assessment? My track record certainly doesn't support you. > I would suggest you are too much of an engineer to use an "inferior" tool like C++ or Java because you know there is something "better" A true engineer solves the problem under the constraints that he is given. I have a this tendency to try to change the constraints -- or the problem. Those can be advantageous personality traits for some tasks, but they make me a damn poor C++ coder.
- MrMan 16y agono genius would deny their own genius unless they were engaging in some strategy that required them to make this statement in pursuit of some higher-level goal. a genius who denies their own genius for any reason other than a strategic one cannot be a genius.
- GrooveStomp 16y agoActually, the author pretty much explicitly states that he's not one of those geniuses. "That still leaves open the possibility that I'm just freakin' brilliant, I could have (and would have) produced the same results in any old programming language. But there is actual data to refute that theory." However, instead of invalidating his argument, he uses this to illustrate why Lisp is largely responsible for his success and why you don't have to be a genius to be attracted to Lisp or to benefit from using it.
- j_baker 16y ago> Linus would probably be more productive in LISP ... > he outcompetes everyone by superior design, by pragmatism and by being a good team-leader. On their face, these statements seem contradictory, don't they? How is it pragmatic to turn down a tool that yields better productivity?
- randallsquared 16y agoHow is it pragmatic to turn down a tool that yields better productivity? Because individual productivity is not the most important thing when you have dozens or hundreds of people contributing to a project... or want to have dozens or hundreds of people contributing to your project. It may not be important at all, frankly. Clever, compact code and extendable, maintainable code are often at odds, and lisps allow you to write very clever, very compact code in comparison to, say, Java and PHP. Or, probably, C, but I haven't written much C, so I won't opine on it. :)
- j_baker 16y agoAhem... the comment I was responding to said that he outcompetes everyone by being pragmatic. Not using a tool that would yield better productivity for himself doesn't count as outcompeting people. It counts as working as part of a team. Part of my point is that the idea of out-competing people is a joke to begin with. You succeed with your entire team. You fail with your entire team. Secondly, I dispute the notion that clever, compact code and extendable, maintainable code are at odds. Code becomes extensible by simple virtue of there being less of it. I do agree that clever, compact code is at odds with one thing: someone else looking smart. Do people write clever, compact code to look smart, or do you dismiss it to look smart? Because my experience is that it's almost always the latter. If I really did write the code in an unmaintainable way, they usually have more precise criticism than "It's too clever and compact."
- cdavid 16y agoIt is dubious whether Linus would be more productive using LISP. I mean, git is based around the idea of being super close to the metal, with a consistant focus on speed. We are talking about people who say (and can reasonably claim !) that java is too slow because it does not support unsigned integers... "being a genius programmer", whatever that means, is not a one dimension thing, and people can excel at some things while sucking at others: programming is very vast. I don't know much about LISP, and have not data to believe (or not believe) the OP claim, but he is not alone in claiming that. For example, P. Norvig has also described how he was surprised that people could be as productive in C++ as in LISP when he arrived at google (I think it was in coders at work ? He made a slightly differente claim concerning the unimportance of language on HN as well (http://news.ycombinator.com/item?id=1803815 http://news.ycombinator.com/item?id=1803815).