A new challenge is on. This time @rtacconi had the idea:
"Idea:
Create a simple persistent key/value storage capable of SET, GET and DELETE actions.
It is forbidden to use Redis, MongoDB, or other ready made key/value solutions,
only storage to file, databases, serialization... are allowed
The UI should be the CLI, not web this time... just for a change."
-
Check the briefing
-
Accept the challenge by commenting on this gist with an upfront estimate.
-
When working on the implementation always have an time tracker running. This is for your your own good, as the better you can estimate yourself the better it is. It only works if your honest with yourself and track the exact working time from start to finish.
-
When you're done, send an link to the publicly available project of yours. You don't have to open the source before the deadline ends.
-
Open source everything and look at other solutions, compare, enjoy!
If you have any questions, don't hesitate to ask @Overbryd. I may moderate comments on this gist so that it stays readable.
I wish you a lot of fun :)
It is not about who's the fastest scripter on the internet. It is more about code quality, choice of weapons and estimation skills. I understand these challenges as a fun way to improving my self estimation skills.
Thank you for the ideas.
The next challenge is knocking on the door, and we already have some great proposals for the third challenge.
I have set up a poll to see what you would like to implement on the next challenge.
Please vote for the topic of the next round
I really like radiospiel's guess that submissions may help others as HOWTOs. That is also why I think that creating a website would be a good fit. With a website, the submissions may be ordered and people can easily find stuff theyre looking for.
I have not found the time to create on yet, but my head has already started thinking about an elegant solution. I really don't want to bloat this nice little challenge up.
I just want to make it better and better every time :)
Regarding evaluation. It seems that three factors stand out pretty clearly: Estimation accuracy, simpleness and quality of code. It can be done through voting. Currently I'm evaluating voting services. Any ideas? At the moment I find polldaddy.com very appealing.