Comments on: Alabama QSO Party County Identifiers http://www.qsoparty.com/rules/alabama-qso-party-county-identifiers.html Details about making the most of the many QSO Parties Mon, 11 Jan 2010 21:26:43 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: admin http://www.qsoparty.com/rules/alabama-qso-party-county-identifiers.html/comment-page-1#comment-1986 admin Thu, 30 Jul 2009 22:34:05 +0000 http://www.qsoparty.com/?p=113#comment-1986 Perhaps, but the point above is AL rules are too loose if they support both 3 and 4 letter abbreviations. Perhaps, but the point above is AL rules are too loose if they support both 3 and 4 letter abbreviations.

]]> By: Pat http://www.qsoparty.com/rules/alabama-qso-party-county-identifiers.html/comment-page-1#comment-1908 Pat Fri, 17 Jul 2009 14:52:17 +0000 http://www.qsoparty.com/?p=113#comment-1908 If software is what holds back rule changes in a qso party then we have a problem. Either the software author should spend the time to code in such a why that things like valid exchange lists, points, modes are dynamically configurable or they should be prepared to make changes. Software, by its very nature, should be configurable. Yes they won't get it exact the first time, but a little forethought will go a long way to making a software program better. Then the software author can concentrate on fixing bugs rather than fixing configuration. This is my anti-hardcoding rant #2738. If software is what holds back rule changes in a qso party then we have a problem. Either the software author should spend the time to code in such a why that things like valid exchange lists, points, modes are dynamically configurable or they should be prepared to make changes. Software, by its very nature, should be configurable. Yes they won’t get it exact the first time, but a little forethought will go a long way to making a software program better. Then the software author can concentrate on fixing bugs rather than fixing configuration.

This is my anti-hardcoding rant #2738.

]]>