User:Rldrenth: Difference between revisions

m
Correct notmylang|Cobol which I "broke" (you can use notmylang|COBOL|just plain ugly|Cobol if you'd prefer the old rendering)
m (Correct notmylang|Cobol which I "broke" (you can use notmylang|COBOL|just plain ugly|Cobol if you'd prefer the old rendering))
 
(7 intermediate revisions by one other user not shown)
Line 1:
{{notmylangbegin|Languages I abstain from}}
{{notmylang|Ruby|too cryptic, Perlish}}
{{notmylang|Cobol|just plain ugly}}
{{notmylang|Ada|excess syntax & keywords}}
{{mylangend}}
{{mylangbegin|Favorite Languages}}
{{mylang|C|advanced}}
{{mylang|C sharp|novice}}
{{mylang|Python|advanced}}
{{mylang|Verilog|intermediate}}
{{mylangend}}
{{mylangbegin|Languages I use}}
{{mylang|AWK|intermediate}}
Line 16 ⟶ 5:
{{mylang|C++|advanced}}
{{mylang|Delphi|rusty}}
{{mylang|Java|beginnernovice}}
{{mylang|JavaScript|when need tonovice}}
{{mylang|Lua|novicebeginner}}
{{mylang|ME10 macro|intermediate}}
{{mylang|Perl|novice}}
{{mylang|SQL|intermediate}}
{{mylang|UNIX Shell|intermediate}}
{{mylangend}}
{{mylangbegin|Favorite Languages}}
{{mylang|C|advanced}}
{{mylang|C sharp|novice}}
{{mylang|Python|advanced}}
{{mylang|Verilog|intermediate}}
{{mylangend}}
{{notmylangbegin|Languages I abstain from}}
{{notmylang|Ada|excess syntax & keywords}}
{{notmylang|RubyCOBOL|toojust cryptic,plain Perlishugly}}
{{mylangend}}
==About Me==
Line 48 ⟶ 47:
SQL - You won't be using this all the time, but you will do enough with it to need to learn it.
 
Assembly - At least a little, so you know what happens down at the machine level. I'ld recommend
learning assembly for a microcontroller such as 8051, PIC, Z-80. Don't start out trying to learn
the assembly for a Pentium class computer. There's too much hardware you'ld have to know in order to understand what most of the instructions are doing. Assembly for the 68000 would be a good one too.
 
VHDL or Verilog or other Hardware Description Language - It's a different way of viewing the world, where timing and sequencing rule. Of the two, I like Verilog better. A discrete event simulation
language would be another option.
 
A Functional Programming language - Main Options: APL, Haskell - You might not use these much, but it may give you insight on alternative ways to implement something in another language.
VHDL or Verilog or other Hardware Description Language - It's a different way of viewing the world, where timing and sequencing rule.
 
===What popular modern language should you not bother to learn?===
Visual Basic or VB.Net. -It's on the way out, being supplanted by C#, Python, and occasionally C.
There's no longer a good reason to use it on new projects. Python is easier for quick apps. C# would use the same development environment and is better for significant projects. If you need an exe, Delphi, C++, or C will give you that. When I've used Visual Basic, the library API's always felt 'kludgy', as a whole.
 
What about C++? - I still like C++. But I think there are other languages that will provide higher programmer productivity in practice. Try D, Objective-C, Java, or Delphi instead.
Anonymous user