Let it speak: when code should speak for itself - but it does not

Mon, 01 Jan 0001 00:00:00 +0000

I’m writing a book about how to write Bash code, and how to write it well.

That book is all about the little things that I would have liked to know when I started putting together my first scripts, contraptions that did what they had to do, but were not pleasant to look to (well, not too much).

One of those contraptions has made it to these days, buried deep down into one of my oldest backups, and I found it while spelunking in search for examples of what not to do in a script.

Expressive Code on Lost in IT | Kromg

Let it speak: when code should speak for itself - but it does not