News for hackers. Stuff that matters.
Re:Why I wrote 33 VSCode extensions and how I manage them by gdfasfklshg4 on Tuesday November 06, 2018 @04:04AM (#18389420)
But why force your students to use a specific tool?

How is this different to writing an Excel macro?

Re:Why I wrote 33 VSCode extensions and how I manage them by jeeva on Tuesday November 06, 2018 @06:08AM (#18389958)
Is your argument really "why teach them to do something specific"?

Why teach C++? Some students might not prefer that to C#.

My problem at school was always "how do I apply this lesson to an actual problem?" Picking _something_ (anything!) to teach is great (to me), because canny students can go off and use the lesson to do _anything_ else.

Re:Why I wrote 33 VSCode extensions and how I manage them by gdfasfklshg4 on Tuesday November 06, 2018 @08:36AM (#18390822)
> Why teach C++? Some students might not prefer that to C#.

Between these two there is very little to choose in terms of concepts the students would be exposed to. I would assume that teaching either of those would aim to teach the underlying concepts of object orientated programming.

The questions that need to be asked instead are: What concepts would building an editor plugin expose students too? And is this the best way to introduce those concepts? (NB I am assuming University level where contact time for taught material is only really enough to introduce concepts not to really go into details.)

Re:Why I wrote 33 VSCode extensions and how I manage them by SmellyGeekBoy on Tuesday November 06, 2018 @05:57AM (#18389905)
Why teach C in University when students might prefer Python or Java? The specific implementation isn't important, it's the overarching concepts that matter.
Re:Why I wrote 33 VSCode extensions and how I manage them by gdfasfklshg4 on Tuesday November 06, 2018 @08:30AM (#18390770)
I would argue that a programming course might want to teach all three of those. They are quite different languages which could be used to teach different underlying concepts (C for pointers and low level stuff (and maybe combined with some assembler), Java for object orientation and Python for dynamic typing).

Python vs PHP vs JavaScript would be another matter. I would say it doesn't matter so much which of those you teach. Same with e.g. Java vs C# vs C++.

The question remains why build an Atom plugin over an Excel macro? And what underlying concepts would you hope to teach students by doing this? And is this the best way to introduce those concepts?

Re:Why I wrote 33 VSCode extensions and how I manage them by guardian5x on Tuesday November 06, 2018 @04:50AM (#18389625)
You can learn a lot from using a specific tool. And hopefully transfer that knowledge to the tool you like.
Re:Why I wrote 33 VSCode extensions and how I manage them by gdfasfklshg4 on Tuesday November 06, 2018 @08:32AM (#18390788)
I assume that the OP is teaching at University level. From experience I know that time is very limited in that environment. Everything done with the students should be well justified. Building an editor add on seems like something I would question strongly. What concepts is the OP aiming to introduce the students to? And is this the best way to introduce those concepts?
Re:Why I wrote 33 VSCode extensions and how I manage them by azhenley on Tuesday November 06, 2018 @08:42AM (#18390861)
I want them to practice concepts behind designing, building, and evaluating usable dev tools. Not just reading about them. The course is a special topics on dev tools.