What does KDE mean to you?
October 14, 2007
In my ongoing series of asking people to reflect on “what does KDE mean to you?”… taking the standard question of “What does KDE stand for?”asked by people curious about the acronym and twisting it around to make it hopefully a more interesting answer and a bit more introspective.
I was discussing AOP (Aspect Oriented Programming) with my team a while back. Spring AOP to be specific. Comparing it to standard OOP and discussing how to implement using agile development or XP. The buzzword siren started going off and we had to get hosed down in the Managerial Decontamination Stall and were quarantined for risk of infecting others with dangerous levels of tech nonsense. Any time I discuss technology I first always wonder about what problem it’s solving. For example: in the case of J2EE, it solved selling larger servers, expensive application servers, and global consulting services to implement over-engineered and architected platforms.
So to apply these buzzwords, and questions about what KDE’s goal, I ended up with:
Now, I think it’s a good looking imagine and gets the point across pretty well. My only problems:
- It’s too cutesy.
- How many people are going to get the pun. And of those who do, who will actually think it’s clever? (rhetorical, I know)
- It fails the ATT pretty badly. The Adriaan Trauma Test.
I put on a a pair of wire rimmed glasses, armed myself with a Canuxidutch accent, and set a photo a Sebas next to me on the desk (since they’re never separated). Yes, yes this image above fails the ATT. So what to do? Fight fire with more fire. If the deficiencies are a suspicious image and a tagline that may be too technical, let’s turn the amp up “to 11” for Ade:
It’s all about turning passive community members into participants. Get it?!? And it’s brutal – I literally can’t stop giggling at it and thinking of Ade’s reaction.. If this doesn’t have Ade looking like he just bit into a big lemon, I’ve failed twice in this blog. Cheer up Ade!