02-03-2011, 01:56 PM
I am trying to find a happy medium here between making the build process so much a community effort that I never get it done (or double/triple my work load) and maximizing the potential benefit for everyone involved.
I can't go building one version for person A and one version for person B and another for person C, when I already have an estimated 6 month backlog. So... I'm going to do it this way. Script gets posted. Errors pointed out, suggestions made. Then I choose what goes in and what does not, and one version is built. Time to find errors and make suggestions is going to be between 6 and 24 hours, depending on circumstances.
This is going to slow down my build process, and force me to catch up by posting and building in batches at a time. I'll evaluate the efficiency of this method over time, and if it works better, I'll keep using it. If it results in infighting, arguments, upset people, frustration, loss of efficiency, etc. I'll find a way to work that corrects the deficiencies found.
Today I am going to build Learn Arabic faster and more easily. But since that script is a template, all I have to do to build the rest is do a find/replace operation on the language name for each variant, and then save the new script as the proper name. This is easy to do without error because I simply have the text editor count the number of times the language name appears, and then report to me how many instances of it have been replaced each time. As long as those two numbers match, I know I have a clean change.
Since that is the case, I can build all the language learning scripts in one batch. Then I'll get to the programs SubTest pointed out.
Suggestions for this title are closed. Thank you to everyone who contributed.
I can't go building one version for person A and one version for person B and another for person C, when I already have an estimated 6 month backlog. So... I'm going to do it this way. Script gets posted. Errors pointed out, suggestions made. Then I choose what goes in and what does not, and one version is built. Time to find errors and make suggestions is going to be between 6 and 24 hours, depending on circumstances.
This is going to slow down my build process, and force me to catch up by posting and building in batches at a time. I'll evaluate the efficiency of this method over time, and if it works better, I'll keep using it. If it results in infighting, arguments, upset people, frustration, loss of efficiency, etc. I'll find a way to work that corrects the deficiencies found.
Today I am going to build Learn Arabic faster and more easily. But since that script is a template, all I have to do to build the rest is do a find/replace operation on the language name for each variant, and then save the new script as the proper name. This is easy to do without error because I simply have the text editor count the number of times the language name appears, and then report to me how many instances of it have been replaced each time. As long as those two numbers match, I know I have a clean change.
Since that is the case, I can build all the language learning scripts in one batch. Then I'll get to the programs SubTest pointed out.
Suggestions for this title are closed. Thank you to everyone who contributed.
Subliminal Audio Specialist & Administrator
The scientist has a question to find an answer for. The pseudo-scientist has an answer to find a question for. ~ "Failure is the path of least persistence." - Chinese Fortune Cookie ~ Logic left. Emotion right. But thinking, straight ahead. ~ Sperate supra omnia in valorem. (The value of trust is above all else.) ~ Meowsomeness!
The scientist has a question to find an answer for. The pseudo-scientist has an answer to find a question for. ~ "Failure is the path of least persistence." - Chinese Fortune Cookie ~ Logic left. Emotion right. But thinking, straight ahead. ~ Sperate supra omnia in valorem. (The value of trust is above all else.) ~ Meowsomeness!
