I'm with gamera here. While tools are certain something you should
touch on, for training/workshops you should not embed them as part of
assignments or anything. They should know about them and what they do
but not have to listen to them. Use them as learning tools, not
governing tools.
- peter
O
We are getting into a discussion more related to pedagogics than any
factual problems in my text.
First of all, the text is not a lesson plan nor is it supposed toe be a
complete overview of every JavaScript quirk.
If anyone is interested, work has been progressing, with many good
suggestion
Hmm, at the risk of sounding a little flamey, I disagree. If you aren't
going to blow students away with something like SICP, you might as well
equip them to experience the joy and pain of building real products.
I'd even suggest you have them release code on day one of class via heroku
or no.de,
I am against the use of linter in the context of teaching. Linters are tools to
aid production, in the context of teams with differently skilled developers.
Teaching should be more about facts, and not shortcuts.
The ECMA-262 standard is a better source of information, IHMO, or the excellent
ser
On Thu, Jan 12, 2012 at 6:57 PM, Lars Gunther wrote:
> Hi again
>
> It seems I have evangelized quite a few fellow teachers in Sweden that
> JavaScript makes a good first language when learning how to program.
>
> However, most teachers have been using Java, C++, PHP or VB + some Pyhon
> and C#.
Hi again
It seems I have evangelized quite a few fellow teachers in Sweden that
JavaScript makes a good first language when learning how to program.
However, most teachers have been using Java, C++, PHP or VB + some Pyhon
and C#. When they start to teach JavaScript they will encounter stuff
