Most innovative/effective learning Techniques for .NET Technologies for all (Beginners, Intermediates, Advanced).
-
What do you think is the most innovative/effective learning techniques for learning .Net for all levels of developers? And how it has helped you learn in an effective manner? Thanks in advance.
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
innovative != effective, necessarily. Best way to learn how to code? Code, and code lots. Be self-critical and see if there are any ways to improve your code. A quick test is "DRY KISS": Don't Repeat Yourseld, Keep It Simple Stupid. If you have repeated code, this can be coverted to a single method/class/class hierarchy which can be re-used. If your code is complicated then you've done something wrong (unless you are doing something actually complicated like high-end maths). To help in this process, you might want to google techniques for re-factorting as most of the code klunge has been seen before and there are a few standard techniques that will help immediately (e.g. repeated switch statements suggest a possible incorrect or missing class structure for example).
PB 369,783 wrote:
I just find him very unlikeable, and I think the way he looks like a prettier version of his Mum is very disturbing.[^]
-
What do you think is the most innovative/effective learning techniques for learning .Net for all levels of developers? And how it has helped you learn in an effective manner? Thanks in advance.
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
Hi Mohammed, 1. put aside WCF, and Knuth, for now 2. decide to what initial "target" you want to develop for: the web, or desktop applications 3. select a specific area in .NET to focus on: one of ASP.NET, Windows Forms, WPF, depending on your selection in #2. 4. get a few good introductory books on the area you chose in #3. 5. start reading: make notes. at the same time as you: 6. start writing small simple applications where you test the concepts you are learning by reading, step-by-step. 7. study the many free samples provided by MS 8. look on CodeProject for examples that interest you, and download them, and study their source code, and how they work. 9. ask specific questions on CodeProject's various technology forums ... WPF, WinForms, ASP.NET, etc. 10. spend less time asking general questions on the Lounge :) Focus, concentrate, study, prototype, test, challenge yourself incrementally, learn from the "masters'" code, divide-and-conquer big challenges into smaller "chunks," slowly build-up your own set of trusted modules of code that have very specific uses so you develop a "toolkit" to use in building future applications. Ignore advice ! good luck, Bill
“Human beings do not live in the objective world alone, nor alone in the world of social activity as ordinarily understood, but are very much at the mercy of the particular language which has become the medium of expression for their society. It is quite an illusion to imagine that one adjusts to reality essentially without the use of language and that language is merely an incidental means of solving specific problems of communication or reflection." Edward Sapir, 1929
-
Hi Mohammed, 1. put aside WCF, and Knuth, for now 2. decide to what initial "target" you want to develop for: the web, or desktop applications 3. select a specific area in .NET to focus on: one of ASP.NET, Windows Forms, WPF, depending on your selection in #2. 4. get a few good introductory books on the area you chose in #3. 5. start reading: make notes. at the same time as you: 6. start writing small simple applications where you test the concepts you are learning by reading, step-by-step. 7. study the many free samples provided by MS 8. look on CodeProject for examples that interest you, and download them, and study their source code, and how they work. 9. ask specific questions on CodeProject's various technology forums ... WPF, WinForms, ASP.NET, etc. 10. spend less time asking general questions on the Lounge :) Focus, concentrate, study, prototype, test, challenge yourself incrementally, learn from the "masters'" code, divide-and-conquer big challenges into smaller "chunks," slowly build-up your own set of trusted modules of code that have very specific uses so you develop a "toolkit" to use in building future applications. Ignore advice ! good luck, Bill
“Human beings do not live in the objective world alone, nor alone in the world of social activity as ordinarily understood, but are very much at the mercy of the particular language which has become the medium of expression for their society. It is quite an illusion to imagine that one adjusts to reality essentially without the use of language and that language is merely an incidental means of solving specific problems of communication or reflection." Edward Sapir, 1929
Thanks a lot Bill, it is a most comprehensive & effective ToDo list you provided :thumbsup:
Quote:
10. spend less time asking general questions on the Lounge
Yes, I think, I must reduced the time spent on the lounge.
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
innovative != effective, necessarily. Best way to learn how to code? Code, and code lots. Be self-critical and see if there are any ways to improve your code. A quick test is "DRY KISS": Don't Repeat Yourseld, Keep It Simple Stupid. If you have repeated code, this can be coverted to a single method/class/class hierarchy which can be re-used. If your code is complicated then you've done something wrong (unless you are doing something actually complicated like high-end maths). To help in this process, you might want to google techniques for re-factorting as most of the code klunge has been seen before and there are a few standard techniques that will help immediately (e.g. repeated switch statements suggest a possible incorrect or missing class structure for example).
PB 369,783 wrote:
I just find him very unlikeable, and I think the way he looks like a prettier version of his Mum is very disturbing.[^]
Thanks Keith for your usual support.
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
What do you think is the most innovative/effective learning techniques for learning .Net for all levels of developers? And how it has helped you learn in an effective manner? Thanks in advance.
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
Every beginner should start with a book. Intermediates and advanced can read online articles. And you should only say that you know X technology when you have developed at-least one pet-project in that technology. You can also try Microsoft Virtual Academy[^], it has wide range of video tutorials.
Remind Me This - Manage, Collaborate and Execute your Project in the Cloud
-
Thrown in at the deep end with a pile of code, a specification, a deadline, internet access and a requirement to justify a decent hourly rate. That's always the most effective technique as long as the learner is capable enough. Of course it's also very high risk if they're not.
"The secret of happiness is freedom, and the secret of freedom, courage." Thucydides (B.C. 460-400)
Thanks.
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
Every beginner should start with a book. Intermediates and advanced can read online articles. And you should only say that you know X technology when you have developed at-least one pet-project in that technology. You can also try Microsoft Virtual Academy[^], it has wide range of video tutorials.
Remind Me This - Manage, Collaborate and Execute your Project in the Cloud
Thanks a lot Rutvik. :thumbsup:
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
What do you think is the most innovative/effective learning techniques for learning .Net for all levels of developers? And how it has helped you learn in an effective manner? Thanks in advance.
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
innovative != effective, necessarily. Best way to learn how to code? Code, and code lots. Be self-critical and see if there are any ways to improve your code. A quick test is "DRY KISS": Don't Repeat Yourseld, Keep It Simple Stupid. If you have repeated code, this can be coverted to a single method/class/class hierarchy which can be re-used. If your code is complicated then you've done something wrong (unless you are doing something actually complicated like high-end maths). To help in this process, you might want to google techniques for re-factorting as most of the code klunge has been seen before and there are a few standard techniques that will help immediately (e.g. repeated switch statements suggest a possible incorrect or missing class structure for example).
PB 369,783 wrote:
I just find him very unlikeable, and I think the way he looks like a prettier version of his Mum is very disturbing.[^]
-
Hi Mohammed, 1. put aside WCF, and Knuth, for now 2. decide to what initial "target" you want to develop for: the web, or desktop applications 3. select a specific area in .NET to focus on: one of ASP.NET, Windows Forms, WPF, depending on your selection in #2. 4. get a few good introductory books on the area you chose in #3. 5. start reading: make notes. at the same time as you: 6. start writing small simple applications where you test the concepts you are learning by reading, step-by-step. 7. study the many free samples provided by MS 8. look on CodeProject for examples that interest you, and download them, and study their source code, and how they work. 9. ask specific questions on CodeProject's various technology forums ... WPF, WinForms, ASP.NET, etc. 10. spend less time asking general questions on the Lounge :) Focus, concentrate, study, prototype, test, challenge yourself incrementally, learn from the "masters'" code, divide-and-conquer big challenges into smaller "chunks," slowly build-up your own set of trusted modules of code that have very specific uses so you develop a "toolkit" to use in building future applications. Ignore advice ! good luck, Bill
“Human beings do not live in the objective world alone, nor alone in the world of social activity as ordinarily understood, but are very much at the mercy of the particular language which has become the medium of expression for their society. It is quite an illusion to imagine that one adjusts to reality essentially without the use of language and that language is merely an incidental means of solving specific problems of communication or reflection." Edward Sapir, 1929
-
Thanks a lot Bill, it is a most comprehensive & effective ToDo list you provided :thumbsup:
Quote:
10. spend less time asking general questions on the Lounge
Yes, I think, I must reduced the time spent on the lounge.
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
Mohammed Bill always gives great advice. He also advised "Ignore advice !" and just remember that everyone needs a little lounge every now and then.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
-
Keith Barrow wrote:
A quick test is "DRY KISS"
I bet your colleagues read that "TRY KEITH"
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Do not feed the troll ! - Common proverb
Nobody wants to try Keith. Not for a long time :^)
PB 369,783 wrote:
I just find him very unlikeable, and I think the way he looks like a prettier version of his Mum is very disturbing.[^]
-
What do you think is the most innovative/effective learning techniques for learning .Net for all levels of developers? And how it has helped you learn in an effective manner? Thanks in advance.
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
One of the best tools I have for learning a technology is writing about it as though I were going to write an article on it. Write lots of little noddy programs that test what you are talking about. By doing this, I find the areas that I don't know well enough to explain properly, and I can spend more time nailing those areas. Don't limit yourself to .NET though - look at what's being done in other tech areas; if you don't, you'll only ever be as good as the existing framework allows you to be. You won't be aware of other techniques that are common practice outside the .NET world.
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier -
Oh right, I see. It's in New York, Dougal.
PB 369,783 wrote:
I just find him very unlikeable, and I think the way he looks like a prettier version of his Mum is very disturbing.[^]
-
One of the best tools I have for learning a technology is writing about it as though I were going to write an article on it. Write lots of little noddy programs that test what you are talking about. By doing this, I find the areas that I don't know well enough to explain properly, and I can spend more time nailing those areas. Don't limit yourself to .NET though - look at what's being done in other tech areas; if you don't, you'll only ever be as good as the existing framework allows you to be. You won't be aware of other techniques that are common practice outside the .NET world.
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easierSupert explanation Pete :thumbsup::thumbsup: Thanks a lot for your usual help.
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
Mohammed Bill always gives great advice. He also advised "Ignore advice !" and just remember that everyone needs a little lounge every now and then.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
Yes, correct...
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
Keith Barrow wrote:
A quick test is "DRY KISS"
I bet your colleagues read that "TRY KEITH"
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Do not feed the troll ! - Common proverb
:-D
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
Oh right, I see. It's in New York, Dougal.
PB 369,783 wrote:
I just find him very unlikeable, and I think the way he looks like a prettier version of his Mum is very disturbing.[^]
Quote:
Oh right, I see. It's in New York, Dougal.
What's that in New York?
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
Quote:
Oh right, I see. It's in New York, Dougal.
What's that in New York?
Previous -> Read "CLR via C#" by Jeffrey Ritcher. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
There is a joke, as old as the hills: Q: How do you get to Carnegie Hall A: Practise. In the UK there was a very famous comdedy called Father Ted, it featured a very stupid (or possibly not) character called Dougal who asks the question. Father Ted answers with the joke reply, only to discover Dougal was serious, so he tell him it's in New York[^]. It was funny on the show (the whole show was funny), but I couldn't find a YouTube clip, written down it isn't all that funny.
PB 369,783 wrote:
I just find him very unlikeable, and I think the way he looks like a prettier version of his Mum is very disturbing.[^]
