December 31st, 2018

(no subject)

Here’s an extract from Richard Stallman’s site that reminds of how people used to talk in the twentieth century:

How to learn programming

First, read a textbook about programming in some language, then manuals for several programming languages including Lisp. If this makes natural intuitive sense to you, that indicates your mind is well-adapted towards programming.

If they don't make intuitive sense to you, I suggest you do something other than programming. You might be able to do programming to some degree with a struggle, but if you find it a struggle you won't be very good at it. What's the point of programming if it is a struggle instead of a fascination?

After that, you need to read the source code of real programs (or parts of them) and figure out what they do. Then start writing changes in them, to add features, or fix bugs if you can find out about specific bugs to fix. Ask some good programmers who are familiar with the code of those programs to read and critique your changes.

If you fix a bug in a free program that people are developing, the developers are likely to be glad to get fixes from you and will tell you the way to write them to make them good to install. Look at their TODO list for features you would like to implement. You will find it is a great satisfaction when the developers incorporate your changes.

Do this over and over and you will become good at developing software.


Even if this is utter bullcrap, I miss this harsh no-nonsense tone, which has become so rare in contemporary online discussions.

(no subject)

Heard that Crockford published a new book on JavaScript. Went to Amazon to check out the contents and saw this:



Gosh, how I hate this apologetic rhetoric!

(no subject)

Substack’s demos are always fun to watch. He managed to sneak some WebAudio and WebGL into this one (that was about a completely different topic):