Etiquette, etc. in Architecture Posted October 18, 2001 Dear all, This bulletin board is an extremely valuable resource, which is why I have continued to follow it for several months. Not only does NNA check in now and then with important information, but the users have supplied me with invaluable and intelligent advice, warnings, and perspectives for the future of the application. I would hope that a few occasions of intemperate expression on the part of some do not spoil anyone's appreciation of the discussion, either at NNA or among VW users. Both users and NNA engineers should spend more effort expressing appreciation for the time spent by each other on this site. It would be nice if NNA could respond more frequently, but I am sure we all understand that they are spread thin. It would be equally nice if users would think twice about venting their frustration with the program and the software engineering process in a way that might create bad feelings. Software is not an easy thing to create, especially in a real world with budgets, deadlines, and marketing. That said, I think we all know how it feels to use an imperfect product day in and day out. Let me ask both "sides" the following question: how much would it be fair to pay for a program that was significantly more useful, bug-free, and responsive to user requests for modification? I'm now a grad student, but used to work in architectural offices and managed the CAD systems there. I'm positive that my former firms would have paid 2-3 times as much for a program with improved capabilities and productivity. Is there a way to increase the ability of NNA to hire more programmers without threatening the base of new users attracted to the initial buy-in price? For example, would architects and engineers be willing to pay extra for a subscription that gives professionals faster fixes and access to new features that others would have to wait for the next release to get?