Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: markspace Newsgroups: comp.lang.java.programmer Subject: Re: Teaching Java, teaching what? Date: Wed, 11 Dec 2013 17:57:34 -0800 Organization: A noiseless patient Spider Lines: 29 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Thu, 12 Dec 2013 01:57:37 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="9358cda03e1e0dfd3c4b757daa608707"; logging-data="713"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+25Hbr5htCSvXZz1EPgaE/NqcKAsPLyTQ=" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 In-Reply-To: Cancel-Lock: sha1:yu+TLjoFFf0JPrfc92y9s0ullYc= Xref: csiph.com comp.lang.java.programmer:26851 On 12/11/2013 3:36 PM, Stefan Ram wrote: > Why students attend, I can only guess! The save guess would > be: »to learn Java«. They range from college students of > computer science, via professional programmers (but in other > languages) to hobbyists. I think is is too broad of a range. I think you should decide whether you want to cater to hobbyists or professionals. (You could even split your class into two, one for each.) The professional class should assume a knowledge of algorithms and programming methodology. The hobbyist course should assume neither. Trying to split the middle ground isn't going to serve either group. > Actually, I like this, because it gives students a reason to > learn about interfaces and spares them from artificial > examples, such as I think this is fine, as long as you are leading up to it. I offered the idea of templates because I was concerned that you might be trying to fit in Swing before it was really needed or useful. As an example of inheritance, interfaces and aggregation, it's great, as long as the students are ready for it. I'm still concerned that you're introducing multi-threading too early, but I'll let you address that as well.