| Connect lewiscowles
Essex, UK
I work at a fintech startup in London. I Really like pair programming, cognition and education, and repeatability. Talk to me about testing, automation, or whatever you are passionate about.
Lewis Cowles (He/Him, They,Them,Theirs)
Authored Comments
Purchased the paperback and downloaded. I do hope the authors get some form of revenue from the paperback, as I noticed the cost was below what LuLu normally charges.
Very interesting.
I'm a fan of sparse, well written, low-effort to maintain docs, which I don't tend to think of as lesser.
I find "wonder-of-the-world" efforts seem to rot most. They require a lot of uphill battles to revise, or have really awful search and browse mechanics (it doesn't matter if it's there, if I have to grep to find a specific phrasing, that can be problematic).
It's not a shortcoming of authors either. How do you design a consistent search by title, and tags, and phraseologies, that has an easy to understand UI, isn't either too lax like something backed by Elasticsearch (which IMO seems to come from the rather insulting supposition that nobody can spell), where quality is abandoned for speed? It's hard!
I wonder if there is a ballpark cost (even if it's in hours) of top-level documentation, and a cost-benefit analysis for each of the levels, or items within (perhaps in saved hours).
I personally could live without contributors documents, CLA's, most of the buttons and badges. I like CI badges, but sometimes the build is internal and they'll have a jenkinsfile or similar, which remits concerns.
Last thing is more of a question. Do you think Issues are there to be closed, or serve as part of the living documentation of user feedback and frustration?