• Six years Java experience with technologies including J2EE, servlets, BEA WebLogic, JDBC, JUnit, XML, XSLT and WAP/WML.
• Five years XML experience, including DOM/SAX parsers, XML Script, XSL, XML Schemas, XHTML and mobile technologies such as WML and VoiceXML. Technical reviewer for several XML programming books published by Wrox Press, chapter author for "Professional XSL".
• Eight years Linux experience, including system administration (security, mail, firewalls, backup, CVS, Perforce, RAID, etc) and Perl programming.
• Reasonable French (was good, but now out of practice) and some German.

I lead the Infrastructure Group at Digital Rum, which has responsibility for server and application architecture, the deployment model, build system, and core design patterns. My job includes line management responsibility for a team of developers, and I report directly to the Head of Development.

From the outset I was heavily involved in producing version 2 of Digital Rum's m-Commerce platform, designed to replace our servlet-based "Digital Shopping Assistant". Maitai, the rum-cocktail codename for v2, is a J2EE system based around WebLogic and Oracle, running on Solaris. Maitai provides shopping and ticketing services, delivers WAP, web and SMS-based content, and interfaces with a variety of vendors and co-branding partners. Digital Rum's customers include Orange, Vodafone and T-Mobile, and our ticketing partners include Odeon and Warner Village Cinemas, and The Way Ahead Box Office and Ticketmaster.

The Infrastructure Group sits between Development and Operations, and has responsibility for producing and supporting a number of critical components used daily by the other teams. We develop and support the build and deployment systems, perform load testing and performance analysis of our applications, and develop and support automated testing tools for our live services.

I introduced the team to Bugzilla, which we use for bug and change-request tracking, and to CVS, which we used for revision control as a replacement for Source Safe. We're now using Perforce, and I have implemented an automatic build/test system for change submissions, as I did at DecisionSoft.

I worked for DecisionSoft as an intern during my university vacations between Christmas 1997 and Easter 1999, and joined the company full time when I graduated in July 1999.

DecisionSoft develop a range of XML processing tools using the XML Script transformation language. XML Script is similar to XSLT, and I was heavily involved in its creation. My main duties included development and support of the core processing kernel, which was written in C++, and on the specification and development of systems using our XML Script server software. I used C++, Xerces, Java and Perl, and developed under Linux, Windows NT and Solaris. We used CVS and Bugzilla for version control and bug tracking, and custom Perl scripts for automated regression testing across platforms. These scripts automatically email diffs to developers, then build and test each code tree whenever a change is submitted, and were inspired by the Mozilla automatic build system. Knowing when the build is broken, who broke it and how they broke it greatly improved our development process!

Whilst working for DecisionSoft on their XML Script product, I was invited to be a technical reviewer for the book Professional XML. This involved reading, correcting and commenting on draft chapters of the book. I was also a technical reviewer for the book Beginning XML.

Wrox invited me to be a chapter author for their book Professional XSL, to which I contributed two chapters.