Merce

Technologies: the regular stuff

Used here every day

Apache, Tomcat, Eclipse These three dissimilar components form the heart of the stack on which we develop and deploy most of our Web applications. . . .

Java We have been working with Java for more than a decade. Almost all the work done has been for browser-based applications, initially as servlets, later with the STRUTS frameworks. . . .

Javascript We have been using Javascript for many years, initially in the raw, later through toolkits to shield our code from browser-specific vagaries. We use Dojo and Digits frequently for recent work. . . .

Template engines We rolled our own template engines for Perl/CGI work more than fifteen years ago. Today, for Java-based Web applications, we use Velocity if we can. We never liked JSP much. . . .

Unix and Linux We live and breathe Unix and Linux. Our management team uses Linux on their laptops; all our servers run Linux. We've developed projects on HP-UX (about twice), IBM AIX (many projects), Sun Solaris (once or twice) and various flavours of Linux (every day). Linux is our home environment. . . .

Relational databases We have worked with MySQL practically for all our initial projects. In the last 5-7 years, most of our work has been on PostgreSQL and IBM DB2, with a smaller number on Oracle and Microsoft SQL Server. . . .

Perl Our founding team starting building large applications in Perl 4 in 1994. We have a strong culture of Perl work even today for back-end daemons and batch processing, though Perl/CGI has given way to Java for Web-based UI coding. We would be lost without Perl. . . .

PHP We have seen PHP from a distance for more than a decade, and have done work in PHP in the last 5-7 years, typically for customising and extending existing PHP-based applications like Drupal and ATutor. . . .

Subversion We moved from CVS to SVN in 2008, and have continued to use it since then. We use SVN on all projects currently and weekly check-in is a minimum rule for all developers. We have set up auto-replication and backups of our SVN repositories. . . .

RELATED READING

  • Models of engagement

    We engage with customers in various models, depending on their requirements.

  • Case studies

    A collection of our case studies, indicating the range and depth of work we have done