productivity - What is Important to you in your choice of developer tools? -

My company sells developer tools itself as a developer, it is not hard to believe what is important to me It's important to many other developers:

1. In our case, the thing in which we have the shortest time is time, so I spend money on things like Microsoft Team Foundation Server I am ready to manage a software project in an integrated fashion Sector is well integrated with Visual Studio various aspects. And installShield Professional, which seems to be more than I think, how much time it saves me, we arguably spend a lot more on the latest and greatest computers and monitors. I have made two out of gaming parts from gaming parts - in one year they are still fast above the line of Dell Precision which we had recently purchased (I was very busy making one at that time)

   • I care a lot about performance and efficiency, so I'm happy to spend money on equipment which helps us to create a faster and smaller product.

   • I am satisfied with the tools we use with one exception - Support It is amazing how bad support from some very successful companies can be.

   • I have a good example of point technical book (K & RC) I mean from this) or the article is a verbatim one.

So, all this probably comes in our product and company:

1. We Do not be embarrassed to charge for your software. We are not the most expensive options, but we are certainly not least expensive.

   • Before we spend a lot of time on a feature display before releasing it, we have spent 27 months on V1 of our product - and read it, write and calculate it Compared slightly in comparison.

   • To ensure that our customers (who are the developers) get good support, our developers (including me) turn to provide phone and e-mail support .

   • We do not literally spend time on the doctor. We have a short / welcome start / tutorial section in our help, but we spend most of our documentation efforts to write typing API reference materials and to create samples that often address the questions our customers ask.

For each of these topics, we can arguably make some smarter:

1. We also have a "free" version with a less expensive limited edition (less features and / or less support) or even suitable borders.

   • We can make more features and spend less time honoring each of them.

   • We can hire the less experienced and less expensive person to support the first line.

   • We write or hire documents that are written by a full time documentation person instead of another developer.

What's important to you?

If you want to get your software here:

< Li> Keep a full-featured demo;
• Stay up-to-date about pricing as soon as your website says "Contact us for pricing" I have lost interest;
• Enough is inexpensive that it can be purchased without getting approval from the CEO. Look at Jira relatively cheap, extremely successful;
• Best Eclipse and Netbeans are free and packed with features but when it comes to Java, I gladly license $ 600 per license because it is better (Ihho) the way its better;
• Competition. If you are doing a source control tool, how well does it compare subversion and relevant plugins (VisualSVN is cheap, TortoiseSVN is free);
• Make me more productive and can not be found in my way (the rational tool is on my way) Another example of this is where the software refuses to work because there is no licensing server to talk about it. Could. Madness about theft will kill you;
• Designed to help programmers and companies have not been designed to be sold (there is no difference)
• Be responsive in support and feature requests; And
• Keep the product release cycle relatively fast, if I'm waiting for a big release for 2-3 years, then sorry that I've lost interest and you've lost the ground for the competition.