Hacker News new | past | comments | ask | show | jobs | submit login

Even a monkey can repair a space shuttle if they have a good manual

I would like to point out that the dependency chain for repairing the space shuttle (or worse: microservices) can turn the need for understanding (or authoring) one document into understanding 12+ documents, or run the risk of making a document into a "wall of text," copy-paste hell, and/or out-of-date.

Capturing the contextual knowledge required to make an administration task straight-forward can easily turn the forest into the trees.

I would almost rather automate the troubleshooting steps than to have to write sufficiently specific English to express what one should do in given situations, with the caveat that such automation takes longer to write than said automation.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: