09 December, 2013

Psychopatic encounter

I just had the most curious encounter in a bar. Well, not entirely new - I've met my share of weirdo's over the years, but it has been a while. My problem seems to be that I'm too nice: I smile and nod at people that ramble and complain to me about life, the universe and everything like I enjoy their company. And what can I do? I LIKE being a nice person, it matters to me. Anyway, on to the story and its consequences.

Food in Nürnberg

Around 8 PM I went to the Bar & Grill California for dinner. Looking around for a place to sit, I smiled at a few folk looking back. As soon as I sat down, one of them came to me and asked if I didn't want to drink a beer with him and have a conversation. I didn't really know what to say, other than disappoint him partially by explaining I don't really drink beer. I would eat and drink something, however. He didn't mind and joined.

The conversation started curious: he shared that he had just kicked at the mirror of a police car and asked what I thought of that. I replied that, besides not liking violence in general, I saw little point in doing that. He pointed out that "cops are thieves, just like everybody else". "Well", I said, "some are, perhaps - rotten eggs can be found anywhere. But by an large, society needs a decent police force. And still, how does kicking a mirror help?". He explained that indeed, police is good, but "they have to be kept under control". Somehow, kicking mirrors helped with that, I didn't really get his argument here (if there was one). Besides, he didn't know what else to do: he had been mistreated by cops, he told me. He explained me he had pressed charges but it was "all covered up". Did he go to a lawyer? No, "they are all like puppies. Afraid of the police." I didn't really agree, but the conversation (or rather, he) became hard to follow.

What do you do for a living?

I decided to inquire into what he did for a job. After a few failed attempts he told me he was a doctor, or at least, learning to be one. Most physicians I know are rather less rambling so I inquired further. It turned out that, indeed, 'normal' physicians are actually trying to kill us. Murderers, he said. Especially psychiatrists. I tried to pursue the subject, instead the discussion turned to politics. He said it's bad in Germany. All politics is corrupted, as bad as in the US. I shared my conviction that while there are corrupt politicians for sure, at least in the Netherlands I'm convinced the vast majority of elected representatives honestly wants to do the right thing. He noted, surprisingly on-topic, that they just don't know what they're doing - something I can't disagree with entirely. After all, the world is a complicated place and honestly, most politicians seem under-educated especially in the area of science. I don't think this argument landed, however, he had turned back to the medical world.

He started talking about evil psychiatrists and mind control, and I decided to tell him I'm a psychologist. He moved a bit away from me, telling me he didn't trust psychologists. "They always blame you for everything!" he said. I answered: "Well, I do believe we are responsible for what we do in the world...". He shared that the medicine you're given is to keep you under control. Knowing the side effects of the medical treatments available to psychiatry (especially anti-psychotics) I couldn't really disagree that much. Meanwhile, he seemed to decide he could trust me, at least for now.

Berlin and the New World Order

He switched subjects again, asking where I came from and I told him I live in Berlin but I was Dutch. He was intrigued. "A while ago", he explained, "I met a very interesting guy. He lives in Berlin, but he is family of the Spanish King. Actually, he SHOULD BE the Spanish king, but..." I didn't really understand the reasons behind this, however, he suggested we (him and me?) should do something about this, put him back on his throne.

Before we could dive in details of this revolution, he moved closer to me, so nobody could hear: "Do you support the New World Order?" I told him I had heard the term but didn't know what it meant. He explained: "It will happen, like, 200 years from now. The human population will be reduced to about the size of Berlin". I asked what would happen to all the other people and he told me people would get injections with feminism (yeah, he really said that, I asked him to repeat it twice) and that would reduce the number of children we had. It had already started, that's why the population in Germany was getting smaller. I told him I thought it was scary and I would be against it. He noted he was a bit torn on the subject: on one hand, killing people is bad, but it would be good for the planet, the environment. Well, yes, it would, I suppose. When asked about how it had already started, he explained: "It is done by their leaders". Who? "Osama Bin Laden, others... Obamasama" (he made a bit of a word jumble there). I noted that Osama was dead but that didn't seem to be a problem: "He is the anti-christ!". We made a short detour to religion - he strongly believed in God, I couldn't figure out which one, although he didn't seem impressed with Allah and it wasn't Santa either. He did note that Jesus was a "servant of God, he was not crucified, they tried but you can't kill a servant of God".

