Software Engineer at Groupon
Hack Reactor alum (April '13 cohort)
Entrepreneur (cofounder of Pagewood Taiwan, 2006-2010)
Thanks for your time and feedback.
Thanks :) we'll fix the design and many other things after NKO.
Thanks for the feedback! We did have some problems with the projectiles disappearing (we are able to check easily if they hit a player but we couldn't get the check of the map correct) hence they disappear on contact with the players but not the map. Also good thought on the health bars you wouldn't happen to play StarCraft would you? (you can hold alt in StarCraft to show health bars).
I've spent a ridiculous amount of time playing SC and other real time strategy games :)
:) Me too and I spend WAY too much time watching them as well (I kind of watch every TeamLiquid Dota 2 and SC2 match)
I would argue that knowing how close to death you are is an important distraction, on par with knowing the road ahead is out. ;)
Thanks for the vote!
Thanks for voting!
Its use case is to automatically document nodejs code using the well known javadoc comment syntax (http://en.wikipedia.org/wiki/Javadoc). By participating in NKO I'm trying to evangelize proper code documentation.
I looked at the repo you tried to document and it doesn't have any javadoc comments:
So, to be able to use hookdoc, the code needs to have javadoc style comments.
The end result would be similar to the provided example: http://jassid.2013.nodeknockout.com/bpedro/node-fs/lib/fs.js.html
Anyway, I really appreciate your feedback if you read this reply!
Ah! Java-style documentation. No wonder. I had thought it would do some kind of code analysis as an IDE might to list functions, parameters, constant variables, etc.
Super low-hanging fruit: add that one word—javadoc—to the description line. If I'd seen that, I'd have skipped it or found a different repo instead of thinking it was broken.
Thanks for the feedback!
The project attempts to analyze the code even if there aren't any javadoc comments present, but it's not perfect (yet).
Even with your repo, it attempted (and succeeded) to grab one function signature (parseQueryString()).
I plan to improve this after the competition ends so, any further feedback is more than welcome, specifically related with what methods/tools to generate documentation you're currently using.