The link appears to be broken, try: http://www.exemark.com/FORTH/Ting_Laws_of_Computing_v4.pdf

Pretty good, and you can make notes & highlight them too

http://www.projectoberon.com/ has all of the source and the Oberon book

The computer mouse was invented back in the 60s, its hardly modern technology

Doesn't that make the author even more wrong?

Isn't the change mainly due to the iPhone being released? Before that it was a copy of the blackberry look & feel

This is mock German - Google translate is probably taking spitzens parken as peak parking. But it is probably a refernce to blinkenlights https://en.wikipedia.org/wiki/Blinkenlights

I think it would help with clarity - too much nesting in a function can mean it's doing too much and might need splitting into several functions

One place where nesting makes things difficult is in error handling.

If at each potential error point you best one level, you quickly find yourself deeply nested.

I find the pattern of exiting early and having the “happy path” running to the end of the scope to make it much easier to comprehend a function (I’m sure there’s a term for this coding style but I can’t find the name of it at the moment).

I also find myself doing a similar thing in loops - 'continue'ing early instead of wrapping everything in conditionals.

  for n in [i for i in range(100) if i%2 == 0]:
    print n

Will work (if a bit repetitive looking)

It's not just repetitive; this particular example actually creates a list before starting the external loop -- imagine it with range(100000000) or something. It is better if you replace [] with (), which creates a generator.

`range()` also takes an optional `step` argument which would help here.