At this point, I decided I really would prefer a quiet dinner, and told him that my food was coming and I'd like to eat that alone, but it was a nice conversation. He agreed, we shook hands - and he left. And I was proud of myself for having ended it in a friendly but firm manner... I am learning, too!

Psychotic? Oh yes.

I've had enough contact with people going through a psychotic episode that I can tell he is. The above 'report' is omitting at least half the rambling and hard to follow conversation (if you can call it that): conspiracy after conspiracy is thrown over the table, often clearly connected to things mentioned earlier. For example, the world population will be reduced to the size of Berlin, because - I just mentioned I live there. Once you notice it, it becomes hard to miss. There is logic - but often twisted and coming from certain (utterly insane) axioms. Overall, there's a lot of free association going on - I guess a psychosis would be awesome in a brain storming session. If you could only keep them on topic at least a little.

It is a REAL disease, harming those who have it

Unfortunately, a psychosis gets worse as these diseases are really damaging to the brain, essentially turning chronic if not treated. Compare it to a untreated wound - it isn't going to get any better if you let it fester. And I know that, while not very pleasant, there are decent medications and treatments out there that can really help. Unfortunately, I also know that as long as somebody is not a danger to him/herself or others, and sufficiently lucid to refuse any help (and the paranoia obviously doesn't help), there is little a doctor can do. Judges often simply lack the experience and knowledge to be willing to lock somebody up who doesn't do any harm and can still reasonably convincingly claim to be just fine. Despite believing Elvis is still alive, Aliens do anal probing and Jesus will walk again, soon. Worse, if they don't have friends or family pushing them to a doctor, chances are that they won't even be on the radar anywhere.

I've heard stories and cases like these recently, in Berlin but also in the Netherlands. And it often goes unnoticed. Most people just think him or her to be 'an odd duck' and there's often drugs involved which can be blamed. This good men was convinced beer helped him, taking his inhibitions away. Yes, it does, but I don't think that that is a good thing... At least, beer isn't as bad as the stuff some patients 'self-medicate' with. The thing is: this is a real disease. As real as cancer or a broken leg. It doesn't SEEM like that as you don't see it on the outside, but having your brain out of whack is seriously bad. Not only for them but, indeed, potentially for others too. After all, if you truly believe the police are the agents of the apocalypse and you get your hands on a guy, doesn't it make perfect sense to shoot a few? Exactly.

And then?

Our modern society seems to, on one hand, increase stress and pressure so more people suffer from these (and other) psychological disorders, yet the decaying social fabric means they get less and less social and medical support. And this is just the worst and most obvious side of it - what about all these people who quietly suffer from anxiety disorders, depression? Really, feeling like killing yourself is NOT healthy. There is something wrong and while indeed it can't be cured by a simple pill, there ARE things which can be done.

As society, we need to be more aware of these issues. Only thing I can do here is urge you to not leave people around you alone if they start to become paranoid and ramble like this: this is most likely caused by a real, tangible, curable medical condition, not an actual alien obduction, religious epiphany or government conspiracy. If a friend of you breaks a leg, you do visit them, help them, don't you? Do the same when they develop a psychosis, please...

07 December, 2013

Summit, Con, Release...

The last weeks before my holiday have been quite crazy for me. SUSECon, openSUSE Summit and of course the openSUSE 13.1 release. Meanwhile, the openSUSE Board Elections have started... I decided to really try and stay away from things for two weeks. I'm not particularly good at that and I did a few thingies but I managed not too shoddy. Saw a museum, did pick up running again, watched some movies...

Now, back to SUSECon, the Summit and the release!

SUSECon,oS Summit

First things first, SUSECon and the openSUSE Summit were awesome. It is always wonderful how much energy these events give - so many enthusiastic people, ideas, plans...



On the press side during SUSECon, I kept myself busy with talking to 7 of the journalists, doing and arranging interviews or finding answers to their questions about openSUSE. And with Robert Schweikert I presented a session (twice) about the collaboration between SUSE and openSUSE. ITWire reported on this talk. We ran a booth at SUSECon as well and it was, as always, great to talk to people there.

On Wednesday was a Pirate Party, Thursday a visit to the Epcot park. I'm not a huge fan of such parks but it was entertaining enough to get food there... And I had great company!



At the Summit I presented two sessions, one about handling a booth and one about building local communities. In both cases, there was a lot of awesome feedback from the room and at the Orlando airport and further during the trip back I worked the suggestions in the presentations for further sharing. Thanks! I also really appreciated the private conversations about these topics which took place later on.



