Code Challenge #2

key value store.md

Code Challenge #2

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."

To join the battle do the following:

1. Check the briefing

2. Accept the challenge by commenting on this gist with an upfront estimate.

3. 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.

4. 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.

5. Open source everything and look at other solutions, compare, enjoy!

The Deadline for submissions is the 23rd of July

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 :)

The goal of these challenges

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.

Previous challenge

• Code Challenge #1

I mean Command Line Interface. I made it interactive, so you do not have to run the command every time. I used YAML, you used JSON. Anyway it looks good to me and you made it in 44! Well done.

@jamesu: bonus points for OptionParser usage!

Trying to build a JS version. Starting now... shouldn't take more than 30 mins

yikes, 8 mins overtime, not too bad... Here it is: a JS implementation that stores the data in itself: https://gist.github.com/1031330. Runs on node.js

It took me 1:30 to write the following. Most of the time was spent by writing a sinatra application. After I've written the sinatra app, I realized that the briefing was meant to be a CLI app.
After that I ported my inital sinatra attempt to GLI and tadaa, we have a super dumb K/V store: https://gist.github.com/1031943

Hehe, LOLz about myself not reading the briefing ;)

What do you think about my approach?

I like your usage of the exception handler to create the default database. Though i noticed a slight flaw with the uuid code in the CLI version: if i set a value i won't be able to determine its uuid except by looking though the entire list to see what has been added.

Never heard of GLI before (seems a bit over-abstracted IMO).

Funny how everyone just about came up with the same underlying solution again, just dressed up differently.

I did not know about GLI and UUID, I have to say that GLI permits to write a command line interface in a very clean way. It is interesting to see the JS version, I hope to try it very soon.

@radiospiel, haha that is awesome... Self contained cli key value store xD
I guess I could do that in Ruby as well, but it already looks great in javascript!

@Overbryd I don't know about a ruby version. Js - or at last node.js - has the nice feature to dump a function's source code, a feature that is missing from ruby. I guess one could put the source into a ruby file and eval it then, though

I've updated my keyvalue_cli.rb to store it's data self contained https://gist.github.com/1031943

:)

I think we have a champion of crazyness here ;)

Hm, talking about evaluation. How do you think should we evaluate the Code Challenges?

I thought about setting up a rating system for different topics. But maybe you guys have an easier "Hot or Not" in mind?
I'm willing to setup a website on these code challenges if the interest is there.

Please give me your opinion on this.

@Overbyrd: the keyvalue_cli.rb stuff is pretty cool :) re/a website: hmm, I don't know. I guess our submissions could help others to find some great HOWTO-examples; but this seems to be a larger project then...

I think we should have a code acceptance deadline, after that anyone would be able to enter the challenge. We should have a date for the end of the challenge: any submission after that date the user will be 'not classified' or NC. After the end all participants should enter a retrospective, where they should vote for time estimate and quality of code and the simplest solution. I think it is better that the judgment should be community driven. It would be useful to have a way to improve our skills from understanding where we have created a poor code and understand what to do to improve our skills.

On 20 June 2011 12:22, Overbryd < ***@***.***>wrote: Hm, talking about evaluation. How do you think should we evaluate the Code Challenges? I thought about setting up a rating system for different topics. But maybe you guys have an easier "Hot or Not" in mind? I'm willing to setup a website on these code challenges if the interest is there. Please give me your opinion on this. ## Reply to this email directly or view it on GitHub: https://gist.github.com/1029706

## Riccardo Tacconi Ruby on Rails and PHP development - System Administration VIRTUELOGIC LIMITED http://github.com/rtacconi http://riccardotacconi.blogspot.com http://twitter.com/rtacconi http://www.linkedin.com/in/riccardotacconi

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.

I think keeping this simple is key. Also keep the challenges simple yet interesting enough so that other people can realistically complete them.

There are two things to evaluate: how well you think you did, and how well everyone else thinks you did.

To me personally this is more about self-estimation and completing an interesting challenge rather than things such as code quality. If anything i'm more interested in code awesomeness. ;)

I would have liked to add a "build a kino.to frontend that is actually usable", but then the police did this already. Not that their use is of any use to me :)

I have a real idea or two: first thing would be a crowdsourced ping service, where users of a website would get a small piece of javascript which gets fetched a URL to ping, ping the url, and report the result back to the server. Could help get you measurements from around the world, even if you don't have users in, say, chile. The other one would be a todo-list (I know, its kind of boring, but yes.)

Wow that is a nice idea too. We need more challenges :))) I recently got to discover http://codebrawl.com/. I've contacted the maintainer of the site, and he gave me access to the application. Currently I'm in a discussion with him, wether to develop a "public contests" feature and give people the possibility to create their own challenges. I'll update here too. Cheers, Lukas 2011/6/23 radiospiel [email protected]:

…

I have a real idea or two: first thing would be a crowdsourced ping service, where users of a website would get a small piece of javascript which gets fetched a URL to ping, ping the url, and report the result back to the server. Could help get you measurements from around the world, even if you don't have users in, say, chile. The other one would be a todo-list (I know, its kind of boring, but yes.) ## Reply to this email directly or view it on GitHub: https://gist.github.com/1029706

Out of curiosity i decided to see how easy it would be to implement the youtube sync thing. Figured i'd get it done in an hour, ended up taking 9 to get the basic system working.

Most difficult part was getting the websocket code working correctly.

Might iron out the major bugs later and upload it somewhere ;)

@jamesu makes me curios. Especially since I didn't understand the youtube sync idea :) Just show it, man!

@radiospiel basically its just a way for multiple people to watch the same youtube video in sync (a prime example of this being synchtube).

My version so far if you were wondering: http://stuff.cuppadev.co.uk/testtube.jpg

@jamesu: I see. Is this synched only on the start or during watching the video too? (I.e. one person fastforwards the video and it gets fast forwarded for all viewers?)

@radiospiel its basically updated about every 2 seconds, so the video stays in sync between all currently connected clients via the power of websockets.