2 ms·
This is rule 7 of 10 in my post 'How to Ask for help in Slack'[1] 1. I have ‘rubber duck debugged’ my own question. 2. I checked that this question hasn’t bee
by thundergolfer 11mo ago
This is rule 7 of 10 in my post 'How to Ask for help in Slack'[1]
1. I have ‘rubber duck debugged’ my own question.
2. I checked that this question hasn’t been asked before.
3. I have noted in my message what I’ve tried.
4. I have avoided the ‘XY problem’ by clearly detailing the core problem, X.
5. I have provided specifics of my issue, not vague
references or descriptions.
6. I have provided URL links to relevant content, and where possible the URL links are immutable.
7. I have not included screenshots of text in my message.
8. I have not used obscure acronyms or abbreviations.
9. I have formatted my message well, particularly paying attention to code formatting and headings.
10. I have not just said “hi” and waited for a reply.
Like other posters, I don't think Apple OCR is sufficient to make up for screenshotting. The biggest problem is search.
1. https://thundergolfer.com/communication/slack/2021/02/24/how-to-ask-for-help-in-slack/ https://thundergolfer.com/communication/slack/2021/02/24/how...
- icehawk 11mo ago> Like other posters, I don't think Apple OCR is sufficient to make up for screenshotting. The biggest problem is search. Both Spotlight and Photos will find text in screenshots.
- thundergolfer 11mo agoI don't think Slack does, nor Github, which is where I most find screenshotting being a problem.
- icehawk 11mo agoI don't think either of those two are within the scope of Apple's OCR. Different horses, then.
- superdocs1 11mo agohttps://screenshotocr.app https://screenshotocr.app does this on Windows (I'm the founder).