KK here's what's up:
I want to learn .NET development. I have limited experience from C++ and have been messing about with C# lately, making server/client apps, connecting to MySQL etc. Good times.
But I'm lost as to what the hell I'm supposed to do now. What am I supposed to learn? I'll be slowly grinding out the uhm, standard C# "library" :), but what do I do in the meantime? I'm perhaps leaving this too open, I guess I'm basically asking what I specifically should focus on to become a good programmer ready to go into a career as a programmer without a school diploma.
Also how does programming go down in the business world? Let's say for a .NET application with 10 or so programmers, how is the project managed, are there any good online documents on this?
>>7
We conjure the spirits of probability with our insurance plans
Name:
Anonymous2010-10-16 17:46
I would forget .NET and C# all together. You want to write code that is portable between platforms. You want to be able to make applications for the ICrap and Android mobile phones and tablets. You want to be able to port to linux.
Just like I would advise against ASP.NET and go with PHP.
Java is pretty damn good at server/client stuff, and portable. Can even compile from java byte code to platform specific if you want the speed boost.
>>1
.NET is good for getting a job. So is Java. /prog/ is not about grinding away at enterprise programming. If you want to get a job, learn .NET or Java and program, monkey boy. If you want to hang out on /prog/, read your SICP.
Ignore the jokers who tell you C# is not portable. Mono/C# on Linux / OS X is damn fine, and you can write C# for Android / iPhone too. (And the thing about compiling to native code for a speed boost? Hah! >>9 doesn't know what he's talking about, native code only speeds up launch times, and the Java->native code compilers are terrible.)
People, before this conversation goes any further, I would like you all to realize >>1 is a troll.
Name:
Anonymous2010-10-17 11:35
>>11 native code only speeds up launch times, and the Java->native code compilers are terrible.
True, and if you get rid of overhead from the JVM and the class libraries — like the Android guys have done — the performance is OK to good, depending on the quality of your JIT engine.