What should I do next....(general programming)

[Xav]

Why not? It's great software!

[InfiniteSpawn]

I just don't know much about the other programs. I thought it would be test to just concentrate on 1 thing at a time.

[Xav]

OK, but give it go.

[R-G]

Probably yes.

Originally Posted by G_Morgan

"If you are into low level systems programming then C and ASM is the right way to go usually."

Well, this would actually be more or less the best thing. There is nothing better than starting to learn the concepts of digital problem solving with the computer programming language Assembly. First you must understand how certain things work.

Later, when people learn computer programming languages like C# and so on, they do the opposite of the point of computational complexity theory study. A lot of people will however disagree (which I expect), because they'll say that you can use high-level computer programming languages to develop efficient software algorithms. This is just the half of the truth. If we compare the concepts of problem solving (for example computer programming languages J# and Assembly) we will see the great difference. The skills and experiences of a computer software developer, with a computer programming language like Assembly can lead to the almost perfect software algorithm.

There are however other problems as well. There is now a question. Why don't all people use this computer programming language as the primary concept of problem solving? Is the answer, because "it is hard"? Actually, no. The answer is, because companies at the market tend to make as much money in the shortest time range as possible.

[Xav]

Shame, really.

[G_Morgan]

Originally Posted by R-G

Probably yes.



Well, this would actually be more or less the best thing. There is nothing better than starting to learn the concepts of digital problem solving with the computer programming language Assembly. First you must understand how certain things work.

Later, when people learn computer programming languages like C# and so on, they do the opposite of the point of computational complexity theory study. A lot of people will however disagree (which I expect), because they'll say that you can use high-level computer programming languages to develop efficient software algorithms. This is just the half of the truth. If we compare the concepts of problem solving (for example computer programming languages J# and Assembly) we will see the great difference. The skills and experiences of a computer software developer, with a computer programming language like Assembly can lead to the almost perfect software algorithm.

There are however other problems as well. There is now a question. Why don't all people use this computer programming language as the primary concept of problem solving? Is the answer, because "it is hard"? Actually, no. The answer is, because companies at the market tend to make as much money in the shortest time range as possible.

All algorithms work in all languages though. That was sort of the point of Turing equivalence. The real issue is if the compiler is clever enough to optimise it effectively but we're into the realms of constant factors there. The constant factors aren't that large between Java and C any more (aided by the fact a JIT can optimise specifically for your processor, JIT should be much better than a static compiler).

I think it's worth learning ASM simply to know how the machine works. When you know what your compiler is going to do it can help you program more effectively. It's worth knowing about allocation models and registers in any case though.

In terms of outright efficiency though. A compiler will beat an assembly programmer on large projects simply because of time constraints (the programmer doesn't have the time to optimise all that assembly). Of course in reality only 3% of your code dominates the CPU performance characteristics and an assembly programmer can outdo a compiler by focusing on such a narrow range of code.

[Xav]

Of course, if you really want some joy, you can't go wrong with C#.