|
I'm totally with you on everything you wrote. I'd only wxchange the order of "written tutorials" and "using the docs", with the caveat that it applies ony if the docs are well written (i.e. Win32 API).
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Griff,
I am stunned everytime I see your signature.
I learned programming on an Amstrad CPC 464 in 1984/85. It is sooo many years, since I laid my hands on Amstrad.
This word is so nostalgic to me.
Thanks for your signature 
|
|
|
|
|
 Agree
Pity is... most of the time, due to the lack of time. Many people end reading a lot staff in internet trying to distinguish good from crap, solve the current issue and change to the next item in the ToDo
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
As somebody who teaches formal courses at a local college, there's nothing I love more than engaged students who ask questions. I have a 300-level course right now where I have the students take turns "driving" at the podium, and the class works through solving problems as a group. With this group of students (my first in 5 years), I get to serve more as a facilitator than an instructor, filling in the knowledge gaps where appropriate. I still create the problems for the students to solve (unless they come up with their own, which is also exciting), and their engagement forces me to be sharp (haha) with the language (C#) and coding principles in general.
TL;DR - Thanks for discussing the importance of formal courses.
|
|
|
|
|
Excellent!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I can agree with you on this to a point. However if I am looking at picking up a new language/technology that I need right now for a client, taking a formal course that will require months of time is not usually the most effective (especially if the client needs results now).
I think that anyone that has been working successfully in our field (at least 10+ years) learns the knack of picking up enough of a new technology quickly to get the job done, at least at first. After that if we keep using that technology we just reinforce and add to our use and understanding of that tech.
Of course this has shortcomings - we may get a stilted view of a new technology, not realizing some of the more elegant solutions it provides. I think then that if this is something we want more of a deep dive into, we take those courses and read the books (among other ways) to get a wider breadth of understanding in such new tech.
|
|
|
|
|
Andreas Mertens wrote: we may get a stilted view of a new technology, not realizing some of the more elegant solutions it provides
And that's the problem with internet based "tutorials" - most of them are created by people who also don't realize what is available!
A good course on a new language doesn't have to take months: heck, an experienced developer could pick up the whole of C# the language in a day or less, but the whole .NET framework it depends on is a lot more to learn. A "basics" course - enough to get you up and running with C#, collections, Linq, events, delegates, databases, threading, and WinForms for example - could be under a week.
And the big problem is that if you "pick it up" enough to get the job done, you won't be given time to learn it properly - because you clearly don't need it as your code works ... 
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: A "basics" course - enough to get you up and running with C#, collections, Linq, events, delegates, databases, threading, and WinForms for example - could be under a week
I totally agree. But when it comes to newer tech (or tech that is in a narrower field), finding some decent learning material amongst the dross that usually pops up is a challenge. And that client is waiting...
Having worked in this field for some time now (40+ years), one thing that I have noticed is that a lot of languages and frameworks that have come out are built on concepts that already existed. For example I was involved in working on one of the Netscape browsers and learned the XUL UI framework that they use. When I started learning WPF, and later Flex (Flash) programming, I found that a lot of the same concepts were incorporated and making it much easier to learn these languages.
One thing too - so many new technologies come out, have their brief moments of "wow", then fade away again. One has to be picky about what technologies you want to put the extra time into.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
