Developer 1: “I think we need to sort this array by it’s value”
\nDeveloper 2: “You should write a hash, store the values in the hash, and then sort it”
\nDeveloper 1: “That’s what I just said…”
\n…
\nDeveloper 1: “Alright, I’m going to sort this array”
\nDeveloper 2: “Alright, but before you do that… I want you to create a hash. Put the values into the hash and then, using the sorting function, sort the array.”
\n…
\nDeveloper 1: “This idea your purposing contradicts statements you previously made about your algorithm. I mean, what you’re purposing causes the work done by previous scripts to be rendered useless or is in essense saying that previous scripts aren’t doing their job right.”
\nDeveloper 2: “No. We are making these changes to the results of the script, we are creating better results down the line.”
\nDeveloper 1: “But, according to you, if those scripts truly did what we designed them to do, then we shouldn’t need to manually edit the results”
\nDeveloper 2: “I don’t understand what you’re getting at. We are improving the results by editing them.”
\nDeveloper 1: “But if the scripts… did their job right… then… *sigh* Whatever”
\n…
\nDeveloper 2: “You know… I thought about it… And I think you’re right, there is something wrong with the algorithm”
\nDeveloper 1: “Okay”
\nDeveloper 2: “But we’re still going to edit the results to better suit what we think should be there…”
\n…
\nDeveloper 1: “How do you plan on going about tackling this problem?”
\nDeveloper 2: “Well… we can try this, this, and this, and then have the algorithm do this…”
\nDeveloper 1: “We’ve already tried that and it didn’t turn out too well, you might want to account for cases such as this in your solution.”
\nDeveloper 2: “I don’t see why this case would occur”
\nDeveloper 1: “Believe me, it often does.”
\nDeveloper 2: “Stop being so pessimistic, we can do anything.”
\nDeveloper 1: “No… I’m just saying you might want to account for this case when you come up with your solution, it’s what makes this problem challenging”
\nDeveloper 2: “You shouldn’t give up just because it’s hard. We can do this, we have a week. You and I should combine our forces, share our ideas, and hammer up a solution that works.”
\nDeveloper 1: “But… I’m already letting you know what I think on it”
\nDeveloper 2: “Trust me, it’ll be okay. We at the very least 75% of the time the script will do what it’s supposed to.”
\nDeveloper 1: “But, it already does that right now…”
\nDeveloper 2: “We’ll see, okay? We’ll see.”<\/p>\n
Ah… I forget how working in teams can sometime feel like running head first into a brick wall.<\/p>\n","protected":false},"excerpt":{"rendered":"
Developer 1: “I think we need to sort this array by it’s value” Developer 2: “You should write a hash, store the values in the hash, and then sort it” Developer 1: “That’s what I just said…” … Developer 1: “Alright, I’m going to sort this array” Developer 2: “Alright, but before you do that… … <\/p>\n