Anonymous user
User:Rldrenth: Difference between revisions
→What Languages Should You Learn
Line 48:
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.
===What popular modern language should you not bother to learn?===
Visual Basic or VB.Net.
There's not a good reason for its existance anymore. Python is easier for quick apps. C# would use the
same development environment and is better for significant projects. If you need an exe, a C program
will give you that.
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.
| |||