Many systems are already in production when we get asked to take a look or, interestingly, a few weeks before deployment. The latter is not optimal, but it's still better than not contacting us until something goes wrong. At Open Query we like to focus on problem prevention and skills transfer. This saves so many hassles and thus over time saves money for the client = win.

The reasons for asking for external input late(r) are diverse, and generally not even technical or financial. But we all know the saying "prevention is better than a cure" and that has benefits for a company's bottom line; potentially even its future. Particularly in the current economic climate, such advantages are gold.

Another other important aspect is scope. MySQL operates in a larger architecture; we can look at the server and improve the configuration there, but if queries are just wrong, they need to be fixed in the application. …

Arjen & gang are looking for skilled and enthusiastic colleagues!
Essentials

• guru level practical skills in MySQL schema/query design, server administration and tuning;
  
• expertise with common dev and deployment infrastructure (mainly Linux but also other *nix and Windows);
  
• freedom to travel without restriction;
  
• self-motivated, ability to work independently (from anywhere - good Internet access required);
  
• excellent written/verbal English, comfortable public speaker.

Being a small, company, the range of possible work tasks can be quite diverse, although you are not required to be able to do everything. That said, your application will be more highly regarded if you exhibit a broad range of skills and interests, both directly technical and otherwise.
Desirable abilities

• shell and Perl scripting;
  
…

Over at ITToolbox Tarry has another blog . He posted an article where he tried to debunk some myths about open source. I feel he needs some help there :)

Let's start with his second Myth , Open Source is Free. Off course it isn't , you need to invest your own time to get familiar with it or pay other people to use it. Compare it to building a house ... you can build one if you have the skills and the time , but you still need to pay for the bricks and the mortar, or you can pay someone who has the skills to build one for you. With software there used to be a similar thing. You could buy software, then install and configure it yourselve, or you could hire someone more skilled than you to install and support it when you run into problems. Now take away the fact that you have to …

I've been hearing a lot of good things about our support guys. How does the community feel? Do you think that we're doing a good job?