3 ms·

Yeah, I think especially in finance companies would be willing to pay for support and feature development. There has to be a way to monetize the project and mak

• Asymmetryk 5y ago
  I am probably not actually being realistic in terms of economic results and ROI, but the FIX library GP seems well established - making it documentation that's the case I would like to put forward : any code in a critical path, and what better than a financial exchange subsystem, can be purchased from any number of vendors with support, but how many have genuinely caring, intelligent, thoughtful and usable beyond the immediate remit, thorough and readable documentation? Cloth letter binder and loose leaf format with theoretical introduction, theory of operation, enumerated common implementation errors for examples together with laying out conventions for the payload / XML DTD - the docs you can write tests and tools against without the code.... I have signed off on a pretty penny or two to obtain docs like this, and hundreds of dollars per copy is totally reasonable. I'd thin film laminate select chapters and affix a dry wipe pen inside (how much would it be to custom some from All express?) and by the sounds of this situation I think you could see a standard adoption and satisfying return. Boxes, ring bind, shrink wrap and a 2nd color printed sparingly add up to something that management likes a lot, usually. Professional product support bridges the economicd to enterprise fees, imo..