Re: Solicitation Of Ideas For "Time Capsule" Project

First off I would second the idea of such a project.... But with some remarks:

- I think that there should be some kind of 'lock' on the thread for the user who created the node in the 'lock'. Otherwise they will visit it and see what others think of it.
- After a set period (lets say one year), the original user should get a notice ( and a link ) to post the new solution to the problem. Only after submitting this solution should he/she be able to see the thread.
- When regarding the above notes, this should/could be an extra feature in PM so people can add there 'timelock node' at any time.

As far as possible project ideas... It could be a number of things..... You could leave it upto the imagination of the author, or create a couple of categories for different skill levels...

.:| If it can't be fixed .. Don't break it |:.

Comment on Re: Solicitation Of Ideas For "Time Capsule" Project

Replies are listed 'Best First'.
Re^2: Solicitation Of Ideas For "Time Capsule" Project by Limbic~Region (Chancellor) on Jun 17, 2005 at 13:48 UTC
aukjan, I think that there should be some kind of 'lock' on the thread for the user who created the node in the 'lock'. I am not proposing that this require any modification to the way the Monastery works now. You have to give a certain amount of trust to your peers or you take away the fun factor. After a set period (lets say one year), the original user should get a notice ( and a link ) to post the new solution to the problem. Only after submitting this solution should he/she be able to see the thread. I will personally be responsible for notifying all the authors that it is time to look inside. I trust that they will wait for that notification before looking. When regarding the above notes, this should/could be an extra feature in PM so people can add there 'timelock node' at any time. In general, people tend to lose sight of the original goal of having fun and get lost in the details. If someone else wants to champion a proposed change to the Monastery I am not going to stop them but I do not want it to be driven by this project. As far as possible project ideas... It could be a number of things..... You could leave it upto the imagination of the author, or create a couple of categories for different skill levels I don't like the idea of leaving it up to the imagination of the author. Part of the fun is comparing yourself to others and for that it needs to be apples to apples. I do like the idea of potentially having several tasks to choose from depending on your skill level so I hope people propose tasks covering a range of skill sets. Cheers - L~R	[reply]
Re^3: Solicitation Of Ideas For "Time Capsule" Project by aukjan (Friar) on Jun 17, 2005 at 14:19 UTC
You have to give a certain amount of trust to your peers or you take away the fun factor. I agree that people will need to have patience and restrain themselves from checking what others think. But it is human nature to be curious and people will be tempted to check what others think of their programming (skilz). I know I will be tempted, but I will just have to put a filter in my proxy server to stop myself from accessing the Thread! I am not proposing that this require any modification to the way the Monastery works now. Clear. This would take up much time and if we assume that people won't check ;-) there will be no need for an adaptation... I will personally be responsible for notifying all the authors Good! So should there be a deadline before which the first post needs to be created? Or will you just parse the start-time from the node's creation time? That would be the most simple task. You could parse it if people will start their time-lock node with a specific subject. (eg: TimeLock: Level1 - Limbic~Region). This could even be one of the little projects.. (yours??) Part of the fun is comparing yourself to others So very true (see Obfuscated Code or Code Catacombs). So yes, lets stick to having a couple of different catagories where people of the same skillset can enter their code and compare how they 'evolved' compared to their skill level compadres! I hope that many people will actually make these little programs. Looking back at code I wrote 3 months ago, there are already many improvements I would like to make! So how long would you suggest for a waiting period?? 6 months, 1 year, more?? I would say 6 months at least. .:\| If it can't be fixed .. Don't break it \|:.	[reply]


Perl Monk, Perl Meditation
	PerlMonks