The outcome of the program has been clear admission of the problems from John Hughes of The Co-op, news that the “completely new system” will be ready in Q2 2010, and that to improve the situation they’ve laid on an extra 20 call centre staff.

Apart from the admission – always nice to have – this is pitiful. 20 call center staff? How is that going to make online banking work for us over the next 6 months? Where were the hard facts? eg “The current system runs on N servers and that is simply not scalable for us, and we are moving to a system that we know will scale from A to at least B easily as we grow”. These are BASIC BASIC questions for an organisation like a bank to be able to answer.

Furthermore, there has been no mention of the “completely new system” already being repeatedly delayed – seemingly for years now. I and others were told many months ago that it was launching Oct/Nov 2009. Now its Q2/Spring 2010. What’s the betting we won’t see it in 2010 at all – after all these problems have existed for years now, why on earth is it taking so long?

What really irks me is that they are acknowledging the problem but giving no idea at all about who was responsible for the existing poor system, and who is putting together the new one. Presumably there was a massive management failure at Co-op when commissioning the previous system.

Are those managers still at the Co-op? Have they been retrained in scalable IT systems procurement?

Is the new team even fit to produce a high quality product? How can we as customers already neglected for years know that things will ever get better. The current system – we were told – was much better than the one before it. We customers beg to differ!

I looked at the board of directors of Co-op to see if we can contact them to write to them and explain that this repeated failure is going to kill their business banking business – and that they better be 10000% sure the new system is going to not only meet basic needs but actually wow us to restore the good faith we had.

However, there seems to be no Chief Technology Officer. In a bank, there is no CTO on the board of directors? Seriously? Is the problem actually that there is no coherent IT management right at the top of the bank’s board?

I’ve had a lot of new blog comments come in echoing the online banking problems with Co-op.

There’s also been some twitter coverage:

http://twitter.com/juxtabook/status/5762990782
http://twitter.com/jarneil/status/5738998022
http://twitter.com/MoeNawaz/status/5734085504
http://twitter.com/InterShortNews/status/5719050325
http://twitter.com/jain_sweden/status/5722958220
http://twitter.com/BBC_News_World/status/5712126686
http://twitter.com/paperfutures/status/5711227650
http://twitter.com/testandgo/status/5707893435

There were a lot more like this, presumably RT’s via BBC website.

At the end of the day, in my view this is a critical problem in the organisation. They pride themselves on ethics and a hence socially-minded outlook, making sure their staff are happy, and providing good customer service.

The problem is that somebody, once the Internet stuff started taking off, forgot that the Internet requires just this high level of customer service too, and you absolutely must put in the systems to guarantee this. Internet banking is not some 2nd-class add-on to phone banking. Well, it is at The Co-op for business customers.

I also notice people commenting that neither Smile nor personal Co-op online banking have seen any new features or improvements for years. This is absolutely true, and Co-op personal banking lags behind many other banks. We can’t search for payments/credits, we can’t filter by date ranges, we don’t have any way to set up automatic alerts/transfers under certain conditions.

Its stoneage

UPDATE: story picked up by ComputerWorld and says the new system we are yet to see is called Finacle and is from Infosys

How come we can’t claim compensation for this? Because we can call up and wait 20min to be served?

Anyway today:

1. Try to log in, can’t. Says NO_RESOURCES error
2. Try to log in again. Same
3. Try to log in again. Same
4. Try to log in. Succeed. Forwards me to “You MUST change you password” screen
5. Annoyed, enter old and new passwords and submit. Says NO_RESOURCES error
6. Have to log in again. Don’t know which password to use now. Try more than 5 times. Sometimes wrong credentials (I don’t know which is right now) and sometimes NO_RESOURCES
7. Finally get in, and taken to “You MUST change you password” screen again
8. Change password OK, and log in. Amen

[UPDATE: An hour later I try to log in to pay my accountant. Log in fine. Get to payment screen, go through the mindachingly awful UI to select a date range - did I mention they changed the default to showing all reports for "today" only to lessen system load? - Try to get list of previous payments... NO_RESOURCES. Returns me to login screen. Log in again, shows me I am "already logged in". Dashboard comes up, half page fails to load "Unable to find service BroadcastMessaging". It goes on....]

