Ge moet weten, ik ben “Gegradueerde in de Toegepaste Communicatie”. Dat zegt U niet veel? Wel, mij ook niet! Ik heb met dat diploma 3 maanden interim bij een Brussels PR-bureau gewerkt. Tijdens de sjieke opening van hotel Le Méridien in Brussel besefte ik dat ik, ondanks dat propere colbert-vestje, niet thuishoorde in de PR. Blijkbaar moest ik de publieke relaties met de etende en drinkende journalisten verzorgen, terwijl ik eigenlijk gewoon stilletjes aan tafel zat en een hapje mee at. Ik heb Toegepaste Communicatie-gewijs ook nog een jaartje als freelance journalist voor “Het Vrije Waasland” gewerkt, maar dat verdiende amper genoeg om tijdens het weekend de dorst te lessen.

Buiten de “professionele communicatie”-sector heb ik evenmin potten gebroken; ik was een paar weken administratief bediende op de commerciële binnendienst van Recticel, een jaartje stafmedewerker bij de MJA en -daar komt de bekentenis- nog tijdens m’n studies ben ik met de zichtbaar succesvolle overbuur bij vrienden en familie gaan leuren met verzekeringen. Van deur tot deur lucht verkopen, ik voelde me precies terug Getuige van Jehovah.

Om maar te zeggen: ik heb in de eerste helft van de jaren ’90 best één en ander geprobeerd op de arbeidsmarkt. Maar m’n werkloosheid in 1994-95, dat was de job die echt het verschil heeft gemaakt. Want tijdens die 15 heerlijke maanden vol verveling en nietsdoenderij heb ik het internet leren kennen, via een gratis inbel-account van de RUG. Zonder die werkloosheid geen fascinatie voor dat vreemde WWW, geen IBO-tewerkstelling bij die PC winkel die ISP wilde zijn en dus geen kleine carrière als webmens.

Nee, als ik ooit terug werkloos zou zijn, laat me dan alsjeblieft rustig van uw belastingen profiteren. Ge kent me, ik zal uw geld wijselijk investeren in kennis-vergaring. Wie weet welke nieuwe microbe ik dan te pakken krijg? Onze economie (en dus uw portemonnee) kan er alleen maar wel bij varen!

Compare that to the way Yammer took off at the company I work for; in less than a months time 800+ colleagues (out of approx. 1500 employees) joined and we’re getting to know new colleagues, discussing more or less work-related topics (1500+ messages) in the open or in multiple interest-specific groups (15 at this moment). Good times!

I don’t know how Yammer is doing in other companies in Belgium (and Europe by extension), but to me is seems that Yammer succeeds where Google Plus is failing; bringing together a group of people (in a more or less “private” environment) that share a common context but who didn’t share a social network before and allowing them to engage and to create engagement.

Google Plus might be neat from a technology & privacy point of view, but it essentially was (and still is, I guess) a “me too” exercise, trying to occupy a market that has already very successfully been taken by Facebook & Twitter. And yes, Yammer does have an API.

Wait, what do I do at work? I try to discover (by experimenting and reading) how web technology can be used and I try to apply that knowledge to help colleagues steer their projects. That’s like … exploring and navigating, no? So as of today I’m Futtta the Web Technology Explorer and Navigator on LinkedIn!

On Thursday, May 12th someone pretty high up in the company hierarchy decided we had to have a web application ready on the 19th. The catch: it had to be able to handle a shitload of traffic in only 2 days time. After consulting with a couple of specialists and reviewing our options, we decided to go for it with our existing web-development partner. Because of available expertise and resources however, we decided to switch from J2EE to .Net and to deploy the application on Microsoft’s “platform as a service” offering, called Azure.

In 5 days time (what weekend was that?), using a shared Google Docs spreadsheet as project hub (for bug-list, todo’s, translation strings and in document IM) the application was developed, tested and hammered upon with a huge load-test and on Wednesday-evening the final version was deployed on Azure.

The most interesting technical tidbits (as designed by a smart and very motivated lead-developer):

• the architecture is based on Azure’s Compute “web role” and “worker role” instances, with the “web role” instances taking care of capturing user data and putting it on a queue and the “worker role” instances asynchronously picking up, processing and storing the data
• data relevant for the “web role” instances is available in distributed cache
• processed data is stored in Azure Storage’s blobs & tables (i.e. not in Azure SQL)
• static files are offloaded to Azure’s CDN

The application handled a huge amount of traffic the first two days. Due to circumstances the load was especially high on Thursday morning (with over 800 HTTP-requests/second), but performance and availability remained perfect. It was like walking on this fluffy cloud, really:

The e110 is a small and light touchscreen device, running Android 1.5 (Cupcake). It comes with 3G+ (HSDPA), Bluetooth, GPS and FM radio and it is one of the cheapest Android-based handset available. And when I say cheap, I mean cheap as in “you can’t even find a decent 2nd hand device for that price”-cheap.

