guestman
maybe you should of joined overclockers uk to help take down p3d hehe. long time lurker and have been reading these parts of the forum for a long time and I do agree that P3D are taking the fun out of it with the " cheating " if you like.
Greetings
guestman, and welcome to our forums
I think it's nice of other teams to say hello and to exchange thoughts and experience. We have all common interest and also we have the common goal to find either an answer, or at best, a cure.
You did a fantastic job in the last Challenge, and we thank you for pushing to the very last day. You made this challenge a really fun and interesting one. You even pulled computers out of your sofa
.
I fully understand the Overclockers UK's urge for a revenge from last time. However, most crunchers around signalize that a 30 day challenge is too long.
Many think it's not ok to ask a team to dedicate resources to one single project for such a long time.
Also, we have a limited attention span as they say
About the ongoing "Ultimate Team Challenge 2015"
Some not so good stuff happened. First it was too soon, too long lasting, and then it was this behavior of P3D.
Most of us entered this challenge out of respect for Overclockers UK, and your wish for revenge.
However, when P3D presented 7-10 days of work the first day, they pulled the plug out of this challenge right there and then.
Many of us just pulled out, leaving just a fraction of our resources.
One can discuss bunkering day in and day out, but there are consequences. One of them we saw right there, people lose interest, and quit.
When a project invite all teams they can get to a, say 10 day challenge, isn't the meaning that the teams compete about how much work they can present over 10 days?
Then why does one team present 20days of work in a 10 challenge?
If they wanted so bad to work on those WU's 10 days ahead, they could, but why not deliver the ready work when ready?
Also, most WU's need validation.
When a big team deliver thousands of thousands of WU's down for validation at day one of a challenge, it will put a crazy strain on the project's hardware, possibly straining the over all performance for the whole project, slowing down the validation time for all other participants.
When a big and strong team as P3D show this tactics, they also show smaller and perhaps new teams how to.
This un-culture may harm the whole challenge spirit among many good teams.
The losers will be the project itself, and that's the exact opposite to what we crunchers want.
We are here to help out the projects.
Bunkering is not cheating, it's a lack of better knowledge.
post edited by Orange_1050 - 2015/01/07 00:22:38