The book is invaluable if you’re interested in setting up or working for a startup, want to know how the hirers and firers think, and really pretty much anything about internet-related business.

The “collection of articles” nature of it means there is a little repetition in places, but Guy’s writing style is entertaining and clear – this isn’t a dull tome of pseudo-scientific business speak – and the repetition serves to drive the message home.

I didn’t think I’d be interested in the “hiring and firing” stuff, nor the stuff related to patents or VC funding etc but it turns out everything in there is extremely interesting, with a real world perspective.

I’m going to be using this new-found insight on a startup project I’m working on at the moment. Let’s see if we can pull it off, with a bit of help from Guy.

As a side note, Guy looks insanely youthful and is successful so he must have done some kind of deal with the devil. Especially since his increasing tendency to have minion post tweets that feel more and more like pyramid selling each week… come on Guy can you get it a bit more real please?

It looks good on the “Grails shack” where I work during the day for my clients and churn out Grails plugins as part of Grails Rocks (what is it? Who knows at the moment) the rest of the time… not including the times when I’m sitting next to my wife in the house working on my laptop instead of being with her, an unfortunate consequence of Grails enthusiasm.

The “shack” is built out of green oak pulled out of a local river, green larch from a local saw mill, cedar roof shingles and some standard pine timber by a local artist called Denius Parsons. I’ve been in it for a year now. I’ve still got to paint the window frames and do some work on the internal floor but… its -2C outside and snowing, and with the killer insulation I need a 400W electric heater on only occasionally. It did the -8C in January without wind/damp fine, felt warmer than today with the -2C and snow.

It’s a lovely place to work, thank you Denius!

It is in the plugin repo now, and “grails install-plugin functional-test” should work.

The docs at http://grails.org/Grails+Functional+Testing have been updated – there were several errata but there are also new features and one breaking change. I know, we started at 1.0 but … its a good change and few people will be affected at this point

New are… Javascript on/off, Grails 1.1 compatibility, text area support, cookie support, proper redirect handling (some limitations currently), and lots of output improvements and fixes.

BREAKING CHANGE:

Setting the value of selects, checkboxes and radio button groups is now just a simple property assignment. So where before you had:

form(‘myform’) {
radioOptions.checked = “option3″
}

You now just have:

form(‘myform’) {
radioOptions= “option3″
}

Which is more consistent with other field access.

Also the test output files contain useful information about followed redirects and values set and items clicked, for when you need to debug a failing test!

Here’s the changelog from JIRA:

GRAILSPLUGINS-772     FIXED     Add support for disabling JavaScript
GRAILSPLUGINS-771     FIXED     Add support for getting/setting textarea fields
GRAILSPLUGINS-773     FIXED     Enable redirect following by default, and add property to turn it off
GRAILSPLUGINS-779     FIXED     Sometimes requests will not update the current page data
GRAILSPLUGINS-783     FIXED     Allow resolution of form buttons by VALUE if no element can be found by id/name
GRAILSPLUGINS-781     FIXED     Allow user to clear the CSS+JS cache during a test
GRAILSPLUGINS-784     FIXED     Breaking change – make it so that setting value of checkbox/radio/selects does not need x.checked or x.select
GRAILSPLUGINS-786     FIXED     Improve output captured so that headers and assignments to fields are easily seen
GRAILSPLUGINS-785     FIXED     Provide access to cookies and enabled/disable cookies
GRAILSPLUGINS-788     FIXED     Rework it so that redirects that are followed show in output and correct request method shown for redirect after POST

Enjoy! Thanks to Peter for the work on Grails 1.1 compat.

The problem: HtmlUnit, which the plugin uses for HTTP interactions, has an extensive hierarchy of classes representing page and form elements. There is however no way to indentify some of these as specific functional groups eg there are 4 different button types, which have no interface or ancestor that is not also shared by some other non-button classes.

So a little ugly logic is needed. For example when the plugin’s form wrapper uses Groovy dynamic property resolution to get a form field for you, it is now doing something like this:

