C#

[teddy710]

Can you all send me links on here for good tutorials or free courses and such that taught you how to code? And also can you tell me how you learned if it wasn't from any of the above? Thanks

[DXMember]

microsoft virtual academy

https://mva.microsoft.com/#imagine

[Nuluvius]

Pluralsight and Lynda.com

[Bacon8tor]

https://msdn.microsoft.com/en-us/library/aa288436(v=vs.71).aspx

[handymanshandle]

This C#, right?

 

 

(I like the way A and B minor sound.)

 

Seriously though, maybe something like Codeacademy or Lynda.com might have something on C#.

I just came here because I saw C# and me being someone that played a violin in my schools' orchestras' since 6th grade. 

 

[DXMember]

2 minutes ago, wcreek said:

This C#, right?

 

 

(I like the way A and B minor sound.)

 

Seriously though, maybe something like Codeacademy or Lynda.com might have something on C#.

I just came here because I saw C# and me being someone that played a violin in my schools' orchestras' since 6th grade. 

 

Why do Java developers wear glasses?

Because they don't C#.

[Ziggs]

http://www.homeandlearn.co.uk/csharp/csharp.html

[teddy710]

1 hour ago, Nuluvius said:

Pluralsight and Lynda.com

Isn't Lynda not free?

[Nuluvius]

53 minutes ago, teddy710 said:

Isn't Lynda not free?

Can't you rustle up some kind of free trial from somewhere?

 

If not excuse me I'm absolutely exhausted.

 

In any event all of this is all well and good but arguably the single most valuable area that you should be focusing on right now is the theory. You should put your maximum effort into learning good engineering and design principles. They are language agnostic and will help you infer knowledge about specific languages and programming paradigms moving forwards.

 

Any chimp may bang away at a keyboard and name the product 'code'... It takes a Software Engineer/Developer (someone who has an understanding of the underlying theory) to produce eloquent, well designed and extensible software.

 

I can elaborate if you are interested.

[teddy710]

8 hours ago, Nuluvius said:

Can't you rustle up some kind of free trial from somewhere?

 

If not excuse me I'm absolutely exhausted.

 

In any event all of this is all well and good but arguably the single most valuable area that you should be focusing on right now is the theory. You should put your maximum effort into learning good engineering and design principles. They are language agnostic and will help you infer knowledge about specific languages and programming paradigms moving forwards.

 

Any chimp may bang away at a keyboard and name the product 'code'... It takes a Software Engineer/Developer (someone who has an understanding of the underlying theory) to produce eloquent, well designed and extensible software.

 

I can elaborate if you are interested.

No I get what you mean and I never really thought about it that way. Thanks for the insight but does that basically just come with learning a language and understanding it or what?

[Nuluvius]

7 hours ago, teddy710 said:

No I get what you mean and I never really thought about it that way. Thanks for the insight but does that basically just come with learning a language and understanding it or what?

Some of it will but more so with time and experience; exposure to real world problems and being mentored through them, being involved in architectural planning and design and also generally learning by osmosis. However understanding the underlying theory gives you a lot of the fore knowledge of how to expect something to work when you pick it up for the first time - be that an whole new language or a new technology or framework.

 

In my opinion some of the most important concepts to grapple with and learn first would be:

 

Principals

• Single responsibility, open-closed, Liskov substitution, interface segregation and dependency inversion (SOLID)
• Atomicity, Consistency, Isolation, Durability (ACID)
• Keep it simple, stupid (KISS)

Patterns

• General Design Patterns, there's a very good library over at Pluralsight for these here.
• Dependency Injection (DI)
• Inversion of Control (IoC)
• Model View View-Model (MVVM), very industry relevent these days.

Methodologies

• Agile
• Test Driven Development (TDD)
• Behaviour Driven Development (BDD)
• Ports and Adapters Pattern (Hexagonal Architecture)

You should also consider learning about the other programming paradigms. When considering other paradigms there are of course paradigm specific permutations on the some of above  

 

Getting to grips with the principals and patterns will generally build you a gut instinct for what is right and what is wrong as you embark upon your journey to becoming a great engineer/developer.

 

These are of course just starting points, it's a rich world out there full of information and opinions and ways of doing things that are never the same. I'd encourage digging deep with all of these. Pluralsight is a really good resource and I have often found it to be pragmatic with it's information.

 

If you have questions then I'm always happy to help.