So what’s not to like? Well, the CPU is pretty slow, there’s no WiFI and the touchscreen needs some tough love. Android 1.5 Cupcake isn’t exactly the latest and greatest Android around either. Although Acer did issue new ROM’s in 2010, those were all based on Android 1.5 and there are no plans for an Eclair or Froyo version. What’s more surprising (although some would consider this a plus) is that the e110 is not a Google-branded phone. This means, amongst other things, that there’s no Google Market and no Contacts synchronization. Add the lack of Exchange integration to the equation and you’ve got very empty contacts and calender, which is pretty frustrating if you want to use your phone for work purposes.

No, Acer’s beTouch e110 certainly is no Hero, but I’ve got my HSDPA, tethering and even Android for a very low price. So I’ll cope until my Hero comes home. And if that doesn’t happen, the unboxing of the Desire Z in July will be all the more exiting.

Apple still stubbornly refuses Flash on the iPhone and more importantly the iPad, Microsoft’s Internet Explorer 9 joined the HTML5-crowd in full force and even Adobe is going HTML5 with support in Dreamweaver and in Illustrator and with a preview of Edge, “a tool for creating animation and transitions using the capabilities of HTML5″.

But is was only in December 2010 that I knew I was dead on with my prediction, when I overheard this conversation at work between a business colleague and a web development partner:

Business Colleague: I would like a personalized dashboard with some nice-looking charts in my web application.
Web Development Partner: No problem, we’ll do it in Flash!
Business Colleague: No, we want this to work on the iPad too!

The year technology-agnostic decision-making business people started telling suppliers not to use Flash, that was the year Flash became irrelevant and “the open web technology stack” (somewhat incorrectly marketed as HTML5) took over.

Tot gisterenavond een voetganger met typisch Brusselse doodsverachting de straat zonder boe of ba overstak, een auto de remmen voor haar moest dichtgooien en ik hetzelfde deed om niet achterop die monovolume te knallen. Remmen dicht, de lucht in, door de achterruit van die vervloekte Opel het Schaarbeekse ziekenhuis binnengevlogen.

Op de spoed moesten ze 3 sneeën op m’n linkerarm dichtnaaien en hebben ze paar mooie zwart/wit foto’s genomen om daar -na lang wachten- op te zien dat er niets gebroken of gebarsten was in pols of nek, waarop ik goed bevonden werd om me terug in het verkeer te begeven, voorlopig wel zonder vouwfiets.

“Het valt mee, het had veel erger kunnen zijn” en “Ge hebt geluk gehad dat ge een helm ophad Mijnheer” zeiden Mario en Pieter (de vriendelijke ambulanciers), verpleegsters en dokters heel de avond lang. Absoluut! Ik en mijn Giro Flak fietshelm, wij zijn vanaf nu helemaal onafscheidelijk. Hopen dat Veerle dat geen belemmering vindt, zo in bed …

But some time ago my laptop got a memory upgrade (from 1 to 2 Gb) and last week Paul Cobbaut wrote about Virtualbox on his blog. I installed this example of German craftsmanship (both a “free as in beer” and an open source version are available, version 3 was just released a few hours ago!) and my computer hasn’t been the same since. I’m now running a fullscreen (guest additions rock) Virtualbox virtual machine with Ubuntu 9.04, using an openssh-provided (with some help from corkscrew, off course) socks-proxy for unlimited internet access and I feel like a kid that has just been allowed in a playground.

Next to Ubuntu, I also installed Opensolaris (which seems to need a shitload of RAM) and a leaked version of the emulator of that much anticipated (well, by me at least) Palm WebOS. On my disktop I installed the Linux-version of Virtualbox and I’ve got OS-weirdness such as ReactOS, Haiku and Syllable running there. Hell, maybe I’ll even install (a clean version of) Windows XP in a virtual machine there, just to make it full circle. ‘Cause I’m free!

Possibly related twitterless twaddle:

• Ubuntu Hardy upgrade a breeze!
• 19 april: Ubuntu Feisty Feestje!
• Unity launcher auto-hides in Natty Narwal

That is why (at work) we decided to include a POC in the last phase of our “web framework and development services” selection process. But not just your normal POC, where you have no control over the context in which the development takes place. No, we brought in Ivan Verborgh to help us organize an “original RAD race“. In such “development competition” you put the participating teams in 1 room and give them 1,5 days to create the same administrative application. And somewhere along the line you throw in a change request as well, just for the kicks of it (and to check agility off course).

Our participants had to use a Java-based solution (as defined in the RFP), but their frameworks were very different, with one opting for a commercial product and the other one for an open source component stack. Without going into too much detail, the RAD-race was a great experience for us as well as for the participants. Although neither team was able to complete the assignment, there was a clear difference in the teams’ performance. For some colleagues the results were a true eye-opener, with one competitor clearly having less knowledge and experience with their chosen framework. The result of the RAD-race was an important element in our decision process and it was a fun experience during an otherwise sometimes dull RFP-process.

Possibly related twitterless twaddle:

• Jakob Nielsen on mobile web usability
• Do you know Amazon EC2 & simpledb?
• Firefox Lorentz: Flash don’t crash here anymore

U ziet me mooi voor de fleetmanager de parkeergarage induiken, de vouwfiets voor de Mercedes. Prachtige symboliek, toch?