User talk:TheGambit

DropTest
Thank you for sharing test results. However, please refrain from creating blank templates such as:
 * Template:DropTest/Beyond the Call/2
 * Template:DropTest/Cardassian Hospitality/2
 * Template:DropTest/Cardassian Hospitality/3
 * Template:DropTest/Long Distance Call/3
 * Template:DropTest/On Their Heels/2
 * Template:DropTest/Putting the Free in Freedom/2
 * Template:DropTest/Putting the Free in Freedom/3
 * Template:DropTest/Pretense of Mercy/1

Unless you're contributing actual data, it would be better not to create the page at all because a blank template prevents the auto-filling of information such as the current month/year and the username of the actual contributor. Generally avoid making too many templates with error messages. If you don't add anything of substance to those pages in the next few days, I will have an admin delete them since those errors are an eyesore. The default placeholder template is much preferable CodeHydro (talk) 21:28, 7 June 2016 (CDT)


 * Also please be sure to give yourself credit when adding data. [ This revision] shows how (note adding ). CodeHydro (talk) 06:47, 8 June 2016 (CDT)


 * Thanks you for your message on my talk page. The way get it to show up faster is to add  to the end of the URL. That is,   becomes  . By the way, to sign your comments, type   after your messages. CodeHydro (talk) 08:40, 8 June 2016 (CDT)

DropTests: order of contributors
Hi! Please do not change the order of contributors in DropTests without reason, and especially not without ALSO changing the order of operands/data in both the |run= line and all the result lines; they must be kept in sync with the contributors, otherwise everyone will lose the connection between name and datasets, which will lead to errors when adding data. Also, another friendly reminder to please not forget to add yourself to the |by= line when adding your data. --Crunch (talk) 11:23, 26 June 2016 (CDT)


 * The order was already adjusted by Captain deMarco. In order of contributions he put himself before others.
 * I also have no idea what you mean with "and especially not without ALSO changing the order of operands/data in both the |run= line and all the result lines; they must be kept in sync with the contributors, otherwise everyone will lose the connection between name and datasets, which will lead to errors when adding data."


 * I figured i was fixing the order of contributors. I don't see particularly the point of showing who contributed other then bragging rights on the published page.
 * If there is some internal issue with the template for the contributors to be listed then that's different.


 * I don't really care about the order, although some like to keep it from highest number of runs to lowest. You can change the order any way you like - BUT if you do, you must also adjust the order of all data, and not just the names - otherwise it will be impossible to reproduce which data belongs to which contributor, and people can no longer add data to their sample set. For example, [ here] you moved Captain deMarco to the end. If you look at the statistics on the left, CodeHydro had 58 samples, Captain deMarco had 25, I had 13, and you had 7. Then you changed the order of NAMES to CodeHydro, Crunch, TheGambit, Captain deMarco - but kept all the data sample in the original order, which doesn't make sense. Now it looks like I did 25, and Captain deMarco did 7. People work on so many DropTests at the same time, they can't check and re-check every data entry each time they want to add samples. For example, I use a script to automatically sum my individual counts I list at the end of each Drop Test, and then replace my data with these new values. As I was now marked as "|by2=" in this DropTest, I would of course assume the second dataset would be mine, and therefore replace all these numbers with the new values - but these are Captain deMarco's samples, which I would then have destroyed, while doubling mine. Is that not obvious? --Crunch (talk) 18:02, 26 June 2016 (CDT)
 * It's not about bragging rights. It's about the sourcing of information. We need to be able to identify which data set came from which tester without having to spend an hour examining the edit history and raw data. If nothing else, it helps testers identify their own data set so that they edit the correct values rather than some else's, as Crunch pointed out— CodeHydro (msg) 22:07, 26 June 2016 (CDT)