3 ms·
> Completely agree. I worked at a company on a Common Lisp project where the Python crew refused to learn Common Lisp because they thought it would look bad on
by enz 6y ago
> Completely agree. I worked at a company on a Common Lisp project where the Python crew refused to learn Common Lisp because they thought it would look bad on their resumes.
They can put only "Python" on their résumés, right?
- dreamcompiler 6y agoOne would think they could just avoid mentioning Lisp. I still don't understand their reasoning.
- kazinator 6y agoThe reasoning is simple: if someone thinks something would look bad on their resume, they probably don't want to spend time on it, either. For example, I wouldn't want PHP or Fortran on my resume, and, consistently with that, I avoid them. I don't have an opportunity to actively avoid them, but that defense mechanism would leap into action, if called upon. However, I know a thing or two about these; I'm not simply applying "meme-based reasoning".
- ksec 6y agoThis really is resume driven development into a whole new level. No wonder why some sane Programming languages Never made it. And it is the reason why I am worry about Ruby's future.
- zihotki 6y agoIt's not a resume driven development but a proper allocation of personal time and skills planning for the future. What's the point of learning something you won't use in the future? If for the sake of learning then there are a lot of better choices.
- kazinator 6y agoJust don't base your choices on the spreading of ignorant memes. Would you want to pass on Lisp because of the ramblings of a rookie web developer with no Lisp experience? That's what you might do if you believe the "Lisp Curse".