private getFieldValue(f) {
  // Note this switch is polymorphic, order of cases is IMPORTANT
  switch (f.class) {
    case BUTTON_CLASSES:
    case HtmlFileInput.class:
      return f // return the field object itself, not its value
    case HtmlSelect.class:
      return f.selected
    case HtmlRadioButtonInput.class:
      return f.checked
    case HtmlCheckBoxInput.class:
      return f.checked
    case HtmlTextArea.class:
    case HtmlInput.class:
      return f.value
    default:
      throw new RuntimeException("Don't know how to get a value from form element of type [${f.class}]")
  }
}

Now, what is special about this is:

1. Groovy’s switch statement is very cool. It calls isCase(value) on the objects used in the case statements. That’s pretty basic Groovy stuff, but is still news to most Java developers.
2. The use of BUTTON_CLASSES in the case is very cool. That property is a list of HtmlUnit classes that are “buttons” in conceptual terms. Groovy will call isCase on the list, which will return true if the list CONTAINS the switch value. That saved me 4 case lines and made my code more DRY as this check is also done elsewhere.
3. The isCase implementation on Class added by the Groovy GDK is polymorphic. So the “case HtmlInput.class” actually catches any descendent of HtmlInput – of which there are several. This is also why the case BUTTON_CLASSES is at the top of the switch, as some of those classes extend HtmlInput and would be incorrectly caught by this HtmlInput clause.

Many people will no doubt say I can simplify the code above further – the “.class” are largely not necessary and I could merge the “return f.checked” cases. I may well do in future, but this is there for clarity at the moment

Getting close to release for the Grails CMS app with my work on it kindly funded by JCatalog AB. Getting improved billing and signup stuff up together for my other client.

Struggled a lot with problems with flows in Grails 1.0.4, really got me down to be honest as it has been such a sinkhole for wasted time. Hopefully I can contrib some fixes or at least isolated test cases to help sort this out.

Work is ongoing on the functional test plugin which is rocking already, but needs a little more polish before release. Also ongoing work on the bean fields taglib for Grails.

So much to do so little time. Have to be with the family and keep up my drum practice!

It looks like I’m booked up again until the end of January. If you are interested in hiring me from Feb 2009 onwards, please get in touch now!

Now it’s a very amusing and quite thought-provoking talk. I now look at things even more critically than I used to, and annoy my wife by telling her how broken something is.

Anyway, the US voting system is broken. Ignore the problems with ballot papers, dodgy voting machines, and the whole lack of security in the electronic voting machines…

The US voting system is broken, I can tell, because all I hear on the news is how people are voting EARLY and yet it is taking them 3-4 hours in many cases, from entering the building to casting their vote.

This is utterly utterly broken, and you have to wonder if it is broken intentionally (one of Seth Godin’s 7 or so reasons for being broken is deliberately broken by the maker).

After all, a long delay to vote is rather a good way of filtering out certain kinds of voters – those with low paid jobs and unhelpful bosses – those who are carers – those who are young and have something better to do with their four hours. Could voting delays alone be the single nascent reason behind the Republican presence in the White House for so long?

Can you imagine the outcry if it took people 4 hours to vote in the UK!?

For your information, last time I voted in the UK it took 5 minutes.

The State will tell us how to teach and what results to aim for, and what the State prescribes will be bad. Its targets are the worst ones imaginable, yet it expects to get the best possible results. Today’s politics work in the direction of regimentation, and it will go even further than this in its attempts to make people conform. Human beings will be treated like puppets on strings, and this will be treated as progress in the extreme. Institutions like schools will be organised in the most arrogant and unsuitable manner

- Dr Rudolf Sterner, from an address given on 20 August 1919 (emphasis added).

Our battle is continuing to prevent the EYFS from clobbering the good work done by Steiner Waldorf schools in the UK.

To install the plugin, which adds support for rendering the mail body from a GSP from within a controller, service or job, run: grails install-plugin mail

Full docs for the mail plugin are here.

To view the “Using the Grails mail plugin” screencast, click on the thumbnail or go to the fledgling “Grails Rocks” page.

This is the first Grails Rocks screencast, but I hope to do many more. The next one is already planned, for the forthcoming release of the Email Confirmation plugin – which was dependent on this mail plugin 0.4 release.