Personally, I find code that is clean,
straightforward, obvious to be
beautiful. The clever stuff usually strikes an odd note, not a good
one.
--lm
I am not a programmer. Almost four decades ago, my first computer was a
TRS80 Model 1 with 16KB RAM. I spent one month disassembling and stepping
through the Z80 code for the resident Microsoft BASIC interpreter. The
entire thing fit in a 12KB PROM so it was originally written in assembly
and tightly optimized. It was fascinating and extremely instructive. All
these years later, I could probably still slap together a Z80 program if I
needed to.
Anyway, I reached one point in the assembly code that I simply could not
understand. It seemed like a mistake, and I went through it again and
again until I finally realized what it was doing. There was a branch/loop
that jumped to the middle of a multi-byte machine instruction, so that
branch had to be disassembled and stepped separately until it "synced" up
with the other branch again. Maybe this is standard practice in
programming (I don't know) but at the time I thought, what kind of evil
genius devised this to save a few bytes of memory?
--corey