It's hard to fit five years of developer marketing and content creation into a single page, but here's a snapshot of work that I think represents my style and approach.
When you're building a product for developers, the content you create isn't marketing, it's part of the product itself.
Developers research before they buy. They'll read your docs, try your examples, and search for how others are using your tool before they ever consider a sales call. The quality of your technical content directly determines whether they'll adopt your product or move on to the next option.
My approach to developer content is simple: write the docs and articles you would want to read. Be technically accurate, show real code, explain the tradeoffs, and don't hide the sharp edges. Developers can smell marketing fluff from a mile away.
Here are some examples of my writing.
Blog posts are narrative-driven technical articles that tell a story. Here are a few:
Guides and tutorials are hands-on, step-by-step instructions that help developers achieve a specific goal. When written properly, a developer should be able to follow along and get the desired outcome. Examples:
Some topics require a deeper dive than a blog post. These articles are typically evergreen, long-form content that explores a topic in detail.
LinkedIn is THE platform for reaching B2B technical decision makers. As a founder, having a consistent presence on LinkedIn is crucial to building credibility and trust.
The secret to effectively using LinkedIn is to built authority on the problem space you are solving, not just your product. No one cares about your most recent release notes (unless you have a very cool video demo to share), but people care about a lot their own problems.
By consistently sharing valuable insights, lessons learned, and your unique take on industry trends, people will begin to associate you with the problems you solve and find you when they need help. Here are some examples of my posts:
Conference talks are one of my favorite ways to tell technical stories.
Doing them well is a two phase process:
My approach to conference talks has always been to focus on deep, unique technical perspectives that provide real value to the audience.
Here are some of my favorite talks:
Full list on my speaking page.
Reddit is an incredibly important platform to reach developers.
For Atlas, Reddit has always been one of the top sources of traffic (after Google). Over the years, Reddit has managed to consistently foster a culture of high-quality, no-BS discussions, which is exactly what developers crave.
Crafting a post that works well on Reddit has many benefits:
Here are some examples of carefully crafted Reddit posts that sparked meaningful discussions:
Getting published on authoritative tech platforms is about more than just SEO: it's about meeting developers where they already go for trusted content.
My approach to technical publications focuses on three things:
Here are some of my published articles:
I take on 2-3 clients at a time. Focused impactful work, no bullshit.
Book a 30-minute call to see if I can help you.
Copyright 2025. All rights reserved.
Inspired by The Monospace Web