News for hackers. Stuff that matters.
Re:MongoDB Interactive Geospatial Tutorial by nuclear_eclipse on Tuesday April 05, 2011 @09:40AM (#2410860)
Personally, my biggest hurdle is that every time the tutorial introduces a new concept, my brain was expecting to just modify the existing query with the new concept, while the tutorial actually wants me to create an entirely new query each time.
Re:MongoDB Interactive Geospatial Tutorial by AlexC04 on Tuesday April 05, 2011 @10:19AM (#2411015)
I was somewhat annoyed that when I typed:

    db.treasures.find()
then hit up arrow I got:

    db.find()
The tutorial would have gone a lot faster if uparrow stored the correct string. Though then again, maybe there's something I don't know about the db.find option. Maybe it is doing it right and I'm wrong.
Re:MongoDB Interactive Geospatial Tutorial by rauljara on Tuesday April 05, 2011 @10:06AM (#2410957)
I love that about the tutorial. One of the few tutorials where I actually have to think.
Re:MongoDB Interactive Geospatial Tutorial by nuclear_eclipse on Tuesday April 05, 2011 @10:08AM (#2410969)
Yes, it would just be nice for it to be a little more upfront/explicit that it wants a new query, instead of using the same wording from before, but with subtle number changes that my mind glosses over...
Re:MongoDB Interactive Geospatial Tutorial by rauljara on Tuesday April 05, 2011 @10:17AM (#2411010)
I kind of disagree. I remember things much better when I screw up doing them. The fact that it isn't immediately evident what exactly is wrong with my query means I have to go back and read, and figure it out. Much like debugging. I know your trouble isn't with the concepts, but I honestly think that the extra step of saying, 'why isn't this working' will make the concepts stick around much longer than they would otherwise.