Recently after listening to an episode of Hanselminutes it occurred to me that a measure of whether or not you’re a Unix geek is how often you see this kind of thing:
In short, if you don’t see it at all or have never noticed strange characters at the start of your text file, you’re likely to reply “to hear the sea?” to the question “what’s your favourite shell?”. In that case, do yourself a favour, go under the bonnet a little and learn about byte order marks (it’s all about enrichment).
Further, if it interests you enough, you may find yourself checking out the hex equivalent of your text file–how you go about that is very telling. Hanselman belied his roots by doing this:
debug Foo.txt (and then enter ‘d’)
On the other hand, having a rather more unixy background, I would do the following:
To be honest,
debug wouldn’t have occurred to me – if I had not had cygwin installed, I would probably have ended up downloading a (free/share-ware) editor that provides such a feature.
My take on this issue may not apply to everyone, but everytime some little app decides to contribute to the “system tray balloon tooltip” party I feel obliged to click on the damn thing just to get rid of it. In a world where there is way too much clicking to start with, I’d rather not care.
Here’s how to suppress balloon tooltips:
You may ask: “Will a
dword:00000001 get them to come back again?”. I tried–doesn’t seem to work. Evidently the presence of the entry suppresses them. Go figure.
Recently someone raised what appears to be a contentious issue, that is, is it acceptable to “design for test”. Personally, initially a proponent of the “don’t-prop-your-code-up-for-the-sake-of-tests” department, I am becoming more inclined to agree with the author of said posting. Being able to completely isolate an object for the purposes of testing is a beautiful thing, but sadly it sometimes requires a whole lot of P.T. in the form of dependency injection frameworks and the like–we’re currently feeling this pain on a big project we’re working on.