Using any language for twenty years straight is going to make you complacent - but goodness, how many languages would have given you that luxury?
COBOL?
How knowing Lisp destroyed my programming career (2006)
11–20 of 433 posts
Re: How knowing Lisp destroyed my programming career (2006)
#12> I saw people whip things up in Perl in a couple of hours that would have taken me days or weeks to do in Lisp.
Perl, my first and only love.
Re: How knowing Lisp destroyed my programming career (2006)
#13Using any language for twenty years straight is going to make you complacent - but goodness, how many languages would have given you that luxury?
> what other programming language would have given you that luxury?
I'm not sure what you mean. C? C++? Java? Perl? Perhaps Python?
Re: How knowing Lisp destroyed my programming career (2006)
#14Using any language for twenty years straight is going to make you complacent - but goodness, how many languages would have given you that luxury?
Perl?
Perl is one of those languages, if you get used to the power of Perl it could be really hard to move to other C based languages.
I can only imagine how it would be for anyone using Lisp. The power there is so much, going to something like Java from there would feel down right suffocating.
Going from Perl to Python in my case largely felt like trying to a run a marathon in chains.
Re: How knowing Lisp destroyed my programming career (2006)
#15Re: How knowing Lisp destroyed my programming career (2006)
#16> knowing Lisp made me all too keenly aware of Java's shortcomings, and I had a very hard time not being angry at how stupid it was that I was being forced
to use it.
I would take this as a the thing to remember from this. When you are too angry at something, you cant learn it. I have seen the emotional refusal to learn new inferior thing (or read comments that amounted to the same) many times already.
It is something to be aware of and avoided.
Re: How knowing Lisp destroyed my programming career (2006)
#17> I saw people whip things up in Perl in a couple of hours that would have taken me days or weeks to do in Lisp. Perl, my first and only love.
Mine too. Until Erlang, and now Ada. I'm building myself a harem.
Re: How knowing Lisp destroyed my programming career (2006)
#18Earlier quoted context omitted.
COBOL?
COBOL and luxury present in one English sentence is a syntax error.
If you never knew anything but COBOL you'd probably love programming it. Knowledge of better techniques can be seriously damaging to your career.
I suffered some damage from not wanting to touch Windows (3.1) after discovering Linux in the early 1990s. Today, most jobs advertisements still look toxic.
Re: How knowing Lisp destroyed my programming career (2006)
#19> I saw people whip things up in Perl in a couple of hours that would have taken me days or weeks to do in Lisp. Perl, my first and only love.
Mine too. Until Erlang, and now Ada. I'm building myself a harem.
I started with Pascal, then learned Perl. When I was writing Pascal I was excited about stuff I could make the computer do, but pascal made me like the actual act of programming.
Re: How knowing Lisp destroyed my programming career (2006)
#20derkeiler.com gets blocked by uMatrix: the domain appears in Dan Pollocks hosts-file http://someonewhocares.org/hosts/ in the 'ads' section.