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