But the most important thing, for me, was meeting old friends again. Andi, Drew, the openSUSE Forms guys, the Greek delegation and many more. And bumping into new people like Navid and Christopher, two guys who run a media production company and want to help out openSUSE with web things. That's where the inspiring conversations happen. There were discussions about how to proceed with the Summit, how to handle community building in the Americas but also the great town hall meeting where I presented the 'Karmafication' idea for our infrastructure. This is something I might blog about later.

After the openSUSE Summit was over, Alex, Stella, Ludwig and myself went for a beach trip, video below. It was fun - although we drove an order of magnitude longer than that we actually spend on the beach ;-)



The release

Then the release, on the day I landed back from the US of A (and yes, they lost my luggage, luckily it is back). I think it went great, and seeing the response from the press I think others agree.

Now, we're debating changes to our development process on the mailing lists. Let's see how that goes!

11 November, 2013

Skype on openSUSE 13.1


Yes, openSUSE 13.1 isn't out yet, but people who've installed RC1 and upgraded via the repositories are very close... So let's call that 13.1_almost, for now. And 13.1_almost has a bit of an issue if you are a Skype user. When starting up Skype you might very well be greated with a very loud and unpleasant sound coming out of the speakers.

Solve it

This is fortunately not hard to solve: start skype from a commandline with the following command:
PULSE_LATENCY_MSEC=60 skype

See this blog for some background information. I am hoping we can get an update in to fix this, but for now - if you suffer from it, use this as a work-around.

Make it permanent

You can change the menu item for Skype so you don't have to start it from the command line, as follows:
Left-click the menu button and choose  "Edit Applications..."









Then, locate the Skype application and add the "PULSE_LATENCY_MSEC=60" in front of the command.



















Save, done. Easy-peasy, yes?

I'm going to be at SUSECon this week, ending in the awesomeness that will be the openSUSE Summit! If you're there, surprise-hug me if you can ;-)


Have a lot of fun!
(and think of the geekos) 

31 October, 2013

Living in Berlin? The Geeko comes to you!

Geeko is coming to Berlin! Javier Llorente arrived at my place and he is organizing an 'openSUSE meetup' this Saturday at C-Base, Berlin's most awesome Geek Spot. It starts around 17:00 and lasts until about 20:00 - but who knows what else will happen.

We will give an overview of what's new and then it is time for some testing and playing with the new release. We will bring some USB sticks with openSUSE 13.1 RC2, so if you bring a laptop to test it on that'd be awesome!

Even without laptops you're very much welcome - a bunch of Geekos meeting always results in fun, no worries about that. Anybody is welcome, even if you happen to run another distribution...

See you there!

