Hacker News new | ask | show | jobs
by latchkey 818 days ago
Agreed. My comment was more relating to the fact that comments about 'what' something is, aren't as helpful as answering the 'why', which you just did. =)
1 comments

Thanks for the feedback! I just extended the comment to touch on the "why" part. :) https://github.com/Dobiasd/articles/commit/53f360259ad8e64ca...
Don't leave me hanging, too specific about what?
That is fantastic. Much appreciated on the quick response. You're hired. =)
I'm not sure if you're actually suggesting that the author expound further on the concept of pseudocode, or if this is just humor.
Mostly humor, but also a suggestion. Why? Because if it was real code I'd want the 'why' to be as specific as possible. It doesn't have to be a novel, but it also shouldn't be left open for interpretation.

Too many times have I gotten some ancient piece of code and cursed the author (sometimes this is even myself) for either not documenting it well or it had a bug or whatnot. "OMG, what were they thinking when they wrote this code?!" I never want to be in the position where someone is cursing me.