Migrating emails from Notes to Outlook (or, programming for failure)

My huge archive of Lotus Notes emails started almost ten years back, and I stubbornly kept most of it around because of why not. Now that I use Outlook 2013 you can imagine I would have liked to have all of them also in my brand new email client. One sure could get some commercial software to do it, but why shouldn’t I try converting them myself? I mean, look, a simple drag and drop from Notes creates in Windows Explorer EML files and we all know EML is a very much standard format (RFC822 or so). Or at least that’s what I thought – Outlook 2013 thinks differently and will not import EML files. Only Outlook Express or Microsoft Live Mail can do that, but who cares about these anyway?? So what are my options?

Continue reading

How simple is simple? (from MongoDB to Elasticsearch)

IT must be easy, oh yeah. After years of courses and university and everything else, just because they were put together by the brightest educational minds you should be able in a second to program this new web application, integrate external web services, add a new GUI and adapt your friend’s broken Excel import, all while cleaning up grandma’s computer for the hundredth time. Even kids are to be taught programming, so it can’t be much in it right? How MANY times I heard this told in various ways “it can’t be so difficult”… Everybody has challenging jobs but as soon these involve computers everything should become a breeze, somehow. When did we get into this???

Trouble

But I digress. So, first a bit of context: I thought it would be big time I followed my own thinking from a month ago (see “Proof of concept, with a concept”) and actually migrate the proof of concept code from “Ractive.js and vert.x integration over the event bus” to use Elasticsearch. Continue reading

Proof of concept, with a concept

One problem I have when trying new technologies is actually seeing them in realistic situations – which translates to having a real use case for them. Think about this: when you build a “hello world” application you actually couldn’t be further away from the real world! I guess that’s why nobody calls it “hello real world” anyway… The whole experience you get from the proof of concept is just random installation trivia if you’re not using it to prove a point. That’s why it’s called “proof of concept” – it should have a concept, silly. Continue reading

Ractive.js and vert.x integration over the event bus

Recently I ran into Ractive.js which seemed like something doing exactly what I’d expect from a client side (browser that is) framework – fetch its own data and create nice web pages with that without getting me from the beginning too deep into JavaScript programming. Nota bene: I’m not a JS programmer and Angular or Ember just scare the s* out of me, plus I have strong moderate opinions against massive JavaScript framework programming so Ractive seemed like a convenient compromise. But would I be able to use it? In a vert.x project? Maybe I should try just that… Continue reading

Vert.x instead of servlets, time for something new

Why

How old are dear servlets? 15 years you say? Hm, maybe it would be time to check on alternative technologies, not because servlets would be necessarily bad but just to check whether new times brought also new concepts forward. And you bet they did – look at Node.js, it‘s quite popular nowadays. JavaScript aside, Node.js has a different way of working – a reactor pattern, not at least a very good way to use the multicore facilities of today’s machines. Node.js is actually not alone in this league – the very popular Nginx (yes, the one stealing Apache web server’s crown) works apparently the same way. But if you want to replace your servlets Java web application, you’ll HAVE to try vert.x. Cool, multithreading without writing yourself threads! NOTE: Worth mentioning here: vert.x can do a lot of stuff and a web application is only one of its possible uses. Continue reading

Me and my Paperwhite – a kind(le) of review

I’m a very late newcomer to the e-books revolution, it wasn’t even a revolution anymore when I got in. It just happens that one of my favorite websites, New Scientist, announced they’d issue a magazine called “Arc” – was it one year ago? A collection of science for dummies, futurology and SF, sounded fine so I looked for ways to read it. Being proud owner of a Samsung Galaxy S2 (in a love-hate relationship but that’s another story) the options were quite a few. First: download via Google Play… neee, no Google Play Books in me country. Second: in Zinio… nice but can you imagine cramming a full-blown newspaper page on a smartphone screen? You either can’t read it, or you fumble like crazy trying to focus your reading window on the current text. So Kindle was the single real option, at least on my smartphone. So this is how it all started, although… battery goes down SO quick! Anyway, after I got to read some more Kindle books on that phone I decided I had enough with the black bars of the Kindle app coming over your text every second second and I should try the real deal: an e-book reader.

Enter Paperwhite. Continue reading