Topic: Primary programming interest

[pkohut]

Just curious what the numbers are.

If your interested in a second or third programming area, add a comment.

[Krushert]

Primary Lisp but if I have time I would like to try my hand C#.  But I never seem to have time. 

[JohnK]

C++

[Kerry]

Voted C#,
but perhaps this says it best.

[MP]

Voted "other" because I'll learn | use what's most appropriate for the task at hand -- could be lisp, could be c#, could be python ...

[JohnK]

You (MP), Kerry and Paul are very good examples for the rest of us newbies; You guys already know the basics of general programming and can therefore jump from one language to the next with little to no problem (just (re)learn the syntax) and off you go. You guys are what i aspire to become as soon as i can learn a real programming language(s).

[ElpanovEvgeniy]

1. Assembler         
2. Visual Lisp...       

[MP]

@John -- I consider the quest to become a programmer much like that of aspiring to become a musician -- even for those that may have natural talent / aptitude it still requires years of diligent study and practice, the carrot always being just beyond one's reach (not necessarily a bad thing). There may be periods when one's ability appears to plateau or the passion wanes -- push through, practice those scales, try to play songs and in styles never experienced before, listen to other artists. Ideally in time you become one with the instrument and are the music -- not merely playing the music.

Rock it.

Banally yours, MP.

[LE3]

The way I am going.... it will be: None.

    

[dgorsman]

1. Assembler         

That explains quite a bit.  With assm code all solutions *must* be elegant.

For me, its LISP.  It gets the most job done in the least amount of time, and if I get hit by a bus its easy to find a replacement.  And, to be frank, theres a lot less RTFM attitude in the AutoLISP community than the dot-NET one.  This community is an exception though.  :kewl:  Us working folks don't always have the time to learn all the little tricks that full-time programmers consider basic knowledge, so those dirty little hacks let us get the job done.

I have been working on C#, especially now that I am getting into some applications that require heavy lifting, but real work ends up getting in the way more often that not.  Its real hard to get something done at that level of complexity when you are getting pulled away every 15 minutes.

[ElpanovEvgeniy]

1. Assembler         

That explains quite a bit.  With assm code all solutions *must* be elegant.

For me, its LISP.  It gets the most job done in the least amount of time, and if I get hit by a bus its easy to find a replacement.  And, to be frank, theres a lot less RTFM attitude in the AutoLISP community than the dot-NET one.  This community is an exception though.  :kewl:  Us working folks don't always have the time to learn all the little tricks that full-time programmers consider basic knowledge, so those dirty little hacks let us get the job done.

I have been working on C#, especially now that I am getting into some applications that require heavy lifting, but real work ends up getting in the way more often that not.  Its real hard to get something done at that level of complexity when you are getting pulled away every 15 minutes.

Unfortunately or fortunately, I was not able to examine the assembler.
My first language that I began to speak freely, was Lisp!

[pkohut]

1. Assembler         

That explains quite a bit.  With assm code all solutions *must* be elegant.

Unfortunately or fortunately, I was not able to examine the assembler.

Very :kewl: Evgeniy

[Matt__W]

Cobal, Fortran and.... oh, yeah... Flash!

[pkohut]

Cobal, Fortran and.... oh, yeah... Flash!

Very  :kewl: Matt.

 

[Keith™]

meh .. whatever happens to suit the mood .. python, ruby, perl, C#, VB, C++ .. whatever gets the job done and whatever is best suited for doing the job ... I wouldn't write a C# application to run on a unix server and I wouldn't use perl to code a desktop application.