I think that including system specs of the machine on which the test was run, should be a [bold]requirement[/bold]. Providing not just speculatation, but concrete numbers to analyze and compare from various configurations. Everyone wants to know if their code will run on a "typical" end user's system. This is a good way to find out.
To DDT's point, I think that seeing all of the different ways to approach a particular coding challenge offers everyone an opportunity to learn something (good and bad). Instead of just seeing one person's perspective on speed issues (per the link).
It goes without saying, but I'm going to say it anyway, no one should be ridiculed/humiliated/hassled for contributing good or bad code. Let's keep this above all of that nonsense, so that everyone (noobs and code wizards) can feel comfortable with their efforts. If there are any comments to be made let's keep them constructive. This is the only way to encourage people to make an effort and contribute.
Count me in!
Andy
To DDT's point, I think that seeing all of the different ways to approach a particular coding challenge offers everyone an opportunity to learn something (good and bad). Instead of just seeing one person's perspective on speed issues (per the link).
It goes without saying, but I'm going to say it anyway, no one should be ridiculed/humiliated/hassled for contributing good or bad code. Let's keep this above all of that nonsense, so that everyone (noobs and code wizards) can feel comfortable with their efforts. If there are any comments to be made let's keep them constructive. This is the only way to encourage people to make an effort and contribute.
Count me in!
Andy