I have a passion for writing and editing documentation. I value clarity and concision and am experienced in tailoring information to a variety of audiences. I excel at paying close attention to details while maintaining a vision of the larger goals for a document. I strive to always continue learning about new technologies and sharing that knowledge with others via technical documentation. I love when something I have written can directly help others to accomplish their technical goals.
Best Practices document
As more people begin to use the publicly accessible Dialogflow software to create their own virtual agents, our team decided that a set of general guidelines was needed .
Along with two of my supervisors I wrote suggestions for the most effective and efficient ways to design various aspects of a virtual agent. Over the course of about two months we added to this document and I tailored the word choice and style to be accessible to the same public audience who was creating their own virtual agents with Dialogflow. Once we were satisfied we shared the document with the Google CCAI engineering team who provided their own input and suggestions. After this final round of edits Google published our document online and you can view it by clicking on the button.
I helped create the public facing document for Google's new open source Python library called SCRAPI. This new library provides scripts and tools which interface with Dialogflow CX to automate a variety of virtual agent development and maintenance tasks.
The SCRAPI library is housed on github and freely accessible to the public so the lead developer asked me to proofread and edit his ReadMe document. I standardized the format using Markdown and created a uniform writing style which highlights crucial information about the contents of the library. SCRAPI is available and you can view the ReadMe document by clicking on the button.
SCRAPI Python Library
Agent Assist LLMs
As a member of the Agent Assist team I edited engineer-authored documents for LLM integration, including three feature documents and two how-to guides. I cannot reveal the titles of these documents as they reflect new features that Google has not yet released to the public.
Software engineers wrote these documents then I proofread and edited them for English grammar and public accessibility. I helped ensure the documentation complied with Google's developer style guide for future publication. You can view the public Agent Assist documentation by clicking on the button.
A team member brought to our attention that the public document for "Creating a conversation dataset" made reference to a deprecated data labeling API. I collaborated with engineers to confirm the deprecation of the API and migration to an external data labeling service. Then I removed the reference and the deprecated link from the public document. I submitted the approved changelog using Critique. The public document no longer suggests that users activate the data labeling API.