About political correctness …

Martin Krafft reports in his blog posting about “Linux for visually-impaired (developers)”, a presentation made by a blind Debian Developer at the LCA:
So when I write about Jason’s presentation and how great it was, I want to highlight how it’s a greater achievement for him than it would be for me, because he is blind and I am not. I don’t mean to single him out or put him on the spot. I am simply impressed, very impressed. And being who I am, I’d like to say so. Thanks, Jason.
Before that comes half a posting worth of excuses, about being impressed when members of minorities achieve anything (his example where women in Debian’s development). His reason: “[Because] when I utter such a comment, it might still greatly annoy someone or yield vicious returns.” Sadly, after going a long way, he doesn’t make the — in my eyes — most important connection: Why does his statement offend? To explore that, let us compare the statements “I was impressed by you presentation” and “I was impressed by your presentation, because you’re blind”. The important question is now, why are we blind people doing great presentations more impressing than people with working eyes doing a great presentation? My personal answer isn’t so great: “because I didn’t expect it.” No wonder people get offended if you I tell’em to their face that I’m impressed with his achievements, because I wouldn’t have expected it. Ouch! I think I still have to work on (against) my prejudices. Observe yourself the next time you’re impressed, can you hear your thinking? Update:Martin has updated his posting with an answer. The most interesting part for me is probably this transcribed quote from Jason:
I want my work to be judged by its merit and not by who I am.
For me, this reflects the fundamental problem with our prejudices.

dasZ.at

dasZ.at - the people behind ZBox.
dasZ.at Logo

Downloads

The lateset download will be available here - soon

Lastet blog

In our blog we talk about the latest developments around our tool ZBox.
>> Blog

Latest blog entries
>> Reference project: Implementing WordPress-based Website

Based on the reference design provided by Sabine herself, we implemented the zartbitter Website. The site is powered by the PHP-based WordPress blog and CMS engine, some additional plugins and a bit of yarn to hold it all together.


>> Setting a permanent search_path, the Right Way

Others recommend setting the search_path in the postgresql.conf. Current versions of PostgreSQL can set the search_path permanently on a per-database basis without having to touch system configuration files


>> Porting Puppet to Windows

In the course of the PuppetCamp Europe, I met with many people I only knew from IRC and email and it was a great time with interesting and inspiring discussions.

Today I want to write about the work I’m currently commisioned for by puppetlabs, porting puppet to Microsoft Windows.


>> Puppetcamp Europe 2010

I’m going to Puppetcamp Europe 2010!


>> Using gendarme with Code Contracts from .NET 4.0

When using gendarme on post-processed assemblies with code contracts and /throwonfailure set, a few things have to be ignored. Put the following lines into your ignore file (for example gendarmeignore.txt) and use it with –ignore on the command line.


>> Microsoft cannot decode Base64: News at 11!

Arthur has found a really nasty bug in Microsoft’s streaming Base64 decoder as used in the WCF: Connect Bug#541494


>> Kolab Connector binaries uploaded

Arthur moved on with programming and testing. Now we uploaded the first packages, which now contain the basic calendar and contacts synchronisation. The plugins already are able to synchronize our personal data.


>> Kolab Sync for Android and Outlook: Developer Preview

We are proud to announce the first developer preview for Kolab sync clients for both Android and Outlook. Both are licensed under the GPLv3.


>> Visual Studio 2008 Debugger

I didn’t know that: the VS2008 debugger has many bugs. Specifically, if you have a solution with multiple websites, debugging doesn’t work!

Symptom: Upon reaching a breakpoint, StepOver/Into do not work, but resume execution. This makes the debugger pretty pointless.


>> Building a simple MSBuild Task

On the “Using Studio’s “Custom Tool” in MSBuild” question, I was prompted to share the code. Here is a stripped down skeleton where I removed the actual calls to the custom tool. Since it is open source I didn’t really need to access the Visual Studio’s registry keys.