Showing posts with label Spring. Show all posts
Showing posts with label Spring. Show all posts

Tuesday, 5 October 2010

Dabblings in open source software projects

Sorry to bore you with yet another post designed to remind myself about what I should be mentioning in job interviews.

This post is a breakdown of some of the various participation that I have had in open source projects in the last few years.


  • Grails - postings on public newsgroup with gotchas of an upgrade to version 1.1.1 with maven versioning


  • Tomcat - following and posting responses to Tomcat users newsgroup; attending presentations by Mark Thomas


  • Linux-HA - participation in newsgroup during set up of cluster for Airways project.


  • Spring - postings on forums; downloaded source for 3.0 to check use of LinkedHashMap as default type for Map in bean properties.


  • Hibernate - postings on forums.


  • JBoss 4.2 - checked out source code from subversion repository to apply patch for ajp issue.


Monday, 4 October 2010

More Spring bashing than usual at The Server Side?

I haven't really paid much attention to The Server Side website for a couple of years, but I had a glance around it this evening when trying out how things look on the iPad.

I came across an article entitled Moving from Spring to Java EE 6: The Age of Frameworks is Over which reminded me of a lengthy blog post that I had read recently Spring to Java EE – A Migration Experience. Sure enough the article ended by linking through to that blog post.

As I first read the blog post I sensed a definite anti-Spring sentiment, and couldn't help but notice that JBoss technologies were being name-dropped and linked to throughout. Sure enough the blog was authored by a JBoss / RedHat employee.

I suppose it would be asking too much for some kind of impartiality in the world of commercial software (if you dig deep enough you might suppose that the author of the article on The Server Side has some interest in a Java EE resurgence, given the books he has authored).

When I recently attended a couple of presentations of JEE6 and Glassfish 3 given by Arun Gupta I got to thinking that the CDI annotations would allow de-coupling from the dependency injection framework in much the same way as JPA can reduce dependence on a persistence provider (e.g. Hibernate, Eclipselink).

Just my thoughts, which are probably biased.

Friday, 14 May 2010

S2G Forum London

A couple of months ago I booked today off work to attend the Spring Source S2G forum.

Unfortunately due to a looming deadline and issues arising back at the office, I felt compelled to miss the last couple of sessions but I still felt that I learnt enough from the day to make it worthwhile.

Mark Thomas did a good job of outlining some of the new features to be expected in Apache Tomcat 7.0.

Rod Johnson was good value with some self-deprecating humour when his live demonstration of Roo struck a couple of hiccups.

I was impressed with Roo's approach to round-trip code generation via AspectJ.

The main disappointment from the day was the thought that my currently planned projects are dependent on a third party - so I can't simply pick up Spring 3.0, Roo and Tomcat 7 for the next green-ish field development.

Monday, 18 January 2010

Am I just being cynical?

A few days ago I noticed a blog post over at SpringSource that announced the intention to move dm Server across to the Eclipse Foundation.

I haven't been attending enough geek meetings lately to appreciate what is going on in the world of OSGi, or the politics of the VMware acquisition of SpringSource for that matter.

A cynical person might observe such an announcement and think, "that project has been identified as not being aligned with the core business, so it is being abandoned in the nicest possible way". Today I might be that cynical person.

The optimist in me is hoping that the Eclipse Foundation can make the system into something that takes off and provides as much benefit as the Eclipse IDE did when IBM released that.

Time will tell.

Wednesday, 15 July 2009

Is London shrinking?

The old expression that "it's a small world" rally rang true for me today.

On my way home from a job interview this afternoon I thought that I recognised an old friend from New Zealand queuing up to use an ATM. Sure enough it was! After nine and a half months I have finally bumped into someone that I know from back home.

As if that wasn't enough, when I attended the London Spring User Group meeting this evening I ended up chatting with one of the 2 people who had interviewed me for a different job yesterday afternoon! Wait for it, later in the meeting I recognised the name of one of the attendees who had won a book in the feedback survey prize draw. Down at the pub for the obligatory socialising and networking afterwards I inquired as to whether he was a recruiter - sure enough it was the agent that I have been dealing with for the job the same job. SMALL WORLD.

This month's Spring user group session was focussed on Spring Batch and what is coming up in Spring 3.0.

I found that I appreciated the details of Spring Batch much more this time around, as opposed to when I first saw a presentation about it - after lunch at the Spring in Finance seminar day back in September 2008.

Seeing the list of what will be removed or deprecated in version 3.0 of Spring made me feel better about not knowing "which controllers" I had used in my experience of Spring MVC - a question that came up in a recent job interview by phone. The hierarchy of form controllers are being ditched in favour of the annotation based approach. So, I have only been using the latest APIs - still doesn't hurt to read about the old way of doing things (even if the MVC chapter in my reference book is 100 pages long).

Monday, 22 June 2009

Grails gotchas / showstoppers effecting uptake

I was somewhat relieved when I came across this blog post which highlights the fact that other developers have also faced a loss of productivity when working with Grails.

The "convention over configuration" approach speeds up development and keeps the learning curve fairly easy for most developers, but the list of open issues on the Jira suggests that there are still some aspects that need tuning - or detuning in some cases (e.g. domain objects not having GORM functionality due to something missing in lazy decoration/injection).

I've been wondering what sort of risks are involved when you use a software product that is essentially just providing a layer of abstraction over several loosely related other products.

