𝐔𝐬𝐢𝐧𝐠 𝐀𝐈 𝐢𝐧 𝐲𝐨𝐮𝐫 𝐚𝐜𝐭𝐮𝐚𝐥 𝐰𝐨𝐫𝐤 𝐭𝐨𝐝𝐚𝐲? 𝐋𝐞𝐭’𝐬 𝐭𝐚𝐥𝐤. I’m pulling together speakers for a hands-on learning session on using AI for technical writing. This isn’t a hype parade. It’s about sharing real workflows, tools, and prompts that people can start using right after the session. No theory. No fluff. Just practical, ready-to-use stuff. 𝐈𝐟 𝐲𝐨𝐮’𝐫𝐞 𝐢𝐧 𝐭𝐡𝐞 𝐭𝐫𝐞𝐧𝐜𝐡𝐞𝐬 𝐮𝐬𝐢𝐧𝐠 𝐀𝐈 𝐭𝐨 𝐠𝐞𝐭 𝐫𝐞𝐚𝐥 𝐰𝐨𝐫𝐤 𝐝𝐨𝐧𝐞, 𝐃𝐌 𝐦𝐞. 𝐎𝐫 𝐭𝐚𝐠 𝐬𝐨𝐦𝐞𝐨𝐧𝐞 𝐰𝐡𝐨 𝐢𝐬. Let’s keep it real and make it useful. #TechnicalWriting #AIatWork #PracticalAI #TechComm #AIforWriters #DocumentationMatters #STCIndia
Prompt 1: Summarize this passage. - Any input document can be gisted out this way. Prompt 2: Identify the gaps in this passage. - Any input doc that needs to be analysed for more inputs can be sorted this way. Prompt 3: Write a conclusion for this passage. - Any input doc that needs to be concluded can use this prompt.. All said, it's important to read the results and refine prompts to either cut the fluff or increase the hype based on what your audience wants to read. In tech writing we use sugar only in coffee.
Worth attending
Using Windsurf AI and Cursor AI IDEs for suggestions and auto completion of text while writing the first draft via docs as code approach. Also, using the GPT4all app on my local desktop to prevent confidential data leaks.
Although I align with Deepa Sriram's view, my curiosity lies in the journey of discovery.
Looking forward to this
Interesting opportunity. Looking forward to the session
I want to connect! Sachin Shenoy
Interested. Let's connect
Documentation Leader | Cloud and AI Security | Admin Guide | REST APIs | SDK | CLI Docs
2moGreat initiative Sachin Shenoy My focus is not just using AI, but to set guardrails on prompts that we send and the response we recieve. Guardrails use cases: - Avoid sensitive data leak on docs, such as a pre-release feature or a bug. - Safeguard the #AIResponse against plagiarism. - Restrict AI prompts to trusted sources. #aiSecurity