Re: Tight programming exercise, using bad programming practices

new topic     » goto parent     » topic index » view thread      » older message » newer message

The bad practices shown, are the lack of indention, meaningful variable names, comments. Multiple statements on a line. Thats all I hope ;)
Thats the approach I would have needed to use on my first computer, a 1 MHz Sinclair ZX-81 with 768 bytes of ram. Ah, the good old days.. :)
I though the question was fairly evil to ask of a non-programmer, coming up with the nested loop I mean. But I did want to show him the way it should not be done too.
By looking at a task and coming up with the algo, we have to analize what our brains are actually doing and then put that into code.
The improvements suggested are more examples of that.
Not everyone has the talent mentioned above, so regardless of how easy Euphoria might be, we can't all be programmers.
Thanks guys

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu