Selected work

I set up more than twenty colleagues with VS Code, GitHub Copilot, Python and Node.js, and showed them which Copilot fits which work. Microsoft 365 Copilot is for finding and using the organization’s own content, within each person’s own access; GitHub Copilot is for builds where I iterate on the same files many times. When a task works well in GitHub Copilot CLI, I transcribe it into a durable skill in the Agent Skills format (agentskills.io) so that colleagues can run it too; we have used these for PowerPoint presentations, HR headcount analysis and governance, risk and compliance (GRC) work.

There was a need for internal newsletters, monthly and half-yearly, one for each department. I build them with GitHub Copilot CLI, and they come out engaging and professional, close to what a designer would produce. Microsoft 365 Copilot does not work for this, because its harness is not built for repetitive work where I keep iterating on the same files and folders under Git version control. GitHub Copilot in VS Code, or GitHub Copilot CLI, is the better tool because of how its harness, environment and context work. Without AI, we would not have thought of the task this way, and we would not have done it.

In early 2025, there was a need for comic strips on cybersecurity topics, so that busy caregivers could understand a topic by glancing at a strip for a minute or two. The image-generation tools we had were not good at placing text in images, so I created the comic panels image by image with Microsoft 365 Copilot’s built-in image generation, then learned Figma to place the dialogue accurately on each panel. Some of the comic strips were used in a couple of newsletters. The rest were appreciated, but they never got a chance to be used at clinical sites, because of some limitations there.

I scripted and produced product videos for an internal cybersecurity platform, from storyboard to motion graphics in Premiere Pro and After Effects.

I rebuilt the engineering blog’s editorial strategy around developer search intent and identity education, alongside messaging and positioning for the company’s customer identity (CIAM) platform.

I ran the engineering blog as an open-source GitHub project with a paid guest-author program. Every post went through engineering review, and 144 merged pull requests on the repository trace the editorial work.

I turned in-house expertise on data privacy and passwordless authentication into long-form eBooks for customer education. They were published under an executive’s name, so they are not linked here.