Arguments – when the loser is the winner

In a recent TED-Talk (TEDx ColbyCollege, Feb. 2013, Daniel H. Cohen: For argument’s sake, see embedded video below) the philosopher Daniel H. Cohen asks an interesting question: How do we approach arguments?

I’m not talking here about arguments about ordinary tasks, like who is taking out the trash or other mundane things, but about intellectual, academic and stimulating arguments. That is, arguments that require thinking, domain knowledge and intellectual wits. Although he probably thought of it as mostly applying to philosophical arguments and debates (he is a philosopher after all), I believe the ramifications of his observations are much broader than just the domain of philosophy.

Continue reading

Accessing the bash history with arrow keys

After saving the bash history appropriately (as described in the previous post Bash history – how to get the most out of it) you will also want to make sure that working with the history during the session is as easy as pie. For that you will have to adjust the .inputrc file.

Traditionally the terminal/console would emulate all kinds of behaviors depending on your historical terminal access to the computer/mainframe. This unfortunately led to a combinatoric explosion of possible key events and configurations, which makes the successful configuration of the .inputrc rather tedious and annoying.

All I wanted is to use the arrow keys as well as page up and page down, home and end to navigate the commands and the history.

The bash can do that, no doubt, several decades of programming knowledge have been distilled in it, but making it behave according to my needs, well, that was a matter of patience.

The .inputrc-file contains all the key-stroke specific information to make sure the bash behaves as you want it to. Unfortunately, the syntax of the the key-stroke pattern is completely brain-dead. This is why I’m trying to reproduce here as many of the keys as possible, just so that I don’t have to go on another Internet odyssey to find them all.

Continue reading

Bash history – how to get the most out of it

One of the major annoyances when moving to a new system is to make everything as comfortable as on the old one. The major work horse for many Linux programmers and system administrators is of course the shell – in particular the bash. While being extremely useful, I always need quite some time until I have it working just right, so that it doesn’t stand in the way of doing productive work. No Linux system I have installed so far had (for me) satisfactory default values of the bash resource file .bashrc.

As I am relying heavily on the bash, in particular on the history of commands typed, this is usually the first thing to adjust. bash has quite some options how to fine-tune the history:

HISTCONTROL:
By specifying one or more parameters you can define how the commands will be entered into the history file.

Continue reading

Heuristos – what does it mean?

The probably most well known expression of the ancient Greeks is the one of Archimedes running through the streets of Syracuse shouting out Heureka (εὕρηκα heúrēka) after he took a bath and suddenly understood that the volume of water displaced must be equal to the volume of the part of his body he had submerged.

Heureka roughly translates to “I have found (it)“. However, a fuller translation, closer to the original meaning, would be: “I am in a state of having found it“.

The infinitive of this ancient Greek verb is called heuriskein or in the first person heurísko (εὑρίσκω): I discover or I find.

The word heuristic comes also from heuriskein, but in an indirect way, namely from the derived adjective heureteos (roughly: discovered or found).

The superlative form of it is called “heuristos“: most discovered or found.

This word has found its way to the ancient Romans who called it heuristicus in Latin. Many modern languages like English, German, French, Spanish etc. imported this word from Latin.

Some dictionary definitions of the word heuristic and its original Greek form heuristos, in its modern use, are:

  • constituting an educational method in which learning takes place through discoveries that result from investigations made by the student.
  • encouraging a person to learn, discover, or solve problems on his or her own, as by experimenting, evaluating possible answers or solutions, or by trial and error
  • pertaining to or based on experimentation, evaluation, or trial-and-error methods.

In my interpretation I use this blog to report on things, which I have found through experimentation, trial and error and other methods mostly involving some kind of mental or physical hard work.

Hence, heuristos – the essence of my dabbling through this world.

Links:
Dictionary definition of “heuristic”
Wikipedia: Eureka Archimedes
Discussion on the etymology of the word heuristic

 

First post – what this is all about

After many years of refusing to have a public blog, or any online presence whatsoever, I decided finally to create my personal space. Why? Probably because it is so passé: being a blogger is not hip any more, blogging has worn out. Paradoxically, this has a certain appeal. I do it simply because I want to have my own easily manageable persistent storage of useful code snippets, essays, ideas and other stuff, which I can access from any computer. If it’s on my blog, then I know I will find it. If it’s somewhere on my many hard drives … good luck finding it again.
This blog is personal. If any of this information is interesting for you, all the better. But I write it primarily for myself, as my creative outlet. Thus there is no theme or main topic about which I “blog”. I just write down thoughts or anything else relevant to my work or hobbies. In fact, really anything that is interesting or appealing to me. Don’t expect me to write only about a certain clearly defined topic. Won’t happen. I reserve the right to keep the freedom to express myself freely about various domains of interest.