Technical content writer & developer content strategist.
I work with dev-tool teams to make their products easier to understand, easier to adopt, and easier to find.
I focus on the gap between how tools are built and how developers actually learn and use them.
Most developer tools expect users to “figure it out.” I write content that removes that friction.
I write practical, experience-driven content around:
- Choosing and using developer tools (when they actually make sense)
- Breaking down confusing docs into usable mental models
- Backend workflows, debugging, and real-world usage patterns
- AI-assisted development that actually helps you ship faster
Some of my work:
- Choosing a React Form Library in 2026 (React Hook Form vs TanStack Form vs Formisch)
- It’s Okay to Use React Context for Global State Management
- How to Activate Claude skills Automatically : 2 Fixes for 95% Activation
- Understanding Valibot: Why It’s Different & When To Use It
- Is your AI search optimization missing developer behavior
- Practical AI search optimization guide for technical content (+7 tips)
I don’t just write articles, I help shape how developer tools are understood.
- Content strategy for developer-focused products
- Documentation direction and restructuring
- SEO & GEO-driven content that still respects developers’ time
- Positioning tools so they’re discoverable and usable
- Contributing to content around Formisch and Valibot
- Exploring better ways to connect search (SEO/GEO) with developer education
- Writing guides that reduce “trial-and-error learning”
Because most developer content assumes too much.
If you’ve ever:
- read docs and still felt stuck
- searched something and found nothing useful
- or had to piece things together from random sources
That’s the problem I’m solving.
- Content strategy roles
- Dev tool collaborations
- Writing opportunities