These and others (including the longer version of The Future of Agile from Bristol BCS) are available on the presentations page.
As if I haven’t written enough…
Slides for the sessions are to be found at
Not all the slides are there yet, they will appear gradually. In the meantime, check out:
If you have a blog about the conference please add it in the comments.
As you might expect from the ACCU conference there was plenty of C++. But the language was far from the only one in town – there were at least 8 others. This year most of the C++ sessions looked at the forthcoming C++ 200x standard. It now looks unlikely that this will be completed this year so we might want to rename is C++ 201x. As to exactly when, well, your guess is better than mind.
Some years ago I said that this standard would be “the longest suicide note in history.” I stand by this comment – indeed I found other people repeating it, either to agree or disagree.
I say this because I believe the language is now so big to be un-teachable, and possibly unusable. I don’t see how making the language so much more complicated will encourage more people to use it, indeed I see the reverse. And I believe this standard will only add to the confusion around C++.
I’ve also been saying for the last few years that we have seen the last generation of C++ programmers. A recent meeting made me rethink this position – a recent graduate who has to learn C++ for his first job. But then, at the conference and without promoting from me, Andrew Holmes said he didn’t think anyone would learn C++ after 2006 so maybe I’m not completely wrong.
Anyway, learning the new C++ will only be an academic exercise for the next decade. It will be a while before any compiler implements it and much longer before a substantial code base exists to work in.
I believe things need to be removed from language to simplify it. So I have also been suggesting for a while – to anyone who will listen – that C++ should split in two. There should be one backward compatible version with minor fixes and enhancements. A second version should break backward compatibility, remove features, fix elements of syntax and make it easier to learn.
After speaking to several people at the conference I believe this has now happening. Not officially but by defacto.
Walter Bright’s D Programming Language is gaining traction. This is the simpler C++ which I – and others – have been looking for. Unfortunately I didn’t get to talk to Walter at the conference, I hope he will return next year with more D and I will get the chance to speak to him. (Walter, if your reading this, can you please present D in 180 minutes?)
Its not a forgone conclusion yet but I hope D will succeed. Actually, I think Oracle’s purchase of Sun could help here. Oracle are quite clear why they are buying Sun: to get Java. This means things will change in the Java world – if only because Oracle want to make money out of Java.
Its too early to tell yet how this will plat out but I expect to see many people rethinking their languages choices as Oracle’s plan plays out.
Attendance was high. People came from as far away as California and Tokyo. Since the move from the Randolph to the Barcelo hotel the conference has been able to cope with 350 attendees. The last couple of years it has been sold out, this year it fell short by about 5. I believe 15 or more bookings happened in the last week.
Given that other conferences are reporting falls of 30% or 40%, and some are cancelling altogether that is remarkable. The success I believe is down to two reasons.
First the obvious: the conference had an extremely strong programme.
The ACCU conference is not just the best software development conference in the UK – possibly in Europe and indeed the world – but it is also the high point of the ACCU year. The ACCU has close to 1,000 members thoughout the world, it publishes 12 journals a year, runs several active mailing lists and holds numerous local events in the UK and USA.
For many members the conference is a chance to meet people face-to-face who they only meet electronically otherwise.
Not a lot to report on Saturday really. I did the keynote – finally called 9 Principles of Successful Software Management – and then delivered my own regular session – The Future of Agile. (I’ll post the presentation soon.)
Lunch, ACCU AGM, goodbye’s and home.
And so I’m not sitting on the train writing up these notes. (OK I was when I wrote these, a little editing since I got home.)
I’m no longer on the conference organising committee but I know the people who are and from what I understand the conference will most likely start on 14 April. I hope the conference will return to the Barcelo Hotel in Oxford, although its outside the centre it is a good venue.
Friday opened with something completely different for an ACCU conference: Neuroscience and women. Baroness Greenfield spoke on the subject of women in science and technology. Much of her talk was given over to exampling the neurological differences between men and women and why they don’t matter. Great stuff – enough to persuade me to buy her book(s).
After that I started to slack off a bit, miss sessions and arrive late. The effects of two late nights and lots of beer. Plus a need to talk more to people outside the sessions.
Several activities this year were designed to support Bletchley Park]. A donation scheme, a raffle, challenge puzzle and a sponsored bike ride (thereby hangs a long story.) In keeping with this theme Simon Greenish from the Bletchley Park Trust and Dr Sue Black from Westminster University gave a talk at lunch time.
The history of Bletchley Park is increasingly well known. Simon and Sue focused on the future, how they trust wanted to improve the park and the difficulties that stood in the way. The key point was that the trust is now in a race against time, the buildings are decaying and need repair if they are to be preserved at all. There are still enough Blethchley Park war veterans alive to make historical projects based on the park worthwhile. Before long much of our history will be lost if we do not act now.
Certainly it was enough to persuade me to make a donation to the Park, and hopefully I’ll go and see it this summer. And….
Friday’s sessions ended with the Pattern Buffet. Anouther innovation, this time from Kevlin Henney and myself. With help from Linda Rising, Michael Feathers, Peter Sommerland, Jim Siddle and Klaus Marquardt we presented 7 patterns in 90 minutes. Each speaker had 10 minutes to tell the audience about a pattern of their choice.
Friday closed with the traditional speaker banquet dinner. As usual this saw conference attendees swapping tables between each cause. After dinner there was the now traditional ACCU Boat Race.
Thursday kicked off with a keynote from Linda Rising in which she described her personal journey of discover of, and with Patterns. I’m lucky enough to count Linda as a friend, and I already knew much of the patterns story she told. Still, I had fresh insights and understanding.
For many of those in the room Linda’s ideas and thoughts were completely new. She finished by presenting us with something of a challenge – albeit on originally thrown down by Christopher Alexander – What are you doing to make a better world?
Next I went along to Phil Nash’s talk on Objective-C. He tried to teach Objective-C in 90 minutes. He almost managed it too! I don’t really code anymore but I enjoyed this insight into another language and how Mac’s and iPhones are programmed.
Mark Delgarno of Software Acumen and Helen Sharp of the Open University workshop on “What motivates software developers?” provided plenty of food for thought.
Helen reported on her research which can be summarised as: “Nobody knows” – basically there are many studies, but none of them actually bothered to define what is a “software developer” so they covered project managers, coders, testers, and possibly many other people who are involved one way or another with creating software but have very different approaches, skills and motivation.
For me Thursday’s sessons finished as they had begun with Linda. The good news from this session is that we, as human beings, are hard wired to be optimistic. The bad news is that consequently that means we cannot estimate work and even when presented with evidence we make the same mistakes. I’ve mentioned our confirmation bias before in this blog, this presentation was a though examination of the issue.
A new innovation at ACCU conference this year was the introduction of lightening talks. After the main sessions on Thursday and Friday an hour was given over to short (5 minute), talks and presentation from various people. The speakers and subjects were only agree on the day and several of the talks were only written in the hours before.
I got several nuggets of information from these talks. Two in particular stick on my mind: the Google Web Toolkit as an alternative to Selenium (Paul Grenyer); and the advantages of giving specifications by example rather than by rule (Keith Braithwaite),
Another year, another great ACCU conference. I counted 9 languages on the conference program, everything from Scala to C++ – yes there was more C++ that anything else but it was far from the only thing going on. Languages plus sessions on design, pattern, management, Agile and neuroscience.
Normally some of the most insightful comments come not in the scheduled sessions but in the discussions over coffee and in the bar afterwards. Sometimes you don’t know these are insightful until after the event when you’ve left and had time to think it all through.
This will always be a special ACCU conference for me because I was the keynote speaker on Saturday. My keynote was well received and the slides ….
So here is a brain dump.
The opening keynote on Wednesday was from Bob Martin – “Uncle Bob” – about software craftsmanship. (I’m watching the software craftsmanship movement with interest and will write a blog about it in future.) Bob suggested that the most successful Agile method – Scrum – was the accidental “winner” of the Snowbird summit in 2001. This was because the Agile manifesto and Agile values said nothing about technical practices.
Scrum, as is well know, does not contain any technical practices. Teams often borrow these from XP. Because of this Bob believes Scrum is a subset of XP – a subset which just deals with project management. Without the technical practices productivity falls off and teams make a “big mess faster.”
Bob’s answer is a renewed emphasis on technical practices – hence software craftsmanship.
Bob is a great showman and his talk was very entraining, if you get the chance to see him do so. Along the way made several Scrum jokes and was quite critical of Scrum Master Certification.
Someone like Bob can do this, Bob has the reputation and standing to be able to take pot shots from a safe(ish) position. This is good because someone needs act as a foil.
Jutta Eckstein’s session on transparency in Agile was interesting. It reminded me of the session I ran here a few years ago called “Exposing problems / Creating awareness.” The these was similar: “Agile as a problem detector.” The session was largely a discussion between Jutta and the various people in the room.
Keith Braithwaite presented the latest instalment of his “Measuring the effects of TDD” research project. I’ve seen Keith talk about this subject before and over time his presentation is getting more and more compelling. His sample size in increasing and its looking like a more convincing case.
If you don’t know the work have a look at Keith’s blog. To summarise it: you can measure code complexity using a measure called cyclomatic complexity. Keith’s research shows there is a correlation between complexity and automated until tests. Namely: code with a high level of automated unit tests exhibits lower complexity metrics and people comment they are “happier” with the code.
Having discovered the metric Keith is still trying to understand the cause-and-effect relationship and, perhaps, more importantly, uncover how this relationship can be used to improve matters.
Nicolai Josuttis finished the day with a second keynote. You could call it the antidote to software craftsmanship: Crappy code.
Although Nico made it jovially it had a serious point: there is a lot of bad code out there and it is likely to be around for a while to come. The economics of software development and business tend to perpetuate this situation. Therefore, we need to get used to crappy code and find ways of dealing with it.
While I agree with Nico I can’t help feeling it was a little defeatist. If we accept this poor state of affairs do we still have hope of a better tomorrow?
Between them Bob and Nico certainly set a debate raging – Good code, or Crappy code?
Wednesday finished with 40 of us in Chutney’s curry house.
A comment to my post on “Three ways to run a stand-up meeting” asked: “Can you give an example of the ‘hidden’ impediments?” so here goes.
First: know the difference between a block and an impediment. A block stops all work, they are seldom hidden because people can’t get on with what they are doing. A impediment is something which gets in the way, slows you down, saps your morale.
Fortunately, or maybe unfortunately, software people are very good at routing around blocks. They find ways to “get stuff done” even if it is not the best way, the fastest way, or the “right way”. So blocks often become impediments. Unless we strive to impediments our teams will not perform to their maximum.
One nasty form of impediment is the “I’m blocked so I’ll make work to look busy.” The work which is created is seldom as valuable as that you are blocked from doing and even worthless.
Anyway, examples of impediments, especially hidden one:
• Vendor is not responsive: someone is waiting on a vendor to deliver something and it isn’t happening; or you are waiting on a vendors technical support, or perhaps you need information from the vendor before deciding whether to use their product or someone elses.
• Build problems: the build is broken, or you need someone else to fix their bit, or you are waiting for access rights, or the compiler seems to have a bug, or … the list goes on
• Waiting on another team: particularly test, source control, user interface, tech support, etc. Idealy we want each team to be vertical, that its, to be self sufficience, to contain the skills and authority to get a job done without needing action from others. But this doesn’t happen as much as it should so you need another team to do something. At this point problems occur because the other team doesn’t have the same prioirities as your team
• Upgrading compiler, OS, app server, etc: some piece of software (or perhaps hardware) needs to be upgraded. So instead of getting on with the task in hand someone is diverted to upgrade the system. And when this takes long than expected, or hits problems, then it becomes an impedimant and even a block.
• Bug – typically in a library: you can’t get on with your own work because of someone elses bug. Ideally you can just jump into their code and fix it but…. if the bug is in a third party library then it not quite so easy. And if the problem is with the compiler, or a vendor you get to one of the problems above.
• Database changes: databases teams seem to work in a completely different temporal dimension . Too often I meet teams who can’t progress because a DB schema change is needed, or the meta-data is a problem, or …. The real solution is two fold: simplify designed and reduce the need for complex databases, and ensure the team has database skills itself.
• Waiting on a management decision: all too common, management can’t make their minds up whether to do it like X or like Y. A particularly nasty version is when you’ve asked for something “Can we buy Z?” and rather than say “No” you are kept hanging on. If they just said “No because…” you could address the reason or find another way of doing it.
When team members can’t report real achievements in a Scrum meetings they usually report ”what they have done“ which includes ”why there isn’t an achievement“. Thats the point at which these kind of impediments are mentioned. A good Scrum Master / Meeting Leader / Agile Coach will spot these issues and move them to impediments.
If you have any more examples of impediments please add them as comments below.
Only a few weeks ago I was pleased Mark Nakamura translated some of my blog entries to Japanese. Now I’m being translated to Russian.