My approach
Every complex product has a gap between what it can do and what people understand it can do. I close it.
I start hands-on: installing the build, writing the sample code, testing the tooling myself. That’s how I produce documentation developers trust, messaging engineers find credible, and content structured for the AI assistants that now read it on your users’ behalf.
What I do
Technical communication
Documentation that gets developers productive, and that AI assistants can read correctly.
Technical product marketing
Positioning and launch content that holds up in front of engineers.
AI enablement
Agent skills, retrieval, and workshops that put AI to work in your team’s writing and development.
How I work
- 1 Use it. I work with your product the way your users will, from install to first working app.
- 2 Find the gap. Between what the product does and what users, buyers, or AI assistants can do with it.
- 3 Close it. With documentation, messaging, or tooling, whichever the gap calls for.
From the Lab
All Lab entries →Signal 31 tests AI tooling on real communication work and publishes what it finds. Experiments, working examples, and honest notes on what holds up.
The experience behind Signal 31
See the experience →- 20+ years documenting developer platforms
- Getting-started content that helped 6,000+ developers adopt Oracle JET
- Co-founder of the Oracle Visual Builder Cookbook
- Oracle certified in OCI Generative AI and AI Vector Search
- Trained in Claude Code (Anthropic)
- Working in English, Spanish, and French
Got a product that’s hard to explain?
That’s the work I like best. Tell me what you’re building and where it isn’t landing.
Let’s talk