News for hackers. Stuff that matters.
Re:Why I wrote 33 VSCode extensions and how I manage them by azhenley on Monday November 05, 2018 @09:35PM (#18387878)
My students next semester are going to each create a VS Code or Atom plug-in as their course project. I’ll definitely be showing them this!
Re:Why I wrote 33 VSCode extensions and how I manage them by snek on Monday November 05, 2018 @10:10PM (#18388012)
what if they prefer ecmacs or vim or sublime or etc, they all have plugin ecosystems as well
Re:Why I wrote 33 VSCode extensions and how I manage them by ncallaway on Monday November 05, 2018 @11:12PM (#18388304)
Then it sounds like a great opportunity for self-learning.

One class can't teach everything. If people have preferences in their tooling, then that's a great opportunity to generalize the lessons they are taught about VS Code.

Re:Why I wrote 33 VSCode extensions and how I manage them by philliphaydon on Monday November 05, 2018 @11:19PM (#18388333)
I actually enjoy digging through plugin code. I was using brackets for a while and found some minor bug where the git plugin wasn't hiding folders correctly. Raised a bug, then downloaded the code and dug through it for a while and figure out a way to fix it, got merged. Made me feel super happy.

https://github.com/brackets-userland/brackets-git/pull/1039

If people are wanting to contribute to OSS i highly recommend finding plugins in your favourite editor to contribute to.

Re:Why I wrote 33 VSCode extensions and how I manage them by azhenley on Monday November 05, 2018 @10:11PM (#18388017)
I can’t teach them all.
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.
Re:Why I wrote 33 VSCode extensions and how I manage them by quickthrower2 on Tuesday November 06, 2018 @12:11AM (#18388553)
That's optional additional homework.
Re:Why I wrote 33 VSCode extensions and how I manage them by fabiospampinato on Tuesday November 06, 2018 @08:42AM (#18390867)
Very flattering, thank you!
Re:Why I wrote 33 VSCode extensions and how I manage them by qubax on Tuesday November 06, 2018 @07:55AM (#18390522)
Isn't that a step down from teaching people VBA macros?

I hope it isn't for a CS class. They should be learning principles rather than creating toy plug-ins which is something anyone can do for a hobby if they wanted.

Re:Why I wrote 33 VSCode extensions and how I manage them by azhenley on Tuesday November 06, 2018 @08:02AM (#18390564)
Creating a plugin allows them to practice the principles that they learn in the course.
Re:Why I wrote 33 VSCode extensions and how I manage them by gdfasfklshg4 on Tuesday November 06, 2018 @08:39AM (#18390844)
There is a vast amount of material to cover in a University course and very limited time to do so. There is only really time to introduce concepts if enough material is to be covered.
Re:Why I wrote 33 VSCode extensions and how I manage them by azhenley on Tuesday November 06, 2018 @08:43AM (#18390874)
In my experience as a student (and as a prof), being taught concepts without an opportunity to apply them is virtually useless. The course is a special topics on dev tools.
Re:Why I wrote 33 VSCode extensions and how I manage them by meowface on Tuesday November 06, 2018 @11:14AM (#18392267)
Ignore what these negative commenters are saying. That's a perfectly good idea for a student project, and I would've loved to have a project like that in my university courses.

But I would agree that if someone uses something else like vim or emacs as their primary editor, they should have the option of writing a plugin for their editor of choice. (As long as they accept that the rest of the class will be taught how to write Atom/VS Code extensions and they'll have to do most of the learning on their own.)

Re:Why I wrote 33 VSCode extensions and how I manage them by gdfasfklshg4 on Wednesday November 07, 2018 @05:35AM (#18398276)
I am coming from this from the angle of having done University level teaching. As an undergrad it seems like there is so much time and so much depth of material. When you are teaching a course you realise that there is actually very limited time and so much to cover. If you choose to dwell a long time on one topic you might well find you don't have time to expose your students to the full range of concepts that they need to be exposed to. In the UK for example you have 3-4 years to take students from finishing school to being ready to do research!
Re:Why I wrote 33 VSCode extensions and how I manage them by gdfasfklshg4 on Tuesday November 06, 2018 @10:19AM (#18391738)
May I ask the degree field?
Re:Why I wrote 33 VSCode extensions and how I manage them by azhenley on Tuesday November 06, 2018 @01:02PM (#18393330)
Computer science for upper-level undergrads or grads.