How knowing Lisp destroyed my programming career (2006)

#1

Post by tinderliker » Wed, Mar 14, 2018, 10:12 AM UTC

How knowing Lisp destroyed my programming career (2006)
coding.derkeiler.com

Re: How knowing Lisp destroyed my programming career (2006)

#2

Post by siddboots » Wed, Mar 14, 2018, 11:00 AM UTC

Man. That's a refreshingly humble outlook.

Re: How knowing Lisp destroyed my programming career (2006)

#3

Post by zaarn » Wed, Mar 14, 2018, 11:03 AM UTC

I think the problem there was complacency, as the author mention in their mail. On the other hand, I totally do recommend that everyone picks up some tutorial or guide or book on LISP and learns what the fuzz is all about.

Even today, I feel like a lot of people could learn a lot from LISP and S-Expressions, both of which are powerful constructs.

(Note: I'm not saying you should use LISP productively, it's something you should learn for the heck of it, not to actually use it)

Re: How knowing Lisp destroyed my programming career (2006)

#4

Post by zero_shift » Wed, Mar 14, 2018, 11:04 AM UTC

Using any language for twenty years straight is going to make you complacent - but goodness, how many languages would have given you that luxury?

Re: How knowing Lisp destroyed my programming career (2006)

#5

Post by jng » Wed, Mar 14, 2018, 11:05 AM UTC

All of it probably to be taken with a grain of salt.

Re: How knowing Lisp destroyed my programming career (2006)

#6

Post by phoe-krk » Wed, Mar 14, 2018, 11:05 AM UTC

The conclusion was inescapable: the problem wasn't Perl or C++ or Java, it was me. I just wasn't a very good programmer any more. Lisp's power had made me complacent, and the world had passed me by.

Lisp can't help you if you're too smug for your own good.

Disclaimer: I'm a Lisper.

Re: How knowing Lisp destroyed my programming career (2006)

#7

Post by Dude2023 » Wed, Mar 14, 2018, 11:07 AM UTC

A required thought-piece for all JavaScript devs. Enjoy monopoly while it lasts, but be humble.

Re: How knowing Lisp destroyed my programming career (2006)

#8

Post by quintin » Wed, Mar 14, 2018, 11:08 AM UTC

phoe-krk wrote: post #6

The conclusion was inescapable: the problem wasn't Perl or C++ or Java, it was me. I just wasn't a very good programmer any more. Lisp's power had made me complacent, and the world had passed me by. Lisp can't help you if you're too smug for your own good. Disclaimer: I'm a Lisper.

Non-English speaker.

What does "smug" mean?

Re: How knowing Lisp destroyed my programming career (2006)

#9

Post by vgy7ujm » Wed, Mar 14, 2018, 11:08 AM UTC

zero_shift wrote: post #4

Using any language for twenty years straight is going to make you complacent - but goodness, how many languages would have given you that luxury?

Perl?

Re: How knowing Lisp destroyed my programming career (2006)

#10

Post by phoe-krk » Wed, Mar 14, 2018, 11:08 AM UTC

quintin wrote: post #8

phoe-krk wrote: post #6

The conclusion was inescapable: the problem wasn't Perl or C++ or Java, it was me. I just wasn't a very good programmer any more. Lisp's power had made me complacent, and the world had passed me by. Lisp can't help you if you're too smug for your own good. Disclaimer: I'm a Lisper.

Non-English speaker. What does "smug" mean?

Via Google's dictionary: having or showing an excessive pride in oneself or one's achievements.