** This thread discusses the article: Third-Party Software **
Ok, Bob, time to get back into the real world. First, consider how large (in terms of revenue) a company would be if it only had 20 users. A $3000 expenditure in such a company would probably be a BIG deal. Especially when you consider how many of those 20 users would be programmers (maybe 1?). You'd be asking the CFO (the most likely IT czar of such a shop) to spend $3000 on a tool for one person who cannot yet demonstrate how much more productive she's going to be using it. Right - like that's going to fly! I have to differ with your illustration of Systemworks, too. Again, if you were only buying Systemworks for the programmers (after all, your article was supposed to be talking about programmer tools), you'd have only spent $119 in my 1-programmer, 20-user shop. Much easier to justify. In our 400 user, 5 programmer shop, we use a PC software product that makes it easy to create scripts to run simple to extremely sophisticated Windows processes. The product costs $500 and we only need one copy, of which any of my 5 programmers can use (but which normally only 1 of us uses). We get great utility from the product and it's paid for itself many times over. Imagine what such a product would have cost if it were priced like typical AS/400 software on our iSeries 825 machine? When we originally purchased this product we were pretty sure it would do what we wanted - but we weren't completely sure. But, $500 was easier to risk than $3000. A $3000 expenditure in our shop would definitely get scrutinzed. Sometimes it's easier to slog through writing it yourself (and you tend to learn more) than it is to spend the time creating a cost justification. And, you fail to recognize the additional investment of time spent learning the tool. Yes, some are very single purpose and easy to learn. Others are much more flexible and exploiting that flexibility means you have to spend a fair amount of time learning it. Certainly, in the case of the $500 tool above, because it was really a language-like product, we spent a lot of time learning it. I wish programmers in general could adopt a personal tool-kit mentality and that programmer software products could be priced to support that, similar to car mechanics and their tools. In this vision, programmers would be able to purchase and add to their own personal arsenal of programming tools, which could be transported with THEM from job to job. It would certainly make it easier for people like me to risk purchasing and trying a tool without knowing that it would actually benefit me. Ok, you can return to fantasy world now. ==Kevin

Reply With Quote