4 ms·
Great writing style on the README. It’s always nice when a corporate tool has docs that were obviously written by people who are having fun at their jobs.
by brookst 2y ago
Great writing style on the README. It’s always nice when a corporate tool has docs that were obviously written by people who are having fun at their jobs.
- xwn 2y agoThanks! Wrote it loooong before it was a corporate tool and was only a labor of love. Now it's both
- sdesol 2y ago[flagged]
- sdesol 2y agoI guess I was a bit direct but I don't fully understand the down vote. I was not implying that the README was bad and it does have corrections that would improve it. My reason for not raising a PR is some repo owners don't care and I really didn't want to go through the effort unless they actually care.
- cortesoft 2y agoThe downvotes were probably because the comment felt like an ad for your tool
- squigz 2y agoThis, and nobody asked, and it was irrelevant to the comment thread.
- retrovrv 2y agoThis is actually pretty cool. Would love to try it!
- sdesol 2y agoExpect to be able to try it by the end of this month if I am lucky. It will be a simple one line docker pull command or if you want to install it, use npm.
- Ldorigo 2y agoAlso, FYI, the majority of "errors" found by your tool are not actually errors.
- sdesol 2y agoYes I agree if the prompt that was used was less strict with regards to verb tense, prepositions and so forth. I wrote this prompt for use for technical writing, which may not fit the style of the author.
- deleted 2y ago[deleted]