Compilation is a form of boredom ;-)
Part of the problem, though, is tools. A lot of things are built for resource use minimization. That made sense 20 years ago, but now I have 8 GB of RAM and 4 fast cores on my desktop, and most of that capacity just sits idle. As far as I'm concerned, if I'm typing and the compiler isn't already running then it's missing an opportunity.
This not a good use of my time, and I hate seeing that console, and I feel bad for being on HN when I could be productive.
./data_mining_job && growlnotify -m "Success!" || growlnotify -m "Failure :-("
(season with while, read and grep to taste)Unit tests would ensure stupidity was not a possibility, and regressions could be tracked. Too late for that, unfortunately.
So I watch.
growlnotify -m "Success! "
(the space tells bash to treat the exclamation point as text) growlnotify -m "$(echo Great\! Success\!)" sub escape {
my $arg = shift;
$arg =~ s/([^a-zA-Z0-9_])/\\$1/g;
return $arg;
}