Meet the team: Nick Maidment

Nick has been testing .NET Reflector for quite some time now, and his sinister chuckle has become the hallmark of particularly evil / fiddly bugs. Persistent and sharp-eyed, the master of the test machine branded “coggy” speaks softly, but carries a large testing framework.

Nick Maidment - Machiavellian Tester

What’s your background?

Previously I’ve worked in support, but having seen the kinds of bugs that prowl out there in the wild, I’ve been hoping to make a difference by catching them during testing. In the last couple of years it’s largely been various flavours of .NET framework and SQL server. Further back, I was involved with oracle databases in Solaris environments. I’m always keen to learn about technologies I’ve not yet used.

What are you working on at the moment?

I’m currently testing Reflector 7.5 and working on some of the engine automation tests

If you could make one change to the .NET Framework, what would it be?

Rather than talk about changes to the .NET framework, I’d really like some of the proposed c#5 features (like async) to be fully released now. Anything to make writing asynchronous code less annoying!

What’s the most interesting / satisfying project you’ve worked on, and why?

My current project, .NET Reflector, is probably the most interesting. There are so many places for it to go wrong, and so many interesting bugs to find. The team is a good bunch of people who work hard and listen to any input I have.

What do you do to relax?

Mostly I read, watch TV and play Video Games. I’ve been enjoying the latest runs of Sons of Anarchy and Dexter of late and I’m looking forward to getting my hands on Skyrim later this month.

What’s your favourite book (technical and / or non-technical), and why?

In terms of graphic novels, I really like Transmetropolitan. It’s something of an ode to Hunter S Thompson. I’ve also been reading a Song of Fire and Ice, though I largely picked up on this because of the TV show Game of Thrones.

Do you have any advice / suggestions / questions for other testers?

Don’t cry wolf, and pick your battles. Be sure that you can re-produce any issue that you find, and make sure it’s serious enough that it’s going to get fixed. I’m still comparatively new at this, however, so any advice is welcome 🙂

This entry was posted in team and tagged , on by .

About Chris

A background in technical publishing; editing articles on Simple-Talk and SQLServerCentral for 3 years now. When I’ve not been editing articles, I’ve been editing or proofing books covering everything from .NET performance testing to Exchange Server, XML Schema Design, and the SQL Server Query Optimizer. I built a few websites to help pay my way through college, but the less said about them, the better.

One thought on “Meet the team: Nick Maidment

  1. Ritchie Annand

    Async programming used to frustrate the crud out of me, and I still don’t understand why the IAsyncResult in .NET didn’t come with an exposed EndInvoke so that you could make a proper separable callback with it using your own class.

    I have been waiting for a feature like ‘async’ to happen for a very, very long time (, but we have a set of componentry stuck in pre-.NET 4.0 which will have to be replaced before we can do this. *sigh* 🙂


Leave a Reply

Your email address will not be published. Required fields are marked *