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???
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
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
Remember Microsoft SQL 2000? Remember it had DTS? And remember they were covertly stored in binary format? Really, I developed an allergy to binary storage since Java serialization abuse. Have you ever had to maintain code saving settings as serialized objects? No? Call yourself lucky. But back to the topic. Continue reading
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
In the beginning the man created CVS. And CVS had some precursors as well, and I don’t care about them as I’m not historian. Thing is only some spirit said, let’s create some software guidelines based on them: and there was Software Guidelines. Java EE software guidelines. Some other spirit saw many years later these guidelines, that they were good: and it wondered why doesn’t our actual code follow them. And it said, let the team create for each file an informational header filled with version-related information: and it was so. Continue reading