We would like call all participants to re-focus the discussion to the initial goal of this project. This has already been stated before, but without much effect.
The main goal of this project, and that's the main reason we have invested our time on it, is to promote Scala and help the beginners among us to get quick-started with Scala.
The last days we have seen (read) very interesting discussions here. However, very few were focusing on sharing knowledge and help novice Scala enthusiasts.
We understand that many of us want to push the boundaries, try different implementations and improve the performance by a few milliseconds. That's great, but we can be sure that many have questions about the syntax and the collections API.
On the other hand we don't want to demotivated those willing to discuss math and algorithms. Therefore we have the following suggestion: instead of creating one issue per Euler Problem we'll create two issues. For instance, "Problem001 [Language]" and "Problem001 [Algorithm]".
If you come up with a solution and want to share and discuss the efficiency of your algorithm, you add a comment on the [Algorithm] issue and ask for feedback. Otherwise, you just announce your solution on the [Language] issue.
If you feel overwhelmed by the syntax and discussions on the [Algorithm] side, you can configure your email client or gmail or yahoo mail or whatever to mute those messages. As such you don't get flooded by emails during your working hours.
We do expect that the more experienced between us will not mute the [Language] issues and will be helping our fellow members. But of course, nobody is obliged to do so.
Sharing your knowledge and being able to explain the beauty of Scala in a simple and accessible way also reveals your proficiency with the language. And sometimes it is more rewarding than 30ms performance gain. :-)
Dear all,
We would like call all participants to re-focus the discussion to the initial goal of this project. This has already been stated before, but without much effect.
The main goal of this project, and that's the main reason we have invested our time on it, is to promote Scala and help the beginners among us to get quick-started with Scala.
The last days we have seen (read) very interesting discussions here. However, very few were focusing on sharing knowledge and help novice Scala enthusiasts.
We understand that many of us want to push the boundaries, try different implementations and improve the performance by a few milliseconds. That's great, but we can be sure that many have questions about the syntax and the collections API.
On the other hand we don't want to demotivated those willing to discuss math and algorithms. Therefore we have the following suggestion: instead of creating one issue per Euler Problem we'll create two issues. For instance, "Problem001 [Language]" and "Problem001 [Algorithm]".
If you come up with a solution and want to share and discuss the efficiency of your algorithm, you add a comment on the [Algorithm] issue and ask for feedback. Otherwise, you just announce your solution on the [Language] issue.
If you feel overwhelmed by the syntax and discussions on the [Algorithm] side, you can configure your email client or gmail or yahoo mail or whatever to mute those messages. As such you don't get flooded by emails during your working hours.
We do expect that the more experienced between us will not mute the [Language] issues and will be helping our fellow members. But of course, nobody is obliged to do so.
Sharing your knowledge and being able to explain the beauty of Scala in a simple and accessible way also reveals your proficiency with the language. And sometimes it is more rewarding than 30ms performance gain. :-)
Thanks and let's keep it moving!