How did you come to be working at Red Gate?

I’ve been working at Red Gate for nine months; before that I had been at a multinational engineering company. A number of my colleagues had left to work at Red Gate and spoke very highly of it, but I was happy in my role and thought, ‘It can’t be that great there, surely? They’ll be back!’ Then one day I visited to catch up them over lunch in the Red Gate canteen. I was so impressed with what I found there, that, three days later, I’d applied for a role as a developer.

And how did you get into software development?

My first job out of university was working as a systems programmer on IBM mainframes. This was quite a while ago: there was a lot of assembler and loading programs from tape drives and that kind of stuff. I learned a lot about how computers work, and this stood me in good stead when I moved over the development in the 90s.

What’s the best thing about working as a developer at Red Gate?

Where should I start? One of the great things as a developer at Red Gate is the useful feedback and close contact we have with the people who use our products, either directly at trade shows and other events or through information coming through the product managers. The company’s whole ethos is built around assisting the user, and this is in big contrast to my previous development roles. We aim to produce tools that people really want to use, that they enjoy using, and, as a developer, this is a great thing to aim for and a great feeling when we get it right.

At Red Gate we also try to cut out the things that distract and stop us doing our jobs. As a developer, this means that I can focus on the code and the product I’m working on, knowing that others are doing a first-class job of making sure that the builds are running smoothly and that I’m getting great feedback from the testers. We keep our process light and effective, as we want to produce great software more than we want to produce great audit trails.

Tell us a bit about the products you are currently working on.

You mean HyperBac? First let me explain a bit about what HyperBac is. At heart it’s a compression and encryption technology, but with a few added features that open up a wealth of really exciting possibilities. Right now we have the HyperBac technology in just three products: SQL HyperBac, SQL Virtual Restore and SQL Storage Compress, but we’re only starting to develop what it can do. My personal favourite is SQL Virtual Restore; for example, I love the way you can use it to run independent test databases that are all backed by a single compressed backup. I don’t think the market yet realises the kind of things you do once you are using these products. On the other hand, the benefits of SQL Storage Compress are straightforward: run your databases but use only 20% of the disk space. Databases are getting larger and larger, and, as they do, so does your ROI.

What’s a typical day for you?

My days are pretty varied. We have our daily team stand-up meeting and then sometimes I will work alone on a current issue, or I’ll be pair programming with one of my colleagues. From time to time we give half a day up to future planning with the team, when we look at the long and short term aims for the product and working out the development priorities. I also get to go to conferences and events, which is unusual for a development role and gives me the chance to meet and talk to our customers directly.

Have you noticed anything different about developing tools for DBAs rather than other IT kinds of user?

It seems to me that DBAs are quite independent minded; they know exactly what the problem they are facing is, and often have a solution in mind before they begin to look for what’s on the market. This means that they’re likely to cherry-pick tools from a range of vendors, picking the ones that are the best fit for them and that disrupt their environments the least. When I’ve met with DBAs, I’ve often been very impressed at their ability to summarise their set up, the issues, the obstacles they face when implementing a tool and their plans for their environment. It’s easier to develop products for this audience as they give such a detailed overview of their needs, and I feel I understand their problems.