May 06, 2017
The atmosphere around Java 9 (and most notably JPMS a.k.a. JSR 376 a.k.a. Jigsaw) is getting really hot. Java community seams to be divided into 3 camps “developers who honestly believe JPMS can simplify modularity”, “developers who have been dealing with modularity long enough to clearly see the issues Java platform architects don’t want to see” and “developers who don’t care (for now)”. I personally think the 3rd group is by far the largest and this is the main issue and the main reason for the noise. Why? Because those are the developers who never cared about modularity. Most of them still don’t care, but now they will be forced to learn about modularity. The question is what will they learn? Real modularity as described in Modulariy Maturiy Model or limited version of it wrapped in a package with a label “simple” on it?
This is not a new thing! The battle between “good quality code” and “simple to write code that works” is something that takes place in every project! And you know which one wins most of the time. At least I think I’ve been in this industry long enough to know, so I though I’ll write down a few prediction based on what I think will happen to JPMS and what impact it will have on Java projects in the following months.
March 16, 2017
I have spoken at quite some conferences over the last years. Part of the talks were just me speaking with some (hopefully not too ugly) slides behind me. Some were live demos. Either way, I’m almost never happy with my talks and therefore constantly looking for ways to improve. But in order to improve, first you need to know what your audience like and don’t like. It all comes down to feedback and constructive criticism. Some conferences are quite good at collecting feedback. Polish Confitura is on the top of my list, sending me a document that not only shows how people voted but also all the comments from their online survey. Most conferences though don’t bother to give feedback to speakers. Some don’t ever bother to collect it. It’s therefore been on my mind for a while to try to find a fun and easy way for attendees to provide feedback during (not after) my talk.
February 21, 2017
As developer advocate, I do a fair amount of traveling. Most of my journeys start with about an hour long drive to the airport. It’s nice highway, not a big deal, easy to do it without needless stops. Yet I like to make one stop, get myself out of the car for a while, grab a coffee, smoke, …
One of the first times I drove there, I stopped at some gas station. It was my first time there. As I was getting out of the car, I realized they had a special place for pets, nearby the main entrance. There was bowl of water and another empty one next to it (presumably to be used to put some food in it). There was also a sign, encouraging pet owners to ask for any assistance they may need. I found this interesting, and proceed to the restroom. A somewhat strange hanger on the wall attracted my attention. It turned out to be a dedicated hanger for motorbike helmets.
September 30, 2016
Some time ago I published a survey asking developers what they think about OSGi. It took a while to reach some reasonable amount of responses and then to process the results, but finally I’m ready to publish them.
In a few weeks period there were 220 responses to the survey. Even though there was no question about the location, I’m pretty sure they come mostly from Europe. That is because I could see the responses coming in groups as the survey was promoted at particular local JUGs. Another thing to take into account is that the information about it reached way more than 10000 developers (based on the published number of members of the groups the information was published). With that in mind you can hardly consider 220 responses representative. Never the less it gives you some ideas and things to think about.
September 21, 2016
Yesterday someone very well known and respected in Java world (I didn’t ask him for permission, so I’m not mentioning his name), approached Liferay’s booth at JavaOne. He expressed his concerns about the word “μServices” in the message printed on our booth’s wall. I wasn’t there at the time this happened. I spoke with my colleagues few minutes later, as the non-developers were getting worried we made a terrible and embarrassing typo. As a non-native English speaker I wasn’t quite sure what the exact argument was, but it was clear to me the person believed we should have used “micro-services” instead. I urged to reassure my colleagues this is not a typo but an important differentiator in today’s buzzword driven world.