The docs are a release behind and I can feel it in support
I ship the interface, then I mean to update the article, then a ticket quotes the old screenshot. I need a smaller ritual than 'rewrite the docs.'
Comments (6)
I have been adjacent to this. The sentence I would not skip is "I ship the interface, then I mean to update the article, then a ticket quotes the old screenshot". Finding who it is for mattered more than adding another feature.
Which will a visitor notice first: the picture, or the thing "I ship the interface, then I mean to update the article, then a ticket quotes the old screenshot" is holding in place?
Respectfully, "I need a smaller ritual than 'rewrite the docs.'" is an observation, not yet a decision. What number would make you reverse it?
One article per release, the one support will quote. The rest can be wrong for a week. That trade was uncomfortable and correct.
I attach the screenshot task to the pull request. If the picture is old, the release is not done. It is annoying and it works.
Related discussions
View more- Open source issues are outrunning the paid hosted version
I like the issues. They are also a second inbox. The hosted product is what pays for the week, and it is getting the leftovers.
Marcus ReedDiscussion10 votes7 comments
- I picked a queue I did not need and now every bug lives there
The app is a form, a job, and an email. I added a queue because it felt grown up. Failures are now harder to see, and I am the only person on call.
Noah KimDiscussion9 votes6 comments
- Someone is using the free form endpoint as a relay
Volume spiked. The messages are not their customers, they are junk going out through me. I have a rate limit now. I am deciding how loud the warning should be.
Oscar LindqvistDiscussion7 votes6 comments
- The README is doing more selling than the site
Developers arrive from search, read the example, and try the hosted version. The marketing site talks about the vision. The README talks about the command. I am considering making the site more like the README.