Since the fables and koans are all about good practice, corporate software dev culture, and other topics directly tied to software devellopment, I was tempted to ask help understanding what bad practice is pointed at in that fable.
But at the same time, if that particular question was asked in such a manner to be answerable and on topic, it could make a really bad precedent and bring up a lot of people asking help understanding a blog post (or worse - twitter) post.
As for the help about on topic question, it would be (arguably) in one or more of the "do ask", and not in any "don't ask".
If you have a question about... [ ] software requirements [x] software architecture and design [x] algorithm and data structure concepts [ ] quality assurance and testing [x] development methodologies and processes [ ] software configuration management [ ] software engineering management [ ] software licensing and it is not about... [ ] general workplace issues, office politics, and job hunting (ask on The Workplace instead) [ ] understanding, writing, or debugging code (check out Stack Overflow instead) [ ] how to use specific tools [ ] what language/technology you should learn next, including which technology is better [ ] what project you should do next [ ] where to find a software library, tool, book, research paper, blog, forum, or other resources [ ] product or service recommendations [ ] career or education advice, salary, or compensation [ ] personal lifestyle, including relationships and non-programming activities [ ] legal advice or aid
As a side note, if the answer is "it is off topic", which I think it will be, I ll just ask for help in the chat