There is nothing wrong with scripting languages. They are creat. But... somehow hurry + medicore programmers + scripting ends up into costly mess.
Using traditional programming languages usually involves thinking phase. Something that quick use of scripting does not seem to involve. Have you seen Perl code reviews lately?
The three principal virtues of a programmer are
Laziness,Impatience, and Hubris. See the Camel Book for why.Maintain perl code to see why not.
Solution: Debug all ductape coders from your system. Let all remaining use the best language.
Indeed, the U.S. Department of Defense has offered research funding for the goal of sustaining a fully wake, fully functional 24/7 soldier, sailor, or airman. -- Professor J. Christian Gillin,
I guess next time I operate my F-16 I can't get so high anymore.
Best language?
on
Ask Larry Wall
·
· Score: 3, Interesting
Larry. What is the best programming language you did not desing?
Siemens engineer, Motorla engineer and Nokia engineer are having meeting together.
Siemens engineer boasts:
We have created phone where mouthpiece is put under
little fingers fingernail and earpiece is under fingernail in index figer.
Motorola engineer boasts:
Whe have reated phone so small that it fits into a teeth.
1. Write less code. Line not written is line without bugs. Don't use languages that make you write lot low level code.
2. Write programs that write code. Write your onwn program specific language or make language framework that generates the code you need. Less human written code is good. Investments into good code generators and frameworks pays off.
3. Use the most highest level language possible. Pyhton, Lisp, Haskell, others. Use many languages if needed. Only 1-10% of code should be human written written in C, Java, C++.
4. Code bottom up. First code utilities, libraries, language-extensions, languages etc. until you can write your applications with these building blocks easily and with less code.
5. Work with the best! Don't hire code monkeys. Hire only from the top (1-5%) programmers. Less is more. Hire 50% less programmers. Pay them 300% more! Most employers want medicore programmers writing medicore and verbose code that looks nice with UML. That's because they want to be able to replace programmesrs easily and they can hire lots of them. They feel secure that way.
Dont work with programmers who can't read code! This is really common problem nowdays. People just don't have concentration to read code trough, line by line.
I have now been learning + programming in Common Lisp about 3-4 years. I have learned that CL gives more degrees of freedom to programmers than any other language I have learned before (C/C++, Java,,Ada,Prolog,Haskell, Pascal, Python, Perl).
It is said that (Common) Lisp is programmer amplifier. The good news is that superior programmers/architects get 100X boost. But my experience is that bad/medicore programmers can shoot themselves in the foot as badly as in Perl (usually in more abstract level).
My question is:
Can Common Lisp be used/learned in company of tens of people who have been using C/C++/Java and only 10 persent of those programmers have masters degree?
Slashdot Mirror
Using traditional programming languages usually involves thinking phase. Something that quick use of scripting does not seem to involve. Have you seen Perl code reviews lately?
The three principal virtues of a programmer are Laziness,Impatience, and Hubris. See the Camel Book for why.Maintain perl code to see why not.
Solution: Debug all ductape coders from your system. Let all remaining use the best language.
1. Those who have option to say no and walk away.
2. Those who don't have that option.
Why it is that many companies prefer no 2 kind of work force?
Indeed, the U.S. Department of Defense has offered research funding for the goal of sustaining a fully wake, fully functional 24/7 soldier, sailor, or airman. -- Professor J. Christian Gillin,
I guess next time I operate my F-16 I can't get so
high anymore.
Larry. What is the best programming language you did not desing?
What did you smoke when you invented perl?
Oly paashegh int the ynvierse where y can get the finhesth Scotch Whisky. Sory yer me spelling but i have Famous Grouse in my glass.
Siemens engineer, Motorla engineer and Nokia engineer are having meeting together.
Siemens engineer boasts:
We have created phone where mouthpiece is put under little fingers fingernail and earpiece is under fingernail in index figer.
Motorola engineer boasts:
Whe have reated phone so small that it fits into a teeth.
Nokia engineer:
FAAARRTT, oh sorry. I got mail.
Use these rules:
1. Write less code. Line not written is line without bugs. Don't use languages that make you write lot low level code.
2. Write programs that write code. Write your onwn program specific language or make language framework that generates the code you need. Less human written code is good.
Investments into good code generators and frameworks pays off.
3. Use the most highest level language possible. Pyhton, Lisp, Haskell, others.
Use many languages if needed. Only 1-10% of code should be human written written in C, Java, C++.
4. Code bottom up. First code utilities, libraries, language-extensions, languages etc. until you can write your applications with these building blocks easily and with less code.
5. Work with the best! Don't hire code monkeys. Hire only from the top (1-5%) programmers. Less is more.
Hire 50% less programmers. Pay them 300% more!
Most employers want medicore programmers writing medicore and verbose code that looks nice with UML. That's because they want to be able to replace programmesrs easily and they can hire lots of them. They feel secure that way.
Dont work with programmers who can't read code! This is really common problem nowdays. People just don't have concentration to read code trough, line by line.
Those of you who want to read the real story (it was not told in US) Short summary: Read this
I have now been learning + programming in Common Lisp about 3-4 years. I have learned that CL gives more degrees of freedom to programmers than any other language I have learned before (C/C++, Java, ,Ada ,Prolog ,Haskell, Pascal, Python, Perl).
It is said that (Common) Lisp is programmer amplifier. The good news is that superior programmers/architects get 100X boost. But my experience is that bad/medicore programmers can shoot themselves in the foot as badly as in Perl (usually in more abstract level).
My question is:
Can Common Lisp be used/learned in company of tens of people who have been using C/C++/Java and only 10 persent of those programmers have masters degree?