Technical Writer · Content Strategist · Web Developer
Hard technical topics, written so people actually read them.
Most technical content loses one of its two readers. Too technical and your buyer stops reading. Too simple and the developer stops believing you. I write the kind people actually finish, which is usually the last thing they read before they decide.
Selected work ↓
Start with these 10
Each one picked for a different kind of reader. Find the badge that sounds like you and start there. Or browse the full archive with filters.
Everything below links to live, published work. Read a few paragraphs of any piece and you'll know whether I'm your writer.
Code & side projects ↓
I build what I write about
The code samples run and the technical claims check out because I ship the same stack. A few things I've built in the open on GitHub.
What hiring me gets you
The technical details hold up
I'm a self-taught developer who builds what I write about. The code samples run and the numbers check out, so readers send questions instead of corrections.
Hard subjects, plain writing
I've explained database sharding to beginners and platform costs to executives. The subject stays hard, the writing doesn't, and that is partly why these pieces rank.
Drafts your editor barely touches
I spent years as a technical editor managing 20+ freelance writers, so I know what wrecks an editor's day. My drafts land clean, with a source behind every claim.
Evaluations that survive the boardroom
Executives read my work right before they spend real money, so it answers the awkward questions. Nobody trusts a comparison where you win every category.
How I work
I ask questions before I write
Send a title, an outline, or just a rough goal. Before anyone writes a word, you get back questions about who this is for and what it needs to do.
I do the research myself
I test the tools and run the code. If a piece makes a claim, I read the source it came from, and I can show you that source later.
I deliver a draft you can publish
It arrives on the agreed date, formatted for your CMS, with internal links and meta copy suggested. I co-founded a design agency before this, so diagrams and screenshots come with it when they help.
I revise until it's right
Reasonable revisions are part of the price. Most drafts need one light pass, and if something misses the brief, I fix it.
What editors say
Placeholder quotes below. Set showTestimonials: false in js/clips.data.js to hide this section until the real ones arrive.
Questions clients ask
What do you write?
Technical tutorials, platform comparisons, migration guides, and the evaluations executives read before signing something expensive. If it sits between developer documentation and a boardroom memo, I've probably written it.
How fast can you turn a piece around?
One to two weeks from brief to draft, depending on how much research it needs. Tell me your deadline in the first email and I'll tell you honestly whether I can hit it.
Do you ghostwrite?
Yes, and it costs a bit more, since I'm giving up the byline. The ghostwritten pieces here are shown with permission. Your name, my drafts, full confidentiality if you want it.
What does it cost?
Depends on how you prefer to buy. Per project, per word, discounted by volume, or a part-time retainer if you need steady output. Send the brief and I'll quote against whichever model you already use.
What if you're not the right fit?
I'll say so in the first reply and point you to someone better suited. A mismatch wastes your time and gets me nothing worth showing.
About me
I'm a self-taught developer who still opens the logs before asking anyone what happened. I just like writing about this stuff more than building it. Somewhere along the way I became the person on the team who wrote down how things actually worked, so the next person didn't have to dig through the code to find out, and that turned out to be the job.
There's a design agency in my past too, which helps more than it sounds like it should, since the visual side of a piece is mine as well. People decide whether to read something before they've read any of it.
The non-writing parts of my life are at salmaniac.com.
- Currently
- Freelance technical writer & content strategist
- Previously
- Content Strategist, rtCamp · Technical Editor, Kinsta
- Published pieces
- 200+ across WordPress and enterprise tech
- Sweet spot
- Content that developers respect and executives act on
Tell me what your content needs to do
You don't need a brief. A rough idea of the piece and who it's for is enough to start, and I'll ask the rest.
I reply within one business day.