Re: NQC programming guide

"Chris Phillips" <[email protected]> Thu, 7 Dec 2006 08:08:49 GMT
Newsgroups gmane.comp.hardware.lego.robotics
Organization None
Message-ID <[email protected]>
In lugnet.robotics, steve <[email protected]> wrote:
> linmix wrote:
>
>> As for which programming language to learn, I'm sure C (or C related) is
>> a perfect choice. For one, as you say NQC is C based. Secondly, learning
>> C should give me a better insight in some of  the things that happen in
>> my Linux machine. Java sounds interesting because it is used for quite a
>> few cross platform applications and because of lejos, but let's take
>> this a step at a time. Once I know my way around NQC I can always decide
>> to learn something else.
>
> Yep - that's definitely the case.
>
> Once you have learned one C-like language (and I'd describe JAVA, NQC,
> C++, Python, Pascal, JavaScript, PHP as 'sufficiently C-like') - it's
> quite easy to learn another.  I needed to learn PHP for a project I
> had planned - I bought the "Sam's PHP in 24 hours" book and picked
> up enough PHP in an hour to write a 3,000 line web-based application
> without needing to refer back to the book even once!
>
> The most important thing about learning to program is that you have
> to write LOTS AND LOTS AND LOTS of programs!  It doesn't matter what
> they do - drive robots, balance your checkbook, play Tetris...just
> so long as you write lots and lots of code in whatever language you
> choose.  There is absolutely no substitute for practice.
>
> I've been programming since the mid 1970's - and still, when I look
> back on a program I wrote a couple of years ago, I say to myself "Wow!
> I was really that bad back then!  I can do SO much better now!".

This is probably the best advice I have *ever* seen given to someone who is just
starting out trying to learn how to program.

Spotlighted!!