[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale] [90dw-lcthw] C as a second language
- Subject: [ale] [90dw-lcthw] C as a second language
- From: cfowler at outpostsentinel.com (Chris Fowler)
- Date: Tue, 1 Dec 2015 11:44:54 -0500 (EST)
- In-reply-to: <[email protected]>
- References: <CACv9p5q7mFCoXeOcLr1GuYMw4NOLntt7pYwzmEtVeoLVDKLHwA@mail.gmail.com> <[email protected]> <[email protected]> <CAAU2BpaHHPMNtXgtaEA8pqhp-DpdXiFazGg6htaC73PA=djtHA@mail.gmail.com> <[email protected]>
> From: "DJ-Pfulio" <djpfulio at jdpfu.com>
> To: ale at ale.org
> Sent: Friday, November 27, 2015 4:36:51 PM
> Subject: Re: [ale] [90dw-lcthw] C as a second language
> And that was the common advice from 1960-1995.
> Since then, we've learned that students don't stick with languages long enough
> if there isn't nearly immediate feedback and the ability to create useful
> programs.
I don't think this has anything to do with new students. I tried to learn every language I could when I was younger, but the ones that stuck were the ones where I needed to use them as a tool.
Perl is an excellent example. Tried the 21 days book back in the 90s. Never stuck and I kept programming in C. I needed a way to hammer our systems, programs, etc so I used Perl as a debugging tool. Make 100,000 connections and look for memory leaks for example. Today, I now write more Perl than I do C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20151201/f6c8d2a5/attachment.html>