EDIT: yeah, forgot to note that it is SATURDAY, not TODAY :(

We're sorry!!!!!!

25 September, 2013

Communication around Frameworks 5

A while ago I asked help in communicating Frameworks 5 and our releases. I'd like to acknowledge the awesomeness of Howard Chan who stepped forward to first write an article about our evolving release plans and now help publish an overview of what Frameworks 5 brings to Qt developers all around the world.

Howard is 15 and active in the Kubuntu community too. He is also participant in the season of KDE - a typical KDE contributor who's all over the place, if you ask me. And has already stopped listening to my suggestions and has figured out what he wants to write next ;-)

You're my hero, Howard! Great work and I'm glad you plan on sticking around.

20 September, 2013

Giving constructive feedback

Feedback is often equated to 'yelling'. But it doesn't have to be - feedback is, after all, central to learning. And in Free Software, where learning is a major motivation for many participants, proper feedback is very important.

Max the Brown Tabby and Burt the Grey Kitten: Cat Argument

Many of you have seen how Linus can yell at people and unfortunately, some mistake that for effective communication. It is not. But what DOES constitute effective feedback?

Three Rules

Plenty of books have been written on the subject. To save you the reading effort, I'll summarize the most important lessons here: three rules for how to give constructive feedback.

RULE 1: find the right time and place (or don't do it at all)

Both you and the other person should be in the right place, mentally and physically, for the feedback. For example, don't embarrass a person in front of a crowd. Feedback is best given in private, unless of course it is explicitly asked for in a group. But even then, think about what you say.

And have the right attitude towards whatever has to change: everybody makes mistakes. Constructive feedback should be building up, not breaking down. None of us is born as a super coder, we all had to learn. If you and/or the other person are angry, it will be a shouting match. If there is no way for the other person to improve, why frustrate him or her with feedback?

The time element is crucial as well. Feedback should be timely: giving feedback on an event that took place weeks ago, most likely long forgotten by the subject, offers little value. Be sure you have a certain event or action in mind and can be specific about when, where, who was involved and what the results were.

Rule 2: Describe, don't judge or infer

Most important, constructive feedback has to focus on the facts of behavior in a concrete case. And on its consequences, not on the person and who they are. That sounds easier than it is. It is best to follow this format when giving feedback:
    I Don't Know What We're Yelling About!
  • describe the specific behavior/action/code itself
  • describe how it made YOU feel (emotional feedback) or the effect it has on $SUBJECT (technical)


To focus on behavior use adverbs to describe action, rather than adjectives describing qualities. Help the other person understand the impact their actions have.

Let me give some examples:
  • unhelpful: "You were really an asshole in the meeting today" -> personal and pretty darn judging
  • unhelpful: "You were trying to derail the discussion! -> inferring goals
  • helpful: "When you talked so loudly during the discussion you made me feel really anxious"
  • unhelpful: "Your patch sucks" -> not concrete
  • helpful: "If you write code like $EXAMPLE you will break $DESIRED_BEHAVIOR"
  • unhelpful: "You always forget to add comments to the code!" -> generalization
  • helpful: "Yesterday when you checked in the code for X, you did not add comments in $FILE, so it took me a while to figure out how it did fit in"

This also works with compliments:
  • unhelpful: "You're a great coder!" -> unspecific
  • helpful: "When you commented the code with that high level overview you made it easy to understand the flow of the class"

Negative feedback which is too vague just frustrates: there is nothing to improve. But unspecific positive feedback is not that great either: people frequently doubt your motives ("Is she trying to get something from me?") and it even makes some people feel insecure.

Note that when giving feedback, people have a tendency to emphasize or even exaggerate. Feedback tends to land much harder than you think, even with people who seem impervious to criticism. It's better to bring it softly and remind people later then to lay it on heavy and make them feel inadequate or not appreciated.

Rule 3: Sandwich it


It matters how you introduce the feedback. If you weren't asked for it, note clearly that you'd like to give some feedback. Perhaps this is a bad time - allow the other to point that out and if so, just let it go.

Then, seek for balance. Certainly there are things to improve, but there is always something that was done well. We tend to focus on the negative. To prevent that, 'sandwich' the negative part with positive feedback: start with something that went well, follow with the part that needs improvement, finish with another part that went well or a silver lining. Not only does this help digest the feedback better, it tends to force you to think about it more as well.

If you can, try to give some tips or hints on how to improve. Share how you dealt with this issue in the past, perhaps. Here, too, be as concrete as you can.

After giving the feedback, let the other talk. It is not unlikely that the recipient will act defensive. Don't take that as meaning the message did not land - most people have trouble admitting mistakes when confronted with them, even if they are brought the Right Way™. Let them respond, say you understand - most importantly, don't pile up more 'evidence'. You've done what you can, it is now their responsibility to take it - or not. If you get no response you might want to ask a open question like: "What do you think".

Note that you can give too much feedback. Improving oneself is a lot of hard work - and one can work only on so many things at once! Recognize progress, even when it is slow, and leave room for mistakes. If a colleague tends to make certain typical mistakes you don't always have to point them out. Give him or her time and opportunity to self-correct, silently accept some of the mistakes and space out the feedback a little.

Feedback 101

There's something to receiving feedback, too, of course. Note that following the rules above isn't always easy and sometimes people are frustrated and do yell. Try not to get angry - feedback, any kind, can help you improve. Even if it is not brought to you in a nice way.

Giving and taking constructive feedback is a hugely useful skill to have - it helps you as well as others to learn and get better. And while most of our communication takes place online, these rules apply as much if not more so. Thanking somebody for a patch, starting by commenting on the good side of it, before you hack and slash in on the less-than-great parts, adding concrete ideas for improvements, and finishing with a high-note in proper sandwich style: it can make the difference between getting an improved patch or never hearing from the contributor again.

If you have comments, feel free to share them ;-)

27 August, 2013

Silverstone FT03mini, Intel Haswell and Linux

I'm a hardware geek. Not really into the gadgets, but I like the tech behind workstation-type systems: CPU's (realworldtech is amazing, so is Anandtech), GPU's and so on. Aside from reading it is of course also nice to build something every now and then. So this summer, just after Intel released their new Haswell CPUs, I decided to build a new desktop system around it in a Silverstone FT03 Mini. Goals were to have it as quiet as possible (cooled by a single 140mm fan) and of course have very decent performance.

FT03 Mini

As you might have guessed from the name, the case isn't very big: mini-ITX. And it is a rather unusual design: a standing tower with a single 140mm fan on the bottom and solid aluminum walls. Quite a beauty, if you ask me. A review here.

Specs

I ordered a Core i5 4670 - not a K one as those miss out on some of the new instruction extensions. Yes, that is actually called Product Sabotage. Well, Intel is not a charity and there simply is no competition in the space above the core i3 performance levels so they have to differentiate their products to extract the 'consumer surplus'.

Aside from the CPU, there's a 256GB Samsung 840 Pro SSD (2.5"), 2x 8GB ram and it is all connected to a ASRock Z87E-ITX motherboard. I also have a passively cooled Zotac GeForce GT 640 Zone Edition graphics card, but more on that later.

Cooling

For cooling I used the recommended all-in-one watercooling - a simple Corsair H60. I contemplated going for a H80 (double-thick cooling block) but that would simply be overkill for the platform and make building it all harder. I've replaced the 140mm silverstone fan with a more quiet Noctua (NF-A14 FLX), which, at its lowest speed, is indeed very quiet. The whirring of the water pump is actually the noisiest thing about the case although it is barely audible.
Going to put it together

Power supply

I'll MAKE it fit!
I did do a few unusual things with the case: I took out the HD cage (I only need one 2.5" SSD) and the slimline DVD player cage to make room for a full ATX modular, Platinum-rated, fully passive Seasonic power supply. The SS-400FL2 required some some creativity in attaching it and the bending of a single metal bar to fit it in - and of course, the tiny space gets even more cramped. But it isn't a huge stretch and it seems Silverstone could easily add a screw hole or two to make this officially supported.

Building

The basics were not hard although this case was the smallest I've ever build and I never played around with AIO water cooling. I didn't yet have the power supply so I used an old one I had still lying around - that's the blue thing on the box in the pic ;-)

Put together - first round, with the passive Zotac
I fired the thing up and lo and behold, it all worked fine. I did play around a bit with the cooling and after some burn-in tests I ended up putting the pump on a variable voltage and the fan on a low, continuous one. That leads to most quietness. Not total silence but I'll survive the noise...

Graphics card - u no fit?

Unfortunately I got in trouble after my new power supply arrived: it didn't fit with the video card. The video card has a huge cooling block and its cooling fins are extruding on the back of the card. Unfortunately, that is where the power supply had to be - the price for not opting for the recommended small form factor variation.

Now I'm stuck with a passive Zotac Geforce GT 640 (anybody interested?). Turns out, the integrated graphics in the i5 are plenty fast for what I need and I don't have to fight with proprietary drivers. So for the time being I'll stick with this... When I decide I want to play more modern games than Warcraft III or have a third screen I'll find a solution that's not only silent but also has no fins on the back ;-)

It's busy in there, yes...
No place for the Zotac card.

Bleh, Broadcom

I did also replace the badly supported Broadcom wireless mini-PCI-express card that came with the motherboard with a decent Intel one (Ultimate-N 6300). I couldn't get the broadcom to work under Linux, the Intel card of course worked out of the box. It is a triple band card but unfortunately I still can't get decent speed out of it - more than 50MB/s won't work and I've got a 100MBIT connection so that's a bit sad. The problem might be that I'd like it to use 5ghz and it is near impossible to find decent antennas for that. The antennas that ASrock included seem to be less than perfect. But honestly, I don't understand antenna tech very well... Maybe I do something wrong.

In the end, I'm fairly happy with the setup. The goal of having only one fan cool the entire case did work out and CPU core temperatures hover consistently between 30 (idle) and 50 (under stress),

Haswel and Linux

Getting the system to work with Linux (that'd be openSUSE, of course) was easy-peasy. After my power supply arrived I had to rely on the integrated graphics and for that, upgrading to the latest kernel from kernel.opensuse.org as well as the latest stable Xorg from the X11:Xorg repo made sure it is now all smooth. Boringly little to say, everything works great and the system is butter smooth - something you'd expect from your new work station.