The Butt Ugly Weblog

One thing that constantly pops up in copyright discussions is that "people must be paid for their work." While I appreciate the sentiment, this is wrong and harmful. The correct form should be "People must be able to ask for money for the work they perform. It must then be equally possible for the employer to say no."

Now, this sounds awfully freemarketlibertarian, yes. However, that's not where I'm aiming at. I recently came across a discussion (in Finnish) where a teacher voices a strong concern about the availability of teaching material devaluing the work of teachers - when material is available for free online, why should the school pay the teacher for his/her time to make material? I know a lot of people - especially computer savvy people who are familiar with Open Source - like to laugh at this, but in fact I think this is a real fear which shouldn't really be dismissed like that.

The underlying problem is quite well defined by Cory Doctorow in this piece on the Guardian: "Just because something has value doesn't mean it has a price." (Seriously, read it. Understand it. Become a better person by internalizing it, even if you disagreed with it.)

The feelings that teachers are going through are nothing new - in fact, the almost exact same fears were voiced when Richard Stallman started working on free software back in 19omnomnom. "Who will pay for my time if I create something which is free?" "Why would I spend hours on something I'm not paid to do?" "By hoarding information I become important and cannot be fired." The answer to all of these questions turned out to be "It'll be okay." Now, I don't know enough about teaching, but I can answer how it all turned out in my profession:

"Who will pay for my time if I create something which is free?"

Everyone. Many people who contribute to projects in Apache or Github or Linux or any of the zillions of other open and free source projects are either hard-core programmers or will be shortly. There's nothing that improves your skill like public review, and good Github or Stack Overflow account is a sure-fire way to get yourself hired.

Also, since the freely available software is so good these days, many companies are actively paying their programmers to participate in these projects, because they realize one truth:

If I put in an hour of my time, and 99 other people do the same, each of us gets 100 hours done for the price of one hour.

"Why would I spend hours on something I'm not paid to do?"

Ward Cunningham, the man who invented wikis, told me once (paraphrasing from memory): "I was showing my wiki to a lot of people. Everyone, who asked 'why should I contribute, what's in in for me' didn't get it. It's not about 'me'. It's about 'us'. The right question is 'what's in it for us'."

Turns out people have a lot of motivations to distribute their work freely. Some people want comments from colleagues. Some people use it as a way of advanced backup. Some people just think it's easier to manage in public (because over the years, we programmers have honed some of our tools to work much better on the internet than on our desktops). For some, it's an ideology. Some people want to pay back for all the stuff they've received. For some, it's just a hobby and they like the interaction with others. Some aspire for fame and greatness. Many reasons, but all benefit the same.

"By hoarding information I become important and cannot be fired."

This is the fear, isn't it. Well, turns out that this is rarely true. If you become a liability to your employer, you will go, no matter what you know. 'cos even if you can't, your boss can look further ahead than you, and she/he should be able to see what is good for the company in the long run. Maybe they'll hurt for a few months after you go, but really, nobody is irreplaceable.

Sharing won't make it easier for you keep your job either. But, it does protect you in two, very important ways: first, if you do a good job, all of it will be visible. And that means that getting a new job is a lot easier - if you're good and can show the code, you're probably hired the next day. Second, you get to keep the stuff you worked on. In many companies, once you go, you lose access to all the work you did and have to replicate many things in the next place. Not so with open source - anything you contributed is available there: you can keep working on it, apply what you learned at the company, and continue to do so in the next place.

Now, especially when it comes to education, I strongly believe that openness is the way to go. Teaching and research are two sides of the same coin. We wouldn't be where we are now if the alchemists hadn't put aside their secret tomes and agreed to share their research with each other. Newton said: "If I have seen further it is by standing on the shoulders of giants." If there's a group of people who should really, really appreciate this, it's teachers.

Wow. This blog just turned ten. OK, so it's entering puberty a bit early, being quiet and pouty (and on occasion, eclectic), but still - ten years. Not too bad.

A lot of the early entries would now be material for Twitter or Facebook, but I guess that's true for most of us oldtime bloggers. Microentries go to microblogs, and the old blog is now a place for longer thoughts.

But that is fine and as it should be. Here's to another ten years!

Upgrade my Macbook Pro to OSX 10.8 (aka Mountain Lion) recently. Frankly, it's not much of an upgrade from 10.6, though I like the new login screen. I'm having trouble adjusting to some features, like the disappearing scroll bars (mostly because the horizontal scroll bar always appears on top of the item I actually want to click, causing endless confusion and minor enragement).

I also think Finder was better in 10.6, mostly because I used the "latest changed files" feature heavily and it seems gone in 10.8... Oh well. Also, for someone who makes a living writing Java code, the hassle of getting everything reinstalled is a pain.

The good thing however (and the major reason why I wanted to upgrade) is that the Bluetooth stack seems a lot more stable than it was in 10.6. It hasn't caused a major freeze even once so far, and unlike the old one, it no longer wants to put my BH-905i headphones into headset mode, but accepts that A2DP is what I mostly want from my headphones, not the crappy headset profile...

However, I did have some issues with the sound quality: terrible popping noise; not loud enough to make sound unbearable, but just enough to annoy me all the time. So after some googling I found a magical command line setting you can use:

defaults write com.apple.BluetoothAudioAgent "Apple Bitpool Min (editable)" 53

Restart music player and Bluetooth (turn it off and on again) and you should be set.