For example, what can you do if you want to upgrade to a later version of one of the underlying technologies (for a fixed bug, or to use a new feature), when the layer above that hasn't been tested or made configurable for that new release? At present, I would expect that you would be stuck with whatever version is compatible with your version of Grails. This could change once OSGi becomes a bit more mainstream, allowing for the use of multiple versions of the same libraries within a single application. I wouldn't want to rely on that being the saviour of any application of mine though.

Friday, 5 June 2009

Ubiquity vs Standards

I noticed a post on SpringSource's blog site the other day that included some a chart of job postings based on some specified criteria. The blog post was about some recent Red Hat announcement, so one I assumed that the chart was intending to compare Spring against Red Hat.

I'll admit that I haven't done a lot of development using RedHat's technologies (unless you count Hibernate - which is practically everywhere - and RichFaces JSF), but I'm pretty sure that the charts weren't giving a fair comparison. Seam and RichFaces are not all that RedHat (JBoss) is about. I posted a comment, then noticed a day or so later that a blog post from somebody at Red Hat had used the same ad statistics system to show a quite different picture.

When companies advertise for a developer (shameless plug - I'm available at the moment), they're not always after somebody who has specific expertise with the particular application server that they are currently using - because that criterian could eliminate a lot of perfectly good candidates. These servers have to get certified as meeting certain standards before they can claim to be "Java Enterprise Edition" after all.

So, I feel that Rich's chart may be a little more reasonable than Rod's if you look at it in terms of what skills the industry has been seeking from new employees.

I'd rather be hearing about the technologies than the - possibly biased - perceived market trends.

(Spring Security 3.0.0.M1 looks like a great update).

Monday, 23 February 2009

It's unique, just like all the others

So, I've been going to a few job interviews lately and I can honestly say that no two have been quite the same.

For the first few weeks after arriving in London, I was applying for contracting roles. It didn't take me long to realise that Spring and Hibernate are a big deal in the local job market, so I started to do a bit of upskilling - Winning 4 days worth of training in the latest Spring technologies was a good start, but the timing of the course - December - was awkward as I had to second guess how that might be treated by a prospective employer - Good: training; - Bad - 4 days off before he's even started really working.

Reading the books and having a course coming up was never going to be enough to get me up to the standard expected when a company is paying top £s for a specialist, so I eventually agreed to look at permanent roles.

The first interview was in Devon and involved a long train journey - which half convinced me that it was not going to be suitable, given that at least some of the reason for my moving to the UK was to be close to Ireland and Europe for quick weekend getaways. After I had proven my technical prowess in a coding exercise and a general "problem solving around the whiteboard" discussion, I had the panel interview with 2 techos and an HR person. I decided not to proceed with the team lead role they were looking to fill as they were also looking to change their entire development methodology - and I could see that being painful.

The next interview was for a role as a consultant and was run in a cafeteria with a couple of techos, that would have involved me working at client sites and from home - which doesn't really fit with my preference to stick with developing as part of an agile team.

The third interview was unusual in that the company involved approached me directly after finding my CV online - as opposed to the agencies that I usually hear from. Their offices seemed nice, and the discussion went well - but I wasn't really expecting to hear back from them, given the timing and the industry sector they are in.

The fourth interview involved another out of town train ride, but ended promisingly with the guy saying HR should be in touch with me with an offer - hopefully before Christmas. So, leading up to Christmas I felt that my quest was at an end, but the holy grail of a steady income with that company ran away in corporate re-structuring and an unrelated subsequent recruitment freeze.

January proved to be quite a quiet month on the recruitment front, so I applied directly with a few companies and followed up on some companies that I had been in touch with pre-Christmas.

In two interviews I foolishly attempted to bluff my way through describing the design of a system that I had been responsible for developing. I kept tripping over how to describe a particular sub-system which a colleague had designed, but which was critical to the description of the product.

The feedback was mixed:
- one company said I was technically great, but recommended that I read a particular couple of books (one of which I had already read, the other I am in the process of reading right now);
- the other company told the agent that I gave the impression that I wasn't interested in working there

Given that I had just spoken to the agent to let them know that I would lower my salary expectations by 10%, as I felt that the company had a great approach and were really innovative in applying agile methodologies to their development, getting that kind of feedback came as a bit of a shock to me.

So, in the next interview I made a point of giving well thought out responses to the touchy feely HR questions as well as the technical ones. I thought that I was on a roll when the interviewer said that a lot of candidates hadn't known some of the aspects that I had covered... The interviewer deliberately skipped his questions about Hibernate, as I had stated on my applciation that I did not have commercial experience with it. So, I think that I was justified in feeling frustrated upon hearing their excuse for not proceeding further with me: the other candidates they spoke to had more experience with Hibernate.

So, now I've finished reading Java Persistence With Hibernate and have started posting solutions to problems other people are reporting on the Hibernate forum site. I like to learn from other people's mistakes, and get a feel for what areas are proving to be challenging. It's been re-assuring to find that the issues encountered are much the same as I found with JPA - but saying that "I don't have experience with Hibernate, but I've got a year of JPA and 3 years of JDO" doesn't mean much to the recruiters.

Now that I have some casual part time work I should be able to fill a few of those silly gaps in the CV and be set to hit the ground running - maybe I could give contracting another look?