Using DirecTV. The introductory offer is really good. Afterwards, they are quite a bit higher than TWC, but the channel offerings are better, and the signal is much better. With TWC, my HD channels would oftern stutter or just black out.
Great web site. Love the info and suggestions I can get here.
So, I have been doing IT work for over 25 years (servers, networks, hardware, etc...) and never delved into the development field. I now have the opportunity to learn writing and modifying code, but I am having a hard time making this logic click.
I have several beginner books on Visual Studio (2005,2010,2012)and have done the training classes offered by a local business.
I am focusing on Visual Basic as my language of choice because the company I work for uses this only.
Any suggestions on how I can make all this info click?
I understand the concepts, but just could not write the code behind a app i lay out in VS Designer to save my life.
Thanks all for the great advice. I sort of suspected I was trying to bite off more than I could chew.
Going to go back simple and work my way up.
Learning Visual Basic will tar you as a n00b forever, and firmly establish a reputation that will be very difficult to get out of. If you are going to learn a CLR language, C# might be a better choice. And if you want to expand your horizons beyond Microsoft, java might be the one.
haha...maybe a Old n00b...
I have read that once you have a language down, it makes learning other languages easier. Vb and VB.Net are what our dev guy uses here, so I need to get this to assist. C# is on my list as well as Java for personal enrichment.
Any suggestions on a n00b learning C# and Java (as well as VB)? Don't seem to have a issue with the tools to design apps, just making it do what I want.
I have read that once you have a language down, it makes learning other languages easier...
This is indeed true to a certain extent. I know about 100 computer languages, and at least in the early days, it was all really just syntax. I was usually able to learn a new language by reading the language reference. There were several exceptions to this (assembly, APL, C). Nowadays that is not quite so true.
What is more important to grasp is the concepts and programming paradigms involved: [assembly], object oriented programming, functional programming, web, templates, lambdas, ...
Next to that is frameworks and environment: MFC, WTL, CLR, unix/linux, ...
Each of these is a separate skill, and shifting from one language to another is a much smaller step if you understand the paradigms involved.
If you are good with one assembly language, you will not have much trouble with another.
Group all kinds of programing languages by their closeness to the hardware and their generations (also roughly equivalent to the prevailing programing model) and you get an accurate impression of how small or big the step from one to another may be.
And in the end they all produce just a lot of bytes that the processor will try to execute as instructions.
at least in the early days, it was all really just syntax.
I am experiencing something like this right now. I know about 3 or more languages (depends on what you consider 'knowing' a language). I was given a test in a language I had never attempted to learn before. I had to fix 3 bugs. The first was just strings that are really dates being sorted alphabetically like "1-Feb-2012" coming before "1-Jan-2012". I had to make it sort chronologically. I got the syntax down, found out how the date types work, and I fixed it. The other 2 bugs had nothing to do with the main code language they were using. The template system they use needed to be modified for the second bug. The third bug involved changing an oracle database table to include two more columns, and having their build scripts and code generation tools pick up these two extra values. I fixed 2 out of 3. I felt awesome when I made that brand new language do what I wanted, and then stupid for not knowing nearly enough about the other components that drive their application. I am on a mission now to learn these things, and what you just said really hit home.
A large part of learning a .Net language is learning the framework, Visual Studio, OO concepts and design patterns eg MVC. Somebody who is a competant VB.Net developer won't have much trouble picking up C# - same framework, same IDE, same OO concepts baked in. The difference is mainly down to syntax. Hence why there are websites offering VB.Net to C# converters and visa-versa!
Of course you will be noob, only because you program on language without ";".
VB.Net and Csharp are 97% like same, only compiler AST are different, in most cases, IL generated are same.
Even in new framework, the compiler will be the same.